From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Vladimir Prus <vladimir@codesourcery.com>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFC] Implement -list-thread-groups.
Date: Fri, 14 Nov 2008 20:46:00 -0000 [thread overview]
Message-ID: <200811141743.57742.pedro@codesourcery.com> (raw)
In-Reply-To: <200811142028.43561.vladimir@codesourcery.com>
On Friday 14 November 2008 17:28:43, Vladimir Prus wrote:
> Done. Indicentally, I know how to configure Emacs to remove trailing
> whitespace on save. But pretty much every source file in gdb already has such
> lines. If somebody tell me how to make Emacs not add lines without trailing
> whitespace, while *not* changing existing lines, it would be gtreat.
I just do 'quilt refresh --strip-trailing-whitespace' which gets rid
of most of the extra whitespace *I'm touching*, but leaves the rest
untouched. Won't work if you don't use quilt. :-)
In addition, in emacs, I tend to switch into whitespace-mode when I'm
doing final editing of my patches, which lets you easily see all the
redundant and wrong indentation in full color.
--
Pedro Alves
next prev parent reply other threads:[~2008-11-14 17:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-12 21:01 Vladimir Prus
2008-11-14 11:46 ` Joel Brobecker
2008-11-14 11:58 ` Michael Snyder
2008-11-14 19:43 ` Vladimir Prus
2008-11-14 19:44 ` Michael Snyder
2008-11-14 21:45 ` Vladimir Prus
2008-11-15 4:58 ` Michael Snyder
2008-11-15 9:00 ` Vladimir Prus
2008-11-15 16:10 ` Michael Snyder
2008-11-15 19:06 ` Vladimir Prus
2008-11-16 8:22 ` Michael Snyder
2008-11-16 8:22 ` Vladimir Prus
[not found] ` <29E9E827072C404C88A05DDC42B45997199E0503FF@PA-EXMBX14.vmware.com>
2008-11-17 9:42 ` Vladimir Prus
2008-11-17 19:48 ` Michael Snyder
2008-11-17 22:02 ` Vladimir Prus
2008-11-14 20:46 ` Pedro Alves [this message]
2008-11-16 1:14 ` Joel Brobecker
2008-11-16 8:20 ` 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=200811141743.57742.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=vladimir@codesourcery.com \
/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