From: Werner LEMBERG <wl@gnu.org>
Cc: Kai.Grossjohann@CS.Uni-Dortmund.DE, ats@acm.org, emacs-devel@gnu.org
Subject: Re: Insert Euro symbol
Date: Sun, 05 May 2002 08:39:41 +0200 (CEST) [thread overview]
Message-ID: <20020505.083941.77253523.wl@gnu.org> (raw)
In-Reply-To: <200205041502.g44F2VW01267@aztec.santafe.edu>
> I started writing changes to add ways to enter some additional
> characters, shown below. But I have doubts about whether these
> sequences are good ones. They might be inconvenient.
A lot of them are inconvenient IMHO since they occur very frequently
e.g. in writing emails. What do you think about having sequences of
three characters? The first one is a kind of escape character, say,
`C-.', followed by your two-character sequences (or a one-character
sequence if that makes sense).
My comments below are only valid if you really want to add
two-character sequences. Otherwise, X compose sequences are probably
the best.
> + ("\"\"" ?¨)
This conflicts with many programming languages where you have to type
\\ regularly.
> + ("''" ?´)
Ditto.
> + (",," ?¸)
Ditto.
> + ("* " ? ) ; Non-breaking space
Hmm, has Emacs a feature to make non-breaking spaces visible?
> + ("+_" ?±)
I would rather use what the compose feature of X uses, namely `+-'.
> + ("-*" ?)
For most fonts, this is graphically the same as a normal hyphen.
Emacs should also provide a means to make them visually different.
> + ("2_" ?½)
> + ("4_" ?¼)
> + ("3_" ?¾)
I don't like to have the underscore in such sequences since it means
an additional keystroke. For my proposed three-character sequences,
a better choice would be `12', `14', and `34', respectively.
> + ("//" ?÷)
`//' is already in use. It produces `°'. I *hate* this one, since
typing URLs is a real pain. With my proposal, this could be come
`C-. o'.
Werner
next prev parent reply other threads:[~2002-05-05 6:39 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-02 13:19 Insert Euro symbol Kai Großjohann
2002-05-02 13:30 ` Alan Shutko
2002-05-02 13:43 ` Kai Großjohann
2002-05-02 15:12 ` Karl Eichwalder
2002-05-02 15:33 ` Kai Großjohann
2002-05-03 18:25 ` Richard Stallman
2002-05-03 19:59 ` Kai Großjohann
2002-05-04 15:02 ` Richard Stallman
2002-05-05 6:39 ` Werner LEMBERG [this message]
2002-05-06 6:24 ` Richard Stallman
2002-05-06 12:16 ` Werner LEMBERG
2002-05-07 4:58 ` Richard Stallman
2002-05-07 7:06 ` Werner LEMBERG
2002-05-08 13:58 ` Richard Stallman
2002-05-06 9:54 ` Kai Großjohann
2002-05-06 12:09 ` Werner LEMBERG
2002-05-05 23:18 ` Stefan Monnier
2002-05-02 13:44 ` Stefan Monnier
2002-05-02 16:06 ` Eli Zaretskii
2002-05-02 20:17 ` Miles Bader
2002-05-03 6:25 ` Eli Zaretskii
2002-05-03 10:48 ` Miles Bader
2002-05-04 6:06 ` Stephen J. Turnbull
2002-05-04 11:52 ` Miles Bader
2002-05-05 5:34 ` Richard Stallman
2002-05-05 11:52 ` Kai Großjohann
2002-05-06 6:24 ` Richard Stallman
2002-05-06 9:50 ` Kai Großjohann
2002-05-06 19:32 ` Richard Stallman
2002-05-07 8:25 ` Kai Großjohann
2002-05-08 13:58 ` Richard Stallman
2002-05-08 15:02 ` Kai Großjohann
2002-05-09 14:59 ` Richard Stallman
2002-05-12 12:21 ` Florian Weimer
2002-05-13 14:18 ` Richard Stallman
2002-05-13 14:28 ` Florian Weimer
2002-05-14 19:41 ` Richard Stallman
2002-05-08 13:58 ` Richard Stallman
2002-05-07 9:12 ` Miles Bader
2002-05-03 9:52 ` Kai Großjohann
2002-05-03 10:41 ` Eli Zaretskii
2002-05-03 11:24 ` Kai Großjohann
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=20020505.083941.77253523.wl@gnu.org \
--to=wl@gnu.org \
--cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
--cc=ats@acm.org \
--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 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.