unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mohsin Kaleem <mohkale@kisara.moe>, Mike Hamrick <mikeh@muppetlabs.com>
Cc: jporterbugs@gmail.com, 62265@debbugs.gnu.org
Subject: bug#62265: Underline does not work in Terminal Emacs
Date: Sun, 19 Mar 2023 14:24:19 +0200	[thread overview]
Message-ID: <83r0tl9bf0.fsf@gnu.org> (raw)
In-Reply-To: <87r0tlm01a.fsf@kisara.moe> (message from Mohsin Kaleem on Sun, 19 Mar 2023 11:51:45 +0000)

> From: Mohsin Kaleem <mohkale@kisara.moe>
> Cc: jporterbugs@gmail.com, 62265@debbugs.gnu.org
> Date: Sun, 19 Mar 2023 11:51:45 +0000
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > However, what about the non-TERMINFO branch?  Do termcap databases
> > support this capability and tigetstr?  I wonder whether we should do
> > one of the following:
> >
> >   . support "smxx" only when TERMINFO is defined
> >   . support "smxx" regardless of whether TERMINFO is defined
> 
> The latter wouldn't be possible for those using terminfo because of the
> issue I described before. I'm okay with the former approach but I
> imagine the author of the original TTY strikethrough patch was building
> Emacs without terminfo and they described the patch as working for them
> so I'd have to conclude termcap does support this (in a non-compliant
> ncurses way). Switching to the former approach might break their
> workflow since if they build without terminfo they'd lose strikethrough
> altogether. I'm happy to test whether this would be the case but not
> sure how to. The difference between termcap and terminfo seem kinda
> arbitrary to me and I can't find any documentation describing the exact
> difference (except this sort of 2 letter restriction in termcap
> extensions).

If your hypothesis is correct, I'm fine with leaving the non-TERMINFO
branch using tgetstr.  But is it indeed correct?

Let's ask the author of that strikethrough patch.  Mike, can you tell
whether you tested the patch on a system with or without terminfo?
And what, if anything, can you tell about using tgetstr for
capabilities whose names are more than 2 characters -- is that
supported with the curses library you were using at the time?

Thanks.





  reply	other threads:[~2023-03-19 12:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-18 17:40 bug#62265: Underline does not work in Terminal Emacs Mohsin Kaleem
2023-03-18 17:51 ` Mohsin Kaleem
2023-03-18 17:55 ` Eli Zaretskii
2023-03-18 18:50   ` Jim Porter
2023-03-19 10:07     ` Mohsin Kaleem
2023-03-19 11:37       ` Eli Zaretskii
2023-03-19 11:51         ` Mohsin Kaleem
2023-03-19 12:24           ` Eli Zaretskii [this message]
2023-04-16  6:22             ` Eli Zaretskii
2023-03-18 18:01 ` Eli Zaretskii
2023-03-18 18:07   ` Mohsin Kaleem

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=83r0tl9bf0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62265@debbugs.gnu.org \
    --cc=jporterbugs@gmail.com \
    --cc=mikeh@muppetlabs.com \
    --cc=mohkale@kisara.moe \
    /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).