From: Eli Zaretskii <eliz@gnu.org>
To: Lester Longley <lester@ieee.org>
Cc: 72761-done@debbugs.gnu.org
Subject: bug#72761: issues with Flymake online documentation
Date: Sat, 31 Aug 2024 12:46:54 +0300 [thread overview]
Message-ID: <86zfotausx.fsf@gnu.org> (raw)
In-Reply-To: <CAA30958BP0PCJqcEJQoX=9GhoLavy+s2r2VUmwpgTSSTA45mBQ@mail.gmail.com> (message from Lester Longley on Sun, 25 Aug 2024 10:06:02 -0400)
> From: Lester Longley <lester@ieee.org>
> Date: Sun, 25 Aug 2024 10:06:02 -0400
> Cc: 72761@debbugs.gnu.org
>
> Hi Eli,
>
> On Sun, Aug 25, 2024 at 8:48 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > Thanks, I've now fixed the relevant HTML page, and also modified the
> > script we use to produce HTML manuals to not perform this kind of
> > "editing" of HTML produced by makeinfo.
>
> Thank you very much. The Flymake manuals work fine now, as regards both issues.
>
> (And the update you made to "admin/admin.el" was instructive, for me,
> re: the manual-generation infrastructure.)
Thanks, I'm therefore closing this bug.
prev parent reply other threads:[~2024-08-31 9:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 16:43 bug#72761: issues with Flymake online documentation Lester Longley via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 18:03 ` Eli Zaretskii
2024-08-22 18:21 ` Lester Longley via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 18:23 ` Eli Zaretskii
2024-08-22 19:07 ` Lester Longley via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-22 19:15 ` Eli Zaretskii
2024-08-22 21:01 ` Lester Longley via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-23 7:06 ` Eli Zaretskii
2024-08-23 7:40 ` Lester Longley via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-25 12:48 ` Eli Zaretskii
2024-08-25 14:06 ` Lester Longley via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-31 9:46 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zfotausx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72761-done@debbugs.gnu.org \
--cc=lester@ieee.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.