I am using the SQL choice from the Languages menu, developing software in PL/SQL. The choice of language seems to be working just fine with one exception.
The -- comment sequence of characters does not operate with the block comment options on the menu or keyboard shortcuts. The sequence is very obviously recognized by the style as a comment - it turns the correct color - but I cannot get the block comment toggle to produce it.
Is there something wrong with the language style definition?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-04-05
I test it and you are right. seems to be a bug
before it is fixed, i suggest you three alternative ways
first, ignore it, DIY :-)
second, create a simple macro - use find/replace to add -- at beginning of each line within the area you quoted (this seems not to work identically, since currently(ver 5.2) Npp's macro cannot save Find(/Replace) operations)
the third way, which i recommend, is to set up a user-define lang.
don't walk away. it's easy work, since much you can use the now-existing sql lang model to decrease your workload -
1. setting - styler configurator
2. copy sql's default keywords to a temporary file
3. view - User Define Dialogue, create new
4. paste the keywords you got before and define the comment symbol as --
5. this step is kind of irritating, add all operators of sql
6. edit stylers.xml in Npp install folder - copy sql's default settings to the block of the language you defined
ok, it's done. now you can use the block comment option.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks a lot. Currently, I'm taking option 1 with a little bit of option 2.
I have a keyboard macro defined to comment / uncomment one line at a time and that's not too bad.
I noted that N++ has a 5.3 release candidate recently. Do you know if the "saving of find/replace info" might be in that new version? Having the ability to save off find/replace info in a macro vastly increases their flexibility.
But then there's the "ultimate option": Dig through the source code to find the bug myself, fix it, and recompile. And of course - get the fix back here somehow.
I'm not walking away from the last option. I may even come back to it in my "copious free time." And I thank you much for the detailed instructions on how to "steal" 90% of the styler information from the existing language.
That was in fact one of my feature requests just last week I think. - "copy a built-in language as the starting point for a user defined one."
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-04-06
You are welcome, Bill.
You said you will try to fix the bug yourself. Wish you good luck :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I am using the SQL choice from the Languages menu, developing software in PL/SQL. The choice of language seems to be working just fine with one exception.
The -- comment sequence of characters does not operate with the block comment options on the menu or keyboard shortcuts. The sequence is very obviously recognized by the style as a comment - it turns the correct color - but I cannot get the block comment toggle to produce it.
Is there something wrong with the language style definition?
Thanks.
I test it and you are right. seems to be a bug
before it is fixed, i suggest you three alternative ways
first, ignore it, DIY :-)
second, create a simple macro - use find/replace to add -- at beginning of each line within the area you quoted (this seems not to work identically, since currently(ver 5.2) Npp's macro cannot save Find(/Replace) operations)
the third way, which i recommend, is to set up a user-define lang.
don't walk away. it's easy work, since much you can use the now-existing sql lang model to decrease your workload -
1. setting - styler configurator
2. copy sql's default keywords to a temporary file
3. view - User Define Dialogue, create new
4. paste the keywords you got before and define the comment symbol as --
5. this step is kind of irritating, add all operators of sql
6. edit stylers.xml in Npp install folder - copy sql's default settings to the block of the language you defined
ok, it's done. now you can use the block comment option.
Thanks a lot. Currently, I'm taking option 1 with a little bit of option 2.
I have a keyboard macro defined to comment / uncomment one line at a time and that's not too bad.
I noted that N++ has a 5.3 release candidate recently. Do you know if the "saving of find/replace info" might be in that new version? Having the ability to save off find/replace info in a macro vastly increases their flexibility.
But then there's the "ultimate option": Dig through the source code to find the bug myself, fix it, and recompile. And of course - get the fix back here somehow.
I'm not walking away from the last option. I may even come back to it in my "copious free time." And I thank you much for the detailed instructions on how to "steal" 90% of the styler information from the existing language.
That was in fact one of my feature requests just last week I think. - "copy a built-in language as the starting point for a user defined one."
You are welcome, Bill.
You said you will try to fix the bug yourself. Wish you good luck :)