Hi,
I'd like to increase the vertical spacing between lines.
I found this issue https://github.com/geany/geany/issues/1592, and so went to "Tools --> Configuration Files --> filetypes.common", but changes I make and save there don't seem to have any effect. So, a few questions:
1. What is the syntax for this config file? Does a leading space indicate a comment? Do I need the pound sign or remove it?
2. What are the units for the line spacing (line_height). Pixels?
3. How do I get my changes here to take affect?
Thanks, -- John
On Sat, 30 May 2020 at 08:15, John Gabriele jgabriele@fastmail.fm wrote:
Hi,
I'd like to increase the vertical spacing between lines.
I found this issue https://github.com/geany/geany/issues/1592, and so went to "Tools --> Configuration Files --> filetypes.common", but changes I make and save there don't seem to have any effect. So, a few questions:
- What is the syntax for this config file? Does a leading space indicate a comment? Do I need the pound sign or remove it?
# == comment
- What are the units for the line spacing (line_height). Pixels?
yes
- How do I get my changes here to take affect?
Save the filetypes.common opened from the menu above WFM.
A quick search for `line_height` finds several issues like this, https://github.com/geany/geany/issues/2287#issuecomment-610713286 where the exact content is shown. You probably are missing the [styling] section.
Cheers Lex
Thanks, -- John _______________________________________________ Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
On Fri, May 29, 2020, at 7:00 PM, Lex Trotman wrote:
On Sat, 30 May 2020 at 08:15, John Gabriele jgabriele@fastmail.fm wrote:
Hi,
I'd like to increase the vertical spacing between lines.
I found this issue https://github.com/geany/geany/issues/1592, and so went to "Tools --> Configuration Files --> filetypes.common", but changes I make and save there don't seem to have any effect. So, a few questions:
- What is the syntax for this config file? Does a leading space indicate a comment? Do I need the pound sign or remove it?
# == comment
Hi Lex. Thanks.
The file is filled with descriptive lines of text, but they are not commented. Is a leading space also considered a comment?
- What are the units for the line spacing (line_height). Pixels?
yes
- How do I get my changes here to take affect?
Save the filetypes.common opened from the menu above WFM.
What does WFM mean?
I've tried changing the settings, uncommenting the `[styling]` marker, changing the font, and restarting Geany, but nothing gets the line spacing to change.
This is on Debian Testing, with Geany 1.36.
A quick search for `line_height` finds several issues like this, https://github.com/geany/geany/issues/2287#issuecomment-610713286 where the exact content is shown. You probably are missing the [styling] section.
Thanks for the link, and the help, but that doesn't appear to fix it. Any ideas what else could be the issue?
Thanks, -- John
On Sat, 30 May 2020 at 09:30, John Gabriele jgabriele@fastmail.fm wrote:
On Fri, May 29, 2020, at 7:00 PM, Lex Trotman wrote:
On Sat, 30 May 2020 at 08:15, John Gabriele jgabriele@fastmail.fm wrote:
Hi,
I'd like to increase the vertical spacing between lines.
I found this issue https://github.com/geany/geany/issues/1592, and so went to "Tools --> Configuration Files --> filetypes.common", but changes I make and save there don't seem to have any effect. So, a few questions:
- What is the syntax for this config file? Does a leading space indicate a comment? Do I need the pound sign or remove it?
# == comment
Hi Lex. Thanks.
The file is filled with descriptive lines of text, but they are not commented. Is a leading space also considered a comment?
- What are the units for the line spacing (line_height). Pixels?
yes
- How do I get my changes here to take affect?
Save the filetypes.common opened from the menu above WFM.
What does WFM mean?
Works for me.
I've tried changing the settings, uncommenting the `[styling]` marker, changing the font, and restarting Geany, but nothing gets the line spacing to change.
This is on Debian Testing, with Geany 1.36.
A quick search for `line_height` finds several issues like this, https://github.com/geany/geany/issues/2287#issuecomment-610713286 where the exact content is shown. You probably are missing the [styling] section.
Thanks for the link, and the help, but that doesn't appear to fix it. Any ideas what else could be the issue?
No, without further information. Maybe attach your filetypes.common, or better still put it on a gist (https://gist.github.com/) and mail a link so you don't spam everybody with your file.
Cheers Lex
Thanks, -- John _______________________________________________ Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
Thanks, Lex. Sorry for the delay. Here's the gist: https://gist.github.com/uvtc/ae80c71aa46a55660ad17c485a04b6c5 It's in ~/.config/geany/filedefs.
This is Geany 1.36,
(built on or after 2019-11-20) Using GTK+ v3.24.20 and GLib v2.64.2 runtime libraries
Thanks. -- John
On Fri, May 29, 2020, at 8:14 PM, Lex Trotman wrote:
On Sat, 30 May 2020 at 09:30, John Gabriele jgabriele@fastmail.fm wrote:
On Fri, May 29, 2020, at 7:00 PM, Lex Trotman wrote:
On Sat, 30 May 2020 at 08:15, John Gabriele jgabriele@fastmail.fm wrote:
Hi,
I'd like to increase the vertical spacing between lines.
I found this issue https://github.com/geany/geany/issues/1592, and so went to "Tools --> Configuration Files --> filetypes.common", but changes I make and save there don't seem to have any effect. So, a few questions:
- What is the syntax for this config file? Does a leading space indicate a comment? Do I need the pound sign or remove it?
# == comment
Hi Lex. Thanks.
The file is filled with descriptive lines of text, but they are not commented. Is a leading space also considered a comment?
- What are the units for the line spacing (line_height). Pixels?
yes
- How do I get my changes here to take affect?
Save the filetypes.common opened from the menu above WFM.
What does WFM mean?
Works for me.
I've tried changing the settings, uncommenting the `[styling]` marker, changing the font, and restarting Geany, but nothing gets the line spacing to change.
This is on Debian Testing, with Geany 1.36.
A quick search for `line_height` finds several issues like this, https://github.com/geany/geany/issues/2287#issuecomment-610713286 where the exact content is shown. You probably are missing the [styling] section.
Thanks for the link, and the help, but that doesn't appear to fix it. Any ideas what else could be the issue?
No, without further information. Maybe attach your filetypes.common, or better still put it on a gist (https://gist.github.com/) and mail a link so you don't spam everybody with your file.
Cheers Lex
Thanks, -- John _______________________________________________ Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
On Mon, 1 Jun 2020 at 09:43, John Gabriele jgabriele@fastmail.fm wrote:
Thanks, Lex. Sorry for the delay. Here's the gist: https://gist.github.com/uvtc/ae80c71aa46a55660ad17c485a04b6c5 It's in ~/.config/geany/filedefs.
As I noted above, lines starting with # are comments, but in your filetypes.common all the lines that are actually comments are without #, so no wonder it confused the keyfile parser and doesn't work.
Cheers Lex
This is Geany 1.36,
(built on or after 2019-11-20) Using GTK+ v3.24.20 and GLib v2.64.2 runtime librariesThanks. -- John
On Fri, May 29, 2020, at 8:14 PM, Lex Trotman wrote:
On Sat, 30 May 2020 at 09:30, John Gabriele jgabriele@fastmail.fm wrote:
On Fri, May 29, 2020, at 7:00 PM, Lex Trotman wrote:
On Sat, 30 May 2020 at 08:15, John Gabriele jgabriele@fastmail.fm wrote:
Hi,
I'd like to increase the vertical spacing between lines.
I found this issue https://github.com/geany/geany/issues/1592, and so went to "Tools --> Configuration Files --> filetypes.common", but changes I make and save there don't seem to have any effect. So, a few questions:
- What is the syntax for this config file? Does a leading space indicate a comment? Do I need the pound sign or remove it?
# == comment
Hi Lex. Thanks.
The file is filled with descriptive lines of text, but they are not commented. Is a leading space also considered a comment?
- What are the units for the line spacing (line_height). Pixels?
yes
- How do I get my changes here to take affect?
Save the filetypes.common opened from the menu above WFM.
What does WFM mean?
Works for me.
I've tried changing the settings, uncommenting the `[styling]` marker, changing the font, and restarting Geany, but nothing gets the line spacing to change.
This is on Debian Testing, with Geany 1.36.
A quick search for `line_height` finds several issues like this, https://github.com/geany/geany/issues/2287#issuecomment-610713286 where the exact content is shown. You probably are missing the [styling] section.
Thanks for the link, and the help, but that doesn't appear to fix it. Any ideas what else could be the issue?
No, without further information. Maybe attach your filetypes.common, or better still put it on a gist (https://gist.github.com/) and mail a link so you don't spam everybody with your file.
Cheers Lex
Thanks, -- John _______________________________________________ Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
On Sun, May 31, 2020, at 9:44 PM, Lex Trotman wrote:
On Mon, 1 Jun 2020 at 09:43, John Gabriele jgabriele@fastmail.fm wrote:
Thanks, Lex. Sorry for the delay. Here's the gist: https://gist.github.com/uvtc/ae80c71aa46a55660ad17c485a04b6c5 It's in ~/.config/geany/filedefs.
As I noted above, lines starting with # are comments, but in your filetypes.common all the lines that are actually comments are without #, so no wonder it confused the keyfile parser and doesn't work.
Wow. That's odd. I don't know why that file contained so many uncommented lines of text. I'm pretty certain it came stock that way with the Debian package.
I commented all the ... commentary lines, and as soon as I hit save the line_height change took effect (I did not need to reload config or anything).
-- John
On Sun, May 31, 2020, at 9:58 PM, John Gabriele wrote:
On Sun, May 31, 2020, at 9:44 PM, Lex Trotman wrote:
On Mon, 1 Jun 2020 at 09:43, John Gabriele jgabriele@fastmail.fm wrote:
Thanks, Lex. Sorry for the delay. Here's the gist: https://gist.github.com/uvtc/ae80c71aa46a55660ad17c485a04b6c5 It's in ~/.config/geany/filedefs.
As I noted above, lines starting with # are comments, but in your filetypes.common all the lines that are actually comments are without #, so no wonder it confused the keyfile parser and doesn't work.
Wow. That's odd. I don't know why that file contained so many uncommented lines of text. I'm pretty certain it came stock that way with the Debian package.
Noticed the same problem (uncomment commentary lines) in
filetype_extensions.conf geany.css snippets.conf ...
Oh boy, this looks like a pervasive issue.
If I go to "Tools --> Configuration Files --> Filetype Configuration", and choose anything in there, the file that comes up seems to have this same problem: lots of lines that are just prose/commentary, but they're not commented. (Not sure what this means, but in the window title bar they say paths like ~/.config/geany/filedefs/filetypes.whatev, but in that directory I only see filetypes.common and filetypes.README.
-- John
On Mon, 1 Jun 2020 at 12:17, John Gabriele jgabriele@fastmail.fm wrote:
On Sun, May 31, 2020, at 9:58 PM, John Gabriele wrote:
On Sun, May 31, 2020, at 9:44 PM, Lex Trotman wrote:
On Mon, 1 Jun 2020 at 09:43, John Gabriele jgabriele@fastmail.fm wrote:
Thanks, Lex. Sorry for the delay. Here's the gist: https://gist.github.com/uvtc/ae80c71aa46a55660ad17c485a04b6c5 It's in ~/.config/geany/filedefs.
As I noted above, lines starting with # are comments, but in your filetypes.common all the lines that are actually comments are without #, so no wonder it confused the keyfile parser and doesn't work.
Wow. That's odd. I don't know why that file contained so many uncommented lines of text. I'm pretty certain it came stock that way with the Debian package.
Noticed the same problem (uncomment commentary lines) in
filetype_extensions.conf geany.css snippets.conf ...
Oh boy, this looks like a pervasive issue.
If I go to "Tools --> Configuration Files --> Filetype Configuration", and choose anything in there, the file that comes up seems to have this same problem: lots of lines that are just prose/commentary, but they're not commented. (Not sure what this means, but in the window title bar they say paths like ~/.config/geany/filedefs/filetypes.whatev, but in that directory I only see filetypes.common and filetypes.README.
Tools->Configuration Files-> etc toggles comments when it opens the file for the first time, which should add #~ to every line. Have you changed the toggle comment setting for .conf filetypes?
The reason this is done is because the edited file is saved in the users config, and overrides the system file. If all settings were set in the user file any fixes in a new version of Geany would be overridden by the old user settings. So they are all commented out (using toggle comment) and the user can just toggle comment for the section titles and settings that they need to change, leaving the rest to be the system values.
Cheers Lex
-- John _______________________________________________ Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users
Noticed the same problem (uncomment commentary lines) in
filetype_extensions.conf geany.css snippets.conf ...
Oh boy, this looks like a pervasive issue.
If I go to "Tools --> Configuration Files --> Filetype Configuration", and choose anything in there, the file that comes up seems to have this same problem: lots of lines that are just prose/commentary, but they're not commented. (Not sure what this means, but in the window title bar they say paths like ~/.config/geany/filedefs/filetypes.whatev, but in that directory I only see filetypes.common and filetypes.README.
Tools->Configuration Files-> etc toggles comments when it opens the file for the first time, which should add #~ to every line. Have you changed the toggle comment setting for .conf filetypes?
In "Preferences --> Editor side tab --> Features tab", the "Comment toggle marker" is blank / empty. Maybe at some point I removed the tilde there because I didn't like how it looked... (? can't recall. Ah, I think at one point I put a single space in there).
I wouldn't know how to change the toggle comment setting for a particular filetype --- I only know the prefs setting I just described above.
Ok. Thanks, I put the "~" back into that "comment toggle marker" field.
The reason this is done is because the edited file is saved in the users config, and overrides the system file. If all settings were set in the user file any fixes in a new version of Geany would be overridden by the old user settings. So they are all commented out (using toggle comment) and the user can just toggle comment for the section titles and settings that they need to change, leaving the rest to be the system values.
Gotcha. Thanks for the explanation.
-- John
On Mon, 1 Jun 2020 at 13:02, John Gabriele jgabriele@fastmail.fm wrote:
Noticed the same problem (uncomment commentary lines) in
filetype_extensions.conf geany.css snippets.conf ...
Oh boy, this looks like a pervasive issue.
If I go to "Tools --> Configuration Files --> Filetype Configuration", and choose anything in there, the file that comes up seems to have this same problem: lots of lines that are just prose/commentary, but they're not commented. (Not sure what this means, but in the window title bar they say paths like ~/.config/geany/filedefs/filetypes.whatev, but in that directory I only see filetypes.common and filetypes.README.
Tools->Configuration Files-> etc toggles comments when it opens the file for the first time, which should add #~ to every line. Have you changed the toggle comment setting for .conf filetypes?
In "Preferences --> Editor side tab --> Features tab", the "Comment toggle marker" is blank / empty. Maybe at some point I removed the tilde there because I didn't like how it looked... (? can't recall. Ah, I think at one point I put a single space in there).
I wouldn't know how to change the toggle comment setting for a particular filetype --- I only know the prefs setting I just described above.
Ok, the comment marker is a global setting, not per filetype, only the actual comment is per filetype.
Ok. Thanks, I put the "~" back into that "comment toggle marker" field.
Yeah, better, it could be anything that is unlikely to occur naturally if you don't like tilde (but space is not only likely, but as you have seen, inevitable).
Toggle comment lines have to be marked so when the user selects a range to toggle comments Geany knows what to do with lines already commented, clearly they should not be simply uncommented (well you have seen what happens then) so the user would have to select around lines that are actual comments, making toggle comments pretty useless for its intended purpose of commenting slabs of code.
So comments made by toggle comments are specifically marked, and adding a tilde was chosen so as to be unusual and unlikely to occur normally (many other characters having been taken by stuff like doxygen comments).
Cheers Lex
The reason this is done is because the edited file is saved in the users config, and overrides the system file. If all settings were set in the user file any fixes in a new version of Geany would be overridden by the old user settings. So they are all commented out (using toggle comment) and the user can just toggle comment for the section titles and settings that they need to change, leaving the rest to be the system values.
Gotcha. Thanks for the explanation.
-- John
Users mailing list Users@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/users