Hi group,
here again with yet another SciTE question :)
In my global/user properties files I had this line:
style.*.33=fore:#404040,back:#DDD9D8,$(font.small)
which is "mapped" in Geany fileprops with this property:
marker_line=0x404040;0xDDD9D8;(bool);(bool)
so I can't make line-number font smaller - my main concern, or even different font, or different font for comments etc.
In Geany it seems that everything has same font, defined in geany.conf:
editor_font=Droid Sans Mono 9
or selected from the menu. And additionally:
tagbar_font=Droid Sans 9 msgwin_font=Droid Sans 9
probably read from OS setttings.
Is there any way I can make line-number font smaller then editor font?
And also I'm curious if I missed some font setting in any configuration file.
Cheers
On Sat, 25 Feb 2012 18:44:33 +0100 klo uo klonuo@gmail.com wrote:
In Geany it seems that everything has same font, defined in geany.conf:
editor_font=Droid Sans Mono 9
It's single-font, Monospace 10 by default.
or selected from the menu. And additionally:
tagbar_font=Droid Sans 9 msgwin_font=Droid Sans 9probably read from OS setttings.
The defaults are Sans 9; no idea why all your fonts are Droid.
Is there any way I can make line-number font smaller then editor font?
No. A new setting may or may not be easy to add - the line-number font may be higher than the editor font, which has the potential to break a lot of functions... though I can't name even one.
OK, thanks for confirmation Fonts were probably like you wrote, I thought it reads my system font set which are set to Droid, but maybe I made them like that.
As I build Geany and plugins from source, if it's not much trouble and some dev can give me a tip how to change Geany source to make linenumber one point smaller then rest of editor font, I'd appreciate it much.
TIA, cheers
On Sat, Feb 25, 2012 at 7:56 PM, Dimitar Zhekov dimitar.zhekov@gmail.comwrote:
Is there any way I can make line-number font smaller then editor font?
No. A new setting may or may not be easy to add - the line-number font may be higher than the editor font, which has the potential to break a lot of functions... though I can't name even one.
I got to probable candidate - STYLE_LINENUMBER, while searching /src/ folder for "line.?number" and file "highlighting.c:798":
set_sci_style(sci, STYLE_LINENUMBER, GEANY_FILETYPES_NONE, GCS_MARGIN_LINENUMBER);
Any comment should I look elsewhere or so? I don't know C/C++ to find my way
On Sat, Feb 25, 2012 at 8:27 PM, klo uo klonuo@gmail.com wrote:
As I build Geany and plugins from source, if it's not much trouble and some dev can give me a tip how to change Geany source to make linenumber one point smaller then rest of editor font, I'd appreciate it much.
On 26 February 2012 07:16, klo uo klonuo@gmail.com wrote:
I got to probable candidate - STYLE_LINENUMBER, while searching /src/ folder for "line.?number" and file "highlighting.c:798":
Geany does not provide a way of setting the font for the linenumbers differently from the editor window.
The three fonts you mention in the previous post can be set in the preferences.
Cheers Lex
set_sci_style(sci, STYLE_LINENUMBER, GEANY_FILETYPES_NONE, GCS_MARGIN_LINENUMBER);
This transfers the settings from filetypes.common to scintilla, but that does not include the font.
Any comment should I look elsewhere or so? I don't know C/C++ to find my way
On Sat, Feb 25, 2012 at 8:27 PM, klo uo klonuo@gmail.com wrote:
As I build Geany and plugins from source, if it's not much trouble and some dev can give me a tip how to change Geany source to make linenumber one point smaller then rest of editor font, I'd appreciate it much.
Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
Hi,
Le 25/02/2012 21:16, klo uo a écrit :
I got to probable candidate - STYLE_LINENUMBER, while searching /src/ folder for "line.?number" and file "highlighting.c:798":
set_sci_style(sci, STYLE_LINENUMBER, GEANY_FILETYPES_NONE,GCS_MARGIN_LINENUMBER);
Any comment should I look elsewhere or so? I don't know C/C++ to find my way
Around that place would be fine, dumb patch attached. [1] It's a hack, but it should do what you want.
I'm not convinced that having a different font and/or size make sense, so I'm not sure adding a setting for that would be useful.
Regards, Colomban
[1] BTW if anybody knows why setting the different size in editor_set_font() doesn't work, I'd very much like to be told about it. Actually it works if setting a new font size in the prefs, but not at startup. I didn't spend time on it, but it still looks weird to me.
On Sun, Feb 26, 2012 at 12:27 AM, Colomban Wendling < lists.ban@herbesfolles.org> wrote:
Around that place would be fine, dumb patch attached. [1] It's a hack, but it should do what you want.
Thanks Colomban :) I was hopelessly digging in Scintilla source to hard code it, but found only how to change listbox font :D for calltips I owe you a beer :)
I'm not convinced that having a different font and/or size make sense,
so I'm not sure adding a setting for that would be useful.
It looks great to me. Maybe I'm used to it, but I surely made it like that on purpose in SciTE. It doesn't go in a way too much this way. At least for me. I did have to change " - 2" to " - 1" as I wanted just one size smaller.
Thanks again for your elegant solution :)
Cheers
Sorry I couldn't resist, just take a look at this screen-shot please: http://www.geany.org/uploads/Gallery/geany_main.png
Line-number characters are bigger then everything there, and because they form linear pattern easy to follow, they are most obvious place to look at first, being larger then anything and with distinct color Excluding yellow icons in Symols tree view, of course...
I don't have some pet here right now, but I'll show later that image for 3 seconds and ask participant what data they remembered Grey background may prove me wrong, but I'll see...
Cheers
On Sun, Feb 26, 2012 at 1:05 AM, klo uo klonuo@gmail.com wrote:
I'm not convinced that having a different font and/or size make sense,
so I'm not sure adding a setting for that would be useful.
It looks great to me. Maybe I'm used to it, but I surely made it like that on purpose in SciTE. It doesn't go in a way too much this way. At least for me. I did have to change " - 2" to " - 1" as I wanted just one size smaller.
Thanks again for your elegant solution :)
Cheers
On 26 February 2012 13:34, klo uo klonuo@gmail.com wrote:
Sorry I couldn't resist, just take a look at this screen-shot please: http://www.geany.org/uploads/Gallery/geany_main.png
Line-number characters are bigger then everything there, and because they form linear pattern easy to follow, they are most obvious place to look at first, being larger then anything and with distinct color Excluding yellow icons in Symols tree view, of course...
I don't have some pet here right now, but I'll show later that image for 3 seconds and ask participant what data they remembered Grey background may prove me wrong, but I'll see...
Well, I would have to say that that experiment is irrelevant, the Geany GUI is designed for staring at for hours at a time, in which case you tune out the line numbers and margins unless you actually need them :)
Cheers Lex
I did expect something like this coming ;)
Apart for locating errors, patches... line-numbers can provide various info just by sitting there, as which bookmark I see (although bookmarks aren't coded to line numbers), where in the code am I right now, how large is file, etc... I just wanted to provide more info to Colomban
Cheers
On Sun, Feb 26, 2012 at 3:59 AM, Lex Trotman elextr@gmail.com wrote:
Well, I would have to say that that experiment is irrelevant, the Geany GUI is designed for staring at for hours at a time, in which case you tune out the line numbers and margins unless you actually need them :)
On 26 February 2012 14:10, klo uo klonuo@gmail.com wrote:
I did expect something like this coming ;)
You shouldn't admit that, you will get accused of trolling...
Apart for locating errors, patches... line-numbers can provide various info just by sitting there, as which bookmark I see (although bookmarks aren't coded to line numbers), where in the code am I right now, how large is file, etc... I just wanted to provide more info to Colomban
Just noting that a three second impression of a GUI meant for hours of use is an irrelevant experiment and won't provide any information, don't waste your time.
Cheers Lex
On Sun, Feb 26, 2012 at 4:33 AM, Lex Trotman elextr@gmail.com wrote:
On 26 February 2012 14:10, klo uo klonuo@gmail.com wrote:
I did expect something like this coming ;)
You shouldn't admit that, you will get accused of trolling...
What's up with you calling me troll when it's evident that you are the one trolling, as I clearly wrote to you that my message isn't addressed to you, but to member who actually provides solutions here instead smalltalk, as I noticed in my short time here?
Apart for locating errors, patches... line-numbers can provide various
info
just by sitting there, as which bookmark I see (although bookmarks aren't coded to line numbers), where in the code am I right now, how large is
file,
etc... I just wanted to provide more info to Colomban
Just noting that a three second impression of a GUI meant for hours of use is an irrelevant experiment and won't provide any information, don't waste your time.
Didn't you make your point already?
On 26 February 2012 14:52, klo uo klonuo@gmail.com wrote:
On Sun, Feb 26, 2012 at 4:33 AM, Lex Trotman elextr@gmail.com wrote:
On 26 February 2012 14:10, klo uo klonuo@gmail.com wrote:
I did expect something like this coming ;)
You shouldn't admit that, you will get accused of trolling...
What's up with you calling me troll when it's evident that you are the one trolling, as I clearly wrote to you that my message isn't addressed to you, but to member who actually provides solutions here instead smalltalk, as I noticed in my short time here?
Sorry, it wasn't meant to actually accuse you. But you did say you posted expecting a certain effect :)
As for addressing the message, this is an open discussion forum.
As a regular user, occasional developer when time allows, and mailing list answerer I also have the right to express my opinions of suggested changes as much as you have the right to suggest them.
Because I don't see the importance of your suggestion doesn't mean others are of the same opinion, but we can all express it here.
Cheers Lex
I agree that having line numbers be less prominent is generally a good thing. In the case of the editors/IDEs that I use regularly (including SciTE), I can easily change the font of the line numbers separately.
In the case of Geany, I think that those who either can't or don't want to recompile their editor (for example with Colomban's patch), the simplest and best solution is to just learn to deal with it. I mean, even though I like less prominent line numbers, the existing ones are not *that* bad, and you can get used to it. And you can try little things to make them less prominent, like adjusting all the text to have greater spacing between lines. (I don't remember if you can set the line spacing separately or if you have to pick a font with more built-in space.) Yes, the trade-off is you can fit fewer lines of code in the same screen space.
If it's an easy change to make in the official Geany distribution, I think it would be nice to be able to adjust the line numbers separately. Geany already has an enormous number of settings; one more won't hurt, in my opinion. ;) But if it's too much of a bother, or if it's going to be the setting that breaks the camel's back, then I would say leave it alone.
If we're voting (using Python-dev convention, which I'm sure is borrowed from somewhere else), I'm +0 on adding this setting to Geany.
John
On 12-02-26 08:35 AM, John Yeung wrote:
I agree that having line numbers be less prominent is generally a good thing. In the case of the editors/IDEs that I use regularly (including SciTE), I can easily change the font of the line numbers separately.
In the case of Geany, I think that those who either can't or don't want to recompile their editor (for example with Colomban's patch), the simplest and best solution is to just learn to deal with it. I
You could set the line number font colour to be less prominent, for example dark grey on medium grey or something (ie. lower contrast).
mean, even though I like less prominent line numbers, the existing ones are not *that* bad, and you can get used to it. And you can try little things to make them less prominent, like adjusting all the text to have greater spacing between lines. (I don't remember if you can set the line spacing separately or if you have to pick a font with more built-in space.) Yes, the trade-off is you can fit fewer lines of code in the same screen space.
If it's an easy change to make in the official Geany distribution, I think it would be nice to be able to adjust the line numbers separately. Geany already has an enormous number of settings; one more won't hurt, in my opinion. ;) But if it's too much of a bother, or if it's going to be the setting that breaks the camel's back, then I would say leave it alone.
IMO, font specifications belong in the colour scheme files for each available style. This way not only could you set the line numbers font, but every other font (braces, comments, function names, etc.).
For example:
[named_styles] margin_line_number=0x000000;0xd0d0d0;false;false;Monospace 8
Cheers, Matthew Brush
[...]
IMO, font specifications belong in the colour scheme files for each available style. This way not only could you set the line numbers font, but every other font (braces, comments, function names, etc.).
No, fonts should definitely be under UI control where they are now. Having to change every filetype file just to make the text larger is a bad thing (tm).
Cheers Lex
For example:
[named_styles] margin_line_number=0x000000;0xd0d0d0;false;false;Monospace 8
Cheers, Matthew Brush
Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 12-02-26 12:59 PM, Lex Trotman wrote:
[...]
IMO, font specifications belong in the colour scheme files for each available style. This way not only could you set the line numbers font, but every other font (braces, comments, function names, etc.).
No, fonts should definitely be under UI control where they are now. Having to change every filetype file just to make the text larger is a bad thing (tm).
No, with colorschemes, you just change one file and it applies to every filetype. It makes no sense to have some parts of the (font) styling like colours and bold and italics specified in the color schemes while other parts like the font face and size to be specified through the UI.
The *best* thing would be to have the color schemes be editable through the GUI (like TextMate, for example), but this is substantially more work.
If you could set the font face and size through the colour scheme, you could leave the GUI setting as a global/default that takes effect if not specified elsewhere (ie. in the color schemes).
Cheers, Matthew Brush
[...]
No, fonts should definitely be under UI control where they are now. Having to change every filetype file just to make the text larger is a bad thing (tm).
No, with colorschemes, you just change one file and it applies to every filetype. It makes no sense to have some parts of the (font) styling like colours and bold and italics specified in the color schemes while other parts like the font face and size to be specified through the UI.
It only applies if the style maker used common styles, maybe the point of the style was to change them all different.
The *best* thing would be to have the color schemes be editable through the GUI (like TextMate, for example), but this is substantially more work.
Somebodys got to do it, plugins are welcome :)
If you could set the font face and size through the colour scheme, you could leave the GUI setting as a global/default that takes effect if not specified elsewhere (ie. in the color schemes).
No, GUIs should always win, or should be set insensitive.
Your suggestion on IRC of allowing schemes to set font size deltas (not absolute values) is a good one, for documentation markups you could make headings one point larger or similar.
Cheers Lex
On 12-02-26 02:35 PM, Lex Trotman wrote:
[...]
If you could set the font face and size through the colour scheme, you could leave the GUI setting as a global/default that takes effect if not specified elsewhere (ie. in the color schemes).
No, GUIs should always win, or should be set insensitive.
Your suggestion on IRC of allowing schemes to set font size deltas (not absolute values) is a good one, for documentation markups you could make headings one point larger or similar.
Yeah after our discussion on IRC, I think either using "smaller" and "bigger" in the color schemes or even just a UI setting next to Editor font for "Line Number Font" is a better idea. I'm not even sure what would happen if you set in the colour scheme a mix of fixed and proportional fonts and stuff like this. Scintilla might not like that and I know my eyes wouldn't :)
Cheers, Matthew Brush
On 27 February 2012 09:41, Matthew Brush mbrush@codebrainz.ca wrote:
On 12-02-26 02:35 PM, Lex Trotman wrote:
[...]
If you could set the font face and size through the colour scheme, you could leave the GUI setting as a global/default that takes effect if not specified elsewhere (ie. in the color schemes).
No, GUIs should always win, or should be set insensitive.
Your suggestion on IRC of allowing schemes to set font size deltas (not absolute values) is a good one, for documentation markups you could make headings one point larger or similar.
Yeah after our discussion on IRC, I think either using "smaller" and "bigger" in the color schemes or even just a UI setting next to Editor font for "Line Number Font" is a better idea. I'm not even sure what would happen if you set in the colour scheme a mix of fixed and proportional fonts and stuff like this. Scintilla might not like that and I know my eyes wouldn't :)
Scintilla actually handles mixed fonts and sizes, and Scite allows you to set them, but (at least in the standard properties) none use it. I think that says something. Note that Scite does not have a GUI font setting.
Cheers Lex
Cheers, Matthew Brush _______________________________________________ Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Sun, Feb 26, 2012 at 6:31 PM, Lex Trotman elextr@gmail.com wrote:
Scintilla actually handles mixed fonts and sizes, and Scite allows you to set them, but (at least in the standard properties) none use it. I think that says something. Note that Scite does not have a GUI font setting.
I don't know what you mean by "at least in the standard properties, none use it". In the global properties file distributed with SciTE, there are
font.base=font:Verdana,size:10 font.small=font:Verdana,size:8 font.comment=font:Comic Sans MS,size:9 font.code.comment.box=$(font.comment) font.code.comment.line=$(font.comment) font.code.comment.doc=$(font.comment) font.code.comment.nested=$(font.comment) font.text=font:Times New Roman,size:11 font.text.comment=font:Verdana,size:9 font.embedded.base=font:Verdana,size:9 font.embedded.comment=font:Comic Sans MS,size:8 font.monospace=font:Courier New,size:10 font.vbs=font:Lucida Sans Unicode,size:10
That's eight different fonts (across five different typefaces) for Windows. Even in GTK, it's still six fonts (five typefaces). And that's not counting bold, italics, and underline, which can be specified independently for each of the fonts.
I completely agree with you that using too many fonts is generally not a good idea. SciTE does not support this assessment, however. In the main editing window alone, it is commonplace to have at least three different fonts (not counting bold and italic): one each for comments, strings, and "regular" code. Open some C++ code in a standard installation of SciTE and you will see what I mean.
John
[...]
Even in GTK, it's still six fonts (five typefaces). And
that's not counting bold, italics, and underline, which can be specified independently for each of the fonts.
Yes, they *can* but all GTK fonts except font.small and font.text are the same size and the same family, the only other difference being sans or serif.
And font.small and font.text appear [1] to be only used in Embedded.
So I was just making the point in reply to Matthew's suggestion of putting font on all settings that it can be done, but even when it is available it is little used and I doubt it is worth the effort to implement. [2]
Cheers Lex
[1] limited check only, I am after all more interested in Geany than Scite :) [2] I don't use windows fonts, maybe your milage differs with them
On Mon, Feb 27, 2012 at 12:37 AM, Lex Trotman elextr@gmail.com wrote:
Even in GTK, it's still six fonts (five typefaces). And
that's not counting bold, italics, and underline, which can be specified independently for each of the fonts.
Yes, they *can* but all GTK fonts except font.small and font.text are the same size and the same family, the only other difference being sans or serif.
There is a big difference between sans and serif. They are very definitely not the same font. Even if you take out font.small and font.text, GTK still uses four fonts in the out-of-the-box configuration of SciTE. And then there are bold and italic as well, which typographically speaking, are yet more fonts.
So I was just making the point in reply to Matthew's suggestion of putting font on all settings that it can be done, but even when it is available it is little used and I doubt it is worth the effort to implement.
I fully understand what your point was. I am saying that all these font settings in SciTE are *not* "little used". If you open C++ code and Python code (perhaps the most widely used languages by SciTE users, including its creator) in a clean release of SciTE, you will see there is a wild profusion of styles, sizes, and colors. It's an utter mess, and it is not at all an example of "but all those settings are not used". Because they *are* used. They are used way the hell too much, in fact.
[1] limited check only, I am after all more interested in Geany than Scite :)
Yet you seem to persist in arguing with me about SciTE, which is what I use for virtually all my coding.
John
John Yeung wrote:
I don't know what you mean by "at least in the standard properties, none use it". In the global properties file distributed with SciTE, there are [...] font.comment=font:Comic Sans MS,size:9 [...]
And that's The Real WTF! (sorry, I couldn't resist :) and I seem to recall Notepad++ had this awful default too)
You could set the line number font colour to be less prominent, for example dark grey on medium grey or something (ie. lower contrast).
This is precisely my strategy in SciTE. I didn't know if it was easy (or possible) to do in Geany.
John Y.
On 27 February 2012 08:04, John Yeung gallium.arsenide@gmail.com wrote:
You could set the line number font colour to be less prominent, for example dark grey on medium grey or something (ie. lower contrast).
This is precisely my strategy in SciTE. I didn't know if it was easy (or possible) to do in Geany.
Geany has UI control of the main window font, the sidebar font and the message window font.
Cheers Lex
John Y. _______________________________________________ Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On Sun, Feb 26, 2012 at 4:25 PM, Lex Trotman elextr@gmail.com wrote:
On 27 February 2012 08:04, John Yeung gallium.arsenide@gmail.com wrote:
You could set the line number font colour to be less prominent, for example dark grey on medium grey or something (ie. lower contrast).
This is precisely my strategy in SciTE. I didn't know if it was easy (or possible) to do in Geany.
Geany has UI control of the main window font, the sidebar font and the message window font.
What does this mean? Are you saying it's easy to do in Geany or impossible? I had thought that the only reason Matthew mentioned it was that it's easy. But that's not the impression I get from your response.
John
On 27 February 2012 10:57, John Yeung gallium.arsenide@gmail.com wrote:
On Sun, Feb 26, 2012 at 4:25 PM, Lex Trotman elextr@gmail.com wrote:
On 27 February 2012 08:04, John Yeung gallium.arsenide@gmail.com wrote:
You could set the line number font colour to be less prominent, for example dark grey on medium grey or something (ie. lower contrast).
This is precisely my strategy in SciTE. I didn't know if it was easy (or possible) to do in Geany.
Geany has UI control of the main window font, the sidebar font and the message window font.
The font face and size is GUI controlled for these items. The other properties are gtkrc controlled IIUC.
Cheers Lex
What does this mean? Are you saying it's easy to do in Geany or impossible? I had thought that the only reason Matthew mentioned it was that it's easy. But that's not the impression I get from your response.
John _______________________________________________ Geany mailing list Geany@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany
On 12-02-26 03:57 PM, John Yeung wrote:
On Sun, Feb 26, 2012 at 4:25 PM, Lex Trotmanelextr@gmail.com wrote:
On 27 February 2012 08:04, John Yeunggallium.arsenide@gmail.com wrote:
You could set the line number font colour to be less prominent, for example dark grey on medium grey or something (ie. lower contrast).
This is precisely my strategy in SciTE. I didn't know if it was easy (or possible) to do in Geany.
Geany has UI control of the main window font, the sidebar font and the message window font.
What does this mean? Are you saying it's easy to do in Geany or impossible? I had thought that the only reason Matthew mentioned it was that it's easy. But that's not the impression I get from your response.
It's easy to change the foreground/background color of the line margin. See the `filetypes.common` file. In that file it's called `margin_linenumber=FGCOLOR;BGCOLOR` or in a colour scheme file it's called `margin_line_number=FGCOLOR;BGCOLOR`.
Cheers, Matthew Brush
On Sun, Feb 26, 2012 at 10:30 PM, Matthew Brush mbrush@codebrainz.ca wrote:
You could set the line number font colour to be less prominent, for example dark grey on medium grey or something (ie. lower contrast).
It's easy to change the foreground/background color of the line margin. See the `filetypes.common` file. In that file it's called `margin_linenumber=FGCOLOR;BGCOLOR` or in a colour scheme file it's called `margin_line_number=FGCOLOR;BGCOLOR`.
Thank you, Matthew. Yes, this is easy enough that it's a superior option than "just dealing with it" if you are not happy with the default line numbers.
John