From: Randy Taylor <dev@rjt.dev>
To: Yuan Fu <casouri@gmail.com>
Cc: "60137-done@debbugs.gnu.org" <60137-done@debbugs.gnu.org>,
Stefan Kangas <stefankangas@gmail.com>,
joaotavora@gmail.com
Subject: bug#60137: [PATCH] ; Put built-in modes first for eglot-server-programs
Date: Sun, 18 Dec 2022 18:46:21 +0000 [thread overview]
Message-ID: <xJyCdrlZEwzKYH6tmEqunjxIVePjHmgNJWiX-37lcvm5cx1EK2f7PWIdpGnSY1yVVGxLrJyA0WAa4NRkO2FAh_9F8C32F8f8qIUWQy4Fqas=@rjt.dev> (raw)
In-Reply-To: <89C407A0-7B83-4F6A-8096-CA43C944BF2A@gmail.com>
On Sunday, December 18th, 2022 at 03:22, Yuan Fu <casouri@gmail.com> wrote:
>
> Randy Taylor dev@rjt.dev writes:
>
> > On Saturday, December 17th, 2022 at 18:44, Yuan Fu casouri@gmail.com wrote:
> >
> > > Randy Taylor dev@rjt.dev writes:
> > >
> > > > Per Stefan's suggestion.
> > >
> > > Does the ordering matter? CC’d Stefan.
> > >
> > > Yuan
> >
> > Nope, Stefan's suggestion was (from Bug#60105, which I probably should've included in the initial bug):
> >
> > > This is a nit, but I think it might make more sense to users if we put
> > > the built-in mode first in the list. After all, the one we ship with
> > > Emacs is, or will be, the standard mode.
> >
> > It makes sense to me, hence the patch.
> >
> > I've CC'd João since eglot is his baby.
>
>
> IMHO, if it doesn’t matter, there is no need to add a commit to the
> history for it. Stefan probably mentioned it because it was in a patch.
>
>
> Yuan
>
I just thought it would be nice to keep everything consistent.
Closing since there's no interest.
prev parent reply other threads:[~2022-12-18 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-17 2:48 bug#60137: [PATCH] ; Put built-in modes first for eglot-server-programs Randy Taylor
2022-12-17 23:44 ` Yuan Fu
2022-12-18 1:56 ` Randy Taylor
2022-12-18 4:13 ` João Távora
2022-12-18 8:22 ` Yuan Fu
2022-12-18 18:46 ` Randy Taylor [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
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='xJyCdrlZEwzKYH6tmEqunjxIVePjHmgNJWiX-37lcvm5cx1EK2f7PWIdpGnSY1yVVGxLrJyA0WAa4NRkO2FAh_9F8C32F8f8qIUWQy4Fqas=@rjt.dev' \
--to=dev@rjt.dev \
--cc=60137-done@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=joaotavora@gmail.com \
--cc=stefankangas@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).