unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tim Landscheidt <tim@tim-landscheidt.de>
Cc: 46804@debbugs.gnu.org
Subject: bug#46804: 27.1; Man page for git-config(1) is partly displayed in overstriked font
Date: Sun, 28 Feb 2021 14:49:19 +0100	[thread overview]
Message-ID: <87y2f8mheo.fsf@gnus.org> (raw)
In-Reply-To: <87h7lwn4ce.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Sun, 28 Feb 2021 05:33:53 +0000")

Tim Landscheidt <tim@tim-landscheidt.de> writes:

> Well, if I had copied & pasted "pre-receive" correctly … :-)

:-)

>> So it's possible what you're seeing has been fixed in Emacs 28.  Would
>> it be possible for you to build the development version of Emacs and see
>> whether the problem is still present there?
>
> I have tested master and it works, and then backported
> 2e2a8e5491bc6259a9ebe8c703c1c501307953e2 to 27.1, and it
> fixes the issue.

Be aware, though, that that patch leads to severe regressions in eshell
(and sometimes in shell mode, too) -- you need f1fa35f0914f to fix that
problem.

And I'm not 100% sure about the fix in f1fa35f0914f, so backporting
these two things to Emacs 27 is out of scope, I think.  (We're only
fixing regressions in Emacs 27 now, and this man.el problem was also
present in Emacs 26, if I remember correctly.)  So this won't be fixed
in Emacs 27, but is fixed in Emacs 28, and I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2021-02-28 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-26 22:10 bug#46804: 27.1; Man page for git-config(1) is partly displayed in overstriked font Tim Landscheidt
2021-02-27  4:50 ` Lars Ingebrigtsen
2021-02-28  5:33   ` Tim Landscheidt
2021-02-28 13:49     ` Lars Ingebrigtsen [this message]

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=87y2f8mheo.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=46804@debbugs.gnu.org \
    --cc=tim@tim-landscheidt.de \
    /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).