Re: [Geany-devel] Set Filetypes Menu - group names
Hi, As I have said before I don't care strongly about the current breakup, I don't really care neither, but... (read ahead) but several people seem to. After some thought I feel that this is likely to be that the breakup is subjective. But the only objective breakup I can think of is alphabetic, with submenus a-k, l-z or whatever arrangement gives nice menus. ...I'm not sure a too large refactoring of these menus is really a good thing for users that may be used to the current splitting, but I admit that the current splitting is quite arbitrary (though I don't know of an entry I better place somewhere else... but I don't know all the languages we have). Now as someone else said this raises questions of localisation, and here my ignorance of other languages started started to show. Having failed to find a good answer on Google I now throw the question to the worldwide Geany dev list: How do you normally handle computer language names in your locale? In locales with a Latin alphabet (ie ASCII is a subset, eg French, German) do you a) leave the name as is, b) if the name is a word (lisp, scheme, racket) do you translate it to the equivalent word c) are acronyms the acronym of the translation of the phrase they are based on Answer from me, a French guy: we don't translate such names. Scheme is still Scheme, Lisp still Lisp, Caml still Caml, XML is not LBX, etc. So there's no problem for french. And IIRC, we don't translate these names currently in Geany, but only something like %s source file. But I agree that even if it's OK for names, it may be not for alphabetical grouping, no idea. [...] Oh and where things are not translated, what do you do if the name/acronym forms a rude/derogatory word in your locale? I never seen such case, so I can't tell... but I guess we'd keep it and laugh at it :D Cheers, Colomban ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Git Switch (again)
Am 30.04.2011 11:52, schrieb Enrico Tröger: But we have git.geany.org. The mirror GIT repositories are synced from SVN and the sync is triggered by commit mails. So, we do have a kind of our own commit hook, from SVN as well as from GIT. I just don't know what I should do in the hook :). Assuming the current git mirror does git svn rebase upon the hook, you could extend the script to do the git push afterwards (according to Jiri's [1] command). You need an intermediate git mirror which does the svn rebase anyway, I don't think github can offer that, but it doesn't necessarily need to be publicly available. [1]: is it OK if I write your name that way? I don't know how to enter the characters on the keyboard. If not, I'm sorry. Best regards. ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GProject - missing Geany patches
On Sat, Apr 30, 2011 at 23:57, Colomban Wendling lists@herbesfolles.org wrote: Le 28/04/2011 22:58, Jiří Techet a écrit : On Thu, Apr 28, 2011 at 19:46, Colomban Wendling lists@herbesfolles.org wrote: Le 28/04/2011 01:49, Colomban Wendling a écrit : Le 10/04/2011 15:03, Jiří Techet a écrit : [...] 2edb068b81cb6d541d667efecd0ec4c346f0df51 Open the file in the msgwindow even if no linenumber is specified I'll review this one later (tomorrow if it goes right). I don't really like the patch and preferred to change msgwin_parse_grep_line() to something that directly parse file[:line[...]] so no need to do everything twice. I agree it's not very nice, on the other hand I think it's the smallest patch that achieves what I need. Modifying msgwin_parse_grep_line() isn't enough, you'd have to modify parse_file_line() and be _very_ careful because you could screw up parse_compiler_error_line() which uses this function too with different parameters. I wrote a different implementation, and I think it works OK. Actually I replaced parse_grep_line() by a more generic implementation of file[:line[...]] parsing. If it has any flaw, just let me know :) Looks good after both looking at the implementation and testing it briefly. Yeah true, even getting it to work properly is quiet a pain, right. Anyway, implemented in SVN now. I've tested it and my plugin works with mainline geany now - great! I'll need one more thing - to bump the plugin API version number. Even though the API hasn't changed, people shouldn't use my plugin with previous versions of geany (it wouldn't work because they couldn't specify the patterns). As the next step I'd like to get the plugin into the Geany Plugins project. Can I get commit access (or how does it work)? Apart from that the plugin is now missing some mandatory files like README's NEWS and so on - I'll fix that in the upcoming days. What else needs to be done? Cheers, Jiri ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GProject - missing Geany patches
Am 02.05.2011 00:03, schrieb Jiří Techet: I've tested it and my plugin works with mainline geany now - great! I'll need one more thing - to bump the plugin API version number. Even though the API hasn't changed, people shouldn't use my plugin with previous versions of geany (it wouldn't work because they couldn't specify the patterns). Doesn't that mean the API actually changed? :) Best regards. ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] GProject - missing Geany patches
On 2 May 2011 08:06, Thomas Martitz thomas.mart...@student.htw-berlin.de wrote: Am 02.05.2011 00:03, schrieb Jiří Techet: I've tested it and my plugin works with mainline geany now - great! I'll need one more thing - to bump the plugin API version number. Even though the API hasn't changed, people shouldn't use my plugin with previous versions of geany (it wouldn't work because they couldn't specify the patterns). Doesn't that mean the API actually changed? :) And did any additions/changes get added to the API docs? Cheers Lex Best regards. ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Git Switch (again)
On Sun, May 1, 2011 at 23:46, Thomas Martitz thomas.mart...@student.htw-berlin.de wrote: Am 30.04.2011 11:48, schrieb Matthew Brush: I think the more important part is, are the core developers going to accept pull/merge requests on github/gitorious, apply commits/patches from there, etc.? If it's only going to be another read-only git mirror, it's kind of pointless. I don't mean to say that it's a bad idea to have the official Geany source available on various projects sites to fork/hack on and stuff, just that it doesn't address the problem being discussed at all. I agree it's not as useful, but I disagree that it'd be pointless. We can still benefit from the social coding aspects of github, including but not limited to an overview over the forks, pull requests between forks. I would greatly love to see that, as I'm subscribed to a number forks by now :) Yes, I would also prefer if there was a proper and complete git switch (it would greatly save maintainer's work IMO) but I haven't seen much enthusiasm from the core developers for the move so it's better if people who use git have at least an up-to-date git mirror from which they can create their private branches. BTW: is there some possibility to have an svn mirror of a git repo. Perhaps if you have admin access to the bare svn repo? I guess you could git svn dcommit from the post-receive hook if you have access to the git repository. But I guess it works for simple commits only and not merges and so on. (To your question regarding writing my name - I write it that way myself too because I'm lazy to switch to Czech keyboard so I guess it's OK ;-) Jiri ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
