From: Pedro Alves <pedro@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [gdbserver/commit] fix whitespace.
Date: Mon, 23 Mar 2009 01:31:00 -0000 [thread overview]
Message-ID: <200903230126.55000.pedro@codesourcery.com> (raw)
In-Reply-To: <20090323011202.GA9472@adacore.com>
On Monday 23 March 2009 01:12:02, Joel Brobecker wrote:
> > I'm also applying these further fixes.
>
> (I can't help myself, sorry)
>
> You know, the current whitespace rule has been really bugging me
> since day one. I would be a very very happy camper if we got rid
> of tabs and just used spaces.
I suspect that the interim period between using tabs and not using
tabs would take a while, and would be a bigger mess, unless we
did wholesale conversion.
> Tabs make it hard for everything:
> hard to edit/navigate in your editor (unless you have a mode that
> makes it transparent for you?),
I can't tell if this was real question? Emacs makes it mostly
transparent.
I also use this mode to easily spot breakage:
http://www.emacswiki.org/emacs/WhiteSpace
> and harder to read patches
> (space display can get off because of the extra character that is
> being put on the first column of each line of the diff).
>
> Iiiiiiihhh!
>
> (nervous breakdown)
>
:-) :-)
Yeah... I can't say I love them either, but...
as long as we have them, might as well be consistent, m'kay?
--
Pedro Alves
next prev parent reply other threads:[~2009-03-23 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 0:22 Pedro Alves
2009-03-23 1:12 ` Pedro Alves
2009-03-23 1:26 ` Joel Brobecker
2009-03-23 1:31 ` Pedro Alves [this message]
2009-03-23 3:54 ` Thiago Jung Bauermann
2009-03-23 6:28 ` Eli Zaretskii
2009-03-23 4:24 ` Eli Zaretskii
2009-03-23 12:49 ` Mark Kettenis
2009-03-23 14:30 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903230126.55000.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox