GNU bug report logs - #34375
Problem with the 'to input' information in what-cursor-position

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 34375 in the body.
You can then email your comments to 34375 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Andy Smith <andyrsmith <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Problem with the 'to input' information in what-cursor-position
Date: Thu, 7 Feb 2019 23:00:01 +0000

[Message part 1 (text/plain, inline)]

I ran what-cursor-position on a unicode char. Get the following ...

position: 12 of 16 (69%), column: 0
            character: Ő (displayed as Ő) (codepoint 336, #o520, #x150)
    preferred charset: unicode (Unicode (ISO10646))
code point in charset: 0x0150
               script: latin
               syntax: w which means: word
             category: .:Base, L:Left-to-right (strong), j:Japanese, l:Latin
             to input: type "C-x 8 RET 150" or "C-x 8 RET LATIN CAPITAL
LETTER O WITH DOUBLE ACUTE"
          buffer code: #xC5 #x90
            file code: #xC5 #x90 (encoded by coding system utf-8-unix)
              display: by this font (glyph code)
    xft:-DAMA-Ubuntu Mono-normal-normal-normal-*-72-*-*-*-m-0-iso10646-1
            (#x12E)

If I follow the 'to input' instructions ... i.e "C-x 8 RET 150" this
doesn't work. i.e. I can roundtrip and insert a copy of the character I
initially looked up. Needed to do "C-x 8 RET 0150" instead.

The to-input field maybe needs to display an octal string properly
prefixed with a zero maybe?

Rgds,

A.

[Message part 2 (text/html, inline)]

Message #8 received at 34375 <at> debbugs.gnu.org (full text, mbox):

From: Andy Smith <andyrsmith <at> gmail.com>
To: 34375 <at> debbugs.gnu.org
Subject: Correction....
Date: Fri, 8 Feb 2019 01:01:16 +0000

[Message part 1 (text/plain, inline)]

Sorry - I said I 'can' roundtrip between the instructions and the
character. I mean't to say "*can't* roundtrip". Sorry for the confusion.

Rgds,

A.

[Message part 2 (text/html, inline)]

Message #11 received at 34375 <at> debbugs.gnu.org (full text, mbox):

From: Robert Pluim <rpluim <at> gmail.com>
To: Andy Smith <andyrsmith <at> gmail.com>
Cc: 34375 <at> debbugs.gnu.org
Subject: Re: bug#34375: Problem with the 'to input' information in
 what-cursor-position
Date: Fri, 08 Feb 2019 08:09:48 +0100

Andy Smith <andyrsmith <at> gmail.com> writes:

> I ran what-cursor-position on a unicode char. Get the following ...
>
> position: 12 of 16 (69%), column: 0
>             character: Ő (displayed as Ő) (codepoint 336, #o520, #x150)
>     preferred charset: unicode (Unicode (ISO10646))
> code point in charset: 0x0150
>                script: latin
>                syntax: w which means: word
>              category: .:Base, L:Left-to-right (strong), j:Japanese, l:Latin
>              to input: type "C-x 8 RET 150" or "C-x 8 RET LATIN CAPITAL
> LETTER O WITH DOUBLE ACUTE"
>           buffer code: #xC5 #x90
>             file code: #xC5 #x90 (encoded by coding system utf-8-unix)
>               display: by this font (glyph code)
>     xft:-DAMA-Ubuntu Mono-normal-normal-normal-*-72-*-*-*-m-0-iso10646-1
>             (#x12E)
>
> If I follow the 'to input' instructions ... i.e "C-x 8 RET 150" this
> doesn't work. i.e. I can roundtrip and insert a copy of the character I
> initially looked up. Needed to do "C-x 8 RET 0150" instead.
>
> The to-input field maybe needs to display an octal string properly
> prefixed with a zero maybe?

(you didnʼt specify which version of Emacs youʼre using)

The number you need to enter is in hex, and C-x 8 ret implicitly
assumes that numbers entered are in hexadecimal format, at least in
26.1 and master, so I suspect youʼre not running either of those.

Robert

Message #14 received at 34375 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andy Smith <andyrsmith <at> gmail.com>
Cc: 34375 <at> debbugs.gnu.org
Subject: Re: bug#34375: Problem with the 'to input' information in
 what-cursor-position
Date: Fri, 08 Feb 2019 09:11:25 +0200

> From: Andy Smith <andyrsmith <at> gmail.com>
> Date: Thu, 7 Feb 2019 23:00:01 +0000
> 
> I ran what-cursor-position on a unicode char. Get the following ...
> 
> position: 12 of 16 (69%), column: 0
>             character: Ő (displayed as Ő) (codepoint 336, #o520, #x150)
>     preferred charset: unicode (Unicode (ISO10646))
> code point in charset: 0x0150
>                script: latin
>                syntax: w which means: word
>              category: .:Base, L:Left-to-right (strong), j:Japanese, l:Latin
>              to input: type "C-x 8 RET 150" or "C-x 8 RET LATIN CAPITAL LETTER O WITH DOUBLE ACUTE"
>           buffer code: #xC5 #x90
>             file code: #xC5 #x90 (encoded by coding system utf-8-unix)
>               display: by this font (glyph code)
>     xft:-DAMA-Ubuntu Mono-normal-normal-normal-*-72-*-*-*-m-0-iso10646-1
>             (#x12E)
> 
> If I follow the 'to input' instructions ... i.e "C-x 8 RET 150" this
> doesn't work.

I cannot reproduce this.  It works for me.  What do you get if you
type "C-x 8 RET 150", as indicated in what-cursor-position's output?

> The to-input field maybe needs to display an octal string properly
> prefixed with a zero maybe?

No, the code is interpreted as hex by "C-x 8 RET".  So I wonder what
went wrong in your case.  Can you show the result of "C-h l" (the
letter ell, not the digit one) after typing "C-x 8 RET 150"?

Message #17 received at 34375 <at> debbugs.gnu.org (full text, mbox):

From: Andy Smith <andyrsmith <at> gmail.com>
To: 34375 <at> debbugs.gnu.org
Subject: Re: bug#34375: Problem with the 'to input' information in
 what-cursor-position
Date: Fri, 8 Feb 2019 10:18:21 +0000

[Message part 1 (text/plain, inline)]

Thanks for getting back.

(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 ...."

2c60 works as expected so maybe it's a problem for characters who have a
hex representation less than four letters.

Cheers,

A.



[image: 2019-02-08_10-11.png]




On Fri, 8 Feb 2019 at 07:11, Eli Zaretskii <eliz <at> gnu.org> wrote:

> > From: Andy Smith <andyrsmith <at> gmail.com>
> > Date: Thu, 7 Feb 2019 23:00:01 +0000
> >
> > I ran what-cursor-position on a unicode char. Get the following ...
> >
> > position: 12 of 16 (69%), column: 0
> >             character: Ő (displayed as Ő) (codepoint 336, #o520, #x150)
> >     preferred charset: unicode (Unicode (ISO10646))
> > code point in charset: 0x0150
> >                script: latin
> >                syntax: w which means: word
> >              category: .:Base, L:Left-to-right (strong), j:Japanese,
> l:Latin
> >              to input: type "C-x 8 RET 150" or "C-x 8 RET LATIN CAPITAL
> LETTER O WITH DOUBLE ACUTE"
> >           buffer code: #xC5 #x90
> >             file code: #xC5 #x90 (encoded by coding system utf-8-unix)
> >               display: by this font (glyph code)
> >     xft:-DAMA-Ubuntu Mono-normal-normal-normal-*-72-*-*-*-m-0-iso10646-1
> >             (#x12E)
> >
> > If I follow the 'to input' instructions ... i.e "C-x 8 RET 150" this
> > doesn't work.
>
> I cannot reproduce this.  It works for me.  What do you get if you
> type "C-x 8 RET 150", as indicated in what-cursor-position's output?
>
> > The to-input field maybe needs to display an octal string properly
> > prefixed with a zero maybe?
>
> No, the code is interpreted as hex by "C-x 8 RET".  So I wonder what
> went wrong in your case.  Can you show the result of "C-h l" (the
> letter ell, not the digit one) after typing "C-x 8 RET 150"?
>

[Message part 2 (text/html, inline)]

[2019-02-08_10-11.png (image/png, inline)]

Message #20 received at 34375 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Andy Smith <andyrsmith <at> gmail.com>
Cc: 34375 <at> debbugs.gnu.org
Subject: Re: bug#34375: Problem with the 'to input' information in
 what-cursor-position
Date: Fri, 08 Feb 2019 12:40:26 +0200

> 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 #23 received at 34375 <at> debbugs.gnu.org (full text, mbox):

From: Andy Smith <andyrsmith <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 34375 <at> debbugs.gnu.org
Subject: Re: bug#34375: Problem with the 'to input' information in
 what-cursor-position
Date: Fri, 8 Feb 2019 10:47:51 +0000

[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)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.