From: Miles Bader <snogglethorpe@gmail.com>
Cc: rms@gnu.org, Joakim Verona <joakim@verona.se>, emacs-devel@gnu.org
Subject: Re: proofreading man/dired.texi
Date: Wed, 16 Feb 2005 10:51:30 +0900 [thread overview]
Message-ID: <fc339e4a050215175158c8775f@mail.gmail.com> (raw)
In-Reply-To: <jwvr7jhoa5w.fsf-monnier+emacs@gnu.org>
On Tue, 15 Feb 2005 15:12:45 -0500, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> > Why does wdired allow self-insertion?
> > Is there a good reason for it?
> > If not, it would seem to be a bug.
>
> The whole purpose of wdired is to allow you to edit your directory (file
> names, permissions, ...) directly with self-insert-command, so it's not at
> all a bug.
BTW, I noticed that wdired seems to be a bit unintuitive:
(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?
(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)?
(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).
Thoughts?
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2005-02-16 1:51 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 [this message]
2005-02-16 4:46 ` Stefan Monnier
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=fc339e4a050215175158c8775f@mail.gmail.com \
--to=snogglethorpe@gmail.com \
--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).