From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 34784@debbugs.gnu.org
Subject: bug#34784: 26.1; Doc of pseudofunction key `<timeout>'
Date: Fri, 8 Mar 2019 09:20:19 -0800 (PST) [thread overview]
Message-ID: <f36457e6-0e75-4a6e-9aad-cb6bf2df1a46@default> (raw)
In-Reply-To: <<838sxp9u54.fsf@gnu.org>>
> > Anyway, back to the point of this bug report: How
> > is a user to know this info about `<timeout>',
> > without digging into the code?
>
> Why should they? This is an internal matter between CUA and itself, a
> detail of its implementation.
Huh? Why shouldn't they? If a user sees this help:
key binding
--- -------
C-c <timeout> copy-region-as-kill
and s?he wants to know how to invoke
`copy-region-as-kill' starting with prefix `C-c',
where is s?he supposed to turn for that info?
If this were "an internal matter between CUA and
itself" then `C-c C-h' wouldn't (and shouldn't)
show it to users.
next parent reply other threads:[~2019-03-08 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<247b0874-cbb1-40e1-996f-5f931c142616@default>
[not found] ` <<83imwta3t0.fsf@gnu.org>
[not found] ` <<b4181ab6-8e04-4851-b3cf-f63723ffcf6a@default>
[not found] ` <<838sxp9u54.fsf@gnu.org>
2019-03-08 17:20 ` Drew Adams [this message]
2019-03-08 18:51 ` bug#34784: 26.1; Doc of pseudofunction key `<timeout>' Eli Zaretskii
[not found] <<<247b0874-cbb1-40e1-996f-5f931c142616@default>
[not found] ` <<<83imwta3t0.fsf@gnu.org>
[not found] ` <<<b4181ab6-8e04-4851-b3cf-f63723ffcf6a@default>
[not found] ` <<<838sxp9u54.fsf@gnu.org>
[not found] ` <<f36457e6-0e75-4a6e-9aad-cb6bf2df1a46@default>
[not found] ` <<837ed99p36.fsf@gnu.org>
2019-03-08 19:39 ` Drew Adams
2019-03-08 19:48 ` Eli Zaretskii
2019-03-08 1:27 Drew Adams
2019-03-08 1:29 ` Drew Adams
2019-03-08 13:33 ` Eli Zaretskii
2019-03-08 16:52 ` Drew Adams
2019-03-08 17:02 ` Eli Zaretskii
2020-08-24 19:22 ` Stefan Kangas
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=f36457e6-0e75-4a6e-9aad-cb6bf2df1a46@default \
--to=drew.adams@oracle.com \
--cc=34784@debbugs.gnu.org \
--cc=eliz@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).