unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: show whitespace problems by default in diff-mode
Date: Thu, 16 Jul 2009 16:19:03 -0700 (PDT)	[thread overview]
Message-ID: <200907162319.n6GNJ3pL027265@godzilla.ics.uci.edu> (raw)
In-Reply-To: <340F28954EE34537B2071D4DE41B77F9@us.oracle.com> (Drew Adams's message of "Thu, 16 Jul 2009 16:06:12 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

  > > Trailing whitespace is an annoyance most of the time,
  > 
  > That's the question - is it? For most Emacs users most of the time? Dunno; just
  > asking.

Yes, it is, please go to your favorite search engine and search for 
trailing whitespace patch or trailing whitespace diff and see you many
hits you get.

  > > and it's not to be conflated with the rest of the whitespace
  > > differences (which diff-mode can ignore just fine -- C-c C-w).
  > 
  > Yes, I know, which is why I didn't conflate them. I mentioned both, in case
  > there is also some desire to deal with whitespace in general this way.

No, there isn't, I intentionally limited the topic to one thing because
of not wanting to have a long discussion that ends nowhere.  So please
stick to the topic at hand.

  > There could be a `diff' switch (or a pseudo-`diff' switch, handled only by
  > Emacs) for trailing whitespace. Just as patch submitters need to get the `diff'
  > switches right for context diff etc. (`-c -w' or whatever), so could they set
  > the switch to show trailing whitespace.

There isn't such a flag, and more, users might not use diff, but
vc-diff.




  reply	other threads:[~2009-07-16 23:19 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 [this message]
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
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=200907162319.n6GNJ3pL027265@godzilla.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.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.
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).