On Wed, 12 Nov 2008 23:24:02 +0100, Frank Lanitz frank@frank.uvena.de wrote:
On Wed, 12 Nov 2008 20:18:57 +0100 Enrico Tröger enrico.troeger@uvena.de wrote:
On Wed, 12 Nov 2008 13:29:27 +0000, Nick Treleaven nick.treleaven@btinternet.com wrote:
On Tue, 11 Nov 2008 19:50:41 +0000 eht16@users.sourceforge.net wrote:
Revision: 3212 http://geany.svn.sourceforge.net/geany/?rev=3212&view=rev Author: eht16 Date: 2008-11-11 19:50:40 +0000 (Tue, 11 Nov 2008)
Log Message:
Add a file template for LaTeX (patch by Herbert Voss, thanks).
TEMPLATES_CREATE_FILE(fname, templates_filetype_html); break; case GEANY_FILETYPES_RUBY: TEMPLATES_CREATE_FILE(fname, templates_filetype_ruby); break; case GEANY_FILETYPES_PYTHON: TEMPLATES_CREATE_FILE(fname, templates_filetype_python); break;
case GEANY_FILETYPES_LATEX:TEMPLATES_CREATE_FILE(fname, templates_filetype_latex); break; default: break; } TEMPLATES_READ_FILE(fname, &ft_templates[ft_id]);
BTW, I think we could remove filetype templates and just use custom file templates instead - they might confuse users into thinking only one template per filetype was supported.
When doing this, I think we shouldn't hard code the creation of default template files, but install them as data files. The advantage would be the user can delete them after installation if they want.
Yep, sounds good. The only not so nice effect we will get is that the config dir of existing users will be cluttered a bit with old template files which are not used anymore.I'm not sure whether we should just document this or taking any action to clean it up. But generally I don't like apps which automatically delete anything in user's configuration directories.
I think this could be combined with the idea moving the config files to .config architecture. by keeping the old .geany as some kind of backup dir.
No, IMO these are complete separate tasks and should not be mixed. Moving the config dir to $XDG_CONFIG_HOME is unrelated and will happen as an opaque action. We won't move only parts or anything.
Regards, Enrico