all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: PPAATT@aol.com
Cc: rms@gnu.org, emacs-devel@gnu.org, eliz@is.elta.co.il
Subject: Re: across terminals
Date: Fri, 26 Apr 2002 11:44:16 EDT	[thread overview]
Message-ID: <86.19bc6735.29facfd0@aol.com> (raw)

> Subj:  Re: across terminals
> Date: 4/26/02 8:26:19 AM Mountain Daylight Time
> From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
...
> If I were you, I'd just bind C-c <X> where <X> is a non-ascii
> character.  Then [ perhaps via C-h n view-emacs-news]
> you read the NEWS files for each new Emacs, in the
> unlikely event that future versions will bind such keys.

Eh?

If the GNU Emacs developers do mean to support binding shifted uses of keys 
that conventionally self-insert chars outside of US-Ascii ... then I should 
consider all of those key sequences reserved for the user?  Not just C-c x 
but also C-x, where by x we mean the unshifted but not-US-Ascii key?

Or I should consider all of these keys reserved for Emacs?

Or else by "what occurs commonly works well; what occurs less commonly works 
less well", when I see the doc not discuss this issue I should clue in and 
work harder to imitate an American at the keyboard?

Pat LaVarre

             reply	other threads:[~2002-04-26 15:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 15:44 PPAATT [this message]
2002-04-26 16:47 ` across terminals Eli Zaretskii
  -- 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-24 13:01 PPAATT
2002-04-25  6:06 ` 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 20:45     ` Paul Eggert
2002-04-26  3:18     ` Richard Stallman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86.19bc6735.29facfd0@aol.com \
    --to=ppaatt@aol.com \
    --cc=eliz@is.elta.co.il \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.