all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s)
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 5312@debbugs.gnu.org
Subject: bug#5312: Why is ‘show-trailing-whitespace’ considered unsafe?
Date: Wed, 06 Jan 2010 16:13:14 +0100	[thread overview]
Message-ID: <87r5q3w9kl.fsf@gnu.org> (raw)
In-Reply-To: <jwvd41ngvpp.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 06 Jan 2010 09:24:03 -0500")

Hi,

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Of course, maybe you can come up with file formats where trailing
> whitespaces are seriously problematic as well.  I just can't think of
> any off the top of my head.

Trailing whitespaces can lead to pointless conflicts when applying
patches.  See, e.g.,
http://www.mail-archive.com/libvir-list@redhat.com/msg04896.html .

In this thread, the project’s policy is to get rid of them, and
‘show-trailing-whitespace’ in ‘.dir-locals.el’ or similar would
definitely help.

Thanks,
Ludo’.






  reply	other threads:[~2010-01-06 15:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <117hrlp5yy.fsf@fencepost.gnu.org>
2010-01-04 13:11 ` bug#5312: Why is ‘show-trailing-whitespace’ considered unsafe? Ludovic =?UTF-8?Q?Court=C3=A8s
2010-01-05 18:56   ` Stefan Monnier
2010-01-06  8:31     ` Ludovic =?UTF-8?Q?Court=C3=A8s
2010-01-06 14:24       ` Stefan Monnier
2010-01-06 15:13         ` Ludovic =?UTF-8?Q?Court=C3=A8s [this message]
2010-01-06 19:33         ` James Cloos
2010-01-06 20:25           ` Stefan Monnier
2010-01-07 14:17             ` Kevin Rodgers
2010-01-07 19:40               ` Stefan Monnier
2010-01-14  6:16   ` bug#5312: marked as done (Why is ‘show-trailing-whitespace’ considered unsafe?) Emacs bug Tracking System

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=87r5q3w9kl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=5312@debbugs.gnu.org \
    --cc=?=5312@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.