all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* describe-char-fold-equivalences
@ 2023-01-08  4:26 T.V Raman
  2023-01-08  5:56 ` describe-char-fold-equivalences Eli Zaretskii
  2023-01-08  6:02 ` describe-char-fold-equivalences Yuri Khan
  0 siblings, 2 replies; 12+ messages in thread
From: T.V Raman @ 2023-01-08  4:26 UTC (permalink / raw)
  To: emacs-devel

Calling describe-char-fold-equivalences and specifying "'"
displays the following --- could we get rid of the '\n'    that
appears on every line as a field delimiter?

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮


': ?\N{APOSTROPHE}
❟: ?\N{HEAVY LOW SINGLE COMMA QUOTATION MARK ORNAMENT}
❛: ?\N{HEAVY SINGLE TURNED COMMA QUOTATION MARK ORNAMENT}
❜: ?\N{HEAVY SINGLE COMMA QUOTATION MARK ORNAMENT}
‘: ?\N{LEFT SINGLE QUOTATION MARK}
’: ?\N{RIGHT SINGLE QUOTATION MARK}
‚: ?\N{SINGLE LOW-9 QUOTATION MARK}
‛: ?\N{SINGLE HIGH-REVERSED-9 QUOTATION MARK}
‚: ?\N{SINGLE LOW-9 QUOTATION MARK}
󠀢: ?\N{TAG QUOTATION MARK}
❮: ?\N{HEAVY LEFT-POINTING ANGLE QUOTATION MARK ORNAMENT}
❯: ?\N{HEAVY RIGHT-POINTING ANGLE QUOTATION MARK ORNAMENT}
‹: ?\N{SINGLE LEFT-POINTING ANGLE QUOTATION MARK}
›: ?\N{SINGLE RIGHT-POINTING ANGLE QUOTATION MARK}
': ?\N{FULLWIDTH APOSTROPHE}

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-08  4:26 describe-char-fold-equivalences T.V Raman
@ 2023-01-08  5:56 ` Eli Zaretskii
  2023-01-08  5:59   ` describe-char-fold-equivalences Ruijie Yu via Emacs development discussions.
  2023-01-08 14:55   ` describe-char-fold-equivalences T.V Raman
  2023-01-08  6:02 ` describe-char-fold-equivalences Yuri Khan
  1 sibling, 2 replies; 12+ messages in thread
From: Eli Zaretskii @ 2023-01-08  5:56 UTC (permalink / raw)
  To: T.V Raman; +Cc: emacs-devel

> Date: Sat, 07 Jan 2023 20:26:44 -0800
> From: "T.V Raman" <raman@google.com>
> 
> Calling describe-char-fold-equivalences and specifying "'"
> displays the following --- could we get rid of the '\n'    that
> appears on every line as a field delimiter?

Which newlines do you want to get rid of?

If those are the newlines between the individual characters, then
removing the newlines will produce a single very long line, which will
be harder to read.



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-08  5:56 ` describe-char-fold-equivalences Eli Zaretskii
@ 2023-01-08  5:59   ` Ruijie Yu via Emacs development discussions.
  2023-01-08 14:57     ` describe-char-fold-equivalences T.V Raman
  2023-01-08 14:55   ` describe-char-fold-equivalences T.V Raman
  1 sibling, 1 reply; 12+ messages in thread
From: Ruijie Yu via Emacs development discussions. @ 2023-01-08  5:59 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: T.V Raman, emacs-devel


Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Sat, 07 Jan 2023 20:26:44 -0800
>> From: "T.V Raman" <raman@google.com>
>>
>> Calling describe-char-fold-equivalences and specifying "'"
>> displays the following --- could we get rid of the '\n'    that
>> appears on every line as a field delimiter?
>
> Which newlines do you want to get rid of?
>
> If those are the newlines between the individual characters, then
> removing the newlines will produce a single very long line, which will
> be harder to read.

I think they mean for each line, instead of saying "?\N{DESCRIPTION}",
just say "DESCRIPTION".

Best,


RY



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-08  4:26 describe-char-fold-equivalences T.V Raman
  2023-01-08  5:56 ` describe-char-fold-equivalences Eli Zaretskii
@ 2023-01-08  6:02 ` Yuri Khan
  2023-01-08 14:57   ` describe-char-fold-equivalences T.V Raman
  1 sibling, 1 reply; 12+ messages in thread
From: Yuri Khan @ 2023-01-08  6:02 UTC (permalink / raw)
  To: T.V Raman; +Cc: emacs-devel

On Sun, 8 Jan 2023 at 11:27, T.V Raman <raman@google.com> wrote:

> Calling describe-char-fold-equivalences and specifying "'"
> displays the following --- could we get rid of the '\n'    that
> appears on every line as a field delimiter?

Those are not newlines (backslash small letter en) but syntax for
specifying a character by its Unicode name (question mark backslash
capital en). Maybe your screen reader does not make that obvious.

> ': ?\N{APOSTROPHE}



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-08  5:56 ` describe-char-fold-equivalences Eli Zaretskii
  2023-01-08  5:59   ` describe-char-fold-equivalences Ruijie Yu via Emacs development discussions.
@ 2023-01-08 14:55   ` T.V Raman
  1 sibling, 0 replies; 12+ messages in thread
From: T.V Raman @ 2023-01-08 14:55 UTC (permalink / raw)
  To: Eli Zaretskii; +Cc: emacs-devel

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 786 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

I meant the verbatim '\n' that appears between the displayed char and
its unicode name -- it's a literal '\n' at least that's what I see in
what I pasted.
>> Date: Sat, 07 Jan 2023 20:26:44 -0800
>> From: "T.V Raman" <raman@google.com>
>> 
>> Calling describe-char-fold-equivalences and specifying "'"
>> displays the following --- could we get rid of the '\n'    that
>> appears on every line as a field delimiter?
>
> Which newlines do you want to get rid of?
>
> If those are the newlines between the individual characters, then
> removing the newlines will produce a single very long line, which will
> be harder to read.

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-08  5:59   ` describe-char-fold-equivalences Ruijie Yu via Emacs development discussions.
@ 2023-01-08 14:57     ` T.V Raman
  0 siblings, 0 replies; 12+ messages in thread
From: T.V Raman @ 2023-01-08 14:57 UTC (permalink / raw)
  To: Ruijie Yu; +Cc: Eli Zaretskii, emacs-devel

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 876 bytes --]

Ruijie Yu <ruijie@netyu.xyz> writes:


correct:-)
Thanks for confirming that that '\n' exists:-)

  > Eli Zaretskii <eliz@gnu.org> writes:
>
>>> Date: Sat, 07 Jan 2023 20:26:44 -0800
>>> From: "T.V Raman" <raman@google.com>
>>>
>>> Calling describe-char-fold-equivalences and specifying "'"
>>> displays the following --- could we get rid of the '\n'    that
>>> appears on every line as a field delimiter?
>>
>> Which newlines do you want to get rid of?
>>
>> If those are the newlines between the individual characters, then
>> removing the newlines will produce a single very long line, which will
>> be harder to read.
>
> I think they mean for each line, instead of saying "?\N{DESCRIPTION}",
> just say "DESCRIPTION".
>
> Best,
>
>
> RY

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-08  6:02 ` describe-char-fold-equivalences Yuri Khan
@ 2023-01-08 14:57   ` T.V Raman
  2023-01-09 14:16     ` describe-char-fold-equivalences Robert Pluim
  0 siblings, 1 reply; 12+ messages in thread
From: T.V Raman @ 2023-01-08 14:57 UTC (permalink / raw)
  To: Yuri Khan; +Cc: emacs-devel

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 747 bytes --]

Yuri Khan <yuri.v.khan@gmail.com> writes:


It did make it obvious, the me the user still got confused -- I wasn't
aware of that particular usage 

> On Sun, 8 Jan 2023 at 11:27, T.V Raman <raman@google.com> wrote:
>
>> Calling describe-char-fold-equivalences and specifying "'"
>> displays the following --- could we get rid of the '\n'    that
>> appears on every line as a field delimiter?
>
> Those are not newlines (backslash small letter en) but syntax for
> specifying a character by its Unicode name (question mark backslash
> capital en). Maybe your screen reader does not make that obvious.
>
>> ': ?\N{APOSTROPHE}

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-08 14:57   ` describe-char-fold-equivalences T.V Raman
@ 2023-01-09 14:16     ` Robert Pluim
  2023-01-09 15:31       ` describe-char-fold-equivalences T.V Raman
  0 siblings, 1 reply; 12+ messages in thread
From: Robert Pluim @ 2023-01-09 14:16 UTC (permalink / raw)
  To: T.V Raman; +Cc: Yuri Khan, emacs-devel

>>>>> On Sun, 08 Jan 2023 06:57:53 -0800, "T.V Raman" <raman@google.com> said:

    TVR> Yuri Khan <yuri.v.khan@gmail.com> writes:
    TVR> It did make it obvious, the me the user still got confused -- I wasn't
    TVR> aware of that particular usage 

See (info "(elisp) General Escape Syntax")

The idea was to produce something that people could copy and use,
without having the unicode codepoint numbers appearing.

Robert
-- 



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-09 14:16     ` describe-char-fold-equivalences Robert Pluim
@ 2023-01-09 15:31       ` T.V Raman
  2023-01-09 15:54         ` describe-char-fold-equivalences Robert Pluim
  0 siblings, 1 reply; 12+ messages in thread
From: T.V Raman @ 2023-01-09 15:31 UTC (permalink / raw)
  To: Robert Pluim; +Cc: Yuri Khan, emacs-devel

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 264 bytes --]

thanks for the explanation.

Perhaps we could make that more discoverable when reading the output of
that function ie the doc string I complained about?


-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-09 15:31       ` describe-char-fold-equivalences T.V Raman
@ 2023-01-09 15:54         ` Robert Pluim
  2023-01-09 18:31           ` describe-char-fold-equivalences T.V Raman
  0 siblings, 1 reply; 12+ messages in thread
From: Robert Pluim @ 2023-01-09 15:54 UTC (permalink / raw)
  To: T.V Raman; +Cc: Yuri Khan, emacs-devel

>>>>> On Mon, 09 Jan 2023 07:31:17 -0800, "T.V Raman" <raman@google.com> said:

    T> thanks for the explanation.
    T> Perhaps we could make that more discoverable when reading the output of
    T> that function ie the doc string I complained about?

Yes. Something like this for emacs-29?

diff --git a/lisp/char-fold.el b/lisp/char-fold.el
index eff2f5558b3..f1da7997407 100644
--- a/lisp/char-fold.el
+++ b/lisp/char-fold.el
@@ -436,7 +436,24 @@ describe-char-fold-equivalences
 describe all available character equivalences of `char-fold-to-regexp'.
 Optional argument LAX (interactively, the prefix argument), if
 non-nil, means also include partially matching ligatures and
-non-canonical equivalences."
+non-canonical equivalences.
+
+Each line of the display shows the equivalences in two different
+ways separated by a colon:
+
+    - as the literal character or sequence
+    - using an ASCII-only escape syntax
+
+For example, for the letter 'r', the first line is
+
+    r: ?\N{LATIN SMALL LETTER R}
+
+which is for the requested character itself, and a later line has
+
+    ṟ: ?\N{LATIN SMALL LETTER R}?\N{COMBINING MACRON BELOW}
+
+which clearly shows what the constituent characters are."
   (interactive (list (ignore-errors
                        (read-char-by-name
                         (format-prompt "Unicode name, single char, or hex"



^ permalink raw reply related	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-09 15:54         ` describe-char-fold-equivalences Robert Pluim
@ 2023-01-09 18:31           ` T.V Raman
  2023-01-10 16:16             ` describe-char-fold-equivalences Robert Pluim
  0 siblings, 1 reply; 12+ messages in thread
From: T.V Raman @ 2023-01-09 18:31 UTC (permalink / raw)
  To: rpluim; +Cc: raman, yuri.v.khan, emacs-devel

yes, this LGTM!

Robert Pluim writes:
 > >>>>> On Mon, 09 Jan 2023 07:31:17 -0800, "T.V Raman" <raman@google.com> said:
 > 
 >     T> thanks for the explanation.
 >     T> Perhaps we could make that more discoverable when reading the output of
 >     T> that function ie the doc string I complained about?
 > 
 > Yes. Something like this for emacs-29?
 > 
 > diff --git a/lisp/char-fold.el b/lisp/char-fold.el
 > index eff2f5558b3..f1da7997407 100644
 > --- a/lisp/char-fold.el
 > +++ b/lisp/char-fold.el
 > @@ -436,7 +436,24 @@ describe-char-fold-equivalences
 >  describe all available character equivalences of `char-fold-to-regexp'.
 >  Optional argument LAX (interactively, the prefix argument), if
 >  non-nil, means also include partially matching ligatures and
 > -non-canonical equivalences."
 > +non-canonical equivalences.
 > +
 > +Each line of the display shows the equivalences in two different
 > +ways separated by a colon:
 > +
 > +    - as the literal character or sequence
 > +    - using an ASCII-only escape syntax
 > +
 > +For example, for the letter 'r', the first line is
 > +
 > +    r: ?\N{LATIN SMALL LETTER R}
 > +
 > +which is for the requested character itself, and a later line has
 > +
 > +    ṟ: ?\N{LATIN SMALL LETTER R}?\N{COMBINING MACRON BELOW}
 > +
 > +which clearly shows what the constituent characters are."
 >    (interactive (list (ignore-errors
 >                         (read-char-by-name
 >                          (format-prompt "Unicode name, single char, or hex"

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

--

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮



^ permalink raw reply	[flat|nested] 12+ messages in thread

* Re: describe-char-fold-equivalences
  2023-01-09 18:31           ` describe-char-fold-equivalences T.V Raman
@ 2023-01-10 16:16             ` Robert Pluim
  0 siblings, 0 replies; 12+ messages in thread
From: Robert Pluim @ 2023-01-10 16:16 UTC (permalink / raw)
  To: T.V Raman; +Cc: yuri.v.khan, emacs-devel

>>>>> On Mon, 9 Jan 2023 10:31:47 -0800, "T.V Raman" <raman@google.com> said:

    TVR> yes, this LGTM!

Now done on the emacs-29 branch.

Robert
-- 



^ permalink raw reply	[flat|nested] 12+ messages in thread

end of thread, other threads:[~2023-01-10 16:16 UTC | newest]

Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-01-08  4:26 describe-char-fold-equivalences T.V Raman
2023-01-08  5:56 ` describe-char-fold-equivalences Eli Zaretskii
2023-01-08  5:59   ` describe-char-fold-equivalences Ruijie Yu via Emacs development discussions.
2023-01-08 14:57     ` describe-char-fold-equivalences T.V Raman
2023-01-08 14:55   ` describe-char-fold-equivalences T.V Raman
2023-01-08  6:02 ` describe-char-fold-equivalences Yuri Khan
2023-01-08 14:57   ` describe-char-fold-equivalences T.V Raman
2023-01-09 14:16     ` describe-char-fold-equivalences Robert Pluim
2023-01-09 15:31       ` describe-char-fold-equivalences T.V Raman
2023-01-09 15:54         ` describe-char-fold-equivalences Robert Pluim
2023-01-09 18:31           ` describe-char-fold-equivalences T.V Raman
2023-01-10 16:16             ` describe-char-fold-equivalences Robert Pluim

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.