From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@stupidchicken.com>
Cc: 'Juri Linkov' <juri@jurta.org>, emacs-devel@gnu.org
Subject: RE: Emacs manual nodes about text replacement
Date: Sun, 16 Nov 2008 23:22:02 -0800 [thread overview]
Message-ID: <002901c94885$30274520$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <87zljz9kfy.fsf@cyd.mit.edu>
> >> Recently Yidong rewrote many parts of the documentation, so
> >> please refer to a newer version.
> >
> > Looking at the CVS version today, it seems to reflect the same
> > structure.
>
> Your opening statement
> The main node, Replace, starts by saying that you don't use global
> search-and-replace that much in Emacs.
> is not true, in the latest version of the manual anyway.
Yes, this opening sentence:
Global search-and-replace operations are not needed
often in Emacs, but they are available.
was changed to this in Emacs 23 (good):
Emacs provides several commands for performing
search-and-replace operations.
So you can skip that first statement I made. AFAICT, the rest of my message is
still pertinent.
The main points: The presentation is backward and misleading. Emphasize
query-replace, not unconditional replace. Present the information top-down, not
bottom up. Give an overview of what you can do before the details about how to
do it. Make it clear that all of the fancy stuff applies to query-replace too,
not just to unconditional replace.
Please see the original message for details.
prev parent reply other threads:[~2008-11-17 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 18:43 Emacs manual nodes about text replacement Drew Adams
2008-11-16 23:27 ` Juri Linkov
2008-11-17 1:36 ` Drew Adams
2008-11-17 2:04 ` Chong Yidong
2008-11-17 7:22 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002901c94885$30274520$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.