SlickEdit Community

SlickEdit Product Discussion => SlickEdit® => Topic started by: dmw on August 31, 2008, 03:09:06 PM

Title: line comment setup won't accept spaces
Post by: dmw on August 31, 2008, 03:09:06 PM

I'm pretty sure that I used to be able to add trailing spaces to the comment characters in line comment setup.  I can still add them, but they are removed after clicking 'OK'. 

Can anyone offer a fix/work-around?

Thanks

Title: Re: line comment setup won't accept spaces
Post by: hs2 on September 04, 2008, 11:58:41 PM

Hmm - this is (still) working as it used to be (compared v12.0.3 vs. v13.0.2).
HS2

Title: Re: line comment setup won't accept spaces
Post by: hs2 on September 05, 2008, 01:15:55 AM

BTW: You might check your <SE-config-dir>/user.vlx file (ini file format) which contains your language lexer mods including the 'linecomment' key.
e.g.

Code: [Select]

[Batch]
...
linecomment="@REM "
...Good luck, HS2

Title: Re: line comment setup won't accept spaces
Post by: mrothman on December 11, 2009, 07:29:58 PM

For what it's worth, a year later, I was having the same problem.  That is, when I select and line comment this (in C++):

This is a comment

it became

//This is a comment

But I wanted this:

// This is a comment

And adding a trailing space to the Comment line characters in the Options configuration GUI didn't stick.

The user.vlx file no longer seems to be the place to go (at least on linux), but instead I found that ubox.ini appears to store the differences in each language comment configuration.  And using '\s' allowed me to specify a trailing space after the // line comment character (for c++).  Here's what the syntax in that file looks like:

nonboxchars=left=//\s right=\e  (color added to emphasize my change)

Now it works!

Title: Re: line comment setup won't accept spaces
Post by: David_O on December 15, 2009, 02:55:30 PM

What version of SE are you using?  Line comments are working with trailing spaces in the current 2009 release.

I take that back (and should have been more thorough).  We were able to reproduce this.  We'll get a fix in the next release or hotfix.

Thanks,