From: Eli Zaretskii <eliz@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: eglot manual suggestions
Date: Mon, 24 Oct 2022 20:03:23 +0300 [thread overview]
Message-ID: <83pmehp31g.fsf@gnu.org> (raw)
In-Reply-To: <87bkq1qkik.fsf@gmail.com> (message from Robert Pluim on Mon, 24 Oct 2022 18:00:35 +0200)
> From: Robert Pluim <rpluim@gmail.com>
> Date: Mon, 24 Oct 2022 18:00:35 +0200
>
> Normally, Iʼd just commit this, but I feel the Grammar Dragon has been
> poked enough for one week. I care not a whit if these are
> characterised as 'style changes' or 'grammar corrections', but I feel
> they are improvements.
In general, LGTM, thanks. However, ...
> -Eglot uses the Emacs's project management infrastructure to figure out
> +Eglot uses the Emacs project management infrastructure to figure out
Is "Emacs's" really wrong?
> -This section provides a reference of the most commonly used Eglot
> +This section provides a reference for the most commonly used Eglot
Is "reference of" incorrect?
> -To have Eglot stay away of some Emacs feature, add that feature's
> +To have Eglot stay away from some Emacs feature, add that feature's
"Stay away of" is incorrect?
> -If possible, we recommend to use these configuration files that are
> +If possible, we recommend to use those configuration files that are
> independent of Eglot and Emacs; they have the advantage that they will
> work with other LSP clients as well.
>
> If you do need to provide Emacs-specific configuration for a language
> -server, we recommend to define the appropriate value in the
> +server, we recommend defining the appropriate value in the
Here, you contradict yourself: if "recommend to use" is OK, then why
"recommend to define" isn't?
And AFAIU, both forms are correct English.
Also, why "those" in preference to "these"?
next prev parent reply other threads:[~2022-10-24 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 16:00 eglot manual suggestions Robert Pluim
2022-10-24 17:03 ` Eli Zaretskii [this message]
2022-10-24 17:56 ` Robert Pluim
2022-10-24 18:37 ` Mark H. David
2022-10-25 0:33 ` Po Lu
2022-10-25 8:29 ` João Távora
2022-10-25 9:39 ` Robert Pluim
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=83pmehp31g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.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).