unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: cloos@jhcloos.com, emacs-devel@gnu.org
Subject: Re: display-supports-face-attributes-p bug?
Date: Fri, 10 Jun 2005 09:34:21 +0300	[thread overview]
Message-ID: <uk6l290uq.fsf@gnu.org> (raw)
In-Reply-To: <fc339e4a0506091759449ab1c1@mail.gmail.com> (message from Miles Bader on Fri, 10 Jun 2005 09:59:04 +0900)

> Date: Fri, 10 Jun 2005 09:59:04 +0900
> From: Miles Bader <snogglethorpe@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>, cloos@jhcloos.com, emacs-devel@gnu.org
> 
> That's correct for the linux console, but underlining _does_ work
> properly on xterm (and on every other X terminal emulator  I've
> tried).

Right.  And that includes many xterm emulators running on Windows as
well, such as PuTTY.

> As it seems unlikely for terminfo to be changed anytime soon (and
> broken installations would remain for a long time anyway), it seems
> that Emacs just needs to special-case the terminal name "linux" to
> reflect that underlining isn't supported there.

Yuck!  I'd prefer we invest our energy in talking the Linux
maintainers into changing their terminfo entries.  Hardcoding terminal
names is ugly and would be a maintenance mess if that terminal expands
its capabilities in the future.

We always insisted in behaving as the terminfo entry says.  The only
places where we currently look at the terminal's name is when there's
no known way if figuring out something, like with the (unknown)
default background color of the terminal.

> Currently there doesn't seem to be a mechanism for overriding the
> low-level C terminal code from lisp though.

Right.  The only existing mechanism is through the tty-color-mode
frame parameter, and it only supports overriding the number of
available colors.

  reply	other threads:[~2005-06-10  6:34 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 [this message]
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
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=uk6l290uq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cloos@jhcloos.com \
    --cc=emacs-devel@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).