From: Miles Bader <miles@lsi.nec.co.jp>
Cc: rms@gnu.org, eliz@is.elta.co.il, emacs-devel@gnu.org
Subject: Re: [Marcus.Brinkmann@ruhr-uni-bochum.de: fonts on terminal?]
Date: 11 Sep 2002 13:17:55 +0900 [thread overview]
Message-ID: <buoy9a9b1n0.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20020911035340.GK474@212.23.136.22>
Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:
> Yeah, I am sorry, that sentence was never spelled out in its entirety. It
> should say: "supporting alternative (italics, bold) faces for font lock mode
> in the term bottom handler of emacs", ie the part that translates abstract
> descriptions to actual terminal escape sequences to produce the corresponding
> face.
Right, that part's simple.
One problem is that emacs allows faces to have `device dependent'
definitions, for cases where the most general definition isn't emulated
well. A fair number of emacs' standard faces have `tty-specific'
definitions, and some of these might assume that ttys never have italic
(bold's probably not a problem, since ttys already sort-of support bold
via intensity).
I recently added capability-testing support (the `supports' clause) to
the face code so any faces that make that assumption about ttys could be
changed to directly test for italic support instead.
[In general I think the above isn't really a problem, since most
`tty-dependent' face definitions actually care about the color depth
(though this is another thing that should be changed to use a
capability-testing model instead).]
-Miles
--
97% of everything is grunge
next prev parent reply other threads:[~2002-09-11 4:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 3:05 [Marcus.Brinkmann@ruhr-uni-bochum.de: fonts on terminal?] Richard Stallman
2002-09-11 3:42 ` Miles Bader
2002-09-11 3:53 ` Marcus Brinkmann
2002-09-11 4:17 ` Miles Bader [this message]
2002-09-16 2:41 ` Marcus Brinkmann
2002-09-16 19:27 ` Richard Stallman
2002-09-19 3:42 ` Eli Zaretskii
2002-09-19 4:10 ` Miles Bader
2002-09-19 11:01 ` Eli Zaretskii
2002-09-19 18:57 ` Richard Stallman
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=buoy9a9b1n0.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=eliz@is.elta.co.il \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=rms@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).