unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: emacs-devel@gnu.org
Subject: Re: master 5044c19 2/2: project.el: A project has only one main root now
Date: Mon, 25 May 2020 20:52:31 +0100	[thread overview]
Message-ID: <87ftbnu70g.fsf@gmail.com> (raw)
In-Reply-To: <9be4d0dd-f794-2b0f-7fbb-a24928b30c2c@yandex.ru> (Dmitry Gutov's message of "Mon, 25 May 2020 22:06:07 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> On 25.05.2020 20:17, João Távora wrote:
> I like this idea on paper, but pretty sure you're going to have this
> situation again. Some obsolete functions will remain outside of core 
> packages, right? And yet necessary to support older Emacs releases.

Yes, I'm not particularly convinced by the idea myself.  Anyway when
Eglot goes in the core that problem will be gone.  At any rate, the
"warning means error" will be a policy of Emacs tests, not Eglot's.
eglot-tests.el will be an abiding citizen of test/lisp like every other
one.

>> Perhaps Eglot should do neighter of those things, but perhaps if you
>> bumped the version in project.el to 0.3.0 then Eglot could just start
>> relying on that.  Or aren't you confident enough in this new API?
>
> I'll bump it now. There will be other breakages in the future,
> though. ;)

Thanks,
João



  reply	other threads:[~2020-05-25 19:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200523015940.19021.91647@vcs0.savannah.gnu.org>
     [not found] ` <20200523015942.848612043D@vcs0.savannah.gnu.org>
2020-05-25 17:17   ` master 5044c19 2/2: project.el: A project has only one main root now João Távora
2020-05-25 19:06     ` Dmitry Gutov
2020-05-25 19:52       ` João Távora [this message]
2020-05-25 20:00         ` Dmitry Gutov
2020-05-25 20:24           ` João Távora
2020-05-25 21:52             ` Dmitry Gutov
2020-05-25 22:01               ` João Távora

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=87ftbnu70g.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.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 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).