unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: PPAATT@aol.com
Cc: emacs-devel@gnu.org, Kai.Grossjohann@CS.Uni-Dortmund.DE
Subject: across terminals
Date: Wed, 24 Apr 2002 09:01:57 EDT	[thread overview]
Message-ID: <170.ca25380.29f806c5@aol.com> (raw)

> Date: 4/20/02 11:28:15 AM MDT
> From: rms@gnu.org (Richard Stallman)
...
> Since such characters are not available
> on all terminals, ...
> People won't want to use these keys
> in major modes or minor modes
> meant for general use.

I remain mystified by this concise statement,
but I've thought up a new way to interpret it ...

A quick glance thru:

        http://www.google.com/search?q=iso+646+vs+ascii

in particular:

        http://www.cs.tut.fi/~jkorpela/chars.html#646
        http://pdc.ro.nu/teletext.html

suggests that keyboards designed by ISO 646 folk
might have keys labelled with the "invariant set" of
printable US Ascii minus the thirteen chars
# $ @ [ \ ] ^ _ ` { | } ~
(i.e.  x  23 24  40  5B 5C 5D 5E 5F 60  7B 7C 7D 7E). 

So across Europe & relations maybe we face
"not available on all terminals" issues
in the default Emacs keymap with the "C-c letter"
concept we have been elucidating in our thread
titled "bindings reserved for users" but then also with:

set-mark-command is on C-@, C-SPC
key ESC is on C-[
abort-recursive-edit is on C-]
toggle-input-method is on C-\
undo C-_, C-/

ispell-word M-$
mark-word is on M-@
delete-horizontal-space is on M-\
delete-indentation is on M-^
tmm-menubar is on M-`
backward-paragraph is on C-up, M-{
shell-command-on-region is on M-|
forward-paragraph is on C-down, M-}
not-modified is on M-~

Fun to see how many of these we have
(and have not) already bound to alternate
key sequences, not to mention mouse actions etc.

I remember in particular that C-h t help-with-tutorial
bemoans the difficulty of finding locally how to undo,
hence we have C-x u advertised-undo (also known as
the undo that C-h w undo does Not advertise).

Pat LaVarre

             reply	other threads:[~2002-04-24 13:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 13:01 PPAATT [this message]
2002-04-25  6:06 ` across terminals Richard Stallman
2002-04-25 11:20   ` Eli Zaretskii
2002-04-25 11:31     ` Stephen J. Turnbull
2002-04-26  1:32       ` Miles Bader
2002-04-25 15:04     ` Localization: keyboards and messages (Re: across terminals) Karl Eichwalder
2002-04-25 18:29       ` Pavel Janík
2002-04-26 10:25         ` Stephen J. Turnbull
2002-04-26 17:38         ` Richard Stallman
2002-04-26 18:06           ` Karl Eichwalder
2002-04-28 15:13             ` Eli Zaretskii
2002-04-25 20:45     ` across terminals Paul Eggert
2002-04-26  3:18     ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-04-26 13:51 PPAATT
2002-04-26 14:18 ` Stefan Monnier
2002-04-26 16:37   ` Eli Zaretskii
2002-04-26 14:25 ` Kai Großjohann
2002-04-26 15:44 PPAATT
2002-04-26 16:47 ` Eli Zaretskii

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=170.ca25380.29f806c5@aol.com \
    --to=ppaatt@aol.com \
    --cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
    --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).