Re: [Geany-devel] SF.net SVN: geany:[5724] trunk
> I seem to remember it was possible to close the autocompletion list with > escape at some time which solved that for me sufficiently, but I remapped > escape ages ago. Now I tried it again it is not possible anymore, the > "cancel autocompletion" keybinding actually inserts the selected item. > Yes, "escape closes menu/dialog" is another GTK built in. But it doesn't really work for me, by the time I've noticed that the autocompletion has been displayed and started to re-program the muscles to press escape (way over the other side of the keyboard from return) I've already pressed return , !@#$%^&*() 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] SF.net SVN: geany:[5724] trunk
Am 17.04.2011 13:13, schrieb Lex Trotman: I can completely understand the problem, I have a similar MAJOR annoyance with Python, anything on the end of the line that is a prefix of a completion gets the first completion chosen when return is typed to end the line. This doesn't happen in C or C++ since rarely do lines end in a word, they mostly end in punctuation. But for other languages the choice of return to select the item from the completion list is inappropriate. I have been forced to turn autocompletion off for Python, but that means remembering it since there is only one preference, not a per language one. I seem to remember it was possible to close the autocompletion list with escape at some time which solved that for me sufficiently, but I remapped escape ages ago. Now I tried it again it is not possible anymore, the "cancel autocompletion" keybinding actually inserts the selected item. Best regards. ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Improving plugin API @since information?
On Thu, 14 Apr 2011 00:19:24 +0200, Colomban wrote: >Hi all, > >I'm thinking about adding an extra information to "since" tag of the >plugin API documentation. >It currently only gives the Geany version the symbol appeared on, but >generally the developer also need to know the plugin API version in >which it was introduced, e.g. in order to get the API requirement >right. > >So, I'm suggesting to add this information whenever we add a new plugin >API function (and why not update the current doc when we can), e.g.: > > @since 0.21 (API 206) > >or whatever format we prefer. I'd say why not. It doesn't hurt. I don't find it totally necessary as plugin developers always should depend on the latest available API version of the current development version of Geany if they use any new features. Still, it's only a bit more information and so why not. About the format: I'd say: * @since 0.21 (GEANY_API_VERSION 209) I used this for now in SVN r5727. But I'm totally open about this. Regards, Enrico -- Get my GPG key from http://www.uvena.de/pub.asc pgpRqY64Sv8AN.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] GeanyCFP
Hello one and all, First of all - appologies as I've not been in contact for a couple of months. Have moved house and the phone company/ISP royally fouled up, and had to change providers so no internet access for about 8 weeks :( Also a couple of family emergencies, and I've a major exam looming, so may be a little slow for the next month or so. Frank Lanitz suggested splitting geanycfp into separate plugins. I think this makes sense for several reasons: by splitting it into GeanyMacros, and GeanyNumberedBookmarks it makes it clearer what the plugins do, and it keeps it more in-keeping with the light-weight/only add what you use mentality of Geany and Geany-Plugins. I have therefore split it into 2 separate plugins. Enrico Tröeger raised problems with my use of a GTK function requiring versions above 2.8. I've edited my code now to make editing the accelerator key combination when you look at all macros only available if you're compiling with a version of GTK of at least 2.10 by using #if GTK_CHECK_VERSION(2,10,0). The code should again compile with any version above 2.8 (and will have the added feature if you use 2.10 or later (but the plugin is perfectly usable without this feature). As for forking a light-weight Geany, I would do one compiled to run using a mark 1 graphite stylus, and cellulose based VDU - pencil & paper Geany. William Fraser ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] {datetime} & {date} are updated only after config reload
U, I have just realised I have misunderstood Franks comment, since I was mostly thinking about file templates and he was talking about insertions, so I'll change my answer. I agree that substitution should happen when the template is put in the buffer not when Geany is started, for both types. The option of substitute when the file is written can only sensibly be applied to file templates, but the above handles all templates uniformly. Cheers Lex ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] {datetime} & {date} are updated only after config reload
On 17 April 2011 20:55, Liviu Andronic wrote:
> Hello
> I'm not sure I follow.
>
>
> On Sun, Apr 17, 2011 at 12:40 PM, Lex Trotman wrote:
>> On 17 April 2011 20:37, Liviu Andronic wrote:
>>> On Fri, Apr 15, 2011 at 6:35 PM, Frank Lanitz wrote:
What about moving this to request time? So not parsing at startup but
parsing it when requested by user to insert?
>>
> This means that when selecting c-menu > insert > changelog the
> {datetime} inserted will be the system current date and time. Correct?
> Inserting a second time, 2 min later, would insert a new date and time
> (again current with respect to the moment of insertion).
>
>
>>>
>>> Yes! This would definitely be much better. Of course, if easy enough
>>> to implement.
>>> Liviu
>>
>> Personally I'd prefer it to happen automatically the first time the
>> file is saved, the way the filename is inserted.
>>
> This would set the date and time to the time of the file first save.
> And then it would stay static. Correct? I'm not sure how useful this
> would be, at least not for me.
Please note my response to Randy, once the string {datetime} or {date}
is replaced it no longer exists in the file, so the date recorded is
always static, no matter when it is done. If you want a variable
date, thats a different piece of functionality to what we are talking
about here.
Cheers
Lex
>
> Regards
> Liviu
>> If its manual I'll forget to request it, guaranteed. :-(
>>
>> Cheers
>> Lex
>> ___
>> Geany-devel mailing list
>> Geany-devel@uvena.de
>> https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
>>
>
>
>
> --
> Do you know how to read?
> http://www.alienetworks.com/srtest.cfm
> http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
> Do you know how to write?
> http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail
> ___
> 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] SF.net SVN: geany:[5724] trunk
> Well, its hard to say, but maybe you are right. At least your points do > sound reasonable. ;) > > Cheers, > Frank I can completely understand the problem, I have a similar MAJOR annoyance with Python, anything on the end of the line that is a prefix of a completion gets the first completion chosen when return is typed to end the line. This doesn't happen in C or C++ since rarely do lines end in a word, they mostly end in punctuation. But for other languages the choice of return to select the item from the completion list is inappropriate. I have been forced to turn autocompletion off for Python, but that means remembering it since there is only one preference, not a per language one. The proper solution would be to stop return selecting the item from the menu, but unfortunately there does not seem to be any way of changing that since it is the default activate keycode defined somewhere deep in GTK. The only implementation I can think of is to make the entire menu inactive so return does not activate it and the key defined by prefs (default tab) does the job. So I don't think a PHP specific solution is appropriate, we do need to look for a general solution. Cheers Lex > -- > Frank Lanitz > > ___ > 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] {datetime} & {date} are updated only after config reload
Hello
I'm not sure I follow.
On Sun, Apr 17, 2011 at 12:40 PM, Lex Trotman wrote:
> On 17 April 2011 20:37, Liviu Andronic wrote:
>> On Fri, Apr 15, 2011 at 6:35 PM, Frank Lanitz wrote:
>>> What about moving this to request time? So not parsing at startup but
>>> parsing it when requested by user to insert?
>
This means that when selecting c-menu > insert > changelog the
{datetime} inserted will be the system current date and time. Correct?
Inserting a second time, 2 min later, would insert a new date and time
(again current with respect to the moment of insertion).
>>
>> Yes! This would definitely be much better. Of course, if easy enough
>> to implement.
>> Liviu
>
> Personally I'd prefer it to happen automatically the first time the
> file is saved, the way the filename is inserted.
>
This would set the date and time to the time of the file first save.
And then it would stay static. Correct? I'm not sure how useful this
would be, at least not for me.
Regards
Liviu
> If its manual I'll forget to request it, guaranteed. :-(
>
> Cheers
> Lex
> ___
> Geany-devel mailing list
> Geany-devel@uvena.de
> https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
>
--
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] {datetime} & {date} are updated only after config reload
On 17 April 2011 20:37, Liviu Andronic wrote: > On Fri, Apr 15, 2011 at 6:35 PM, Frank Lanitz wrote: >> What about moving this to request time? So not parsing at startup but >> parsing it when requested by user to insert? >> > Yes! This would definitely be much better. Of course, if easy enough > to implement. > Liviu Personally I'd prefer it to happen automatically the first time the file is saved, the way the filename is inserted. If its manual I'll forget to request it, guaranteed. :-( Cheers Lex ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] {datetime} & {date} are updated only after config reload
On Fri, Apr 15, 2011 at 6:35 PM, Frank Lanitz wrote: > What about moving this to request time? So not parsing at startup but > parsing it when requested by user to insert? > Yes! This would definitely be much better. Of course, if easy enough to implement. Liviu ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] SF.net SVN: geany:[5724] trunk
On Thu, 14 Apr 2011 20:37:01 +0200 Colomban Wendling wrote: > Le 14/04/2011 19:15, Frank Lanitz a écrit : > > Hi, > > Hi Frank, > > > On Wed, 13 Apr 2011 21:55:31 + > > colomb...@users.sourceforge.net wrote: > > > >> Revision: 5724 > >> http://geany.svn.sourceforge.net/geany/?rev=5724&view=rev > >> Author: colombanw > >> Date: 2011-04-13 21:55:31 + (Wed, 13 Apr 2011) > >> > >> Log Message: > >> --- > >> Avoid triggering autocompletion on PHP open tags (closes #3199442) > > > > I'm not sure whether this is really useful as this is adding (not much) > > complexity and more check on typing time, but not increasing typing > > comfort much IMHO. > > I saw you responded to the bug report and said wontfix, but I personally > agree with the reporters of #3199442 that when writing PHP code it's > common to type " length set to 3 or less it's annoying to have the completion coming up. > Generally I don't even notice the completion came up and get the first > item where I wanted nothing, forcing me to remove it/undo. > So I think it's a useful thing for PHP writers, worth having a special > case for it. And I think Geany is widely used for PHP code editing, so I > think (again) that it'd help many users, not only a few ones. > > Moreover, I don't think the check I added is likely to have a real > overhead on typing, especially with non-PHP code. I tried to built the > condition correctly for it not to match as soon as possible (e.g. the > less likely stuff first) but you might want to optimize it even further > (maybe at the cost of a little readability) by e.g. > > *) use G_UNLIKELY() > *) reorder the check even better, though I think it's less readable: >ft->id == GEANY_FILETYPES_PHP && >rootlen == 3 && >startword >= 2 && >style == SCE_HPHP_DEFAULT && >strcmp(&root[-2], " > However, I agree that this adds a little complexity in the code, but > AFAIK we don't have (currently?) any other solution to support this -- > and I don't think it's really useful to have a generic solution, since > there's not so many special cases like this. > > That's my opinion, but feel free to convince me it's wrong (e.g. > measurements of the speed cost showing it's a significant overhead, or > whatever) -- or even that it's just "bad, that's all" and I must go with > it [1] :D Well, its hard to say, but maybe you are right. At least your points do sound reasonable. ;) Cheers, Frank -- Frank Lanitz pgpzYjrXm5s2L.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] {datetime} & {date} are updated only after config reload
On Fri, 15 Apr 2011 22:57:00 +1000
Lex Trotman wrote:
> On 15 April 2011 21:51, Randy Kramer wrote:
> > On Thursday 14 April 2011 08:02:17 pm Lex Trotman wrote:
> >> Yes the {datetime} and {date} are substituted when the templates are
> >> initialised, usually when Geany is opened. As you say this may not
> >> be very useful.
> >>
> >> This can be changed just by moving the call to
> >> templates_replace_default_dates, but where to?
> >>
> >> Options are:
> >>
> >> 1. when the document is created from the template
> >> 2. when the document is saved as a file (when untitled gets replaced)
> >>
> >> Votes please.
> >
> > I haven't yet used those templates (and might never, my file format is a
> > multi-record format and I will want to timestamp the creation of each
> > record, but I anticipate doing that with a recorded (or Lua) macro).
> >
> > I can't remember how those dates are handled in something like Microsoft
> > Word (the last time I can remember using something like those
> > tempates--but close to 10 years ago, now), but I'm pretty sure it would
> > *not* be a good idea to change them each time the document is saved.
>
> Apologies if it was unclear, but after the {date} or {datetime} marker
> is *replaced* by the date/time the first time it no longer exists so
> no further updates occur.
What about moving this to request time? So not parsing at startup but
parsing it when requested by user to insert?
Cheers,
Frank
--
Frank Lanitz
pgpnIK3BFrv89.pgp
Description: PGP signature
___
Geany-devel mailing list
Geany-devel@uvena.de
https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
