From: Eli Zaretskii <eliz@gnu.org>
To: Lester Longley <lester@ieee.org>
Cc: 72761@debbugs.gnu.org
Subject: bug#72761: issues with Flymake online documentation
Date: Thu, 22 Aug 2024 21:03:01 +0300 [thread overview]
Message-ID: <868qwosaei.fsf@gnu.org> (raw)
In-Reply-To: <CAA3095_2+zW5jp95cK15Ej5wg76kievc2acNvk9c3wcmCYkVDQ@mail.gmail.com> (bug-gnu-emacs@gnu.org)
> Date: Thu, 22 Aug 2024 12:43:23 -0400
> From: Lester Longley via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> I see two issues at manual page: https://www.gnu.org/software/emacs/manual/html_mono/flymake.html
>
> (1) in sentence "See Eglot Features in Eglot: The Emacs LSP Client Flymake is also designed to be easily
> extended to support new backends via an Elisp interface.",
> the embedded link
> https://www.gnu.org/software/emacs/manual/html_node/eglot_html/Eglot-Features.html#Eglot-Features
> doesn't work (404 error)
> I think the correct link should be:
> https://www.gnu.org/software/emacs/manual/html_node/eglot/Eglot-Features.html#Eglot-Features
>
> The same issue is present at the "html_node" page
> https://www.gnu.org/software/emacs/manual/html_node/flymake/index.html
I don't see this here. First, the links are to
https://www.gnu.org/software/emacs/manual/html_mono/eglot.html#Eglot-Features
and not as you say, and they both work here.
> (2) the section https://www.gnu.org/software/emacs/manual/html_mono/flymake.html#Mode-line-status is
> empty, when I view it in Chrome 127, on a Chromebook, or in Chrome, on an Android phone.
> Here's browser snapshot from Chromebook; Android phone gives similar view:
I do see this. It's probably some problem with the produced HTML,
because the HTML is not empty:
<p>The following statuses are defined:
</p>
<table>
<tr><td width="25%">[<var>nerrors</var> <var>nwarnings</var> ...]</td><td width="75%">Normal operation. <var>nerrors</var> and <var>nwarnings</var> are, respectively,
the total number of errors and warnings found during the last buffer
check, for all backends. They may be followed by other totals for
other types of diagnostics (see <a href="#Flymake-error-types">Customizing Flymake error types</a>).</td></tr>
<tr><td width="25%"><code>Wait</code></td><td width="75%">Some Flymake backends haven’t reported since the last time they
where questioned. It is reasonable to assume that this is a temporary
delay and Flymake will resume normal operation soon.</td></tr>
<tr><td width="25%"><code>!</code></td><td width="75%">All the configured Flymake backends have disabled themselves: Flymake
cannot annotate the buffer and action from the user is needed to
investigate and remedy the situation (see <a href="#Troubleshooting">Troubleshooting</a>).</td></tr>
<tr><td width="25%"><code>?</code></td><td width="75%">There are no applicable Flymake backends for this buffer, thus Flymake
cannot annotate it. To fix this, a user may look to extending Flymake
and add a new backend (see <a href="#Extending-Flymake">Extending Flymake</a>).</td></tr>
</table>
Maybe some HTML expert can tell what is wrong with this <table>?
next prev parent reply other threads:[~2024-08-22 18:03 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 [this message]
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
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=868qwosaei.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72761@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.