From: Kaushal <kaushal.modi@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: C-x 8 shorthands for ≤ and ≥
Date: Mon, 11 May 2015 14:57:44 +0000 [thread overview]
Message-ID: <CAFyQvY3_mMvUXQ28ZzQDveaC2sAjvn=1CHNhxVG7Br48WNLYfg@mail.gmail.com> (raw)
In-Reply-To: <jwvr3qn182o.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
Thanks. I personally never needed to use ». But for someone already using
that, the ">>" binding is pretty intuitive (and same applies to "<<").
I'd vote for that change to happen so that we can have ">=" and "<="
bindings, and others beginning with "<" and ">" in future.
On Mon, May 11, 2015 at 10:53 AM Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> >> ("_<" . [?≤])
> >> ("_>" . [?≥])
> >> Can the bindings be changed to these:
> >> ("<=" . [?≤])
> >> (">=" . [?≥])
>
> FWIW, I agree.
>
> > ">" is already bound to »
> > "<" is already boudn to «
>
> ">>" and "<<" would seem to be better choices.
> The shorter `C-x <' used so far made sense when we restricted C-x 8 to
> something like Latin-1, but if we want to extend coverage, I don't think
> we can afford such short bindings.
>
>
> Stefan
>
[-- Attachment #2: Type: text/html, Size: 1754 bytes --]
next prev parent reply other threads:[~2015-05-11 14:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 13:22 C-x 8 shorthands for ≤ and ≥ Kaushal
2015-05-11 13:29 ` Kaushal
2015-05-11 14:53 ` Stefan Monnier
2015-05-11 14:57 ` Kaushal [this message]
2015-05-11 15:08 ` Artur Malabarba
2015-05-11 15:24 ` Marcin Borkowski
2015-05-11 15:40 ` Yuri Khan
2015-05-11 15:46 ` Kaushal
2015-05-11 16:27 ` Artur Malabarba
2015-05-11 16:34 ` Rasmus
2015-05-11 16:54 ` Kaushal
2015-05-11 20:34 ` Marcin Borkowski
2015-05-11 22:13 ` Stefan Monnier
2015-05-11 22:33 ` C-x 8 shorthands for = and = Drew Adams
2015-05-12 14:14 ` C-x 8 shorthands for ≤ and ≥ Kaushal
2015-05-12 15:58 ` Kaushal
2015-05-11 18:26 ` Werner LEMBERG
2015-05-11 19:41 ` Kaushal
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='CAFyQvY3_mMvUXQ28ZzQDveaC2sAjvn=1CHNhxVG7Br48WNLYfg@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).