From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: `k' in Dired with inserted subdirectories.
Date: Thu, 15 Jul 2004 16:16:59 -0500 (CDT) [thread overview]
Message-ID: <200407152116.i6FLGxM07737@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1BkoT4-0004Dj-Du@fencepost.gnu.org> (message from Richard Stallman on Wed, 14 Jul 2004 14:26:58 -0400)
Richard Stallman wrote:
If you use this command with a prefix argument to kill the
line for a subdirectory, and you've dispayed the subdirectory
contents in the buffer with \\[dired-insert-subdir], it kills
the subdirectory's lines too.
"with \\[dired-insert-subdir]" is a more precise and clear way to identify
the case in question than any description could be.
(This concerns the `dired-do-kill-lines' docstring.)
I have two problems with the above:
"the line for a subdirectory" could be misunderstood as the
subdirectory header line and "\\[dired-insert-subdir]" is going to
come out as `M-x dired-insert-subdir', unless C-h f was issued from a
Dired buffer. This might look cryptic to non-Elisp users, thinking of
this as `i'. \\<dired-mode-map>\\[dired-insert-subdir] is going to
come out worse if dired is not yet loaded.
What about:
If you use this command with a prefix argument to kill the line for
a file that is a directory, which the Dired buffer also displays as
a subdirectory, then it deletes that subdirectory from the buffer
as well.
next prev parent reply other threads:[~2004-07-15 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 19:55 `k' in Dired with inserted subdirectories Luc Teirlinck
2004-07-13 20:19 ` Luc Teirlinck
2004-07-13 20:43 ` Luc Teirlinck
2004-07-14 18:26 ` Richard Stallman
2004-07-15 21:16 ` Luc Teirlinck [this message]
2004-07-16 16:08 ` Richard Stallman
2004-07-16 16:57 ` Luc Teirlinck
2004-07-18 7:18 ` Richard Stallman
2004-07-15 21:19 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2004-06-07 2:06 Luc Teirlinck
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=200407152116.i6FLGxM07737@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@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).