unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: [OFFTOPIC] Re: Invoking a function from a list of functions
Date: Wed, 21 Nov 2018 10:05:25 -0500	[thread overview]
Message-ID: <jwvwop6lbst.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: 87sgzwl1fg.fsf@aminb.org

> Same with Lean: lean-mode comes with lean-input which is based on
> agda-input with minor changes, and it makes it /super/ convenient
> to insert commonly used unicode characters: \a for α, \b for β,
> a\1 for a₁, \and for ∧, \|- for ⊢, and hundreds more.  I’ve
> actually come to like lean-input so much that I’ve set it as my
> default-input-method so I can toggle it with C-\ and easily type
> unicode symbols whenever and wherever I want.

Maybe we should add a "math" input method along the lines of those
Agda/Lean input methods.  I currently use the TeX input method for such
purposes but it tends to be a bit more verbose than I like.

> It’s possible to change the input prefix from
> backslash to something else to avoid clashes when writing TeX¹.

In my experience (using the TeX input method when writing LaTeX),
I think the main problem with the clash on \ is that when the LaTeX
command I write has a valid prefix in the input method, the input method
rewrites that prefix.  If we could fix it so that "\b" inputs "β" but
"\beta" isn't rewritten to "βeta" then I might even be able to have \
play both roles without going bonkers.


        Stefan




  reply	other threads:[~2018-11-21 15:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3677.1541718983.1284.help-gnu-emacs@gnu.org>
2018-11-12  5:39 ` Invoking a function from a list of functions Rusi
2018-11-12 15:19   ` [OFFTOPIC] " Stefan Monnier
     [not found]   ` <mailman.3921.1542036006.1284.help-gnu-emacs@gnu.org>
2018-11-16  2:48     ` Rusi
2018-11-16 16:40       ` James K. Lowden
2018-11-17 15:59         ` Rusi
2018-11-19 22:23           ` James K. Lowden
2018-11-19 23:11             ` Stefan Monnier
2018-11-20  6:15               ` Amin Bandali
2018-11-21 15:05                 ` Stefan Monnier [this message]
2018-11-23  3:41                   ` Amin Bandali
     [not found]               ` <mailman.4291.1542694542.1284.help-gnu-emacs@gnu.org>
2018-11-28 14:14                 ` Rusi
2018-12-11 18:48                   ` Amin Bandali
     [not found]             ` <mailman.4280.1542669123.1284.help-gnu-emacs@gnu.org>
2018-11-28 14:10               ` Rusi
2018-11-28 16:31                 ` Eli Zaretskii
2018-11-28 18:15                   ` Yuri Khan
2018-11-28 18:57                     ` Eli Zaretskii
2018-11-28 19:08                       ` Yuri Khan
     [not found]                       ` <mailman.4820.1543432126.1284.help-gnu-emacs@gnu.org>
2018-11-29  5:37                         ` Rusi
2018-11-16 16:40       ` James K. Lowden
2018-11-16 17:15         ` Drew Adams

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=jwvwop6lbst.fsf-monnier+gmane.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@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.
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).