Recent Posts

Pages: 1 2 [3] 4 5 ... 10
Features and/or Improvements / Re: Why is "Sort" grayed out?
« Last post by Dan on Today at 12:42:26 pm »
I can't reproduce this.  What kind of file are you working with?  How many lines are selected?
Features and/or Improvements / Why is "Sort" grayed out?
« Last post by Researcher5 on Today at 11:56:23 am »
I'm a 20-year user of VS, new to v22.
I open a text file, Select-All, go to the Tool menu, and Sort is grayed out.

Why is Sort grayed out?  How do I sort?

Thanks - Researcher5
SlickEdit® / Re: Suggestion: Vim command mode should be normal mode
« Last post by Clark on April 18, 2018, 07:27:03 pm »
Thanks again. v22.02 has a new def_vi_command_mode_msg variable which defaults to blank so you get no "-- NORMAL --" or "-- COMMAND --" message by default. However, we missed the "Already in command mode" message. We will tweak this too.

v23 will have an option for Vim syntax regular expressions (new default for Vim emulation). Also you will be able to turn off regular expressions to effect the '/' and :substitute commands and optionally turn regex on for a specific command (currently deviates from Vim options). For example, "/a*b/n" will disable regex syntax. If the regex is turned off, "/a*b/~" will turn on Vim syntax regex ("/a*b/l" would turn on Perl syntax).

Personally, I like to have regex syntax disabled and only turn it on for specific search commands when I want it. If Vim has a way to do this, I'm not aware of it. \V almost turns off all regex stuff but backslash is still a special character.
SlickEdit® / Re: Suggestion: Vim command mode should be normal mode
« Last post by davea on April 18, 2018, 02:36:37 pm »

The somewhat vi centric error message:
"Already in command mode"

displayed when <ESC> is hit too many times, should be changed to the more vim centric:
"Already in normal mode"

Thanks.  I've got a couple of possibilities to look at now.  I'll let you know once I have something for you to try. 
That seems to have fixed the high utilization. It is now running at a respectable level.
Ok.  Can you try starting it like this, letting it settle down and see if you still have high cpu utilization:
Code: [Select]
QT_NO_GLIB=1 /path/to/install/bin/vs_exe +new

I can sometimes get a trace similar to yours on one of my systems, but it's very unreliable - doesn't always happen, and when it does, if I look at it funny, it will go back to normal cpu utilization.
SlickEdit® / Re: Assembly Syntax Highlighting Headaches (SlickEdit 2016 v21.0.1)
« Last post by jmurphy on April 16, 2018, 06:14:55 pm »
Hey Dennis,

Thanks so much for taking the time to provide an answer.  It worked perfectly.  I was so caught up in lexers and comment setup dialog boxes that I never ventured over to the "Document" menu.  So simple I'm kind of embarrassed I didn't find it  ::), but at least I'll know for next time.  Much appreciated...
SlickEdit® / BigFind search takes much longer in special case
« Last post by rowbearto on April 16, 2018, 02:36:20 pm »
I sent a file called "ec.vpj" to

Searching using BigFind with the settings in the attached screenshot:

Search for: "boardmgr"
"List all occurrences" checked
"List matching lines once only" checked
"List current context" checked

It takes a really long time. If I do the search without "List matching lines once only" and "List current context", the search is much faster.
Nope, private project. Did you really think it would be that easy?

Attached is the perf data for the high utilization issue.

Pages: 1 2 [3] 4 5 ... 10