From: Lifepillar <lifepillar@lifepillar.me>
To: vim_use@googlegroups.com
Cc: bug-gnu-emacs@gnu.org,help-nano@gnu.org
Subject: Re: Neither Emacs nor Vim nor Nano handle ligature literal insertion well
Date: Sat, 3 Feb 2018 10:56:11 +0100 [thread overview]
Message-ID: <p540ru$7u0$1@blaine.gmane.org> (raw)
In-Reply-To: <CAHXt_SV2P_ieU+UNHx8QoGX9CfoT38BoO01u9Er4dVqqm2Bxyw@mail.gmail.com>
On 02/02/2018 23:31, Andrew Pennebaker wrote:
> Hello,
>
> I would really like convenient access to ligatures in my word processing
> software. Unfortunately, none of the major text editing applications
> appears to handle ligatures intelligently: Each of Emacs, Vim, Nano, MS
> Word, Google Drive, Libre Office, and InDesign type a dumb "ae" when the
> user presses the a and e keyboard keys, whereas historically this
> sequence is typically rendered with the ash æ rune.
>
> I am able to work around this limitation in most applications by
> configuring TextExpander (macOS, Windows) or autokey (Linux) to match
> the keyboard sequence "ae" and replace this with "æ". This allows most
> UTF-8 compatible graphical software, from Web browsers to document
> editors, to correctly insert æ in place of ae. However, traditional text
> editors including Emacs, Vim, and Nano are evidently NOT able to handle
> a literal æ rune insertion, and tend to raise a generic error message
> when the text expander application attempts to insert this key.
Besides what others have suggested, on macOS I'd recommend Ukelele
(http://scripts.sil.org/ukelele). It allows you to easily define your
own system-wide keyboard layouts. According to the web site: "Ukelele
can assign multiple-character strings and can create "dead keys", where
a keystroke sets a new state that modifies the output of the following
keystroke."
Hope this helps,
Life.
--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2018-02-03 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 22:31 Neither Emacs nor Vim nor Nano handle ligature literal insertion well Andrew Pennebaker
2018-02-02 23:38 ` bug#30331: " Alan Third
2018-02-02 23:58 ` Stephen Berman
2018-02-03 8:45 ` Eli Zaretskii
2018-02-03 9:56 ` Lifepillar [this message]
2018-02-03 19:13 ` 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='p540ru$7u0$1@blaine.gmane.org' \
--to=lifepillar@lifepillar.me \
--cc=bug-gnu-emacs@gnu.org \
--cc=help-nano@gnu.org \
--cc=vim_use@googlegroups.com \
/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.