unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: lekktu@gmail.com, spacibba@aol.com, emacs-devel@gnu.org
Subject: Re: Tab bar tabs landed on master
Date: Sun, 06 Oct 2019 22:38:23 +0300	[thread overview]
Message-ID: <838spx1x74.fsf@gnu.org> (raw)
In-Reply-To: <87imp1k79d.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 06 Oct 2019 22:23:42 +0300)

> From: Juri Linkov <juri@linkov.net>
> Cc: spacibba@aol.com,  lekktu@gmail.com,  emacs-devel@gnu.org
> Date: Sun, 06 Oct 2019 22:23:42 +0300
> 
> > Does it mean the tab-bar related "C-x 6" prefix conflicts with 2C?  If
> > so, perhaps we should use "C-x 7" instead, as long as the genie is not
> > far from the bottle.
> 
> "C-x 6" is the perfect prefix for tab commands because it's easier to
> remember as continuation of the sequence with window prefix "C-x 4"
> and frame prefix "C-x 5":

I agree, but if "C-x 6" is already used, it's taken.  Is it such a
catastrophe to use "C-x 7"?

> > I'd like to avoid backward-incompatible changes if possible.
> 
> Actually it's not quite backward-incompatible because it's still
> available after loading two-column.el.

And then the tab-bar commands cannot be invoked via "C-x 6".  That's
very confusing, I think.  We should avoid a situation where 2 core
packages fight each other over key bindings.

> Also please read this comment in two-column.el that admits it's not mnemonic:
> 
>   ;; This one is for historical reasons and simple keyboards, it is not
>   ;; at all mnemonic.  All usual sequences containing 2 were used, and
>   ;; f2 could not be set up in a standard way under Emacs 18.
>   (global-set-key "\C-x6" '2C-command)

It says nothing about whether people still use it, nor what exactly
"simple keyboards" means.  Sorry, I still think there's a problem
here.



  reply	other threads:[~2019-10-06 19:38 UTC|newest]

Thread overview: 82+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-01 20:17 Tab bar tabs landed on master Juri Linkov
2019-10-01 21:43 ` Juanma Barranquero
2019-10-01 22:28   ` Juri Linkov
2019-10-01 22:35     ` Juanma Barranquero
2019-10-01 23:27     ` Ergus
2019-10-03 22:10       ` Juri Linkov
2019-10-05 21:55       ` Juri Linkov
2019-10-06 17:13         ` Eli Zaretskii
2019-10-06 18:48           ` Juri Linkov
2019-10-06 19:12             ` Eli Zaretskii
2019-10-06 19:23               ` Juri Linkov
2019-10-06 19:38                 ` Eli Zaretskii [this message]
2019-10-06 19:53                   ` Juri Linkov
2019-10-07 17:18                     ` Eli Zaretskii
2019-10-07 17:31                       ` Lars Ingebrigtsen
2019-10-07 17:49                       ` Ergus
2019-10-06 21:11                   ` Stefan Monnier
2019-10-06 21:27                     ` Juri Linkov
2019-10-06 22:53                       ` Stefan Monnier
2019-10-06 22:58                       ` add Tab to ELPA other-frame-window Stephen Leake
2019-10-07 16:07                         ` Eli Zaretskii
2019-10-07 20:14                         ` Juri Linkov
2019-10-08  7:48                           ` Eli Zaretskii
2019-10-10 22:46                             ` Juri Linkov
2019-10-11  8:10                               ` Eli Zaretskii
2019-10-19 22:07                                 ` Juri Linkov
2019-10-20  6:24                                   ` Eli Zaretskii
2019-10-20 17:37         ` Tab bar tabs landed on master Juri Linkov
2019-10-23 20:54           ` Juri Linkov
2019-10-26 22:16             ` Juri Linkov
2019-10-27 23:05               ` Juri Linkov
2019-10-23 20:59         ` Juri Linkov
2019-11-01 23:13           ` Ergus
2019-11-02  7:20             ` Eli Zaretskii
2019-11-02 11:46               ` Ergus
2019-10-02  8:55     ` martin rudalics
2019-10-02 16:30       ` Juri Linkov
2019-10-02 15:03   ` Eli Zaretskii
2019-10-02 16:27     ` Juri Linkov
2019-10-02 17:07       ` Eli Zaretskii
2019-10-02 19:55         ` Juri Linkov
2019-10-05 14:33           ` Eli Zaretskii
2019-10-05 22:07             ` Juri Linkov
2019-10-06 17:06               ` Eli Zaretskii
2019-10-07 19:15                 ` Juri Linkov
2019-10-07 19:23                   ` Eli Zaretskii
2019-10-09 10:51                     ` Eli Zaretskii
2019-10-09 18:43                       ` Juri Linkov
2019-10-09 18:59                         ` Eli Zaretskii
2020-01-11 23:57                           ` Juri Linkov
2020-01-12  3:28                             ` Eli Zaretskii
2020-01-12 23:25                               ` Juri Linkov
2020-01-13 16:49                                 ` Eli Zaretskii
2020-01-13 23:35                                   ` Juri Linkov
2020-04-18 23:56                                     ` Juri Linkov
2020-04-19 14:06                                       ` Eli Zaretskii
2019-11-14 23:37                       ` Juri Linkov
2019-11-15  8:21                         ` Eli Zaretskii
2019-10-03  8:16         ` martin rudalics
2019-10-03  8:15       ` martin rudalics
2019-10-03  3:40 ` Stefan Kangas
2019-10-03  9:02 ` Robert Pluim
2019-10-07 13:15 ` Stefan Kangas
2019-10-07 13:21 ` Stefan Kangas
2019-10-07 15:53   ` Ergus
2019-10-07 20:23     ` Juri Linkov
2019-10-07 20:58       ` Ergus
2019-10-07 21:48       ` Zach Pearson
2019-10-07 22:29         ` Juri Linkov
2019-10-08 14:29           ` Eli Zaretskii
2019-10-09 22:43             ` Juri Linkov
2019-10-10  7:52               ` Eli Zaretskii
2019-10-07 16:40   ` Eli Zaretskii
2019-10-07 20:19   ` Juri Linkov
2019-10-08  7:52     ` Eli Zaretskii
2019-10-20 22:39   ` Juri Linkov
2019-10-20 23:06     ` Ergus
2019-10-21  6:54       ` Eli Zaretskii
2019-10-21  6:43     ` Eli Zaretskii
2019-10-21 21:40       ` Juri Linkov
  -- strict thread matches above, loose matches on Subject: below --
2019-10-03 11:23 Andrii Kolomoiets
2019-10-03 12:19 ` Robert Pluim

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=838spx1x74.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=lekktu@gmail.com \
    --cc=spacibba@aol.com \
    /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).