Recent Posts

Pages: 1 [2] 3 4 ... 10
11
SlickEdit® / Re: SlickEdit 25.0.1 C++ initializer list indents
« Last post by patrick on April 09, 2021, 01:32:09 pm »
It looks like this was changed when some initializer list settings were added.  It does need a new setting to go back to the old indent behavior.  I'll take a closer look this afternoon.  I suspect it's not hot-fixable, but I should be able to to put it in for 25.0.2.
12
SlickEdit® / SlickEdit 25.0.1 C++ initializer list indents
« Last post by jnairb on April 08, 2021, 08:41:08 pm »
When I try to type initializers for a C++ class, SlickEdit keeps trying to indent the list when I don't want it. The first initializer is indented 3 spaces (my normal indent) and subsequent initializers are indented 2 more spaces. (Not sure where 2 comes from -- continuation indent is also 3.) SE 24 doesn't do this. I searched for a Formatting option to control this, but couldn't find one. Is there one that I missed?

FYI, this is what my preferred formatting is:
Code: [Select]
ABC::ABC()
: member1(0)
, member2(1)
{
   ...
}
13
SlickEdit® / Re: Help on Error Start Debugger
« Last post by Dennis on April 08, 2021, 05:21:14 pm »
When you tried step (4), did you do that in a terminal in the same environment you are launching SlickEdit in.

What happens if you try the same "gdb --version" commands from the SlickEdit build window?

Try the logging again.  Just to be certain nothing is getting in the way, I would recommend closing SlickEdit and restarting it before hand.  There should be a lot more output than just the information about vsdebugio.

Final check, verify that you had not accidently modified the project to try to use a debugger other than GDB (Project > Project Properties... > Run/Debug)
14
SlickEdit User Macros / Interface to PLANTUML
« Last post by mike603 on April 08, 2021, 05:19:50 pm »
Does any have a macro that allows a buffer to be compiled by plantuml?

It can display in a separate window.

I'm just looking for something simple.

Thank you.
15
Features and/or Improvements / Interface to PLANTUML
« Last post by mike603 on April 08, 2021, 05:15:49 pm »
Add PLANTUML as a possible "language" that can be edited and when "compiled" it would generate the graphical output.

The output can be in a separate window.

I'm looking for something simple.

            Thank you
16
SlickEdit® / Re: F1 language help not working
« Last post by Clark on April 08, 2021, 12:35:59 am »
Yes. I’ll add a hot fix for this.
17
SlickEdit® / Re: F1 language help not working
« Last post by LBCEi on April 08, 2021, 12:20:53 am »
Thanks.

That seems to do the trick.

Can I assume that an official fix will be forthcoming?
18
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...
19
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.
20
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
Pages: 1 [2] 3 4 ... 10