unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alfie John <alfie@rustjobs.com>
Cc: 67159@debbugs.gnu.org
Subject: bug#67159: Flymake manual typos
Date: Tue, 14 Nov 2023 16:21:28 +0200	[thread overview]
Message-ID: <83ttpos9ef.fsf@gnu.org> (raw)
In-Reply-To: <01553D15-A16A-4BB5-BDE2-7E3D91EA5045@rustjobs.com> (bug-gnu-emacs@gnu.org)

> Date: Tue, 14 Nov 2023 10:52:30 +1100
> From:  Alfie John via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> Hi,
> 
> Here's a few minor changes to the FlyMake manual I believe should be made:
> 
> 	- These commands may affect more than one visited file belong to the project.
> 	+ These commands may affect more than one visited file belonging to the project.
> 
> 	- If there are, you the choice to execute
> 	+ If there are, you then choice to execute
> 
> 	- Ask Flymake system to display diagnostics
> 	+ Ask Flymake to display diagnostics

Thanks, but I seem to be unable to find these texts in the current
flymake.texi, both on the emacs-29 and the master branch.  What did I
miss?





  parent reply	other threads:[~2023-11-14 14:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13 23:52 bug#67159: Flymake manual typos Alfie John via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-14 10:50 ` João Távora
2023-11-14 14:21 ` Eli Zaretskii [this message]
2023-11-14 19:07   ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-14 19:16     ` 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

  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=83ttpos9ef.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=67159@debbugs.gnu.org \
    --cc=alfie@rustjobs.com \
    /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).