From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#62265: Underline does not work in Terminal Emacs Date: Sun, 16 Apr 2023 09:22:53 +0300 Message-ID: <83o7nobb2a.fsf@gnu.org> References: <87wn3ex8ik.fsf@kisara.moe> <83edpmaqrs.fsf@gnu.org> <7cf462de-97f7-26ef-a33f-e3ff59c8b55e@gmail.com> <87mt49jbql.fsf@kisara.moe> <83v8ix9dlh.fsf@gnu.org> <87r0tlm01a.fsf@kisara.moe> <83r0tl9bf0.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5408"; mail-complaints-to="usenet@ciao.gmane.io" Cc: jporterbugs@gmail.com, 62265-done@debbugs.gnu.org To: mohkale@kisara.moe, mikeh@muppetlabs.com Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Apr 16 08:23:23 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pnvnG-0001EH-Oj for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 16 Apr 2023 08:23:22 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pnvmy-0007ld-I3; Sun, 16 Apr 2023 02:23:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pnvmw-0007kd-Ic for bug-gnu-emacs@gnu.org; Sun, 16 Apr 2023 02:23:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pnvmw-0001A2-AS for bug-gnu-emacs@gnu.org; Sun, 16 Apr 2023 02:23:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pnvmw-000541-6L for bug-gnu-emacs@gnu.org; Sun, 16 Apr 2023 02:23:02 -0400 Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-To: bug-gnu-emacs@gnu.org Resent-Date: Sun, 16 Apr 2023 06:23:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: cc-closed 62265 X-GNU-PR-Package: emacs Mail-Followup-To: 62265@debbugs.gnu.org, eliz@gnu.org, mohkale@kisara.moe Original-Received: via spool by 62265-done@debbugs.gnu.org id=D62265.168162618019442 (code D ref 62265); Sun, 16 Apr 2023 06:23:02 +0000 Original-Received: (at 62265-done) by debbugs.gnu.org; 16 Apr 2023 06:23:00 +0000 Original-Received: from localhost ([127.0.0.1]:50510 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pnvmu-00053V-BT for submit@debbugs.gnu.org; Sun, 16 Apr 2023 02:23:00 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:53230) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pnvms-00053I-HX for 62265-done@debbugs.gnu.org; Sun, 16 Apr 2023 02:22:58 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pnvmm-00019E-Ce; Sun, 16 Apr 2023 02:22:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=7S9OzokyjrsHCquAi4/OsJoLuXvxvHTwTfrB9b12Ht8=; b=Mo35wSoQD9G4 wACTR7roGzwC5IXGg+hxieSUS/hhV3bvhyFSZ8+4qYr4mjrqEVeTG2ygzAgxIGXz5lmLs5f6lFwBK PI3784z3grvjBoQTshmmA5SK8D8a36CAr8cLhFntuMct+kNdUKsRXEThqeiUnYl8BXCxpphtK9iRK PNO8Hmol++oYBlQC0EAtdrb/x2FEQjcXZB6EingoU0s9er2rYWZFYiJ3fFQg2ejP7GK7SYgJuwzdJ ILOYOQnUEHFQLgFVFmLCCAJeh0AzGWZZ2wUtiRMhWsrKtZwtpJoPm1BYGQA0HrbhJiQuarBZiQXTa aAwQqCuZrvqpfvNic8klZg==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pnvml-0002qI-HM; Sun, 16 Apr 2023 02:22:51 -0400 In-Reply-To: <83r0tl9bf0.fsf@gnu.org> (message from Eli Zaretskii on Sun, 19 Mar 2023 14:24:19 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:260096 Archived-At: > Cc: jporterbugs@gmail.com, 62265@debbugs.gnu.org > Date: Sun, 19 Mar 2023 14:24:19 +0200 > From: Eli Zaretskii > > > From: Mohsin Kaleem > > Cc: jporterbugs@gmail.com, 62265@debbugs.gnu.org > > Date: Sun, 19 Mar 2023 11:51:45 +0000 > > > > Eli Zaretskii 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? No further comments, so I've installed a fix for this along the lines we discussed, and I'm closing this bug.