unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: show whitespace problems by default in diff-mode
Date: Fri, 17 Jul 2009 08:38:24 +0900	[thread overview]
Message-ID: <873a8wryfj.fsf@catnip.gol.com> (raw)
In-Reply-To: <200907162214.n6GMEo5o025706@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Thu, 16 Jul 2009 15:14:50 -0700 (PDT)")

Dan Nicolaescu <dann@ics.uci.edu> writes:
> Why not turn on whitespace-mode by default in diff-mode?  It makes
> spotting whitespace problems very easy, and will make it also easy to
> fix.

I guess, it's the same as with normal files:  some people are very
concerned with whitespace problems, but many do not care; for the
latter, whitespace indication would simply be annoying noise.

It's good if it's _easy_ to turn on, but it seems far less obvious that
it should be turned on by default.

[I know many in the git community seem quite obsessed with catching
whitespace problems in patches etc, but I've found git's various
whitespace-detecting frobs etc simply annoying (I don't know if it's
still turned on by default, but I had to actively disable it).]

-Miles

-- 
Fast, small, soon; pick any 2.




  parent reply	other threads:[~2009-07-16 23:38 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 [this message]
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=873a8wryfj.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --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).