From: Dan Nicolaescu <dann@ics.uci.edu>
To: Miles Bader <miles@gnu.org>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: show whitespace problems by default in diff-mode
Date: Thu, 16 Jul 2009 20:36:54 -0700 (PDT) [thread overview]
Message-ID: <200907170336.n6H3asxS000667@godzilla.ics.uci.edu> (raw)
In-Reply-To: <buobpnkm1of.fsf@dhlpc061.dev.necel.com> (Miles Bader's message of "Fri, 17 Jul 2009 12:24:48 +0900")
Miles Bader <miles@gnu.org> writes:
> Óscar Fuentes <ofv@wanadoo.es> writes:
> > It's not only about pedantry. The worst thing about trailing whitespace
> > is that it tends to come and go while editing the file and when finally
> > the changes are committed it creates noise on VCS diffs and is
> > considered antisocial. This is why on some sites trailing whitespace is
> > forbidden and people there would appreciate a method for easy detection
> > and some tools for deletion.
>
> No doubt. But that's a specific special case: when you're viewing a
> diff of changes over which one has easy control (e.g., vc-diff of the
> working tree).
>
> I can see an argument for turning on highlighting of "introduced
> trailing whitespace" (not in the context lines) by default for vc-diff
> of the working tree, but more general ("pedantic") highlighting
> shouldn't be on by default.
The feature we are talking about here is exclusively about highlighting
the "introduced trailing whitespace"...
next prev parent reply other threads:[~2009-07-17 3:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 22:14 show whitespace problems by default in diff-mode Dan Nicolaescu
2009-07-16 22:33 ` Drew Adams
2009-07-16 22:53 ` Dan Nicolaescu
2009-07-16 23:06 ` Drew Adams
2009-07-16 23:19 ` Dan Nicolaescu
2009-07-16 23:38 ` Miles Bader
2009-07-17 1:35 ` Dan Nicolaescu
2009-07-17 1:45 ` Miles Bader
2009-07-17 2:29 ` Óscar Fuentes
2009-07-17 3:24 ` Miles Bader
2009-07-17 3:36 ` Dan Nicolaescu [this message]
2009-07-17 4:15 ` Óscar Fuentes
2009-07-17 4:26 ` Miles Bader
2009-07-17 6:39 ` Dan Nicolaescu
2009-07-17 7:49 ` Miles Bader
2009-07-17 0:03 ` Óscar Fuentes
2009-07-17 1:37 ` Dan Nicolaescu
2009-07-17 3:14 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200907170336.n6H3asxS000667@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=ofv@wanadoo.es \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).