From: "Drew Adams" <drew.adams@oracle.com>
To: "'Andreas Schwab'" <schwab@suse.de>
Cc: bug-gnu-emacs@gnu.org
Subject: RE: node Subdirectories in Dired in Emacs manual
Date: Wed, 5 Mar 2008 07:13:15 -0800 [thread overview]
Message-ID: <001701c87ed3$704f65f0$0600a8c0@us.oracle.com> (raw)
In-Reply-To: <jeod9tsce4.fsf@sykes.suse.de>
> >> > This text in the node is misleading or unintelligible:
> >> >
> >> > If the subdirectory's contents are already present in the
> >> > buffer, the `i' command just moves to it.
> >> >
> >> > I tried `i' everywhere in the buffer, and it did nothing of the
> >> > kind...except if the cursor is over the subdir line of the parent
> >> > directory. That needs to be said.
> >>
> >> That's exactly what the preceding paragraph says.
> >
> > Not at all. Hitting `i' *WHERE*
>
> "on a line that describes a file which is a directory"
Which could also be interpreted to mean a subdir header line.
And the sentence "If the subdirectory's..." should not be in a separate
paragraph, especially if you expect someone to assume the same context (e.g.
location) for hitting `i'.
> > just moves to *WHERE*?
>
> "the subdirectory's contents"
That's not a place. The English and the logic are bad.
> Just as the paragraph says.
You seem interested in justifying, rather than learning.
Take it from a user: the text is not as clear as it should be. Or take it
from someone who has been writing, editing, and managing technical
documentation professionally for a couple decades. Or not - remain stubborn
and don't try to learn or improve. Your choice.
prev parent reply other threads:[~2008-03-05 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 23:53 node Subdirectories in Dired in Emacs manual Drew Adams
2008-03-05 0:51 ` Andreas Schwab
2008-03-05 3:19 ` Drew Adams
2008-03-05 10:17 ` Andreas Schwab
2008-03-05 15:13 ` Drew Adams [this message]
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='001701c87ed3$704f65f0$0600a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=schwab@suse.de \
/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).