From: Martin Stjernholm <mast@lysator.liu.se>
Cc: Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>
Subject: Re: gratuitous changes
Date: 02 Feb 2003 00:28:21 +0100 [thread overview]
Message-ID: <5b3cn7lgx6.fsf@lister.roxen.com> (raw)
In-Reply-To: <E18f5qs-00048y-00@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> wrote:
> But I still think that what happened with keyboard.c is bad:
> turning every whitespace-only line into an empty line.
>
> I see what you mean. At the same time, it is tidier
> not to have those excess spaces; we don't want to treat
> them as sacred.
I don't know why this got cc'd to the CC Mode address, but I have
something to say on the subject of spurious whitespaces anyway:
The matter of whitespace handling is a personal preference, be it
handling on whitespace on empty lines, other trailing whitespace, or
indent-tabs-mode. While everyone should use whatever settings they
like, it becomes a problem when someone applies his/her preference
over a whole file in a shared development environment, as this thread
has shown.
To address that, I developed the package ws-trim.el. What's special
about it is that it normally only trims whitespace on lines which are
changed through other editing. In my experience this works well; the
code edited by oneself gets the whitespace trimming one likes, while
other code in the same file isn't affected so cvs differences seldom
become unnecessarily large.
The trimming is done whenever the point leaves a line that has been
changed. Editing that affects more than one line, e.g. pasting of
blocks, is normally not affected.
I'm willing to contribute this package if there's interest. (I said
that when I announced it back in -97 too, but RMS thought at that
point that the all-or-nothing approach in whitespace.el was
sufficient.)
next prev parent reply other threads:[~2003-02-01 23:28 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 21:48 gratuitous changes Stefan Monnier
2003-01-31 22:16 ` Andreas Schwab
2003-01-31 22:51 ` John Wiegley
2003-01-31 23:01 ` Juanma Barranquero
2003-02-01 0:00 ` Stefan Monnier
2003-02-01 6:51 ` Robert Anderson
2003-02-03 15:09 ` Stefan Monnier
2003-02-03 16:20 ` Robert Anderson
2003-02-01 9:54 ` Juanma Barranquero
2003-02-01 2:11 ` Miles Bader
2003-02-01 18:44 ` Bill Wohler
2003-02-01 22:11 ` Richard Stallman
2003-02-01 23:28 ` Martin Stjernholm [this message]
2003-02-02 5:52 ` Eli Zaretskii
2003-02-02 6:14 ` Miles Bader
2003-02-06 16:34 ` Martin Stjernholm
2003-02-06 17:22 ` Miles Bader
2003-02-10 0:29 ` Martin Stjernholm
2003-02-03 14:57 ` Stefan Monnier
2003-02-02 5:56 ` Eli Zaretskii
2003-02-02 12:56 ` Juanma Barranquero
2003-02-02 13:59 ` Kim F. Storm
2003-02-03 13:01 ` Richard Stallman
2003-02-03 14:11 ` Juanma Barranquero
2003-02-03 14:54 ` Stefan Monnier
2003-02-03 15:01 ` Juanma Barranquero
2003-02-04 14:59 ` Juanma Barranquero
2003-02-04 16:09 ` Robert Anderson
2003-02-04 16:44 ` Juanma Barranquero
2003-02-04 17:14 ` Robert Anderson
2003-02-04 17:22 ` Juanma Barranquero
2003-02-04 19:46 ` Eli Zaretskii
2003-02-04 20:16 ` Juanma Barranquero
2003-02-04 20:22 ` Stefan Monnier
2003-02-04 20:44 ` Nick Roberts
2003-02-04 22:59 ` Edward O'Connor
2003-02-04 23:19 ` Juanma Barranquero
2003-02-05 0:32 ` Kim F. Storm
2003-02-05 0:39 ` Kim F. Storm
2003-02-05 0:49 ` Kenichi Handa
2003-02-05 4:24 ` Luc Teirlinck
2003-02-05 4:51 ` Miles Bader
2003-02-06 2:42 ` Richard Stallman
2003-02-06 4:09 ` Luc Teirlinck
2003-02-07 9:18 ` Richard Stallman
2003-02-04 23:18 ` Juanma Barranquero
2003-02-05 0:42 ` Stefan Monnier
2003-02-05 6:03 ` Eli Zaretskii
2003-02-06 2:42 ` Richard Stallman
2003-02-06 2:54 ` Luc Teirlinck
2003-02-04 23:14 ` Juanma Barranquero
2003-02-05 6:01 ` Eli Zaretskii
2003-02-05 8:18 ` Juanma Barranquero
2003-02-05 15:30 ` Eli Zaretskii
2003-02-14 22:56 ` Thien-Thi Nguyen
2003-02-05 0:14 ` Richard Stallman
2003-02-07 14:02 ` Francesco Potorti`
2003-02-10 1:47 ` Miles Bader
2003-02-10 10:09 ` Francesco Potorti`
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=5b3cn7lgx6.fsf@lister.roxen.com \
--to=mast@lysator.liu.se \
--cc=bug-cc-mode@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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.