emacs-devel
[Top][All Lists]
Advanced

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

Re: emacs-28 a866674b2a: Fix inaccuracies in "lax search" documentation


From: Eli Zaretskii
Subject: Re: emacs-28 a866674b2a: Fix inaccuracies in "lax search" documentation
Date: Wed, 31 Aug 2022 19:40:10 +0300

> From: Robert Pluim <rpluim@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
> Date: Wed, 31 Aug 2022 18:36:23 +0200
> 
> >>>>> On Wed, 31 Aug 2022 19:09:34 +0300, Juri Linkov <juri@linkov.net> said:
> 
>     >> I have one comment: using `read-char-by-name' is kind
>     >> of cumbersome when all you want to do is find the equivalents to
>     >> e.g. 'a'. Would it make sense to have something similar to
>     >> `read-char-by-name' but that accepted single characters *without*
>     >> treating those as hex? Youʼd still be able to enter single digit
>     >> hex characters by prefixing them with '0'.
> 
>     Juri> Wouldn't it be cleaner to use just (read-char-from-minibuffer 
> "Character: ")
>     Juri> where you can either type a character directly or use 'C-x 8 RET'
>     Juri> to insert a character by its name.
> 
> I guess that works as well, but then youʼre assuming knowledge of 'C-x
> 8 RETʼ. I canʼt come up with a strong argument either ways, so Iʼm
> going to chicken out here and see what Eli says ☺️

Eli says that he was mightily surprised to see that just typing a
character at the prompt didn't take that character literally, but
instead interpreted it as a hex codepoint.



reply via email to

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