Re: Neither Emacs nor Vim nor Nano handle ligature literal insertion well

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 [email protected].
For more options, visit https://groups.google.com/d/optout.