Recent Posts

Pages: [1] 2 3 ... 10
SlickEdit® / Re: SE v27 loses workspace window positions
« Last post by Graeme on June 07, 2024, 07:51:53 PM »
They're in the vpwhist workspace file.,18811.msg74616.html#msg74616

I have no idea what would cause it.  If you make the vpwhist file readonly, and open the workspace multiple times, do you get the same results each time?  The file vrestore.slk has similar info in it.  Do you move this file between PCs  - that would cause problems I think.

See also this, dunno if these commands would help you,16601.msg64027.html#msg64027
Enhancements to named auto-restore commands
Commands save_named_files/load_named_files. Writes to windowstate.slk and restores files only.
Commands save_named_layout/load_named_layout. Writes to layoutstate.ini and restores tool windows and tool bars.
Commands save_named_state/load_named_state. Writes to state.ini and restores everything (files, tool windows, toolbars). Anyone
        who previously used saved_named_state/load_named_state will need to use save_named_files/load_named_files instead.
SlickEdit® / Re: Python issues in macOS
« Last post by Clark on June 07, 2024, 05:19:05 PM »
A hot fix is available for this.

Download the hot fix here:

Then load the hot fix: Help>Product Updates>Load Hot Fix...
SlickEdit® / Re: Python issues in macOS
« Last post by Clark on June 07, 2024, 04:26:43 PM »
Function call indent style=Continuation Indent-- Smart indenting bug. we will add a hot fix for this.

Doxygen comment support for Python would be nice using triple quoted strings.
SlickEdit® / Python issues in macOS
« Last post by jorick on June 07, 2024, 03:29:42 PM »
Options->Languages->Scripting Languages->Python->Formatting->(Edit)->Indent->Function call indent style = Continuation Indent

This setting is ignored and instead uses Align on Parens.

Options->Languages->Scripting Languages->Python->Comment->Documentation comments

Any way to enable this block?

Options->Languages->Scripting Languages->Python->Comment Wrap

This would be nice to have, like C/C++.  Working with comments in Python is a nightmare.  When typing a comment starting with # and I hit the end of the line, the cursor starts a new line but doesn't add a #.  If I'm typing in the middle of a multi-line comment and the end of the comment hits the end of the line, it will start moving the words at the end of the line to the beginning of the next line but before the #.

SlickEdit Pro 2023 (v28.0.2.0)

Serial number: [redacted]
Licensed number of users: Single user
License file: /Library/Application Support/SlickEdit/28/slickedit.lic

Build Date: April 4, 2024   (State file: April 26, 2024)
Emulation: CodeWright

OS: macOS Sonoma
OS Version: 14.5.0
Processor Architecture: Apple M3 Max (16 cores)

Memory: 95% Load, 62618MB/65536MB Virtual
Shell Information: /bin/bash -i
Screen Size: 1920 x 1080 (0 0), 1728 x 1117 (1920 0), 1920 x 1080 (-1920 0)

Project Type: Python
Language: .py (Python)
Encoding: UTF-8, no signature

Installation Directory: /Applications/
Configuration Directory: /Users/Richard-Bennet/Library/Application Support/SlickEdit/28.0.2/
Spill File: /tmp/slkspill.Richard-Bennet.95005

/Users/Richard-Bennet/Library/Application Support/SlickEdit/28.0.2/hotfixes/ Revision: 7   (currently loaded)

SlickEdit® / SE v27 loses workspace window positions
« Last post by pmsteinm on June 07, 2024, 03:07:36 PM »
I've been having the problem for at least a year but now it's getting more annoying. I have a workspace that is pointing to a Visual Studio project. I have a main window split vertically with different files open on each side. I also have a floating window on another monitor with multiple tabs. Most of the time when I close and open my project the windows appear in the correct place. But sometimes (which seems more frequent now) the windows are randomly moved around (i.e. some stuff that was on the left is now on the right, or in the floating window, and vice versa). All the windows are open that I expect, just in what appears to be random places. I thought it was just when I went from home (3 external 4k monitors, plus laptop 3840x2400) to work (2 external 4k + laptop). But now even without undocking the window locations can get messed up when I open the workspace. I sometimes have 2 instances of SE open (2nd is a different project) but that doesn't seem to be required for this problem to occur. Can I look at the file that stores the window positions? Any ideas on what might cause this?

I'm running with latest hotfixes on Windows 11 Enterprise 23H2.

SlickEdit® / Re: SGrep Issue with Wildcard (-wc) Switch
« Last post by mek on June 06, 2024, 09:59:39 PM »
Thanks Clark

I concur that your "fix" of explicitly providing a "default" directory (i.e. .) when using -wc does indeed produce the results I would expect.
SlickEdit® / Re: SGrep Issue with Wildcard (-wc) Switch
« Last post by Clark on June 06, 2024, 09:49:49 PM »
Interesting. It doesn't seem to work right unless you specify a path like this:

    sgrep -i -t -pc jojo . -wc dbo.Test* dbo.RunTest*

the above is equivalent to this:

    sgrep -i -t -pc jojo dbo.Test* dbo.RunTest*

The reason -wc was added is for users to avoid having to repeat long paths multiple times.

consider the following:

     sgrep -i -t -pc jojo c:\some\really\long\long\path\dbo.Test* c:\some\really\long\long\path\dbo.RunTest*

In this case use -wc like this:

     sgrep -i -t -pc jojo c:\some\really\long\long\path -wc dbo.Test* dbo.RunTest*

For now, always specify a path when using -wc.

We will look into this. It should still work without a path.
SlickEdit® / Re: SGrep Issue with Wildcard (-wc) Switch
« Last post by mek on June 06, 2024, 08:11:17 PM »
Thanks Clark -- unfortunately quoting or not quoting the wildcard parameters does not make a difference in the results (this is on Windows btw). 

If I were a betting man, it really does look like there is a command line argument parsing issue with sgrep where it's accidentally turning on the "-w" switch when only a -wc switch is being supplied (again that's just my conclusion based on the observed behavior).
SlickEdit® / Re: SGrep Issue with Wildcard (-wc) Switch
« Last post by Clark on June 06, 2024, 07:30:47 PM »
If you're on Linux or macOS, you should quote the wildcards to make sure something weird doesn't happen.

sgrep -i -t -pc jojo -wc "dbo.Test*" "dbo.RunTest*"
SlickEdit® / SGrep Issue with Wildcard (-wc) Switch
« Last post by mek on June 06, 2024, 04:08:47 PM »
I'm using the version of sgrep distributed with VS 2023 and am encountering an issue when using the -wc switch to include multiple file name masks for searching against.  It would appear that when this option is enabled, the searching behaves in a manner that would be consistent with the -w (Match whole word) being enabled as well -- this is not what I desire :(

failing example:  sgrep -i -t -pc jojo -wc dbo.Test* dbo.RunTest*

Text that looks like "test_jojo" will not be matched, but if the command is changed to use individual sgrep invocations for each wildcard mask, the match will be found...

passing example:  sgrep -i -t -pc jojo dbo.Test*

Don't know when this behavior started as this is really the first time I've attempted to use the -wc switch...

Thanks for your help.
Pages: [1] 2 3 ... 10