unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: emacs-devel <emacs-devel@gnu.org>,
	Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: eglot.el defcustomʼs
Date: Tue, 25 Oct 2022 14:35:53 +0200	[thread overview]
Message-ID: <874jvsozbq.fsf@gmail.com> (raw)
In-Reply-To: <CALDnm51n6sCg7JRDRgMQ3H5MXUXsOROPX=kQQPGN9SPhZ5Gfiw@mail.gmail.com> ("João Távora"'s message of "Tue, 25 Oct 2022 13:26:01 +0100")

>>>>> On Tue, 25 Oct 2022 13:26:01 +0100, João Távora <joaotavora@gmail.com> said:

    >> all the defcustomʼs in eglot.el lack a :version tag. Is that
    >> intentional?


    João> No really, probably oversight and the fact that Eglot being a
    João> GNU ELPA package (presumably easy to upgrade) doesn't usually mean
    João> such version tags are so important.

Theyʼre not important until we start changing defaults, and then they
offer an easy way for people to identify from when they can start
shouting at us :-)

    João> That and the fact that Eglot doesn't really have that many defcustoms.

    João> So, if you want to add :version tags, go ahead.  Note that Eglot
    João> does GNU ELPA double-duty as a :core package, so not sure what
    João> you should put there, but others are perhaps better informed than
    João> me.

Iʼm not sure what the interaction is between :version in defcustomʼs
and eglot being a :core package, which is why I asked. Maybe Stefan
can enlighten us?

Robert
-- 



  reply	other threads:[~2022-10-25 12:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 12:21 eglot.el defcustomʼs Robert Pluim
2022-10-25 12:26 ` João Távora
2022-10-25 12:35   ` Robert Pluim [this message]
2022-10-25 13:24     ` Robert Pluim
2022-10-25 14:03       ` João Távora
2022-10-25 14:22         ` 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=874jvsozbq.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    /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).