GNU bug report logs -
#34375
Problem with the 'to input' information in what-cursor-position
Previous Next
Reported by: Andy Smith <andyrsmith <at> gmail.com>
Date: Fri, 8 Feb 2019 00:25:01 UTC
Severity: normal
Tags: notabug
Done: Glenn Morris <rgm <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
<facepalm>
yes you're right. Helm is the culprit :-(. Sorry for wasting your time, my
intentions were honest!
I've just double checked with 'emacs -Q'. All works as expected.
Thanks for your help!
Cheers,
A.
On Fri, 8 Feb 2019 at 10:40, Eli Zaretskii <eliz <at> gnu.org> wrote:
> > From: Andy Smith <andyrsmith <at> gmail.com>
> > Date: Fri, 8 Feb 2019 10:18:21 +0000
> >
> > (version)
> > "GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.30)
> > of 2018-07-05"
> >
> > Just to explain what I'm seeing. Apologies for having to use screenshot
> but the I'm not sure if the unicode stuff
> > will translate well via email :-(
> >
> > My point is that 'what-char-position' gives an incorrect instruction to
> the user for character 150. I think it should
> > really say ....
> >
> > to input: type "C-8 RET 0150 ...."
> >
> > instead of
> >
> > to input: type "C-8 RET 150 ...."
>
> Are you seeing this problem in "emacs -Q"? (It's "C-x 8 RET", btw,
> not "C-8 RER", right?)
>
> The character that you get is U+1009F LINEAR B IDEOGRAM B150. Its
> name includes "150" as a substring, so perhaps you did something that
> caused Emacs to auto-complete the name? Like typing TAB or using some
> optional completion package? That's why I ask about "emacs -Q".
>
[Message part 2 (text/html, inline)]
This bug report was last modified 6 years and 155 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.