From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: James Cloos <cloos@jhcloos.com>
Cc: 5312@debbugs.gnu.org
Subject: bug#5312: Why is ‘show-trailing-whitespace’ considered unsafe?
Date: Wed, 06 Jan 2010 15:25:27 -0500 [thread overview]
Message-ID: <jwvy6kbgezr.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m3eim3yqnv.fsf@lugabout.jhcloos.org> (James Cloos's message of "Wed, 06 Jan 2010 14:33:00 -0500")
Stefan> Of course, maybe you can come up with file formats where trailing
Stefan> whitespaces are seriously problematic as well. I just can't think
Stefan> of any off the top of my head.
> One seen recently -- on the groff list, IIRC -- involved continuation
> lines. <\><NL> works, <\><SP><NL> does not.
That also affects C, C++, Elisp, and many other formats. The fact that we
haven't mentioned them indicates that it's not considered "seriously
problematic" enough.
Actually, font-lock can also be used in those modes to highlight such
suspicious forms: it's more useful than show-trailing-whitespace since
it can more specifically target those trailing whitespaces that are
semantically significant.
Stefan
next prev parent reply other threads:[~2010-01-06 20:25 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
2010-01-06 19:33 ` James Cloos
2010-01-06 20:25 ` Stefan Monnier [this message]
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
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=jwvy6kbgezr.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=5312@debbugs.gnu.org \
--cc=cloos@jhcloos.com \
/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).