From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Keith David Bershatsky <esq@lawlist.com>, emacs-devel@gnu.org
Subject: Re: C equivalent for: (face-attribute 'region :background (selected-frame) 'default)
Date: Thu, 05 Oct 2017 16:11:44 +0900 [thread overview]
Message-ID: <wl376yf4r3.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <83mv56xf9o.fsf@gnu.org>
>>>>> On Thu, 05 Oct 2017 09:47:15 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> Date: Wed, 04 Oct 2017 17:24:50 -0700 From: Keith David Bershatsky
>> <esq@lawlist.com> Cc: emacs-devel@gnu.org
>>
>> My preference is that multiple fake cursors and crosshairs be
>> implemented entirely in C, with just a little bit of Lisp to access
>> those tools. I also felt that relying on Lisp might somehow slow
>> things down a bit, and speed is really important.
> I don't think you will gain speed by moving these functions to C,
> because their slow part is already implemented in C.
And as I already commented, creating LSL vector or something from a
face in a platform-independent code is not a good design in the sense
that it is inconsistent with the current code. Each drawing backend
can get color information (as GC, in all the platforms other than NS)
from a given face as I showed in the code `mac_gc_for_face_id'.
Also, erasing crosshairs or cursors could be done by imitating the
code in `expose_area'. I think you don't need to know which face is
used in the erased area.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2017-10-05 7:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 0:24 C equivalent for: (face-attribute 'region :background (selected-frame) 'default) Keith David Bershatsky
2017-10-05 6:47 ` Eli Zaretskii
2017-10-05 7:11 ` YAMAMOTO Mitsuharu [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-06 3:53 Keith David Bershatsky
2017-09-27 0:24 Keith David Bershatsky
2017-09-27 5:58 ` YAMAMOTO Mitsuharu
2017-09-26 22:11 Keith David Bershatsky
2017-09-29 20:33 ` Philipp Stephani
2017-09-26 22:06 Keith David Bershatsky
2017-09-26 18:38 Keith David Bershatsky
2017-09-29 13:25 ` Eli Zaretskii
2017-09-26 4:38 Keith David Bershatsky
2017-09-26 18:46 ` Philipp Stephani
2017-09-26 23:19 ` YAMAMOTO Mitsuharu
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=wl376yf4r3.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=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).