One of the modifications in the Doc patch about Tools->Reload Configuration is in the *Inserting Unicode characters* section. Here is the modified excerpt:
With GTK 2.10 and above, you can insert Unicode code points by hitting
Ctrl-Shift-u, then still holding Ctrl-Shift, type some hex digits representing the code point for the character you want, then let go of Ctrl-Shift and hit Enter or Return.
For this to work in Geany, you'll need to first unbind Ctrl-Shift-u in the `keybinding preferences`_, then select *Tools->Reload Configuration*
or restart Geany. Note that it works slightly differently from other GTK applications, in that you'll need to continue to hold down the Ctrl and Shift keys while typing the code point hex digits.
I tried this when checking for Reload Configuration effects. I noted that currently (revision 4675) Ctrl-Shift-u is not bound in the *keybinding preferences*, and that using Enter or Return to end the Unicode specifier actually entered a carriage return in the text. Intuitively, a space after the code should be enough to end the specifier, and indeed it does. I'm not sure whether this is a bug in the code, or a needed document modification. I didn't go looking for the point in revision history where the behavior changed.
- tony
On Fri, 19 Feb 2010 22:36:29 -0800, Tony wrote:
One of the modifications in the Doc patch about Tools->Reload Configuration is in the *Inserting Unicode characters* section. Here is the modified excerpt:
With GTK 2.10 and above, you can insert Unicode code points by hitting
Ctrl-Shift-u, then still holding Ctrl-Shift, type some hex digits representing the code point for the character you want, then let go of Ctrl-Shift and hit Enter or Return.
For this to work in Geany, you'll need to first unbind Ctrl-Shift-u in the `keybinding preferences`_, then select *Tools->Reload Configuration*
or restart Geany. Note that it works slightly differently from other GTK applications, in that you'll need to continue to hold down the Ctrl and Shift keys while typing the code point hex digits.
I tried this when checking for Reload Configuration effects. I noted that currently (revision 4675) Ctrl-Shift-u is not bound in the *keybinding preferences*, and that using Enter or Return to end the Unicode specifier actually entered a carriage return in the text. Intuitively, a space after the code should be enough to end the specifier, and indeed it does. I'm not sure whether this is a bug in the code, or a needed document modification. I didn't go looking for the point in revision history where the behavior changed.
Weird, never noticed that finishing the input with Space works as well. Anyway, the note about unbinding Ctrl-Shift-u in the preferences was added because in older versions we accidently used Ctrl-Shift-u as default for another keybinding. Maybe the note could be changed to reflect that. However, I don't get it to insert a line break even when using Enter/Return to finish the Unicode input.
Regards, Enrico
2010/2/22 Enrico Tröger enrico.troeger@uvena.de
On Fri, 19 Feb 2010 22:36:29 -0800, Tony wrote:
One of the modifications in the Doc patch about Tools->Reload Configuration is in the *Inserting Unicode characters* section. Here is the modified excerpt:
With GTK 2.10 and above, you can insert Unicode code points by hitting
Ctrl-Shift-u, then still holding Ctrl-Shift, type some hex digits representing the code point for the character you want, then let go of Ctrl-Shift and hit Enter or Return.
For this to work in Geany, you'll need to first unbind Ctrl-Shift-u in the `keybinding preferences`_, then select *Tools->Reload Configuration*
or restart Geany. Note that it works slightly differently from other GTK applications, in that you'll need to continue to hold down the Ctrl and Shift keys while typing the code point hex digits.
I tried this when checking for Reload Configuration effects. I noted that currently (revision 4675) Ctrl-Shift-u is not bound in the *keybinding preferences*, and that using Enter or Return to end the Unicode specifier actually entered a carriage return in the text. Intuitively, a space after the code should be enough to end the specifier, and indeed it does. I'm not sure whether this is a bug in the code, or a needed document modification. I didn't go looking for the point in revision history where the behavior changed.
Weird, never noticed that finishing the input with Space works as well. Anyway, the note about unbinding Ctrl-Shift-u in the preferences was added because in older versions we accidently used Ctrl-Shift-u as default for another keybinding. Maybe the note could be changed to reflect that. However, I don't get it to insert a line break even when using Enter/Return to finish the Unicode input.
Enrico, I think the problem is that the manual says let go ctrl-shift before typing return, holding ctrl-shift and typing return inserts the Unicode point without the return but any character, including return, typed after releasing the ctrl-shift inserts the Unicode point and itself. I thought this was a feature :-D
Cheers Lex
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.asc
Geany-devel mailing list Geany-devel@uvena.de http://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
On Sun, Feb 21, 2010 at 1:29 PM, Lex Trotman elextr@gmail.com wrote:
Weird, never noticed that finishing the input with Space works as well. Anyway, the note about unbinding Ctrl-Shift-u in the preferences was added because in older versions we accidently used Ctrl-Shift-u as default for another keybinding. Maybe the note could be changed to reflect that. However, I don't get it to insert a line break even when using Enter/Return to finish the Unicode input.
Enrico, I think the problem is that the manual says let go ctrl-shift before typing return, holding ctrl-shift and typing return inserts the Unicode point without the return but any character, including return, typed after releasing the ctrl-shift inserts the Unicode point and itself. I thought this was a feature :-D
Cheers Lex
I realized about holding ctrl-shift for the Enter/Return, and just figured that I mis-read the the manual (without actually checking), but Lex beat me to the punch. I guess this is a doc modification, too. I'll do it, unless somebody else beat me to that, too.
- tony
On Sun, Feb 21, 2010 at 1:49 PM, Tony Rick tonyr42@gmail.com wrote:
On Sun, Feb 21, 2010 at 1:29 PM, Lex Trotman elextr@gmail.com wrote:
Weird, never noticed that finishing the input with Space works as well. Anyway, the note about unbinding Ctrl-Shift-u in the preferences was added because in older versions we accidently used Ctrl-Shift-u as default for another keybinding. Maybe the note could be changed to reflect that. However, I don't get it to insert a line break even when using Enter/Return to finish the Unicode input.
Enrico, I think the problem is that the manual says let go ctrl-shift before typing return, holding ctrl-shift and typing return inserts the Unicode point without the return but any character, including return, typed after releasing the ctrl-shift inserts the Unicode point and itself. I thought this was a feature :-D
Cheers Lex
I realized about holding ctrl-shift for the Enter/Return, and just figured that I mis-read the the manual (without actually checking), but Lex beat me to the punch. I guess this is a doc modification, too. I'll do it, unless somebody else beat me to that, too.
- tony
...and here's the patch for the manual (against revision 4688).
- tony
Am Sonntag, den 21.02.2010, 14:09 -0800 schrieb Tony Rick:
On Sun, Feb 21, 2010 at 1:49 PM, Tony Rick tonyr42@gmail.com wrote: On Sun, Feb 21, 2010 at 1:29 PM, Lex Trotman elextr@gmail.com wrote:
Weird, never noticed that finishing the input with Space works as well. Anyway, the note about unbinding Ctrl-Shift-u in the preferences was added because in older versions we accidently used Ctrl-Shift-u as default for another keybinding. Maybe the note could be changed to reflect that. However, I don't get it to insert a line break even when using Enter/Return to finish the Unicode input. Enrico, I think the problem is that the manual says let go ctrl-shift before typing return, holding ctrl-shift and typing return inserts the Unicode point without the return but any character, including return, typed after releasing the ctrl-shift inserts the Unicode point and itself. I thought this was a feature :-D Cheers Lex I realized about holding ctrl-shift for the Enter/Return, and just figured that I mis-read the the manual (without actually checking), but Lex beat me to the punch. I guess this is a doc modification, too. I'll do it, unless somebody else beat me to that, too. - tony...and here's the patch for the manual (against revision 4688).
Applied, thanks!
On Sun, 21 Feb 2010 23:46:05 +0100, Dominic wrote:
Am Sonntag, den 21.02.2010, 14:09 -0800 schrieb Tony Rick:
On Sun, Feb 21, 2010 at 1:49 PM, Tony Rick tonyr42@gmail.com wrote: On Sun, Feb 21, 2010 at 1:29 PM, Lex Trotman elextr@gmail.com wrote:
Weird, never noticed that finishing the input with Space works as well. Anyway, the note about unbinding Ctrl-Shift-u in the preferences was added because in older versions we accidently used Ctrl-Shift-u as default for another keybinding. Maybe thenote could be changed to reflect that. However, I don't get it to insert a line break even when using Enter/Return to finish the Unicode input.
Enrico, I think the problem is that the manual says let go ctrl-shift before typing return, holding ctrl-shift and typing return inserts the Unicodepoint without the return but any character, including return, typed after releasing the ctrl-shift inserts the Unicode point and itself. I thought this was a feature :-D
Cheers Lex I realized about holding ctrl-shift for the Enter/Return, and just figured that I mis-read the the manual (without actually checking), but Lex beat me to the punch. I guess this is adoc modification, too. I'll do it, unless somebody else beat me to that, too.
- tony...and here's the patch for the manual (against revision 4688).
Applied, thanks!
Get my thanks, too. Tony, sorry for not reading your initial mail carefully enough, Lex thanks for pointing out my mistake and finally thanks to all for the doc correction :).
Regards, Enrico