[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#30331: Neither Emacs nor Vim nor Nano handle ligature literal insert

From: Alan Third
Subject: bug#30331: Neither Emacs nor Vim nor Nano handle ligature literal insertion well
Date: Fri, 2 Feb 2018 23:38:21 +0000
User-agent: Mutt/1.9.3 (2018-01-21)

On Fri, Feb 02, 2018 at 04:31:05PM -0600, Andrew Pennebaker wrote:
> 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.

I’m not sure about the use of TextExpander as I’ve never heard of it
before, but Emacs on macOS can handle the insertion of æ using alt‐’,
but you might need to change the default binding of the alt key

Aside from that Emacs allows you to enter æ using:


It’s a bit of a handful though, I know, but you can enter all sorts of

    ffl fi 🙲

You should be able to configure abbrev-mode to automatically convert
ae to æ. Or maybe prettify symbols mode would do:


Proper ligature support is purely a presentation issue, though, and
should happen automatically on software that supports it even if
you’re loading in text written in software that doesn’t.
Alan Third

reply via email to

[Prev in Thread] Current Thread [Next in Thread]