Re: [Github-comments] [geany/geany] FEATURE: Add language field to templates info (#1759)

2018-02-05 Thread pmralbuquerque
Closed #1759. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1759#event-1457551085

Re: [Github-comments] [geany/geany] FEATURE: Add language field to templates info (#1759)

2018-02-05 Thread pmralbuquerque
Great, thank you for your time! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1759#issuecomment-363034911

Re: [Github-comments] [geany/geany] FEATURE: Add language field to templates info (#1759)

2018-02-05 Thread elextr
Essentially there are an unlimited number of fields that could be substituted into templates. If you want to contribute good code to add such a field its likely to be accepted (at least until the dialog is full). But in the meantime you can edit the template files to set the language you want,

Re: [Github-comments] [geany/geany] FEATURE: Add language field to templates info (#1759)

2018-02-05 Thread pmralbuquerque
Maybe I didn't explain correctly. I mean Menu Edit->Preferences->Templates There is no field for language, and yet some of the templates create by Menu File->New (with template) do use 'en' as language, namely html, html5, php... -- You are receiving this because you are subscribed to this threa

Re: [Github-comments] [geany/geany] FEATURE: Add language field to templates info (#1759)

2018-02-04 Thread elextr
The template info does not assume any language, you can write anything you want there. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1759#issuecomment-363001046

[Github-comments] [geany/geany] FEATURE: Add language field to templates info (#1759)

2018-02-04 Thread pmralbuquerque
Hi I think it could be useful to have a language field on the general info for templates, instead of assuming en globally. I know I prefer pt wherever it's applicable. HTML, for instance (). Regards, Pedro -- You are receiving this because you are subscribed to this thread. Reply to this email