From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, rms@gnu.org,
Joakim Verona <joakim@verona.se>,
miles@gnu.org
Subject: Re: proofreading man/dired.texi
Date: Tue, 15 Feb 2005 23:46:52 -0500 [thread overview]
Message-ID: <jwv1xbhqfu5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <fc339e4a050215175158c8775f@mail.gmail.com> (Miles Bader's message of "Wed, 16 Feb 2005 10:51:30 +0900")
> (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
next prev parent reply other threads:[~2005-02-16 4:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m31xbjtgh4.fsf@naru.home>
2005-02-15 17:27 ` proofreading man/dired.texi Richard Stallman
2005-02-15 20:12 ` Stefan Monnier
2005-02-16 1:51 ` Miles Bader
2005-02-16 4:46 ` Stefan Monnier [this message]
2005-02-17 10:35 ` Richard Stallman
2005-02-17 14:29 ` Matt Hodges
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=jwv1xbhqfu5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=miles@gnu.org \
--cc=rms@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).