unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: display-supports-face-attributes-p bug?
Date: Thu, 09 Jun 2005 06:54:38 +0300	[thread overview]
Message-ID: <uy89k89s1.fsf@gnu.org> (raw)
In-Reply-To: <m3wtp4pnse.fsf@lugabout.cloos.reno.nv.us> (message from James Cloos on Wed, 08 Jun 2005 17:00:01 -0400)

> Cc: rms@gnu.org, emacs-devel@gnu.org
> From: James Cloos <cloos@jhcloos.com>
> Date: Wed, 08 Jun 2005 17:00:01 -0400
> 
> Strace(8)ing setterm(1) shows that it also uses terminfo and get's the
> same escape sequence for underline for xterm as it does for linux.
> 
> So emacs should know that \033[4m turns on underline in both cases,
> but somehow doesn't output it if %ENV{TERM} ~= 'linux' (to use Perl
> syntax -- I forget the elisp construct).  Is something special-casing
> consoles?

I don't think Emacs does anything special for the Linux console, if
that's what you meant.

I think the way to debug this is to step through the code in term.c
that produces underlining.  First, make sure that
TS_enter_underline_mode and TS_exit_underline_mode hold the right
strings, then, in turn_on_face, make sure that the check

  if (face->tty_underline_p && MAY_USE_WITH_COLORS_P (NC_UNDERLINE))

does TRT (where TRT is to underline if the Linux console can mix
underlining with colors).

If it turns out that Emacs thinks the Linux console cannot mix colors
with underlining, you can try "emacs --color=no" to see if that causes
underlining to work.  If it does, it means that mixing colors with
underlining is the issue; if the Linux terminal can actually do that,
perhaps the way Emacs checks for this needs some work.

  reply	other threads:[~2005-06-09  3:54 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 [this message]
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
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=uy89k89s1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@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).