Recent Posts

Pages: 1 ... 8 9 [10]
91
SlickEdit® / Go To Definition error: Can not jump to symbol ": No file name!
« Last post by rowbearto on April 08, 2018, 02:05:46 pm »
When I use Ctrl+. (Go to definition), I get a dialog box with a few choices of which definition to go to.

Occasionally when I double click on one of the options I see error message: "Can not jump to symbol ": No file name!". Attached is a screen shot. SE does not go to my definition when I see this error.

If I try a next time, I don't get this error, and SE does go to the definition.

It also happens occasionally when I single click select one of the options and click "OK".

I haven't figured out how to systematically reproduce this, but it happens often enough that it is annoying.

I'm using 22.0.2 on Linux x64/CentOS 7 with hotfix 3.
92
SlickEdit® / Re: Set Default Empty File to Edit (Or create key binding?)
« Last post by Graeme on April 07, 2018, 08:37:36 pm »
It looks like the standard edition lets you record a macro so you could try recording a macro that creates a new sql file.
93
SlickEdit® / Re: Set Default Empty File to Edit (Or create key binding?)
« Last post by indy042 on April 07, 2018, 06:52:39 pm »
Thank you for the help! Looks like I need the pro version to load it. (running the standard version)
I did save this so if I do upgrade down the line, I can give it a whirl.

-Andy
 
94
SlickEdit® / Re: "Expecting close parenthesis" in vim mode / search
« Last post by Clark on April 07, 2018, 06:06:37 pm »
Vim emulation will default to Vim regex syntax (always \m syntax which is Vim's default). It turns out that Vim has several minor variations to how escaping is handle which corresponds to \v, \m, \M, and \V. Typically these are used at the start of a Vim syntax regex. \v means "very magic" which is where there are many more special characters like in other regex syntax. \V means "very no magic" where the only special character is backslash and if you want regex meaning you must use a backslash (\* means 0 or occurrences). \M means "no magic" and seems pretty useless to me.

I do think first-time Vim emulation users will want this and it will make it easier to get Vim users to switch to SE. It is odd that it took so long for us to get this feedback. There is still a ton of a Vim users out there.

95
SlickEdit® / Re: "Expecting close parenthesis" in vim mode / search
« Last post by rowbearto on April 07, 2018, 05:48:29 pm »
Thanks Clark!

Does this mean that the default for VIM emulation searching with / will use the VIM syntax? What does \v, \m, \M and \V mean? If you default to using the VIM syntax in a / search then it would be easier to get VIM users to switch to SE.
96
SlickEdit® / Re: "Expecting close parenthesis" in vim mode / search
« Last post by Clark on April 07, 2018, 04:03:36 pm »
V23 will have Vim syntax regular expressions with support for the four different syntax modes (\v, \m (default), \M, and \V). Also, there will be an option to turn regular expression syntax off or choose another regular expression syntax (like Perl which is the current setting). The vim commands (like '/' and :substitute) will have override options to either turn off regex syntax or choose a specific regex syntax.
97
Features and/or Improvements / Re: Open slickedit help to the community
« Last post by jporkkahtc on April 06, 2018, 09:41:19 pm »
Its not just the content, but the container.
The current Qt help container has lots of bugs - and has been mentioned that Slick has been unable to resolve.

Of the most annoying problems:
Bookmarks: These sort of work, but they are always lost on updates - making them useless for me.
Sync With Contents: Mostly doesn't work - works for some pages, but lots of pages it doesn't work for.
Poor indexing and searching.
98
After I launch slickedit 22.0.1.0 I am seeing really high CPU utilizations (95-100%). I have no buffers open, no workspace open.  This is constant. I have run the run-time profiler and attached the tsv. My home directory is nfs mounted and I am running a really old kernel (CentOS 6.1 2.6.32) due to our IT dept not wanting to upgrade due to clearcase. I guess they think if it ain't broke don't upgrade it.
On the same machine I have a VirtualBox VM (CentOS 7.4) with 8G allocated to it running 22.0.2.1 (clearcase running but not used). It has the same NFS mounted home dir. I am not seeing the high CPU utilization but if I load up a workspace with ~8300 files the tagging says it completes pretty quickly but then it continues with high CPU and memory utilization until it finally crashes.

Any help would be appreciated.
99
SlickEdit® / Re: Open File Dialog favorites?
« Last post by jprod1038 on April 06, 2018, 04:27:08 pm »
Clark, that is perfect!  I didn't know you could do that, but is exactly what I was looking for!
100
SlickEdit® / Re: Options Window Size Too Large
« Last post by jprod1038 on April 06, 2018, 03:48:58 pm »
Thanks Graeme, resizing the _color_form worked for me!  Thanks for everyone's help and suggestions!
Pages: 1 ... 8 9 [10]