Recent Posts

Pages: 1 2 [3] 4 5 ... 10
SlickEdit® / Re: F1 language help not working
« Last post by LBCEi on April 08, 2021, 12:20:53 am »

That seems to do the trick.

Can I assume that an official fix will be forthcoming?
SlickEdit® / Re: F1 language help not working
« Last post by Clark on April 07, 2021, 11:13:25 pm »
There's an error in def_word_help_url.

Change the # to an &

Macro> Set Macro Variable...
SlickEdit® / Re: Help on Error Start Debugger
« Last post by slin on April 07, 2021, 10:55:59 pm »
Thanks Dennis.
Here are what I got following your instructions:
1. changing the default native debugger between /usr/bin/gdb and slickedit-pro2020/bin/gdb does not make difference.
2. The debug log only had one line for each try "debug[2021-04-07T22:13:55Z]stopping 'vsdebugio' process"
3. I am using SE in a docker which essentially runs centos7, the host is centos8.
4. The version check returns as follows
[vagrant@0d328535f5bd logs]$ /vagrant/opt/slickedit-pro2020/bin/gdb --version
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
ImportError: No module named site
[vagrant@0d328535f5bd logs]$ /usr/bin/gdb --version
GNU gdb (GDB) 8.2.1

More information. I also have an old platform that runs the same docker with 2019 SlickEdit. That one has not ever had issue using gdb.
SlickEdit® / Re: Help on Error Start Debugger
« Last post by Dennis on April 07, 2021, 09:45:55 pm »
First thing to try is to switch which GDB you are using:

1) Debug > Debugger Options > GDB Configurations...   
    Look at the one in bold.
    Is that /usr/bin/gdb or the one distributed with SlickEdit?
    Either way, they should both be in the list, click on the other, then check
    [ x ] Default native debugging configuration

2) If switching debuggers does not work, we have some logging to help narrow down
    what is going on.  Macro > Set Macro Variable... > def_debug_logging=1
    Then try to start debugging.
    Set def_debug_logging back to 0.
    The log file will be in your configuration directory under logs/debug.log

3) What Unix platform/distro are you on?

4) From a terminal window, try to run the GDB distributed with SlickEdit?
    /vagrant/opt/slickedit-pro2020/bin/gdb --version

5) Do the same for /usr/bin/gdb
    /usr/bin/gdb --version
SlickEdit® / F1 language help not working
« Last post by LBCEi on April 07, 2021, 08:20:44 pm »
In 25.0.1 with hotfix 2, pressing F1 on a printf (for example) in an ANSI-C or C/C++ file doesn't open help in my browser like it used to.  It used to take me to (for example

I'm thinking this may be an issue with Chrome rather than SE.

The url from an C/C++ file is

For ANSI-C it is

I also tried it in with hotfix 5.  Same result.
SlickEdit® / Help on Error Start Debugger
« Last post by slin on April 07, 2021, 07:49:51 pm »
I was trying to run gdb in slickedit but go the following errors in a pop-up window: "Error starting debugger: connection closed". In the output window, it shows:
[SE vagrant@0d328535f5bd ucpp]$ /vagrant/opt/slickedit-pro2020/bin/vsdebugio -port 8001  -prog  "/vagrant/temp/testcode/ucpp/Debug/ucpp"
Exiting with error: -103370

This is a new machine and I just installed Pro
The project I was testing is the SampleProject/ucpp.

What could be the problem here?
SlickEdit® / Re: external formatter
« Last post by mzel on April 06, 2021, 07:44:54 pm »
Thanks, let me try this
Features and/or Improvements / Re: Multiple cursor alignment
« Last post by Dennis on April 06, 2021, 05:24:02 pm »
This is a great idea, we are looking into it for the next release.
SlickEdit® / Re: Linux vsdiff not working
« Last post by Dan on April 06, 2021, 05:12:38 pm »
Go to Macro>Set Macro Variable.

For the variable name, put "def_smart_diff_limit".  For the value, put 100,000 (no comma, I just wanted it to be clearly readable).  This should fix the issue with the one instance of "('len(blk[2]=4066',)" in file2 that has been matching at the bottom of the inserted section instead of the top. 

def_smart_diff_limit is a very, very old option, and we will either be setting a new limit, or possibly getting rid of it altogether in v26.0.0 (we'll have to do testing on files with a huge number of differences).

A few other lines before the inserted section show up as inserted too.  I'm not sure why that is exactly, but it is the same result as we got before the diff engine changed v23.0.0.  I'll be looking into this too.
SlickEdit® / Re: Keyboard shortcut to show\pin and hide\unpin Search Results
« Last post by Dennis on April 06, 2021, 04:18:05 pm »
For 25.0.2, I added a suite of commands (no default key bindings for them) toggle_*_pinned, similar to the existing toggle_* commands for toggling whether a tool window was visible or not.

Example:  toggle_search_pinned

1) If "Search Results" was not visible, it will make it visible, doing exactly what "toggle_search_results" would do.

2) If "Search Results" is visible and docked, it will unpin it (make it an auto-hidden tool window), along with all other tool windows in it's tab group.

3) If "Search Results" is unpinned (auto-hidden), it will pin it, making it a docked tool window, along with all other tool windows in it's tab group.

4) If "Search Results" is visible and floating, it will unpin it  (make it an auto-hidden tool window).
Pages: 1 2 [3] 4 5 ... 10