Hi,
Not sure whether this is the best idea, but I've jsut created a page
inside the wiki at http://wiki.geany.org/patches/review_list where we
could collect patches/patchsets to just keep an overview as it appears
on this mailing list some patches might get lost due lot of
traffic/discussion.
All,
Lex and I have had a little bit of off-line conversation about his
document, the Build System User Guide. He suggested that I put it on
the wiki.
I made a feeble attempt, and now recommend instead that, at least on a
temporary basis, it be put on the geany.org website with one or more
Le 18/05/2011 02:05, Matthew Brush a écrit :
On 05/17/11 08:30, Colomban Wendling wrote:
Le 16/05/2011 05:45, Matthew Brush a écrit :
I was wondering if anyone had time to review some changes I've been
working on?
No really as you see, times is rare these days :/
But I'm trying to do my
Le 18/05/2011 02:15, Matthew Brush a écrit :
On 05/17/11 08:40, Colomban Wendling wrote:
2) the space is useless in [:= ] since it'd be matched just after
I'll trust you on this :)
Hum, actually you shouldn't I was wrong, it has not the same meaning.
The space in that character range allowed
Am 18.05.2011 14:26, schrieb Randy Kramer:
All,
Lex and I have had a little bit of off-line conversation about his
document, the Build System User Guide. He suggested that I put it on
the wiki.
I made a feeble attempt, and now recommend instead that, at least on a
temporary basis,
I'm wondering why this shouldn't be part of the official manual?
I disagree that information about Geany's core features should be at
different places.
Best regards.
___
Geany-devel mailing list
Geany-devel@uvena.de
Am 18.05.2011 16:28, schrieb Matthew Brush:
On 05/18/11 01:22, Frank Lanitz wrote:
Hi,
Not sure whether this is the best idea, but I've jsut created a page
inside the wiki at http://wiki.geany.org/patches/review_list where we
could collect patches/patchsets to just keep an overview as it
On Wed, 18 May 2011 16:45:47 +0200, Frank wrote:
Am 18.05.2011 16:45, schrieb Frank Lanitz:
Am 18.05.2011 16:28, schrieb Matthew Brush:
On 05/18/11 01:22, Frank Lanitz wrote:
Hi,
Not sure whether this is the best idea, but I've jsut created a
page inside the wiki at
On 19 May 2011 00:24, Frank Lanitz fr...@frank.uvena.de wrote:
Am 18.05.2011 14:26, schrieb Randy Kramer:
All,
Lex and I have had a little bit of off-line conversation about his
document, the Build System User Guide. He suggested that I put it on
the wiki.
I made a feeble attempt, and now
Btw, I think we should keep the Wiki discussion on one list,
preferably, the geany list.
Whilst a reasonable idea this is going to add lots of devel stuff to
the geany list for a while whilst these things get sorted. But I
guess until someone complains thats ok :-)
Cheers
Lex
That's what I meant for set_text_full(). Basically we don't need to show
the real SCI api here, just what's useful to us. If it means wrapping to
calls, I'd say it's just fine.
And having such a wrapper will help user (here meaning client code) to
properly give a length parameter where
On 05/18/11 07:45, Frank Lanitz wrote:
Am 18.05.2011 16:28, schrieb Matthew Brush:
On 05/18/11 01:22, Frank Lanitz wrote:
Hi,
Not sure whether this is the best idea, but I've jsut created a page
inside the wiki at http://wiki.geany.org/patches/review_list where we
could collect
On 05/18/11 17:07, Lex Trotman wrote:
That's what I meant for set_text_full(). Basically we don't need to show
the real SCI api here, just what's useful to us. If it means wrapping to
calls, I'd say it's just fine.
And having such a wrapper will help user (here meaning client code) to
properly
13 matches
Mail list logo
