unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
Cc: lute.kamstra.lists@xs4all.nl, emacs-devel@gnu.org
Subject: Re: etc/refcard.tex update.
Date: Sat, 09 Jul 2005 23:57:29 +0300	[thread overview]
Message-ID: <87u0j3qzq7.fsf@jurta.org> (raw)
In-Reply-To: <E1Dqdxr-0004a4-Ps@fencepost.gnu.org> (Richard M. Stallman's message of "Thu, 07 Jul 2005 17:31:23 -0400")

>     2. In the section `Getting Help' keys `C-x 1' and `C-M-v' in
>
>     \key{remove help window}{C-x 1}
>     \key{scroll help window}{C-M-v}
>
>     don't work after typing C-h or F1 that were suggested to type
>     in the beginning of the same section.
>
> I don't understand the problem.  What is the full scenario?

I meant that `C-h ? C-M-v' doesn't work.  But don't worry, refcard
is not a place for such nuances, and the phrase `follow the directions'
is sufficient.

>     Currently such highly related operations as Search and Replace are
>     described on different refcard pages.  Wouldn't it be better to move
>     `Incremental Search' down and place it immediately before `Query
>     Replace'?
>
> Having them near each other would be better.  However, searching is
> pretty important, so perhaps moving it later is a change for the
> worse.  I am not sure which way is better overall--it is not
> self-evident.  One needs to look at both versions printed out.

As Lute pointed out, on a 2 column refcard they are side by side,
so let's not move them.

What still bothers me in `Query Replace' is that `C-M-%' is not
mentioned.  Lute added a comment saying that it can't be typed on
consoles.  But is it a reason for majority of users (X, xterm,
MSWindows, MacOS) to not know about `C-M-%'?  Users who can't type
`C-M-%' on consoles, have other means (manuals, help facility) to find
a replacement command.

-- 
Juri Linkov
http://www.jurta.org/emacs/

  reply	other threads:[~2005-07-09 20:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-06 10:21 etc/refcard.tex update Lute Kamstra
2005-07-06 21:44 ` Juri Linkov
2005-07-07  8:10   ` Lute Kamstra
2005-07-06 21:45 ` Juri Linkov
2005-07-06 23:34   ` Andreas Schwab
2005-07-07  6:02     ` Juri Linkov
2005-07-07  8:46       ` Andreas Schwab
2005-07-07  8:32   ` Lute Kamstra
2005-07-09 20:57     ` Juri Linkov
2005-07-10  7:51       ` Lute Kamstra
2005-07-11  0:05         ` Juri Linkov
2005-07-11 16:53           ` Richard M. Stallman
2005-07-11  5:34         ` Richard M. Stallman
2005-07-10 17:35       ` Richard M. Stallman
2005-07-10 18:30         ` David Kastrup
2005-07-07 21:31   ` Richard M. Stallman
2005-07-09 20:57     ` Juri Linkov [this message]
2005-07-10 17:35       ` Richard M. Stallman
2005-07-10 23:48         ` Juri Linkov
2005-07-11  8:14           ` Kim F. Storm
2005-07-12  6:38             ` Juri Linkov
2005-07-12 11:19               ` Kim F. Storm
2005-07-13  5:17               ` Richard M. Stallman

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=87u0j3qzq7.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=lute.kamstra.lists@xs4all.nl \
    /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).