unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Per Starbäck" <per@starback.se>
To: David De La Harpe Golden <david@harpegolden.net>
Cc: emacs-devel@gnu.org
Subject: Re: Completion keys and rectangles
Date: Mon, 16 Nov 2009 23:14:02 +0100	[thread overview]
Message-ID: <912155b0911161414g5b514f0ft410f3e32a2ff25d4@mail.gmail.com> (raw)
In-Reply-To: <4B01C564.1010001@harpegolden.net>

2009/11/16 David De La Harpe Golden <david@harpegolden.net>:
> Per Starbäck wrote:
>>
>> M-TAB is very often used by the window manager.
>
> True, or at least M-<tab> is (what? See below),  but that's typically an
> easily reconfigured option in the window manager preferences (except on
> windows).

Yes, but most people don't change that. And certainly most new Emacs users
wouldn't want to change something they already are used to just to accomodate
to a "new" program they are trying out.

>> What do you think is the best solution to the window mangers vs.
>> completion in emacs problem? Would it be better if
>> key-description described M-TAB as ESC TAB or C-M-i if there is reason
>> to think M-TAB won't work?
>
> M-TAB pretty much /is/ emacs saying M-C-i

Yes, but how key-description describes it can change what keys users
actually press.
OK. I should have written "there is reason to think <M-tab> won't work".

>> Would it be good to have an  alternative key for M-TAB?
>
> I tend to view C-M-i (M- C-i) /as/ the memorable alternative to M-TAB.

It's not memorable for most new users. But maybe there is nothing
better left to use.
Then I think it would be good if key-description avoided description
that might lead
people to press combinations of keys that won't work at least. (Just
like it's good that

  backward-kill-sexp is on ESC <C-delete>, ESC <C-backspace>

doesn't mention <C-M-delete> or <C-M-backspace>...

> Showing my age I guess, but this was once something "everyone knew" in
> computing:
>
> ASCII TAB = 9.   9 + 64 = 73. 73 = ASCII I
> ASCII BS  = 8.   8 + 64 = 72. 72 = ASCII H
> ASCII ESC = 27. 27 + 64 = 91. 91 = ASCII [
>
> So, ^I for TAB, ^H for backspace, ^[ for escape etc.

Sure, but I don't like that to be prerequisite knowledge for using Emacs.




      reply	other threads:[~2009-11-16 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 19:58 Completion keys and rectangles Per Starbäck
2009-11-16 21:29 ` Drew Adams
2009-11-16 21:32 ` Stefan Monnier
2009-11-17  4:32   ` Miles Bader
2009-11-16 21:34 ` David De La Harpe Golden
2009-11-16 22:14   ` Per Starbäck [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

  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=912155b0911161414g5b514f0ft410f3e32a2ff25d4@mail.gmail.com \
    --to=per@starback.se \
    --cc=david@harpegolden.net \
    --cc=emacs-devel@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).