all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Andrew Pennebaker <andrew.pennebaker@gmail.com>
Cc: 30331@debbugs.gnu.org
Subject: bug#30331: Neither Emacs nor Vim nor Nano handle ligature literal insertion well
Date: Sat, 03 Feb 2018 14:13:12 -0500	[thread overview]
Message-ID: <E1ei3FQ-00021m-GQ@fencepost.gnu.org> (raw)
In-Reply-To: <CAHXt_SV2P_ieU+UNHx8QoGX9CfoT38BoO01u9Er4dVqqm2Bxyw@mail.gmail.com> (message from Andrew Pennebaker on Fri, 2 Feb 2018 16:31:05 -0600)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > 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'd expect that Quail input methods could handle this for Emacs.  They
notice when you enter a' and convert it to á, so they could notice ae
and convert it to æ.

When you want separate a and e, you'd type another e.



-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
Skype: No way! See https://stallman.org/skype.html.






      parent reply	other threads:[~2018-02-03 19:13 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
2018-02-03 19:13 ` Richard Stallman [this message]

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=E1ei3FQ-00021m-GQ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=30331@debbugs.gnu.org \
    --cc=andrew.pennebaker@gmail.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.