On 12-03-20 06:06 PM, Matthew Brush wrote:
[...]
I actually was meaning to bring this up, and I think it was discussed in
passing on IRC since I've made a branch on geany-themes to implement it.
What if the color schemes and filetypes.* files had a version key in
them that Geany could check and
On 12-03-20 06:09 AM, Nick Treleaven wrote:
On 20/03/2012 04:46, Lex Trotman wrote:
+ Filetypes
+ * Move all named styles into color schemes and keep only mappings in
the
+ filetypes files. Filetypes should no longer contain styling
information,
+ except `filetypes.common` which contains the def
On 21 March 2012 00:09, Nick Treleaven wrote:
> On 20/03/2012 04:46, Lex Trotman wrote:
>>
>> + Filetypes
>> + * Move all named styles into color schemes and keep only mappings in
>> the
>> + filetypes files. Filetypes should no longer contain styling
>> information,
>> + except `f
On 20/03/2012 04:46, Lex Trotman wrote:
+Filetypes
+* Move all named styles into color schemes and keep only mappings in the
+ filetypes files. Filetypes should no longer contain styling information,
+ except `filetypes.common` which contains the default color scheme. Breaks
+
On 20 March 2012 13:08, Matthew Brush wrote:
> On 12-03-19 05:29 PM, Lex Trotman wrote:
>
>>> Agree, I think Colomban's idea of adding incompatible/important changes
>>> to
>>> the NEWS file as we go, and at the top, would work well.
>>
>>
>> Sounds like we are approaching a plan.
>>
>
> This soun
On 12-03-19 05:29 PM, Lex Trotman wrote:
Agree, I think Colomban's idea of adding incompatible/important changes to
the NEWS file as we go, and at the top, would work well.
Sounds like we are approaching a plan.
This sounds like a fine idea to me. Something like the attached patch is OK?
C
[...]
>>
>> Its incompatible with users fingers, and thats a *major* incompatibility.
>> :)
>
>
> Agree. I might be able to improve this a bit with a workaround, I'll
> investigate.
>
Neat.
>>
>> Yeah, plugins is an important one.
>
>
> I may have missed some things but offhand is this just the p
On 19/03/2012 01:41, Lex Trotman wrote:
On 19 March 2012 12:12, Matthew Brush wrote:
On 12-03-18 05:20 PM, Lex Trotman wrote:
Hi All,
I recently ran into Nicks change of the default keybinding-t
from transpose to gototag. This made me realise we need to keep a
list of incompatibilities to a
Le 19/03/2012 01:20, Lex Trotman a écrit :
> Hi All,
>
> I recently ran into Nicks change of the default keybinding -t
> from transpose to gototag. This made me realise we need to keep a
> list of incompatibilities to add to the release notes when 1.22 is
> released.
>
> I would have thought tha
On 19 March 2012 12:12, Matthew Brush wrote:
> On 12-03-18 05:20 PM, Lex Trotman wrote:
>>
>> Hi All,
>>
>> I recently ran into Nicks change of the default keybinding-t
>> from transpose to gototag. This made me realise we need to keep a
>> list of incompatibilities to add to the release notes wh
On 12-03-18 05:20 PM, Lex Trotman wrote:
Hi All,
I recently ran into Nicks change of the default keybinding-t
from transpose to gototag. This made me realise we need to keep a
list of incompatibilities to add to the release notes when 1.22 is
released.
I don't know if I'd consider changing a
Hi All,
I recently ran into Nicks change of the default keybinding -t
from transpose to gototag. This made me realise we need to keep a
list of incompatibilities to add to the release notes when 1.22 is
released.
I would have thought that anything incompatible would have been
forgotten by then u
12 matches
Mail list logo
