From: Miles Bader <miles@gnu.org>
To: Vinicius Jose Latorre <viniciusjl@ig.com.br>
Cc: rgm@gnu.org, mwd@cert.org, rms@gnu.org, rv@gnu.org,
emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; whitespace.el mishap
Date: Sat, 16 Feb 2008 12:04:52 +0900 [thread overview]
Message-ID: <87y79lvbxn.fsf@catnip.gol.com> (raw)
In-Reply-To: <47B65876.7040009@ig.com.br> (Vinicius Jose Latorre's message of "Sat, 16 Feb 2008 00:28:54 -0300")
Vinicius Jose Latorre <viniciusjl@ig.com.br> writes:
> Well, indeed the old whitespace-buffer had reported
> where the bogus whitespace had happened.
>
> Instead of reporting, the new whitespace-mode
> displays visually the bogus whitespace.
>
> Is it ok if the new whitespace-buffer is removed?
>
> Maybe a better alternative should be to create a
> whitespace-report command which reports like the old
> whitespace-buffer.
My personal opinion is that the old whitespace mode was pretty wacky,
and had lots of unneeded features and features which didn't follow Emacs
conventions. It doesn't seem necessary to me to _exactly_ preserve the
interface (maybe some def-obsolete-alias could be used in some case),
just keep those commands which were actually useful, and maybe try to
make them follow emacs conventions better.
E.g., how about:
+ `suspicious-whitespace-mode' -- highlights only "suspicious"
whitespace, i.e., that which probably should be removed. This is
sort of like the old "whitespace-buffer" command, but implemented as
a proper mode, or like your "whitespace-mode", but only highlights
suspicious whitespace. [dunno about the term "suspicious", but you
know what I mean]
+ `cleanup-whitespace' -- removes suspicious whitespace [same
definition as suspicious-whitespace-mode]
-Miles
--
Defenceless, adj. Unable to attack.
next prev parent reply other threads:[~2008-02-16 3:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 21:33 23.0.60; whitespace.el mishap Michael Welsh Duggan
2008-02-06 4:53 ` Rajesh Vaidheeswarran
2008-02-06 14:33 ` Michael Welsh Duggan
2008-02-07 3:35 ` Rajesh Vaidheeswarran
2008-02-07 5:07 ` Glenn Morris
2008-02-07 6:03 ` Miles Bader
2008-02-07 15:27 ` Rajesh Vaidheeswarran
2008-02-08 4:15 ` Richard Stallman
2008-02-08 12:04 ` Vinicius Jose Latorre
2008-02-16 3:28 ` Vinicius Jose Latorre
2008-02-16 3:04 ` Miles Bader [this message]
2008-02-16 20:47 ` Vinicius Jose Latorre
2008-02-17 13:22 ` Richard Stallman
2008-02-20 4:24 ` Rajesh Vaidheeswarran
2008-02-20 4:27 ` Miles Bader
2008-02-20 4:41 ` Rajesh Vaidheeswarran
2008-02-17 13:22 ` Richard Stallman
2008-02-17 14:40 ` Vinicius Jose Latorre
2008-02-16 3:32 ` Vinicius Jose Latorre
2008-03-01 19:00 ` Vinicius Jose Latorre
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=87y79lvbxn.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=mwd@cert.org \
--cc=rgm@gnu.org \
--cc=rms@gnu.org \
--cc=rv@gnu.org \
--cc=viniciusjl@ig.com.br \
/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.