unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Keith David Bershatsky <esq@lawlist.com>
Cc: emacs-devel@gnu.org
Subject: Re: Adding new variable for face-list in internal-make-lisp-face.
Date: Sat, 04 Nov 2017 10:05:37 +0200	[thread overview]
Message-ID: <8360aqv57y.fsf@gnu.org> (raw)
In-Reply-To: <m21slfkon5.wl%esq@lawlist.com> (message from Keith David Bershatsky on Fri, 03 Nov 2017 15:01:34 -0700)

> Date:  Fri, 03 Nov 2017 15:01:34 -0700
> From:  Keith David Bershatsky <esq@lawlist.com>
> Cc:  emacs-devel@gnu.org
> 
> I have a tab buffer-display-table entry that looks like:
> 
> [(187 . 120) (9 . 121)]
> 
> Your suggestion to use GLYPH_FACE would be more efficient than my using the C equivalent of:
> 
> (aref buffer-display-table ?\t)
> 
> ... and then iterating over the vector elements looking for a cons cell containing the number 9.
> 
> I will work on incorporating GLYPH_FACE into my code, instead of using the above iteration.  Thank you for the suggestion.
> 
> Once the face id is obtained, I have been using C implementations of the following:

I believe I already explained how to get the fore- and back-ground
colors of a face given its ID in my message Re: Can we use FRAME_RIF
to return a Lisp_Object result?  I think you should use the same
technique here.



  reply	other threads:[~2017-11-04  8:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 22:01 Adding new variable for face-list in internal-make-lisp-face Keith David Bershatsky
2017-11-04  8:05 ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-11-04 17:46 Keith David Bershatsky
2017-11-04 18:16 ` Eli Zaretskii
2017-11-04  6:56 Keith David Bershatsky
2017-11-04  8:13 ` Eli Zaretskii
2017-11-03  3:50 Keith David Bershatsky
2017-11-03 10:17 ` 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=8360aqv57y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esq@lawlist.com \
    /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).