all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Jason Vas Dias <jason.vas.dias@gmail.com>
Cc: larsi@gnus.org, 51757@debbugs.gnu.org
Subject: bug#51757: 27.2; [patch] man.el : wait for all man(1) output to be buffered before fontifying
Date: Sat, 13 Nov 2021 19:38:20 +0200	[thread overview]
Message-ID: <86bl2oezid.fsf@mail.linkov.net> (raw)
In-Reply-To: <CALyZvKxWM8VJFkKUHM6Yys0vph8+UXdoPBzowKGXqqZgU_0YGA@mail.gmail.com> (Jason Vas Dias's message of "Fri, 12 Nov 2021 15:54:00 +0000")

> Oops, I meant:
> $ rpm -q emacs man-db groff-base
> emacs-27.2-5.fc34.x86_64
> man-db-2.9.3-3.fc34.x86_64
> groff-base-1.22.4-7.fc34.x86_64
>
> unless you are running these versions, with the Red Hat patches,
> you may not see this bug.

Sorry, I have a completely different configuration (Emacs 28 and Debian packages)
that might explain why I'm not seeing the problem.

Do you see it with `emacs -Q`?  Then installing Fedora 34 with exactly the
same package versions and the Red Hat patches could help to reproduce this.





  reply	other threads:[~2021-11-13 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10 23:45 bug#51757: 27.2; [patch] man.el : wait for all man(1) output to be buffered before fontifying Jason Vas Dias
2021-11-11  3:51 ` Lars Ingebrigtsen
2021-11-11 11:36   ` Jason Vas Dias
2021-11-11 11:51     ` Lars Ingebrigtsen
2021-11-11 12:08     ` Jason Vas Dias
2021-11-11 12:09       ` Lars Ingebrigtsen
2021-11-11 15:05       ` Eli Zaretskii
2021-11-11 17:35         ` Juri Linkov
     [not found]           ` <CALyZvKxJppsmxTPY7+Gzhc82eYY-a6cCdL25cQ23KbdD=RUU_Q@mail.gmail.com>
2021-11-12 15:50             ` Jason Vas Dias
2021-11-12 15:54               ` Jason Vas Dias
2021-11-13 17:38                 ` Juri Linkov [this message]
2021-11-15 23:06 ` Dan Čermák
2021-11-16  3:28   ` Eli Zaretskii
2021-12-23 10:24     ` Lars Ingebrigtsen

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86bl2oezid.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=51757@debbugs.gnu.org \
    --cc=jason.vas.dias@gmail.com \
    --cc=larsi@gnus.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.