unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: James Cloos <cloos@jhcloos.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org, rms@gnu.org, miles@gnu.org
Subject: Re: display-supports-face-attributes-p bug?
Date: Thu, 09 Jun 2005 22:38:30 -0400	[thread overview]
Message-ID: <m3r7fbkkbd.fsf@lugabout.cloos.reno.nv.us> (raw)
In-Reply-To: <fc339e4a050609192028441a7a@mail.gmail.com> (Miles Bader's message of "Fri, 10 Jun 2005 11:20:37 +0900")

>>>>> "Miles" == Miles Bader <snogglethorpe@gmail.com> writes:

Miles> If it's impossible to tell whether there's correct underlining
Miles> support, it seems safer to assume there's not -- or at the
Miles> least don't _advertise_ that there is.  In other words,
Miles> probably the right thing to do is still emit
Miles> enter/exit-underlining escape codes for underlined faces, but
Miles> have `display-supports-face-attribute-p' return nil for the
Miles> :underline attribute.

Sounds like a most reasonable compromise.

Miles> It also seems reasonable to base the default Emacs behavior on
Miles> the current state of the most popular platform, in cases where
Miles> there's no way of distinguishing.

Certainly.  I just pointed out that things might change because there
is a desire in lkml-land to move the vt100-ish part of the console
from kernelspace to userspace, and that will likely result in
emulation that is much more like xterm than anything else.  And since
xterm supports real underlining....

Miles> [Of course if we add a hack to override terminfo, it would also
Miles> be good to have a way for the user to override that.]

That would be cool.

-JimC

(I'll probably bow out of this thread now.)
-- 
James H. Cloos, Jr. <cloos@jhcloos.com>

  reply	other threads:[~2005-06-10  2:38 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 16:00 display-supports-face-attributes-p bug? Richard Stallman
2005-06-08 18:16 ` James Cloos
2005-06-09 14:40   ` Richard Stallman
2005-06-08 18:36 ` Eli Zaretskii
2005-06-08 21:00   ` James Cloos
2005-06-09  3:54     ` Eli Zaretskii
2005-06-09  4:44       ` Miles Bader
2005-06-09 19:48         ` Eli Zaretskii
2005-06-09 21:38           ` James Cloos
2005-06-10  6:21             ` Eli Zaretskii
2005-06-10 13:30             ` Richard Stallman
2005-06-10 14:06               ` Andreas Schwab
2005-06-10 14:11               ` Miles Bader
2005-06-10 13:29           ` Richard Stallman
2005-06-09  4:46       ` James Cloos
2005-06-09 19:46         ` Eli Zaretskii
2005-06-10  0:14       ` Richard Stallman
2005-06-10  0:59         ` Miles Bader
2005-06-10  6:34           ` Eli Zaretskii
2005-06-10  6:41             ` Miles Bader
2005-06-10  7:48               ` Eli Zaretskii
2005-06-10  8:05                 ` Miles Bader
2005-06-10  9:38                   ` David Kastrup
2005-06-10 18:36               ` James Cloos
2005-06-10  1:44         ` James Cloos
2005-06-10  2:20           ` Miles Bader
2005-06-10  2:38             ` James Cloos [this message]
2005-06-10 22:36             ` Richard Stallman
2005-06-10  6:23         ` Eli Zaretskii
2005-06-08 20:26 ` Andreas Schwab
2005-06-08 21:38 ` Miles Bader
2005-06-08 22:30   ` Andreas Schwab
2005-06-08 23:31     ` Miles Bader
2005-06-09  9:03       ` Andreas Schwab

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=m3r7fbkkbd.fsf@lugabout.cloos.reno.nv.us \
    --to=cloos@jhcloos.com \
    --cc=eliz@gnu.org \
    --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).