From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: emacs-devel@gnu.org
Subject: Re: How to walk a Lisp_String?
Date: Fri, 02 Sep 2022 09:43:28 +0300 [thread overview]
Message-ID: <838rn2qnsf.fsf@gnu.org> (raw)
In-Reply-To: <87ler2963r.fsf@elite.giraud> (message from Manuel Giraud on Thu, 01 Sep 2022 22:45:12 +0200)
> 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.
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?
> Finally, I'd like to walk this Lisp_String and call FACE_FOR_CHAR for
> each charater of this frame. And then be able to call XftDrawStringUtf8
> (or XmbDrawString) on each substring/font pair. WDYT?
Po Lu answered about the XftDrawStringUtf8 part.
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.
next prev parent reply other threads:[~2022-09-02 6:43 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 [this message]
2022-09-02 7:18 ` Manuel Giraud
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838rn2qnsf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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 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.