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

> 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.

> 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.

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.

>   > I don't have a particular axe to grind, here. It's just 
>   > not clear that most people will want to show whitespace
>   > diffs (or even trailing whitespace) most of the time.
>   > If you can support that claim, then sure, go for it.
> 
> I have yet to see anyone that wants to have trailing whitespace (which
> are the only thing that might post is concerned with), but it's common
> to see patches being rejected, or people asked to fix the patches
> because of trailing whitespace problems.  Making it easy to 
> spot and fix such issues just helps our users.

As I see it, the claim is still not supported. The question is about most Emacs
users of `diff' most of the time. You seem to be addressing the population of
most submitters of Emacs patches most of the time that they submit an Emacs
patch (or other patch where trailing whitespace is a no-no). Those aren't the
same thing.

Again, I don't know whether your claim might also be true for most Emacs users
of `diff' most of the time. But you haven't supported that, at least.

(And yes, I'm likely to be bit by this gotcha, myself. The question still should
be about Emacs users of `diff' in general, not about Emacs patch submitters.)





  reply	other threads:[~2009-07-16 23:06 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 [this message]
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
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=340F28954EE34537B2071D4DE41B77F9@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=dann@ics.uci.edu \
    --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).