I think just adding something like the "Filter Selection" option of NEdit would go a long way to solving issues like this. You can select some text, pipe it into an external command or shell script, and replace the selection with the output of the command.
For instance, you could use something like this perl script to emulate the "Justify Paragraph" option: http://directory.fsf.org/all/rewrap.html
But "Filter Selection" would also allow for all sorts of other user-specific filters, without adding a lot of bloat to Geany, almost like a sort of "plugin" or "macro"
- Jeff
PS: Sorry if you got this twice, John - I still haven't gotten accustomed the geany list not munging the mail headers. All other lists I subscribe to use a Reply-To:<list> header.
On 2/18/07, Jeff Pohlmeyer yetanothergeek@gmail.com wrote:
I think just adding something like the "Filter Selection" option of NEdit would go a long way to solving issues like this. You can select some text, pipe it into an external command or shell script, and replace the selection with the output of the command.
For instance, you could use something like this perl script to emulate the "Justify Paragraph" option: http://directory.fsf.org/all/rewrap.html
But "Filter Selection" would also allow for all sorts of other user-specific filters, without adding a lot of bloat to Geany, almost like a sort of "plugin> or "macro"
Jeff, that would be a really excellent and generally useful feature to have. Especially if there were a mechanism to bind a key combination to it.
I'd love to be able to assign a key combo that would pipe the selected text through a given script, replacing said text with the script's output. This opens up possibilities such as spell-checking, numbering lines, putting special symbols around paragraphs (like comment boxing, or quoting for email replies), etc.
I'm not familiar with the Geany codebase, haven't touched C in years, and my free time is hovering around 0 at the moment. Seems like it would be a simple feature to add, but I don't think I'm currently up for the task.
Would any of the core developers care to offer some tips here on how they'd go about adding such a feature? Which files would you look at first, and why? Is there a "new developer's guide and overview" tucked away anywhere? :)
Thanks, ---John
Would any of the core developers care to offer some tips> here on how they'd go about adding such a feature?
Well I'm not a core developer, but in a nutshell, I think it would be something like:
sci_get_selected_text_length(); sci_get_selected_text() ; g_spawn_async_with_pipes(); sci_replace_sel();
The build_spawn_cmd() function in geany/src/build.c could give some ideas for the g_spawn_* code.
If I get some time next week, I might give it a try, unless someone else beats me to it ;-)
- Jeff
On Sun, 18 Feb 2007 05:00:54 -0600, "Jeff Pohlmeyer" yetanothergeek@gmail.com wrote:
Would any of the core developers care to offer some tips> here on how they'd go about adding such a feature?
Well I'm not a core developer, but in a nutshell, I think it would be something like:
sci_get_selected_text_length(); sci_get_selected_text() ; g_spawn_async_with_pipes(); sci_replace_sel();
Yes, looks quite good. I think I'll add this tomorrow. Seems to be a nice feature and isn't hard to implement.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
On Sun, 18 Feb 2007 01:23:39 -0600, "Jeff Pohlmeyer" yetanothergeek@gmail.com wrote:
Hi,
PS: Sorry if you got this twice, John - I still haven't gotten accustomed the geany list not munging the mail headers. All other lists I subscribe to use a Reply-To:<list> header.
Because many people seems to have problems with answering mails without explicit reply-to header, I just activated it and from now on, all mails sent to this list will have the reply-to header with this list's mail address unless there was alerady another reply-to header in the mail.
Hope that helps you and your strange MUAs ;-). Please remember, these problems are not caused by this list but by your MUA's. IMO it's a shame for Google, that their gmail interface can't handle mailing lists without the reply-to header which shouldn't be necessary for good MUAs.
regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
I have been down loading the SVN tarballs and seeing that the Project additions are beginning to be added. As indicated in a previous email I have an interest in using Geany as a IDE for our undergraduates, hopefully giving a single editor with a simple gui that can be used, at least for the first year or so, for a number of different languages, typically C/C++/Assembler/Octave/Matlab/Basic and possibly Latex. One thing I am interested in doing is running c/c++ both locally and cross compiled and wondered if anything like this planned for your project management, i.e. the understanding of different target directories for different architectures.
Also I noticed that the documentation seems to be a 1-2 of verssions behind and wondered one what timescales it might be upgraded. Also if anyone is using or planning to use Geany for teaching and if anyone had written any suitable documentation before we 're-invent the wheel'.
Thanks again for all the work being put in on the package,
Regards
Peter
On 19 Feb 2007 14:47:29 +0000, "P.J.G. Long" pjgl2@cam.ac.uk wrote:
I have been down loading the SVN tarballs and seeing that the Project additions are beginning to be added. As indicated in a previous email I have an interest in using Geany as a IDE for our undergraduates, hopefully giving a single editor with a simple gui that can be used, at least for the first year or so, for a number of different languages, typically C/C++/Assembler/Octave/Matlab/Basic and possibly Latex. One thing I am interested in doing is running c/c++ both locally and cross compiled and wondered if anything like this planned for your project management, i.e. the understanding of different target directories for different architectures.
I'm not sure what you mean. Can you go into more detail?
Also I noticed that the documentation seems to be a 1-2 of verssions behind and wondered one what timescales it might be
Really? Look at http://geany.uvena.de/manual/, there is the manual for 0.10. Only the HTML files in SVN are a bit outdated(they are from the 0.10 release) but the file geany.docbook is up to date. Where did you find an older version of the document?
And yes, even the most current version is not yet complete...
Regards, Enrico
P.S.: could you please post with the same email address (pjgl2@eng.cam.ac.uk) as you are subscribed to this list? This would save me from manually accepting your mails. Thanks.
-- Get my GPG key from http://www.uvena.de/pub.key
On 2/19/07, Enrico Tröger enrico.troeger@uvena.de wrote:
On Sun, 18 Feb 2007 01:23:39 -0600, "Jeff Pohlmeyer" yetanothergeek@gmail.com wrote:
Hi,
PS: Sorry if you got this twice, John - I still haven't gotten accustomed the geany list not munging the mail headers. All other lists I subscribe to use a Reply-To:<list> header.
Because many people seems to have problems with answering mails without explicit reply-to header, I just activated it and from now on, all mails sent to this list will have the reply-to header with this list's mail address unless there was alerady another reply-to header in the mail.
Hope that helps you and your strange MUAs ;-). Please remember, these problems are not caused by this list but by your MUA's. IMO it's a shame for Google, that their gmail interface can't handle mailing lists without the reply-to header which shouldn't be necessary for good MUAs.
It's really a shame for Google, but I'm happy you did this. I couldn't find anyway to let google know that I was having such problems.
Thanks, Alexandre Moreira.
regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
Geany mailing list Geany@uvena.de http://uvena.de/cgi-bin/mailman/listinfo/geany
On 02/19/2007 02:47:29 PM, P.J.G. Long wrote:
I have been down loading the SVN tarballs and seeing that the Project additions are beginning to be added. As indicated in a previous email I have an interest in using Geany as a IDE for our undergraduates, hopefully giving a single editor with a simple gui that can be used, at least for the first year or so, for a number of different languages, typically C/C++/Assembler/Octave/Matlab/Basic and possibly Latex. One thing I am interested in doing is running c/c++ both locally and cross compiled and wondered if anything like this planned for your project management, i.e. the understanding of different target directories for different architectures.
We're not planning on extending the build system, but we will add support for a project root directory and a project executable. For a build procedure any more complicated than a compile and link, I would suggest using a Makefile. In your case perhaps you could write a default target for the Makefile that builds the code for Linux and a special target, say 'make arm' that builds for the ARM based microcontroller. Then you could use the 'Make Custom' command with the 'arm' argument to cross-compile.
[...] Also if anyone is using or planning to use Geany for teaching and if anyone had written any suitable documentation before we 're-invent the wheel'.
We welcome any documentation sent to us for the manual or any tutorials we can link to on the website. I'm not aware of any tutorials yet.
There was a short message that mentioned using 'Geany to write small programs with my students', but I don't know what happened after that. http://lists.uvena.de/pipermail/geany/2006-January/000037.html
I'd be interested to know how you get on with Geany, and which things could be improved. We are unlikely to implement big feature changes however (although in the medium-term a plugin system is planned).
Regards, Nick
On Mon, 19 Feb 2007 14:57:39 +0100, Enrico Tröger enrico.troeger@uvena.de wrote:
On Sun, 18 Feb 2007 05:00:54 -0600, "Jeff Pohlmeyer" yetanothergeek@gmail.com wrote:
Would any of the core developers care to offer some tips> here on how they'd go about adding such a feature?
Well I'm not a core developer, but in a nutshell, I think it would be something like:
sci_get_selected_text_length(); sci_get_selected_text() ; g_spawn_async_with_pipes(); sci_replace_sel();
Yes, looks quite good. I think I'll add this tomorrow. Seems to be a nice feature and isn't hard to implement.
Just for your interest: I'm about to implement this but it will still take some days...so please be patient.
Thanks, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
On Thu, 22 Feb 2007 20:46:11 +0100, Enrico Tröger enrico.troeger@uvena.de wrote:
On Mon, 19 Feb 2007 14:57:39 +0100, Enrico Tröger enrico.troeger@uvena.de wrote:
On Sun, 18 Feb 2007 05:00:54 -0600, "Jeff Pohlmeyer" yetanothergeek@gmail.com wrote:
Would any of the core developers care to offer some tips> here on how they'd go about adding such a feature?
Well I'm not a core developer, but in a nutshell, I think it would be something like:
sci_get_selected_text_length(); sci_get_selected_text() ; g_spawn_async_with_pipes(); sci_replace_sel();
Yes, looks quite good. I think I'll add this tomorrow. Seems to be a nice feature and isn't hard to implement.
Just for your interest: I'm about to implement this but it will still take some days...so please be patient.
It took some more days than expected and it wasn't that trivial ;-). But now it's in SVN and should work, at least a little bit.
You can define several custom commands and execute them via the edit and/or popup menu in Geany with SVN r1334. This only works if there is a selection. Then the selected text will be written to the standard input of the chosen command and its output on its standard output will be used to replace the selection. If the executed command prints any error messages on its standard error, these messages will be printed on Geany's standard output. My tests worked but I'm sure there might be some bugs in the code, so please test it.
The code needs further improvements in the future because there is somewhere a bug when writing and reading the commands pipes. I have workaround'ed it but it needs a fix not only a workaround ;-).
Currently, it doesn't work on Windows. Without any investigation, I guess it doesn't work because of the usage of pipes. Maybe anyone knows how to do it on Windows otherwise I would disable it for Windows.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
On 2/25/07, Enrico Tröger enrico.troeger@uvena.de wrote:
It took some more days than expected and it wasn't that trivial ;-). But now it's in SVN and should work, at least a little bit.
You can define several custom commands and execute them via the edit and/or popup menu in Geany with SVN r1334. This only works if there is a selection. Then the selected text will be written to the standard input of the chosen command and its output on its standard output will be used to replace the selection. [snip]
Nice! Thank you Enrico! The first custom command I added was simply ``/usr/bin/fmt'' and now Geany happily reformats my paragraphs, re-wrapping lines nicely. Geany just got more functional for me. :)
---John
But now it's in SVN and should work, at least a little bit.
Nice work, Enrico - it looks like a great start!
But I'm running into a some problems, along with a few other comments...
My system is set to plain old-fashioned ASCII, and the g_get_charset() call in utils_set_up_io_channel() returns "ANSI_X3.4-1968" but apparently g_io_channel_read_line() doesn't like this, it still tries to read UTF-8, which causes it to fail, and cc_iofunc() never finishes reading, which causes something like an endless loop. That smells like a bug in the glib documentation, but at any rate changing the encoding to NULL for g_io_channel_set_encoding() seems to solve the problem. ( That's really weird, because the build commands have always worked fine, I'm not sure why this is any different. )
I also don't think the g_io_channel_read_line() loop is quite right, it seems like it should keep looping as long as it returns G_IO_STATUS_NORMAL or G_IO_STATUS_AGAIN, and the cc_iofunc() should *always* return false, because unless you save the contents of the GString somewhere, it will always get clobbered if the function gets called more than once.
Finally, this one doesn't appear to cause any problems, but regarding the write() call in tools_execute_custom_command() the libc documentation says:
"Your program should always call write in a loop, iterating until all the data is written."
so I think it might be better to make sure all the data gets written, just in case.
Here is a patch with the above-mentioned changes, any opinions/feedback are welcome.
Regards, - Jeff
On Wed, 28 Feb 2007 17:39:51 -0600, "Jeff Pohlmeyer" yetanothergeek@gmail.com wrote:
But now it's in SVN and should work, at least a little bit.
Nice work, Enrico - it looks like a great start!
But I'm running into a some problems, along with a few other comments...
[...]
Here is a patch with the above-mentioned changes,
Thank you. I applied it with some small changes.
Great changes which fix some problems but one problem still remains: The do-while-loop in cc_iofunc() runs very often without receiving any data(msg is NULL). This slows down the whole process because the replacement is first done when all data is read. I have no idea why it gets called so often and no data is sent.
The encoding of all GIOChannels used in Geany is set to NULL now. I'm not sure whether this causes other problems, so we should keep some attention on this.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
On 3/1/07, Enrico Tröger enrico.troeger@uvena.de wrote:
...one problem still remains: The do-while-loop in cc_iofunc() runs very often without receiving any data(msg is NULL). This slows down the whole process
I think the problem is because the channel really should block when no data is available - can you try commenting out line 1218 in utils.c?
// g_io_channel_set_flags(ioc, G_IO_FLAG_NONBLOCK, NULL);
As far as I can tell, that solves the problem without any side effects.
- Jeff
On Thu, 1 Mar 2007 14:57:55 -0600, "Jeff Pohlmeyer" yetanothergeek@gmail.com wrote:
On 3/1/07, Enrico Tröger enrico.troeger@uvena.de wrote:
...one problem still remains: The do-while-loop in cc_iofunc() runs very often without receiving any data(msg is NULL). This slows down the whole process
I think the problem is because the channel really should block when no data is available - can you try commenting out line 1218 in utils.c?
// g_io_channel_set_flags(ioc, G_IO_FLAG_NONBLOCK, NULL);
As far as I can tell, that solves the problem without any side effects.
Yes and no. It solves the do-while-problem because we indeed want blocking at this point(furthermore a sync spawn process would be even better).
But we don't want blocking when using some build commands. If you do for example a "Make all" and blocking is enabled, there will be no messages in the compiler window and the whole GUI of Geany is freezed. I'll change the code so that blocking is disabled when using build commands and enabled when using the custom commands.
Thanks for pointing this out.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
On 2/25/07, Enrico Tröger enrico.troeger@uvena.de wrote:
On Thu, 22 Feb 2007 20:46:11 +0100, Enrico Tröger enrico.troeger@uvena.de wrote:
Yes, looks quite good. I think I'll add this tomorrow. Seems to be a nice feature and isn't hard to implement.
Just for your interest: I'm about to implement this but it will still take some days...so please be patient.
It took some more days than expected and it wasn't that trivial ;-). But now it's in SVN and should work, at least a little bit.
You can define several custom commands [snip]
Enrico, why limit key combos to only the first three?
As it happens, I've already got four:
1. rewrap paragraph (fmt)
2. rewrap #-commented paragraph (fmt --prefix=# --width=70) (Note, possible bug: this one only works if I *don't* put single or double quotes around the # symbol.)
3. my own script to create a nice comment box for various heading-type comments.
4. my own script to comment lines by just putting a '# ' at the beginning of each line. Geany's default ``comment lines'' puts the comment symbol right in front of the first non-whitespace character, and I think it's less readable than a nice uniform vertical line of comment symbols right at column 0.
So, can we have all 10 (Ctrl-1, Ctrl-2, Ctrl-3, ... Ctrl-0)? Or are they unavailable, or maybe earmarked for some other purpose? If you're a haggling man, how `bout 5? ;)
Thanks, ---John
On Fri, 2 Mar 2007 13:08:27 -0500, "John Gabriele" jmg3000@gmail.com wrote:
On 2/25/07, Enrico Tröger enrico.troeger@uvena.de wrote:
On Thu, 22 Feb 2007 20:46:11 +0100, Enrico Tröger enrico.troeger@uvena.de wrote:
Yes, looks quite good. I think I'll add this tomorrow. Seems to be a nice feature and isn't hard to implement.
Just for your interest: I'm about to implement this but it will still take some days...so please be patient.
It took some more days than expected and it wasn't that trivial ;-). But now it's in SVN and should work, at least a little bit.
You can define several custom commands [snip]
Enrico, why limit key combos to only the first three?
It was to not have so many keybindings defined. And I assumed that most users wouldn't use so many scripts. But we can increase the number to 5 or maybe even 10. Nick, what do you think?
- rewrap #-commented paragraph (fmt --prefix=# --width=70)
(Note, possible bug: this one only works if I *don't* put single or double quotes around the # symbol.)
Hmm, sounds like a quoting problem in the code. I will have a look at this, but maybe first on Monday or Tuesday.
- my own script to comment lines by just putting a '# ' at the
beginning of each line. Geany's default ``comment lines'' puts the comment symbol right in front of the first non-whitespace character, and I think it's less readable than a nice uniform vertical line of comment symbols right at column 0.
You can adjust this. There is a variable "comment_use_indent" in each filetype definition file where you can specify whether the comment character(s) should be placed on first column or after indention. Look at http://geany.uvena.de/manual/ch04.html#filetypes_format, there is some documentation for it.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
On 3/2/07, Enrico Tröger enrico.troeger@uvena.de wrote:
On Fri, 2 Mar 2007 13:08:27 -0500, "John Gabriele" jmg3000@gmail.com wrote: [snip]
- my own script to comment lines by just putting a '# ' at the
beginning of each line. Geany's default ``comment lines'' puts the comment symbol right in front of the first non-whitespace character, and I think it's less readable than a nice uniform vertical line of comment symbols right at column 0.
You can adjust this. There is a variable "comment_use_indent" in each filetype definition file where you can specify whether the comment character(s) should be placed on first column or after indention. Look at http://geany.uvena.de/manual/ch04.html#filetypes_format, there is some documentation for it.
Thanks Enrico.
So, you've pared me back down to 3 for the time being. :)
---John
On 3/2/07, John Gabriele jmg3000@gmail.com wrote:
On 3/2/07, Enrico Tröger enrico.troeger@uvena.de wrote: [snip]
You can adjust this. There is a variable "comment_use_indent" in each filetype definition file where you can specify whether the comment character(s) should be placed on first column or after indention. Look at http://geany.uvena.de/manual/ch04.html#filetypes_format, there is some documentation for it.
Thanks Enrico.
Actually, just noticed 2 points about the docs you pointed out:
1. The 2nd verbatim example in the Description of comment_use_indent should be
# command_example();
instead of
#command_example();
2. The Note says the setting only works for single line comments, but for me it's working for multi-line selections as well.
---John
On 3/2/07, John Gabriele jmg3000@gmail.com wrote:
On 3/2/07, John Gabriele jmg3000@gmail.com wrote:
On 3/2/07, Enrico Tröger enrico.troeger@uvena.de wrote: [snip]
You can adjust this. There is a variable "comment_use_indent" in each filetype definition file where you can specify whether the comment character(s) should be placed on first column or after indention. Look at http://geany.uvena.de/manual/ch04.html#filetypes_format, there is some documentation for it.
Thanks Enrico.
Actually, just noticed 2 points about the docs you pointed out:
- The 2nd verbatim example in the Description of comment_use_indent should be
# command_example();
instead of
#command_example();
- The Note says the setting only works for single line comments, but
for me it's working for multi-line selections as well.
I didn't read the docs, but perhaps it's talking about single line, as opposed to block, comments. Like // ... versus /* ... */
---John
Geany mailing list Geany@uvena.de http://uvena.de/cgi-bin/mailman/listinfo/geany
On Fri, 2 Mar 2007 13:52:20 -0500, "John Gabriele" jmg3000@gmail.com wrote:
On 3/2/07, John Gabriele jmg3000@gmail.com wrote:
On 3/2/07, Enrico Tröger enrico.troeger@uvena.de wrote: [snip]
You can adjust this. There is a variable "comment_use_indent" in each filetype definition file where you can specify whether the comment character(s) should be placed on first column or after indention. Look at http://geany.uvena.de/manual/ch04.html#filetypes_format, there is some documentation for it.
Thanks Enrico.
Actually, just noticed 2 points about the docs you pointed out:
- The 2nd verbatim example in the Description of comment_use_indent
should be
# command_example();
instead of
#command_example();
Oops, thank you. Fixed in SVN r1361 and the online documentation is updated, too.
- The Note says the setting only works for single line comments, but
for me it's working for multi-line selections as well.
Well yes. But the other way doesn't work. If you have "comment_use_indent" set to "true", it makes no difference because multi line comments start always at the beginning of the line. Therefore using of indention makes only sense when using single line comments.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
On Fri, 2 Mar 2007 16:08:22 -0300, "Alexandre Moreira" alexandream@gmail.com wrote:
On 3/2/07, John Gabriele jmg3000@gmail.com wrote:
On 3/2/07, John Gabriele jmg3000@gmail.com wrote:
On 3/2/07, Enrico Tröger enrico.troeger@uvena.de wrote: [snip]
You can adjust this. There is a variable "comment_use_indent" in each filetype definition file where you can specify whether the comment character(s) should be placed on first column or after indention. Look at http://geany.uvena.de/manual/ch04.html#filetypes_format, there is some documentation for it.
Thanks Enrico.
Actually, just noticed 2 points about the docs you pointed out:
- The 2nd verbatim example in the Description of
comment_use_indent should be
# command_example();
instead of
#command_example();
- The Note says the setting only works for single line comments,
but for me it's working for multi-line selections as well.
I didn't read the docs, but perhaps it's talking about single line, as opposed to block, comments. Like // ... versus /* ... */
Exactly.
Sorry John, I didn't read your mail carefully. Of course, it works also for multi line _selections_. When talking about a single line comment, I referred to // and multi line comments should be /* */ (for C, C++ of course). It doesn't matter whether you have selected one or multiple lines.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key
On 3/2/07, Enrico Tröger enrico.troeger@uvena.de wrote:
On Fri, 2 Mar 2007 16:08:22 -0300, "Alexandre Moreira" alexandream@gmail.com wrote:
[snip]
I didn't read the docs, but perhaps it's talking about single line, as opposed to block, comments. Like // ... versus /* ... */
Exactly.
Sorry John, I didn't read your mail carefully. Of course, it works also for multi line _selections_. When talking about a single line comment, I referred to // and multi line comments should be /* */ (for C, C++ of course). It doesn't matter whether you have selected one or multiple lines.
Doh. Of course. Though, as long as you make a point to mention it in the docs, for clarity, you might change the note from:
``This setting only works for single line comments.''
to
``Of course, this setting only applies to single-line style comments (as opposed to multi-line).''
Thanks, ---John
You can define several custom commands [snip]
Enrico, why limit key combos to only the first three?
Just a thought, but if you really need more options, you could always rely on some sort of "helper" application.
For instance, you could assign a script like this for one of your custom commands:
##################################### #!/bin/bash
xmessage -nearmouse "Choose a script:" \ -buttons "Upper:1,Lower:2,Hello:3"
case $? in 1) awk '{print toupper($0)}' ;; 2) awk '{print tolower($0)}' ;; 3) echo "Hello world :-)" ;; *) cat ;; esac #####################################
- Jeff
On 3/2/07, Jeff Pohlmeyer yetanothergeek@gmail.com wrote:
You can define several custom commands [snip]
Enrico, why limit key combos to only the first three?
Just a thought, but if you really need more options, you could always rely on some sort of "helper" application.
For instance, you could assign a script like this for one of your custom commands:
### [snip]
Hehehe. :) That's a delightful idea, Jeff. Thanks. That actually would give me fewer key combos to remember. When my little gui dialog pops up, it'll get focus and I can at that point have key combos to choose the little util I want -- while I'm looking right at a list of the names (shown in the dialog).
Cool idea. I'm going to try and use this method I think. Another good thing about it is that it doesn't hog up all the Ctrl-<number> Geany key combos.
---John
On Fri, 2 Mar 2007 15:09:53 -0500, "John Gabriele" jmg3000@gmail.com wrote:
On 3/2/07, Enrico Tröger enrico.troeger@uvena.de wrote:
On Fri, 2 Mar 2007 16:08:22 -0300, "Alexandre Moreira" alexandream@gmail.com wrote:
[snip]
I didn't read the docs, but perhaps it's talking about single line, as opposed to block, comments. Like // ... versus /* ... */
Exactly.
Sorry John, I didn't read your mail carefully. Of course, it works also for multi line _selections_. When talking about a single line comment, I referred to // and multi line comments should be /* */ (for C, C++ of course). It doesn't matter whether you have selected one or multiple lines.
Doh. Of course. Though, as long as you make a point to mention it in the docs, for clarity, you might change the note from:
``This setting only works for single line comments.''
to
``Of course, this setting only applies to single-line style comments (as opposed to multi-line).''
I added some single line comment examples. I hope this will help.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.key