From: "Rajesh Vaidheeswarran" <rv@gnu.org>
To: "Miles Bader" <miles@gnu.org>
Cc: Glenn Morris <rgm@gnu.org>, Michael Welsh Duggan <mwd@cert.org>,
emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; whitespace.el mishap
Date: Thu, 7 Feb 2008 10:27:55 -0500 [thread overview]
Message-ID: <a4cf0b680802070727g6771df9cn692ad43d45140538@mail.gmail.com> (raw)
In-Reply-To: <buor6fpjobu.fsf@dhapc248.dev.necel.com>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Yes, I am now really confused. Looks like I missed the booting out of the
whitespace.el that I wrote. I did see that the whitespace-buffer was
behaving differently, but chalked it up to me being tired late at night.
So, I guess, at this point, someone else is responsible for fixing this.
rv
On Feb 7, 2008 1:03 AM, Miles Bader <miles.bader@necel.com> wrote:
> Glenn Morris <rgm@gnu.org> writes:
> >> That's good. However, I'm unable to reproduce it on the installed emacs
> >> in fencepost.
> >
> > In case you're confused, the whitespace.el in question is not the one
> > you wrote (as far as I can tell). Someone recently renamed that one to
> > old-whitespace.el and installed a new one, which seems like a recipe
> > for exactly this kind of confusion. This "whitespace.el" is only in
> > the Emacs CVS trunk (I think).
>
> I gather that Richard wanted the new functionality to use the
> "whitespace" name, which makes some sense, but it seems seems to have
> been done rather clumsily in some cases. E.g. the new
> "whitespace-buffer" command seems completely different than the old
> "whitespace-buffer" command, and really there seems no good reason for
> it. [It's more or less a mode, but isn't called "...-mode", doesn't
> follow emacs mode conventions well, e.g., it doesn't togglex, and
> there's _also_ "whitespace-mode" which offers different, but related,
> functionality...]
>
> -miles
>
> --
> My books focus on timeless truths. -- Donald Knuth
>
[-- Attachment #2: Type: text/html, Size: 2005 bytes --]
next prev parent reply other threads:[~2008-02-07 15:27 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 [this message]
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
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
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=a4cf0b680802070727g6771df9cn692ad43d45140538@mail.gmail.com \
--to=rv@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=miles@gnu.org \
--cc=mwd@cert.org \
--cc=rgm@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).