Recent Posts

1

Features and/or Improvements / Re: Improve work over SFTP

« Last post by byates on April 10, 2021, 02:05:34 pm »

I agree. This is the only feature that keeps me from being able to use SE. We work on remote VMs in Azure. SSH access only through a jumphost. VSCode works perfectly this way.

2

SlickEdit® / Re: Java enum values not shown in autolist of an enum

« Last post by Dennis on April 09, 2021, 10:48:53 pm »

Reproduced.  Looks like our Java enum parsing is failing to get the enumerators in that class.  Will fix for 25.0.2.

Thanks again for your patience on these gray old bugs.

3

SlickEdit® / Re: C++ push-tag-filter-overloads bug when function NOT overloaded

« Last post by Dennis on April 09, 2021, 09:53:41 pm »

This bug will be fixed in the next iteration of the 25.0.1 hot fix (Revision 9).

Thanks for the detailed sample code and instructions, and thanks for your patience on this one.  Let me know if you have any problems with the fix when you get it.

4

SlickEdit® / Re: Help on Error Start Debugger

« Last post by slin on April 09, 2021, 08:46:08 pm »

Hi Dennis,
The problem was resolved after I restarted the machine. The logging becomes normal after that too. Thanks for you help!

I hit another other issues after that, which does not show in my old machine either.

1. When I press F5 (or F7), a window/tab with the name "Build(.process)" jumps out into the editor window. It shows the same content as Build tool window at the bottom.  How can I disable it?
2. The above one is a minor issue.  What really bother me is when I press F5, the gdb did not go to the breakpoints that I set. In stead, it seems running until I hit the pause button and then it goes to the breakpoint.
3. I also observed some stack_log complains, after which the tool windows at the left side was forced off.
I attached the logs and screen captures for the above issues.
Thank!
Update: I installed 2019 version 2400, which has been used in my old machine.  I tried several times on the same workspace. I haven't seen any of the above problems yet. I will keep using 2400 right now.

5

SlickEdit® / Re: python f-string color coding problem with escaped braces

« Last post by Clark on April 09, 2021, 08:21:54 pm »

It's the same problem for all the f-string definitions. I fixed them all.

6

SlickEdit® / Re: Autosave untitled files leftovers

« Last post by Clark on April 09, 2021, 08:21:09 pm »

Good catch!

Untitled files (and autosave files) should be stored in an unversioned directory like backup history. Then this won't continue to happen. We will fix this for 25.0.2. We will need to make sure the old versioned "autosave" directory is not copied when 25.0.2 upgrades the config.

7

SlickEdit® / Re: python f-string color coding problem with escaped braces

« Last post by rowbearto on April 09, 2021, 08:11:44 pm »

Thanks. It also happens when using f""" (triple quotes) as well, maybe you have the same code for handling triple quotes as single.

8

SlickEdit® / Re: python f-string color coding problem with escaped braces

« Last post by Clark on April 09, 2021, 07:59:19 pm »

Ah..we missed that. Thanks for posting

Hot fix add for this

9

SlickEdit® / Autosave untitled files leftovers

« Last post by jporkkahtc on April 09, 2021, 07:28:48 pm »

There is a leak of "Untitled" files - finally figured this one out!

Untitled files are kept in the config path, e.g.: %SLICKEDITCONFIG%\25.0.0\autosave\Untitled*
Full paths to these files are kept in workspace *.VPWHIST files.

When I upgrade to the next version of slick (from 25.0.0 to 25.0.1), existing workspaces keep full paths to these untitled files, but the untitled files are also copied into the config\autosave directory for the new version of slickedit.

After upgrading, if I open an old workspace and modify one of its untitled files, then close the workspace, the original untitled file in the old config folder is modified.

When I close an older untitled file, the file is removed from the 25.0.0\autosave, but it remains in the 25.0.1\autosave

Code: [Select]

>dl "Untitled 2020-11-11 1437"  /s
       93973 04/09/2021 12:11:52 %SLICKEDITCONFIG%\25.0.0\autosave\Untitled 2020-11-11 1437
       93973 11/23/2020 18:36:28 %SLICKEDITCONFIG%\25.0.1\autosave\Untitled 2020-11-11 1437
Modify the Untitled file, and see the date update in 25.0.0

Code: [Select]

>dl "Untitled 2020-11-11 1437"  /s /od
       93994 04/09/2021 12:12:47 %SLICKEDITCONFIG%\25.0.0\autosave\Untitled 2020-11-11 1437
       93973 11/23/2020 18:36:28 %SLICKEDITCONFIG%\25.0.1\autosave\Untitled 2020-11-11 1437

Closed the Untitled file, and see the file removed from 25.0.0, but remains in 25.0.1

Code: [Select]

>dl "Untitled 2020-11-11 1437"  /s /od
       93973 11/23/2020 18:36:28 %SLICKEDITCONFIG%\25.0.1\autosave\Untitled 2020-11-11 1437


Presumably, the same problem applies to named files in the autosave folder.

10

SlickEdit® / python f-string color coding problem with escaped braces

« Last post by rowbearto on April 09, 2021, 06:59:18 pm »

In a Python f-string if you want to print an actual opening curly brace one uses 2 curly braces in a row - {{

But this throws off the color coding in python.

Example attached.