From: Howard Melman <hmelman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Michael Albinus <michael.albinus@gmx.de>, emacs-devel@gnu.org
Subject: Re: Introducing thread-safe Tramp
Date: Mon, 6 Aug 2018 11:52:12 -0400 [thread overview]
Message-ID: <6FE4BF06-5CD2-49B1-AC7F-F8BA49F09254@gmail.com> (raw)
In-Reply-To: <8476cec3-45ab-486b-854b-fe045fbff902@default>
> On Aug 6, 2018, at 10:52 AM, Drew Adams <drew.adams@oracle.com> wrote:
>
>>> My sense is that the proposed C-x & is a prefix, because it
>>> is used before another key sequence. It is not an argument
>>> because it doesn't affect the functions' argument list the
>>> way C-u does.
>>> Maybe the term should be "prefix sequence"?
>
>> I like this proposal. "Prefix key sequence" would be more precise, but
>> it doesn't read fluid. If there isn't any objection over the next week,
>> I'll apply your wording.
>
> Please don't.
>
> This is _not_ a prefix key. A key is a key sequence. A prefix key is a key sequence that is a prefix of a larger key sequence. But in Emacs a prefix key also has the specific meaning of a key sequence that is bound to a keymap. `C-x &' is not bound to a keymap, and is thus not a prefix key (sequence).
>
> Until and unless we really do decide to baptize this and document it, please just what RMS suggested: don't call it anything. Certainly please do not call it just a "prefix" or a "prefix key (sequence)".
Having reread the Keys section of the Emacs manual I see your objection. Since "key" is short for "key sequence", then indeed it's not a "prefix key (sequence)" or a "(prefix key) sequence". My intention was to read it as "prefix (key sequence)", as something that comes before a key sequence, though clearly the ambiguity is an issue.
> What is it a prefix of? A prefix is part of what it is a prefix of.
It's a prefix of a key sequence, and it is a key sequence itself ("a sequence of one or more input events is is meaningful as a unit"). It's kind of a "complete key" ("a key sequence [that] invokes a command"), though it's a "complete key" that needs more. Maybe it's a "semi-complete key" as something between the existing terms "complete key" and "prefix key" and the full sequence C-x & C-x C-f is still a complete key sequence.
As you pointed out, technically C-u isn't a prefix key because it calls the command universal-argument, maybe it also is a semi-complete key. (Though clearly it would always be more useful to describe C-u as beginning a prefix argument).
>>> Wasn't there are a proposal at one point to do something
>>> similar for C-x 4 and C-x 5 so that there didn't have to be
>>> -other-window and -other-frame variants of so many
>>> commands?
>>
>> I'm not aware of such a proposal (which only means that my memory is
>> bad), but it makes sense.
>
> I believe he's thinking of Stefan's wish to have prefix keys `C-x 4' and `C-x 5' work automatically, without defining separate other-window and other-frame commands. That's something completely different. Let's please not let this thread wander farther than it already has.
Yes, that's what I was thinking of. I'm not sure if there was a proposed implementation or if it was similar to this one, but the usage struck me as similar. Since this is a proposal to name a new kind of thing, it didn't feel like wandering to to test it against other similar kinds of proposals to see if it would cover them as well.
Howard
next prev parent reply other threads:[~2018-08-06 15:52 UTC|newest]
Thread overview: 125+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 15:58 Introducing thread-safe Tramp Michael Albinus
2018-07-23 16:06 ` Eli Zaretskii
2018-07-23 16:11 ` Michael Albinus
2018-07-23 16:37 ` Eli Zaretskii
2018-07-23 16:55 ` Michael Albinus
2018-07-24 8:25 ` Ken Raeburn
2018-07-24 12:52 ` Michael Albinus
2018-07-24 13:20 ` martin rudalics
2018-07-25 9:51 ` Michael Albinus
2018-07-25 14:44 ` Eli Zaretskii
2018-07-25 17:32 ` Eli Zaretskii
2018-07-25 17:53 ` Michael Albinus
2018-07-26 7:56 ` martin rudalics
2018-07-26 8:14 ` Michael Albinus
2018-07-26 9:02 ` martin rudalics
2018-07-26 17:24 ` Eli Zaretskii
2018-07-24 15:06 ` Drew Adams
2018-07-25 9:46 ` Michael Albinus
2018-07-25 11:54 ` Phil Sainty
2018-07-25 12:14 ` Andreas Schwab
2018-07-25 13:02 ` Michael Albinus
2018-07-25 13:31 ` Robert Pluim
2018-07-27 15:05 ` Michael Albinus
2018-08-01 16:27 ` Robert Pluim
2018-08-01 21:28 ` Michael Albinus
2018-07-27 19:04 ` Filipp Gunbin
2018-07-27 19:42 ` Michael Albinus
2018-07-28 0:14 ` Filipp Gunbin
2018-07-28 7:01 ` Eli Zaretskii
2018-07-28 9:48 ` Michael Albinus
2018-07-29 18:29 ` Drew Adams
2018-07-30 8:44 ` Michael Albinus
2018-07-30 14:23 ` Eli Zaretskii
2018-08-04 12:47 ` Michael Albinus
2018-08-04 12:49 ` Michael Albinus
2018-08-04 15:00 ` Eli Zaretskii
2018-08-04 15:12 ` Michael Albinus
2018-08-04 15:43 ` Eli Zaretskii
2018-08-04 15:58 ` Michael Albinus
2018-08-04 16:11 ` Eli Zaretskii
2018-08-04 16:18 ` Michael Albinus
2018-08-04 16:58 ` Eli Zaretskii
2018-08-04 17:29 ` Michael Albinus
2018-08-04 18:34 ` Eli Zaretskii
2018-08-05 9:51 ` Michael Albinus
2018-08-05 15:06 ` Eli Zaretskii
2018-08-06 10:54 ` Michael Albinus
2018-08-06 14:55 ` Drew Adams
2018-08-06 15:25 ` C-x & (was: Introducing thread-safe Tramp) Michael Albinus
2018-08-06 17:59 ` Drew Adams
2018-08-06 19:17 ` C-x & Michael Albinus
2018-08-06 20:57 ` Drew Adams
2018-08-06 23:16 ` Drew Adams
2018-08-07 7:05 ` Michael Albinus
2018-08-07 7:01 ` Michael Albinus
2018-08-06 15:48 ` Introducing thread-safe Tramp Stefan Monnier
2018-08-06 15:24 ` Eli Zaretskii
2018-08-06 15:29 ` C-x & (was: Introducing thread-safe Tramp) Michael Albinus
2018-08-06 18:32 ` Introducing thread-safe Tramp Filipp Gunbin
2018-08-07 14:20 ` Michael Albinus
2018-08-07 14:53 ` Stephen Berman
2018-08-07 15:02 ` Robert Pluim
2018-08-07 15:06 ` Stephen Berman
2018-08-07 16:00 ` Michael Albinus
2018-08-07 15:58 ` Michael Albinus
2018-08-07 15:33 ` Drew Adams
2018-08-07 16:01 ` Michael Albinus
2018-08-07 16:12 ` Drew Adams
2018-08-07 16:18 ` Michael Albinus
2018-08-07 15:56 ` Michael Albinus
2018-08-07 16:24 ` Eli Zaretskii
2018-08-07 16:30 ` Michael Albinus
2018-08-07 15:56 ` Eli Zaretskii
2018-08-07 16:09 ` Michael Albinus
2018-08-07 16:23 ` Drew Adams
2018-08-07 16:46 ` Drew Adams
2018-08-07 16:54 ` Michael Albinus
2018-08-07 17:11 ` Eli Zaretskii
2018-08-08 8:18 ` Michael Albinus
2018-08-08 19:01 ` Filipp Gunbin
2018-08-08 20:52 ` Stefan Monnier
2018-08-08 20:54 ` Drew Adams
2018-08-04 15:42 ` Drew Adams
2018-08-04 15:56 ` Michael Albinus
2018-08-04 16:16 ` Drew Adams
2018-08-04 17:36 ` Michael Albinus
2018-08-04 22:41 ` Drew Adams
2018-08-05 10:03 ` Michael Albinus
2018-08-04 16:08 ` Eli Zaretskii
[not found] ` <<7c28f9d8-e2bb-4778-ab92-92707f12718f@default>
[not found] ` <<837el6t8r3.fsf@gnu.org>
2018-08-04 16:27 ` Drew Adams
2018-08-04 16:59 ` Eli Zaretskii
2018-08-05 1:59 ` Richard Stallman
2018-08-05 10:07 ` Michael Albinus
2018-08-06 1:20 ` Richard Stallman
2018-08-05 15:36 ` Drew Adams
2018-08-06 4:21 ` Howard Melman
2018-08-06 4:39 ` Werner LEMBERG
2018-08-06 8:07 ` Michael Albinus
2018-08-06 13:50 ` Clément Pit-Claudel
2018-08-06 14:57 ` Drew Adams
2018-08-06 14:52 ` Drew Adams
2018-08-06 15:52 ` Howard Melman [this message]
2018-08-06 15:46 ` Stefan Monnier
2018-07-27 21:08 ` Eli Zaretskii
2018-07-28 0:24 ` Filipp Gunbin
2018-07-28 9:02 ` Michael Albinus
2018-07-27 19:19 ` Dmitry Gutov
2018-07-27 19:32 ` Michael Albinus
2018-07-27 19:40 ` Yuri Khan
2018-07-27 19:43 ` Michael Albinus
2018-07-27 20:09 ` Yuri Khan
2018-07-27 21:15 ` Eli Zaretskii
2018-07-28 9:11 ` Michael Albinus
2018-07-28 9:57 ` Eli Zaretskii
2018-07-28 10:04 ` Michael Albinus
2018-07-27 22:57 ` Dmitry Gutov
2018-07-27 22:59 ` Dmitry Gutov
2018-07-28 9:18 ` Michael Albinus
2018-07-28 9:36 ` Dmitry Gutov
2018-07-28 9:51 ` Michael Albinus
2018-07-28 9:59 ` Dmitry Gutov
2018-07-28 10:13 ` Michael Albinus
2018-07-28 22:20 ` Dmitry Gutov
2018-07-29 9:54 ` Michael Albinus
2018-08-08 16:49 ` Dmitry Gutov
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=6FE4BF06-5CD2-49B1-AC7F-F8BA49F09254@gmail.com \
--to=hmelman@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.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).