Recent Posts

Pages: [1] 2 3 ... 10
Fixed for the next beta drop.  You'll notice that it will also pull in the whole FOR statement the first time you hit down arrow, which is what it's supposed to do. 

I do see a related issue where in some cases surround can't pull in the last line of a python function.  The fix for that is simple enough, but won't make it in time for the next beta drop.
Hi Dan,
Sorry for the late reply! It is hard to spot in the Task manager if an SVN thread is launched, because there are a LOT of background processes... by the time I've scrolled down, it has probably disappeared again  :(

Please send me the DLL with debug and I'll do the legwork for you.


You can speed up the the task manager, that might help.

I'll happily send you a DLL, but I'll have to wait until at least after the release candidate goes out.  Also some of the work will be in filewatcher.e.
Hi Dan,
If I may be so bold as to suggest a new feature... maybe a green tick should be overlaid to show that the file is unchanged (the same way that TortoiseSVN works now). This gives positive feedback that the SVN checking thread is working and has returned a result.

This is an interesting idea.
Thanks for taking a look! Also when I said "it would be a little busy though" to have function name on the same line, I don't mind the busy :). If you could squeeze in an option like this I would sincerely appreciate it.
Whoa.  That was working earlier in the beta cycle, I will have see what changed.  I'll get it fixed.  Thanks for the report.
Sweet! I did not notice that!

Just tried it with a single file search and it looks good! It would be nice to also have an option to print the function name on the same line as the search result too, I understand that could get a little busy though.

I just tried it with "Find in Files" though and SE appears to have frozen :(.
Have you tried the new option in v22 in Search Results options for List current context?  The matches are sorted by
 filename, then by function in the results, and are collapsable.
Any chance this feature would make it into Version 22? It would be very useful.
Slick-C® Macro Programming / saving data structures in the state file
« Last post by Graeme on Today at 09:32:25 am »
Despite writing slick macros for several years I'm not sure I fully grasped the fact that slick saves all of your "variable data" in the state file.  I have a hash array as below indexed by buffer name and for each buffer there is a linked list.  It's a history of where the current line has been.  This could amount to a fair amount of memory over time, not sure how much.  It turns out that it's useful to have slick keep this information, possibly saves me reading and writing to disk - though there's no check for corruption. 

Is it a bad idea to leave this information in the state file?  Should I try to delete it on shutdown?

static dlist    buffer_retrace_cursor_list:[];
SlickEdit 2017 v22 Beta Discussion / Re: Encoding options
« Last post by Clark on Today at 09:08:48 am »
Logged issues #1 and #2. Help fixed.
Pages: [1] 2 3 ... 10