unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Vinicius Jose Latorre <viniciusjl@ig.com.br>
To: rms@gnu.org
Cc: rgm@gnu.org, rv@gnu.org, mwd@cert.org, emacs-pretest-bug@gnu.org,
	miles@gnu.org
Subject: Re: 23.0.60; whitespace.el mishap
Date: Sun, 17 Feb 2008 11:40:27 -0300	[thread overview]
Message-ID: <47B8475B.2030307@ig.com.br> (raw)
In-Reply-To: <E1JQjTJ-0002po-Tu@fencepost.gnu.org>


>     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.
>
> Ok, we know what the old whitespace-buffer does.
> And we know what the new whitespace-mode does.
>
>     Is it ok if the new whitespace-buffer is removed?
>
> What does the new whitespace-buffer do?  How does it differ
> from whitespace-mode?
>   

The new whitespace-buffer only force whitespace-chars to contain
the symbols to visualize the "bogus" whitespaces.
It seems that the new whitespace-buffer is not so useful.

The old whitespace-buffer highlights the "bogus" whitespaces
(via text properties) and generates a report in a buffer,
if there is any "bogus" whitespace.

Now, whitespace-mode and global-whitespace-mode highlights
all whitespaces including the "bogus" one, if the user specifies
in the whitespace-chars variable.

> Can you make it provide the features of the old whitespace-buffer?
>   

Yes, I think that is missing the "bogus" report
(via a new whitespace-report command).





  reply	other threads:[~2008-02-17 14:40 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
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 [this message]
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=47B8475B.2030307@ig.com.br \
    --to=viniciusjl@ig.com.br \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=miles@gnu.org \
    --cc=mwd@cert.org \
    --cc=rgm@gnu.org \
    --cc=rms@gnu.org \
    --cc=rv@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).