From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: proofreading man/dired.texi Date: Tue, 15 Feb 2005 23:46:52 -0500 Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1108530413 4011 80.91.229.2 (16 Feb 2005 05:06:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 16 Feb 2005 05:06:53 +0000 (UTC) Cc: emacs-devel@gnu.org, rms@gnu.org, Joakim Verona , miles@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 16 06:06:52 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D1HO4-0000ng-54 for ged-emacs-devel@m.gmane.org; Wed, 16 Feb 2005 06:06:08 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D1Hdw-0006rz-A4 for ged-emacs-devel@m.gmane.org; Wed, 16 Feb 2005 00:22:32 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D1Hcz-0006Za-Ix for emacs-devel@gnu.org; Wed, 16 Feb 2005 00:21:33 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D1Hcs-0006TK-C8 for emacs-devel@gnu.org; Wed, 16 Feb 2005 00:21:26 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D1Hco-0006Mj-CJ for emacs-devel@gnu.org; Wed, 16 Feb 2005 00:21:22 -0500 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D1H5V-0008Gn-2R; Tue, 15 Feb 2005 23:46:57 -0500 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 847918282A6; Tue, 15 Feb 2005 23:46:56 -0500 (EST) Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 0AF162CC004; Tue, 15 Feb 2005 23:46:53 -0500 (EST) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id E92EE4BB76; Tue, 15 Feb 2005 23:46:52 -0500 (EST) Original-To: snogglethorpe@gmail.com In-Reply-To: (Miles Bader's message of "Wed, 16 Feb 2005 10:51:30 +0900") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-4.802, requis 5, autolearn=not spam, AWL 0.10, BAYES_00 -4.90) 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33523 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33523 > (1) The function name "wdired-change-to-wdired-mode" is bizarre; why > not just `wdired-mode'???? Is there another way one is supposed to > enter it? If it behaved like a minor mode, that would make sense. But it behaves more like a major mode right now, so it makes sense to have a separate command which does the pre-processing needed before entering the wdired-mode major mode. In any case, it's probably more accidental than anything else. > (2) One must hit `C-c C-c' for changes to take effect; this seems a > bit heavy-weight -- why not just RET (which seems to be what other > systems use)? I don't know of any other system that allows you to do what wdired does. Most others I know are more like dired-efap: they allow you to edit just one file name. > (3) Similarly, in analogy to other systems, it might be nice if there > was some obvious visual indication that wdired was active and > filenames "open for editting" -- e.g., if the filenames looked like a > customize-style "input field" (one might even use the same abstract > face for both, e.g. define an `input-field' face, and have customize > inherit from it). Similarly, other systems only provide "one field at a time". But since wdired only handles modifications in some fields and not in others, it might indeed make sense to "highlight" the parts that can be changed. Maybe with an `input-field' face. Stefan