From: Manuel Giraud <manuel@ledu-giraud.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: How to walk a Lisp_String?
Date: Fri, 02 Sep 2022 09:18:59 +0200 [thread overview]
Message-ID: <87wnam6y70.fsf@elite.giraud> (raw)
In-Reply-To: <838rn2qnsf.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 02 Sep 2022 09:43:28 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Manuel Giraud <manuel@ledu-giraud.fr>
>> Cc: emacs-devel@gnu.org
>> Date: Thu, 01 Sep 2022 22:45:12 +0200
>>
>> I'm working into lwlib only. So I've made a function to get the frame
>> of the menu widget (mw). I'm also converting the char* display_string
>> of each menu entry to a Lisp_String with make_string (note: I don't know
>> if I should have done that but it seems the way to get a proper
>> multi-byte string from a char*).
>
> make_multibyte_string is better, I think.
make_string seems to be a higher level interface: it calls
make_unibyte_string or make_multibyte_string whether the string is uni-
or multi-byte.
> And I don't think I understand how you get the Lisp string to have the
> face information. The original C char* string cannot have that
> information as part of the string's data, so where will the face data
> for the Lisp string come from?
I don't understand your question. I thought it was the job of
FACE_FOR_CHAR: you give it a char and a frame and it returns the face
for this char in this frame. What am I missing?
[...]
> For the faces part, I think face_at_string_position is a better
> interface. It returns a face ID, from which you can get to the
> corresponding 'struct face' via FACE_FROM_ID.
Thanks, it is a much better interface.
--
Manuel Giraud
next prev parent reply other threads:[~2022-09-02 7:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 15:34 How to walk a Lisp_String? Manuel Giraud
2022-09-01 15:42 ` Stefan Monnier
2022-09-01 15:42 ` Eli Zaretskii
2022-09-01 15:49 ` Eli Zaretskii
2022-09-01 20:45 ` Manuel Giraud
2022-09-02 1:08 ` Po Lu
2022-09-02 6:32 ` Eli Zaretskii
2022-09-02 8:27 ` Po Lu
2022-09-02 10:36 ` Eli Zaretskii
2022-09-02 11:03 ` Po Lu
2022-09-02 11:15 ` Eli Zaretskii
2022-09-02 12:48 ` Po Lu
2022-09-02 13:17 ` Eli Zaretskii
2022-09-02 6:51 ` Manuel Giraud
2022-09-02 7:20 ` Eli Zaretskii
2022-09-02 8:31 ` Po Lu
2022-09-02 6:43 ` Eli Zaretskii
2022-09-02 7:18 ` Manuel Giraud [this message]
2022-09-02 7:30 ` Eli Zaretskii
2022-09-02 8:56 ` Manuel Giraud
2022-09-02 10:52 ` Eli Zaretskii
2022-09-02 11:40 ` Manuel Giraud
2022-09-02 12:51 ` Po Lu
2022-09-02 15:07 ` Manuel Giraud
2022-09-03 0:58 ` Po Lu
2022-09-03 5:46 ` Tomas Hlavaty
2022-09-03 6:19 ` Po Lu
2022-09-03 8:05 ` Tomas Hlavaty
2022-09-02 13:08 ` Eli Zaretskii
2022-09-02 14:58 ` Manuel Giraud
2022-09-02 15:33 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wnam6y70.fsf@elite.giraud \
--to=manuel@ledu-giraud.fr \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).