Hi, I've removed the 'Hard tab width' GUI pref for the 'Tabs and Spaces' indent type. (This does not affect the other indent types). This is because IME it is always 8, and removing it makes the dialogs clearer.
In case anyone has changed that option, the setting is still read from the configuration file(s).
If there is a good reason to keep it configurable in the dialog, please let me know.
Regards, Nick
On Wed, 28 Apr 2010 14:14:21 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Hi Nick.
I've removed the 'Hard tab width' GUI pref for the 'Tabs and Spaces' indent type.
I'm running a "german" geany. Not sure if you mean the tab width setting inside the editor settings (tab "indentation")?
(This does not affect the other indent types). This is because IME it is always 8, and removing it makes the dialogs clearer.
If so, you are right.
There are many people out there using tabs with a width of 4 to get the C indentation. This behaviour can still be setup with the remaining settings.
In case anyone has changed that option, the setting is still read from the configuration file(s).
Why that? If such a user install a new geany, he will get another behaviour of the indentation code. So why not print a warning while migrating an old configuration file and than remove it?
What I'm really missing are the emacs modelines. My colleague uses tabs (with an width of 4) to indent his code. After adding the corresponding modeline, emacs recognizes his style and all went fine. Now I'm using Geany and I have some trouble with mixing his files with mine. So modelines would definitely a good thing.
On Thu, 29 Apr 2010 07:21:12 +0200 Joerg Desch jd.vvd@web.de wrote:
On Wed, 28 Apr 2010 14:14:21 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Hi Nick.
I've removed the 'Hard tab width' GUI pref for the 'Tabs and Spaces' indent type.
I'm running a "german" geany. Not sure if you mean the tab width setting inside the editor settings (tab "indentation")?
This is why I removed the GUI setting - it is so confusing for people who don't know the tab compression of spaces ('Tabs AND spaces') indent mode.
This doesn't affect Tabs only or Spaces only indentation.
In case anyone has changed that option, the setting is still read from the configuration file(s).
Why that? If such a user install a new geany, he will get another behaviour of the indentation code. So why not print a warning while migrating an old configuration file and than remove it?
You can't migrate a non-standard *hard* tab width setting.
What I'm really missing are the emacs modelines. My colleague uses tabs (with an width of 4) to indent his code. After adding the corresponding modeline, emacs recognizes his style and all went fine. Now I'm using Geany and I have some trouble with mixing his files with mine. So modelines would definitely a good thing.
This is another subject. Try posting in a new thread.
Regards, Nick
On Thu, 29 Apr 2010 15:55:32 +0100 Nick Treleaven nick.treleaven@btinternet.com wrote:
Why that? If such a user install a new geany, he will get another behaviour of the indentation code. So why not print a warning while migrating an old configuration file and than remove it?
You can't migrate a non-standard *hard* tab width setting.
I think I don't understand what are planing to do. Do you want to silently use the old "non-standard *hard* tab width setting"? IMO this isn't a good idea. So, if you ignore this old seting, it shouldn't be ignored silently.
What I'm really missing are the emacs modelines.
This is another subject. Try posting in a new thread.
I currently have no spare time. But as soon as I have the time, I plan to write a plugin or a LUA script to add modelines and timestamps (search for the sequence "Time-Stamp:" inside the first comment/lines and insert the date+time behind it). One point inside a huge TODO list. ;-)
On Fri, 30 Apr 2010 10:25:25 +0200 Joerg Desch jd.vvd@web.de wrote:
Why that? If such a user install a new geany, he will get another behaviour of the indentation code. So why not print a warning while migrating an old configuration file and than remove it?
You can't migrate a non-standard *hard* tab width setting.
I think I don't understand what are planing to do. Do you want to silently use the old "non-standard *hard* tab width setting"? IMO this isn't a good idea. So, if you ignore this old seting, it shouldn't be ignored silently.
OK, you're right - I'll add a warning. Thanks for the feedback ;-)
Regards, Nick