From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Vinicius Jose Latorre Newsgroups: gmane.emacs.devel,gmane.emacs.pretest.bugs Subject: Re: 23.0.60; whitespace.el mishap Date: Sun, 17 Feb 2008 11:40:27 -0300 Message-ID: <47B8475B.2030307@ig.com.br> References: <47A93D3A.90308@gnu.org> <47AA7C97.2020505@gnu.org> <47B65876.7040009@ig.com.br> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1203255628 17887 80.91.229.12 (17 Feb 2008 13:40:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 17 Feb 2008 13:40:28 +0000 (UTC) Cc: rgm@gnu.org, rv@gnu.org, mwd@cert.org, emacs-pretest-bug@gnu.org, miles@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Feb 17 14:40:50 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JQjlA-0002DA-P5 for ged-emacs-devel@m.gmane.org; Sun, 17 Feb 2008 14:40:49 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQjkg-0004mM-ER for ged-emacs-devel@m.gmane.org; Sun, 17 Feb 2008 08:40:18 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JQjhy-00034R-3n for emacs-devel@gnu.org; Sun, 17 Feb 2008 08:37:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JQjhw-00033L-Gc for emacs-devel@gnu.org; Sun, 17 Feb 2008 08:37:29 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JQjhw-000335-92 for emacs-devel@gnu.org; Sun, 17 Feb 2008 08:37:28 -0500 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JQjhv-0004dP-Vv for emacs-devel@gnu.org; Sun, 17 Feb 2008 08:37:28 -0500 Original-Received: from mx10.gnu.org ([199.232.76.166]) by fencepost.gnu.org with esmtp (Exim 4.67) (envelope-from ) id 1JQjhv-0003ay-Kc for emacs-pretest-bug@gnu.org; Sun, 17 Feb 2008 08:37:27 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1JQjhs-0004cj-EL for emacs-pretest-bug@gnu.org; Sun, 17 Feb 2008 08:37:27 -0500 Original-Received: from an-out-0708.google.com ([209.85.132.251]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JQjhs-0004c5-5v for emacs-pretest-bug@gnu.org; Sun, 17 Feb 2008 08:37:24 -0500 Original-Received: by an-out-0708.google.com with SMTP id c25so252143ana.84 for ; Sun, 17 Feb 2008 05:37:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=h/wTwPNg+HOfUh1Hva9vRVXma6/piQ4tOHBzLPbBE5E=; b=YfD1Hmcun75NLWMynmJW1kwZA9owrL3FP6V/TqqZik5tNvAM+lXoyyB76VotjVFZpZZfoVNtsLm8hL07GKYj6cuC+CnvnXn8EUIjQHOIU0HqFWkVl70dsty4mEO1P80jrmKJOa0XEx/zY1d0zt8ytCUIb9B4y4GItrE5G9yc25Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=XO9jn+hCEKY63/xAxDW3KlvqcImh66FV/BmFCj8smbbWALJ+k2HYtp5UeabLssq4FpUcfu8/LY+s0flQ7F8EJOBaA/sHKk2x5iT3dSNy9ySwWH+220GA7ZQQT2aws41q5Ig5PLjBs5TqHZWI98er+YXqNPkQQdTyBu+Ep8MDO/w= Original-Received: by 10.100.215.5 with SMTP id n5mr8860614ang.3.1203255442421; Sun, 17 Feb 2008 05:37:22 -0800 (PST) Original-Received: from ?192.168.0.100? ( [200.208.45.93]) by mx.google.com with ESMTPS id c20sm11623310ana.13.2008.02.17.05.37.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 17 Feb 2008 05:37:20 -0800 (PST) User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.12) Gecko/20080201 SeaMonkey/1.1.8 In-Reply-To: X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 2) X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:89344 gmane.emacs.pretest.bugs:21156 Archived-At: > 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).