On 03/13/11 20:23, Lex Trotman wrote:
It seems to me that the assumption is that the template file encoding
is UTF-8 or ASCII (as a subset of UTF-8) as its contents are just
pasted straight into the Scintilla buffer. The standard templates are
ASCII, but it may not be true for user defined temp
On 14 March 2011 05:53, Matthew Brush wrote:
> On 03/13/11 03:19, Lex Trotman wrote:
>>
>> I don't think this is a good idea since g_strstrip() doesn't actually
>> change the size recorded in the GString, it might appear to work
>> sometimes but it might also fail. Note that a GString also does no
On 14 March 2011 01:30, Frank Lanitz wrote:
> On Sun, 13 Mar 2011 13:43:48 +1100
> Lex Trotman wrote:
>
>> Of course leaving all the content in
>> makes the mailing much larger and its harder to find the new content.
>> To combat this learn to use your mailers quoted text hiding features,
>> and
On 14 March 2011 01:24, Randy Kramer wrote:
> On Saturday 12 March 2011 09:43:48 pm Lex Trotman wrote:
>> This howto is very worthwhile, but one of the problems with this, and
>> many other lists, is that many people don't read the whole thread, so
>> if you cut all the old content out you are for
On 13 March 2011 23:36, Thomas Martitz
wrote:
> I agree with Frank, I hate unecessary full quotes.
>
>
> On 13.03.2011 03:43, Lex Trotman wrote:
>>
>> Hi all,
>>
>> I'd like to add a couple of points to Franks excellent comments
>>
>> On 13 March 2011 05:18, Frank Lanitz wrote:
>>>
>>> Hi guys,
>
On Sunday 13 March 2011 10:30:08 am Frank Lanitz wrote:
> On Sun, 13 Mar 2011 13:43:48 +1100
>
> Lex Trotman wrote:
> > Of course leaving all the content in
> > makes the mailing much larger and its harder to find the new
> > content. To combat this learn to use your mailers quoted text
> > hidin
On 03/13/11 07:17, Frank Lanitz wrote:
On Sun, 13 Mar 2011 12:08:32 +0800
Chow Loong Jin wrote:
You could actually use .git/info/exclude instead for that
functionality. Then you can use stuff like git clean -fdx, and not
worry about accidentally purging your .gitignore. .gitignore should
only
On Sun, 13 Mar 2011 13:43:48 +1100
Lex Trotman wrote:
> Of course leaving all the content in
> makes the mailing much larger and its harder to find the new content.
> To combat this learn to use your mailers quoted text hiding features,
> and if it doesn't have them, switch to one that does.
I
On Saturday 12 March 2011 09:43:48 pm Lex Trotman wrote:
> This howto is very worthwhile, but one of the problems with this, and
> many other lists, is that many people don't read the whole thread, so
> if you cut all the old content out you are forcing them to reply
> without all the background.
On Sun, 13 Mar 2011 15:18:09 +0100, Colomban wrote:
>Le 13/03/2011 15:08, Enrico Tröger a écrit :
>> On Sun, 13 Mar 2011 14:52:24 +0100, Thomas wrote:
>>> On 13.03.2011 14:50, Enrico Tröger wrote:
On Sun, 13 Mar 2011 14:39:29 +0100, Thomas wrote:
> On 13.03.2011 14:35, Enrico Tröger wrote
Hi,
On Sun, 13 Mar 2011 09:57:36 +0100
Enrico Tröger wrote:
> Do you want to integrate these flags into the build system? I don't
> think this is a good idea. Such flags should be set outside of the
> build system by the developer/user, not automatically.
> This is why they are mentioned in HAC
Le 13/03/2011 15:08, Enrico Tröger a écrit :
> On Sun, 13 Mar 2011 14:52:24 +0100, Thomas wrote:
>> On 13.03.2011 14:50, Enrico Tröger wrote:
>>> On Sun, 13 Mar 2011 14:39:29 +0100, Thomas wrote:
On 13.03.2011 14:35, Enrico Tröger wrote:
>>> Something like ./configure --enable-extra-c-warn
On Sun, 13 Mar 2011 12:08:32 +0800
Chow Loong Jin wrote:
> You could actually use .git/info/exclude instead for that
> functionality. Then you can use stuff like git clean -fdx, and not
> worry about accidentally purging your .gitignore. .gitignore should
> only be used if you want to commit it i
On Sun, 13 Mar 2011 14:52:24 +0100, Thomas wrote:
>On 13.03.2011 14:50, Enrico Tröger wrote:
>> On Sun, 13 Mar 2011 14:39:29 +0100, Thomas wrote:
>>
>>> On 13.03.2011 14:35, Enrico Tröger wrote:
>> Something like ./configure --enable-extra-c-warnings (or shorter
>> if you prefer ^^)
.
On 13.03.2011 14:50, Enrico Tröger wrote:
On Sun, 13 Mar 2011 14:39:29 +0100, Thomas wrote:
On 13.03.2011 14:35, Enrico Tröger wrote:
Something like ./configure --enable-extra-c-warnings (or shorter
if you prefer ^^)
...so this sounds good to me. Maybe that option could also display a
hint to
On Sun, 13 Mar 2011 14:39:29 +0100, Thomas wrote:
>On 13.03.2011 14:35, Enrico Tröger wrote:
>>> >Something like ./configure --enable-extra-c-warnings (or shorter
>>> >if you prefer ^^)
>> ...so this sounds good to me. Maybe that option could also display a
>> hint to check HACKING for more inform
On 13.03.2011 14:35, Enrico Tröger wrote:
>Something like ./configure --enable-extra-c-warnings (or shorter if you
>prefer ^^)
...so this sounds good to me. Maybe that option could also display a
hint to check HACKING for more information about flags.
Why disabled by default? I don't quite un
On Sun, 13 Mar 2011 14:27:24 +0100, Colomban wrote:
>On Sun, 13 Mar 2011 21:32:48 +1100, Lex wrote:
> We could maybe add a little wrapper script into the scripts/
> directory which sets a bunch of compiler options we like, for
> convenience.
Having scripts like these is non-s
On Sun, 13 Mar 2011 21:32:48 +1100, Lex wrote:
We could maybe add a little wrapper script into the scripts/
directory which sets a bunch of compiler options we like, for
convenience.
>>>
>>> Having scripts like these is non-standard so it would have to be
>>> *well* documented. I st
I agree with Frank, I hate unecessary full quotes.
On 13.03.2011 03:43, Lex Trotman wrote:
Hi all,
I'd like to add a couple of points to Franks excellent comments
On 13 March 2011 05:18, Frank Lanitz wrote:
Hi guys,
Please give me the chance to point to the world famous usenet quoting
howt
On 11.03.2011 19:37, Colomban Wendling wrote:
Do you have objections, comment or whatever?
I largely agree with all of what Lex said.
* I routinely add temporary debug code without the proper headers
(because I know it works) so making this break the build would be
inconvinient for me (and
On 13 March 2011 17:10, Matthew Brush wrote:
> On 03/12/11 19:46, Lex Trotman wrote:
>>
>> On 13 March 2011 13:36, Colomban Wendling
>> wrote:
>>>
>>> Agreed. Maybe the easiest way to go would be to write this wrapper
>>> library in Vala, at least as a start point:
>>> 1) it's an OO language, and
On Sun, 13 Mar 2011 21:32:48 +1100, Lex wrote:
>Actually I check whether the compiler understand each flag, so it
>would be easy to support any compiler. I only talk about GCC
>warnings because I only know GCC's flags, but if somebody knows
>some other, we might add them.
On 13 March 2011 19:18, Matthew Brush wrote:
> Hi,
>
> I wasn't sure if I should make a feature request or a bug report, so if
> needed, let me know which and I'll file it on the project site.
>
> The patch attached to this message does a few things, sorry I didn't split
> them into different patc
2011/3/13 Enrico Tröger :
> On Sun, 13 Mar 2011 03:57:59 +0100, Colomban wrote:
>
> Hey,
>
> I didn't read all of the thread, so I might be missing something. But
> still.
>
>
>>> PS we are only talking about gcc flags here but I think we only
>>> supprt gcc even on Windows, right Enrico?
>
> Nope.
Geany Newsletter
Volume 1
CC-BY -- The Geany-Newsletter team
Table of Contents
-
1 Geany 0.20 has been released
2 Geany-Plugins 0.20 have beenreleased
2.1 New plugins
2.1.1 UpdateChecker
2.1.2 WebHelper
2.2 Updates & Bugfixes
2.2.1 GeanyExtraSel
2.2.2 GeanyGenD
On Sun, 13 Mar 2011 03:57:59 +0100, Colomban wrote:
Hey,
I didn't read all of the thread, so I might be missing something. But
still.
>> PS we are only talking about gcc flags here but I think we only
>> supprt gcc even on Windows, right Enrico?
Nope.
We try to support ANSI C and so support an
Hi,
I wasn't sure if I should make a feature request or a bug report, so if
needed, let me know which and I'll file it on the project site.
The patch attached to this message does a few things, sorry I didn't
split them into different patches, but it's so small and related that
it's hardly w
28 matches
Mail list logo
