unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jussi Piitulainen <jpiitula@ling.helsinki.fi>
Subject: Re: Emacs on OS X - configuration package
Date: 02 Mar 2004 22:04:01 +0200	[thread overview]
Message-ID: <qotvflnrp72.fsf@venus.ling.helsinki.fi> (raw)
In-Reply-To: %i51c.103949$4o.121381@attbi_s52

videoxfer writes:
> Jussi Piitulainen wrote:
>> So if you type `C-h c opt-u' it both says something like "M-u runs
>> the command upcase-word" and waits for the next keypress?
> 
> If you type 'C-h c opt-u' it does nothing, since it's waiting for

I see it now. If you type it, that happens; if I type it, I get the
response "M-u runs ...". We have different keyboards. See below.

>> Then you may have option as meta and M-u as a prefix key. 
> 
> Afaik emacs knows nothing about prefix keys; that's a mac thing.  I
> don't think the standard emacs key processor even _sees_ the initial
> opt-u.

(I thought it would have been a prefix in the way that C-x and C-c
are, an Emacs thing. I understand now.)

>> You don't seem to get what you bargained for, if simply pressing
>> opt-u does not insert a character.
> 
> Do you run any form of macos?  Opt-u would never insert anything.
> It's a prefix character that adds umlaut to whatever you type next
> (if what you type next can take an umlaut).  Exactly the same thing
> happens in carbon emacs, so I get exactly what I'm paying for.

I run Mac OS X 10.3.2, Panther, and opt-u usually inserts u-umlaut. In
Carbon Emacs with opt as meta it upcases a word. I don't use it much
either, but I use M-c and M-l, and for me those are a similar case.

Finnish keyboards have ordinary keys for what you call a-umlaut and
o-umlaut, and for a-with-ring-above, and there is a separate prefix
key that serves as umlaut/dieresis, circumflex and tilde prefix, and
another prefix key that gives grave and acute accents. The latter two
behave like your opt-u. Our opt-u is not a prefix key.

Different hardware, different problems. That's why we had difficulty
understanding each other, but I hope it's clear now.

  reply	other threads:[~2004-03-02 20:04 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-27 21:37 Emacs on OS X - configuration package David Reitter
2004-02-28 19:50 ` Arjan Bos
2004-02-29  4:39 ` Stefan Monnier
2004-02-29  5:21   ` Tim McNamara
2004-02-29 23:08     ` Stefan Monnier
2004-03-01  2:19       ` Tim McNamara
2004-03-01 18:30         ` Stefan Monnier
2004-03-01 21:55           ` videoxfer
2004-03-01 23:03             ` Tim McNamara
2004-03-01 23:01           ` Tim McNamara
2004-03-02 15:13             ` Stefan Monnier
2004-02-29 13:53   ` videoxfer
2004-02-29 23:18     ` Stefan Monnier
2004-03-01 13:36       ` videoxfer
2004-03-01 18:37         ` Stefan Monnier
2004-03-01  9:45     ` Piet van Oostrum
2004-03-01 12:17       ` Jussi Piitulainen
2004-03-01 13:43       ` videoxfer
2004-03-01 14:47         ` Jussi Piitulainen
2004-03-01 21:50           ` videoxfer
2004-03-02 15:04             ` Jussi Piitulainen
2004-03-02 19:32               ` videoxfer
2004-03-02 20:04                 ` Jussi Piitulainen [this message]
2004-03-03  0:03                   ` videoxfer
2004-03-01 23:41         ` David Steuber
2004-03-02 12:30           ` videoxfer
2004-03-02 15:17           ` Stefan Monnier

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=qotvflnrp72.fsf@venus.ling.helsinki.fi \
    --to=jpiitula@ling.helsinki.fi \
    /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.
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).