From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 62720@debbugs.gnu.org, joaotavora@gmail.com,
monnier@iro.umontreal.ca
Subject: bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot
Date: Wed, 12 Apr 2023 20:10:50 +0000 [thread overview]
Message-ID: <87pm88kgj9.fsf@posteo.net> (raw)
In-Reply-To: <83edop6sdy.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 12 Apr 2023 18:18:33 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Philip Kaludercic <philipk@posteo.net>
>> Cc: joaotavora@gmail.com, monnier@iro.umontreal.ca, 62720@debbugs.gnu.org,
>> larsi@gnus.org
>> Date: Wed, 12 Apr 2023 13:42:56 +0000
>>
>> >> After thinking about this for a bit, I think that the right approach is
>> >> to use package-install instead of writing a separate command. After
>> >> all, this will make the behaviour of package-install consistent with
>> >> that of the package menu.
>> >
>> > Is this for master or for the release branch?
>>
>> Personally I am indifferent, it should be compatible with both
>
> If we want to install this on the release branch, the changes must be
> very safe, which in this case basically means "do not touch any code
> used when updating non-core packages".
>
> If the patch you presented is all there is to it, then I'm afraid it
> doesn't satisfy the above condition, because it does affect the use
> case of updating an ELPA package that is not in core. So I cannot
> agree to installing this on emacs-29 in the form you posted, sorry.
I understand your concern,
>> > And I thought we all agreed built-in packages need special treatment
>> > anyway, didn't we? Then why having a separate command is not a
>> > natural next step?
>>
>> I don't necessarily agree that "special treatment" requires a separate
>> command.
>
> Even if you don't agree with that in general, having a separate
> command would allow us to install that command on emacs-29 without any
> fears. So that alone is a significant advantage, even if the rest are
> not yet agreed upon.
Would this be a permanent thing, or would the command be deprecated by
emacs-30? I get the need under the circumstances, but it doesn't seem
like the best solution if we were to set aside release-concerns.
>> I think it is wrong the assume that an built-in package should
>> automatically be updated to a ELPA package whenever possible.
>
> This seems to be an argument in favor of a separate command? Or what
> did you mean by that, and how is it related to the issue at hand?
I don't think package-update should switch from a built-in package to a
package that was installed from ELPA. The user should at least once
commit to the switch (be it with a separate command or package-install).
>> >> It might work but it should be tested somewhat thoroughly before the
>> >> patch is applied. In the meantime, I just finished a similar approach
>> >> that does not modify `package-installed-p', but just adds another
>> >> utility function:
>> >
>> > A new utility function is fine by me, even if this is e branch. But I
>> > don't quite understand how this is supposed to work in package-install
>> > to allow updating built-in packages, and do that in a way that will
>> > not touch the existing code for non-built-in packages in significant
>> > ways (assuming you propose this from the release branch). Can you
>> > elaborate on that?
>>
>> The only reason we couldn't install built-in packages is that when
>> planning to install packages `package-compute-transaction' believes that
>> if a built-in package is provided, then everything is fine and we don't
>> need to proceed with installing any packages. All I propose is to lift
>> this assumption, then this works fine.
>
> My problem is _how_ to lift this assumption. The way you propose
> doing that affects updating non-core packages in ways that we will not
> have enough time to test well enough, not compared to the year that
> these commands exist in package.el and were used by many people in
> many cases. So we have the following alternatives for the way
> forward:
>
> . install your changes on master only, and leave the problem of
> updating a core package unsolved in Emacs 29 (with the workaround
> mentioned in the beginning of this bug's discussion available to
> alleviate the problem to some extent)
> . come up with safer changes for package-install that could be
> installed on emacs-29
> . add a new command for updating a core package, which can then be
> safely installed on emacs-29
>
> The last 2 alternatives can be for emacs-29 only, whereas on master we
> install your proposed change (or something else).
I would like to investigate option 2, but if nothing is found we can
fall back to 3. But even if there are issues in this case, I don't
consider the matter in general to be that drastic. If all Joao wants is
to avoid confusion, we can also improve the error message that
`package-install' generates when it says that a package ins already
installed.
> For the 2nd alternative above to be acceptable, the added/modified
> code must be completely separate from the code we have now, so that
> any possibility of its destabilizing the current code could be
> eliminated. It could be a separate code, triggered by the prefix
> argument, for example.
OK.
>> One point that might be deliberated is that this means all built-in
>> dependencies are also installed, even if these are not strictly
>> necessary. It shouldn't matter that much, since most users would
>> upgrade them eventually, but worth mentioning I guess?
>
> That just confirms my fears that we are opening a Pandora's box. We
> have no idea what this will do, and no time to test the results.
> Unintended consequences are abundant. We must draw any such
> consequences to the absolute minimum, at least the way the commands
> work by default. Even if the result is less than elegant.
Intuitively I would want to argue that this change has an upper-bound to
how much harm it could do, but as I cannot prove it in any way I'll
rather not assert that the point.
>> >> +(defun package-core-p (package)
>> >> + "Return non-nil the built-in version of PACKAGE is loaded."
>> >
>> > Didn't you say the "core" terminology was confusing people?
>>
>> TBH I am not really satisfied with the name (so any other suggestion is
>> just as fine for me), and as Joao said it would be better to make the
>> predicate as internal so that users are not expected to deal with it.
>
> The name should still be self-explanatory enough, because we the Emacs
> maintainers will read this code and should be able to understand what
> the function does without reading is source every time.
OK.
>>
>> >> + (let ((package (if (package-desc-p package)
>> >> + (package-desc-name package)
>> >> + package)))
>> >> + (and (assq package (package--alist))
>> >> + (package-built-in-p package))))
>> >
>> > It sounds like this doesn't check whether a package is "core", it
>> > checks whether it's built-in and can be updated? So maybe the name
>> > should be changed to reflect that? And the doc string as well (what
>> > it means by "is loaded")?
>>
>> Right the "loaded" doesn't make sense. How about this:
>>
>> +(defun package--upgradable-built-in-p (package)
>> + "Check if a built-in PACKAGE can be upgraded.
>> +This command differs from `package-built-in-p' in that it only
>> +returns a non-nil value if the user has not installed a more
>> +recent version of the package from a package archive."
>
> Note that what the doc string says is not what the name tells us.
> "Upgradeable" and "user has not installed a more recent version" are
> not the same. What the doc string says calls for a name like
> package--built-in-and-up-to-date or something.
>
>> + (and (not (assq (cond
>> + ((package-desc-p package)
>> + (package-desc-name package))
>> + ((stringp package) (intern package))
>> + ((symbolp package) package)
>> + ((error "Unknown package format: %S" package)))
>> + (package--alist)))
>> + (package-built-in-p package)))
>
> Why do we need all these conditions, where we didn't need them in the
> current code?
Practically speaking these conditions are not necessary, I just added it
in case there was the need to use the function elsewhere at some point.
> Also, package-alist is documented as "alist of all packages available
> for activation", so it is not clear how the fact that assq returns nil
> is evidence that "the user has not installed a more recent version".
> Looking at what package--alist and package-load-all-descriptors do, it
> looks like they just collect packages that were downloaded into the
> relevant directories? Is that enough to consider any package not in
> the list to be "not installed"?
The point is that package.el will add all packages it manages (ie. are
"available to activation") to package-alist. Built-in/core packages are
not managed by package.el, but just "acknowledged" via
`package--builtins'. So this looks like a safe assumption to me.
> And what about the "more recent
> version" condition -- this doesn't seem to be tested anywhere in
> package--alist?
You are right, but this is a misphrasing.
> The above questions and undocumented subtleties is what scares me in
> installing such changes at this late stage. I'm not sure everyone
> involved, yourself included, have a clear understanding of what the
> modified code will do in each possible use case. That is why I very
> much prefer separate code, which will then free us from the need of
> considering all these subtleties, as the last year of user's
> experience with this code can vouch that it does its job correctly, by
> and large.
next prev parent reply other threads:[~2023-04-12 20:10 UTC|newest]
Thread overview: 370+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 22:12 bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot João Távora
2023-04-08 1:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-08 10:43 ` Philip Kaludercic
2023-04-08 10:48 ` João Távora
2023-04-08 14:42 ` Philip Kaludercic
2023-04-08 15:25 ` João Távora
2023-04-08 15:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-10 16:01 ` João Távora
2023-04-10 18:13 ` Philip Kaludercic
2023-04-11 11:02 ` João Távora
2023-04-11 11:40 ` Eli Zaretskii
2023-04-11 12:52 ` João Távora
2023-04-11 17:55 ` Eli Zaretskii
2023-04-11 18:31 ` João Távora
2023-04-11 18:52 ` Eli Zaretskii
2023-04-11 20:08 ` João Távora
2023-04-11 20:25 ` João Távora
2023-04-12 5:49 ` Eli Zaretskii
2023-04-12 7:58 ` João Távora
2023-04-12 8:19 ` Eli Zaretskii
2023-04-12 8:51 ` João Távora
2023-04-12 10:23 ` Eli Zaretskii
2023-04-12 10:38 ` João Távora
2023-04-12 11:01 ` Eli Zaretskii
2023-04-12 11:00 ` João Távora
2023-04-12 11:08 ` Eli Zaretskii
2023-04-12 11:15 ` João Távora
2023-04-12 11:22 ` Eli Zaretskii
2023-04-12 11:35 ` João Távora
2023-04-12 11:47 ` Eli Zaretskii
2023-04-12 12:01 ` João Távora
2023-04-12 12:00 ` Philip Kaludercic
2023-04-12 12:18 ` João Távora
2023-04-12 12:28 ` Philip Kaludercic
2023-04-12 12:55 ` João Távora
2023-04-12 12:30 ` Eli Zaretskii
2023-04-12 13:42 ` Philip Kaludercic
2023-04-12 14:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-12 14:14 ` João Távora
2023-04-12 14:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-12 14:20 ` João Távora
2023-04-12 15:18 ` Eli Zaretskii
2023-04-12 16:13 ` João Távora
2023-04-12 16:16 ` João Távora
2023-04-12 16:53 ` Eli Zaretskii
2023-04-12 17:14 ` João Távora
2023-04-12 17:22 ` Eli Zaretskii
2023-04-12 17:43 ` João Távora
2023-04-12 19:09 ` Eli Zaretskii
2023-04-12 19:39 ` Philip Kaludercic
2023-04-13 5:30 ` Eli Zaretskii
2023-04-13 7:38 ` Philip Kaludercic
2023-04-13 8:11 ` Eli Zaretskii
2023-04-13 11:23 ` Philip Kaludercic
2023-04-13 15:03 ` Eli Zaretskii
2023-04-13 15:10 ` Philip Kaludercic
2023-04-13 15:56 ` Eli Zaretskii
2023-04-13 17:49 ` Philip Kaludercic
2023-04-13 18:15 ` Eli Zaretskii
2023-04-13 18:49 ` Philip Kaludercic
2023-04-14 10:54 ` Eli Zaretskii
2023-04-14 12:34 ` Robert Pluim
2023-04-14 12:56 ` João Távora
2023-04-14 13:52 ` Robert Pluim
2023-04-14 15:34 ` João Távora
2023-04-14 15:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-14 16:05 ` João Távora
2023-04-14 16:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-14 16:34 ` Dmitry Gutov
2023-04-14 16:40 ` João Távora
2023-04-14 16:53 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-14 17:49 ` Eli Zaretskii
2023-04-14 18:32 ` João Távora
2023-04-14 18:49 ` Eli Zaretskii
2023-04-14 19:03 ` João Távora
2023-04-14 19:18 ` Eli Zaretskii
2023-04-14 19:31 ` João Távora
2023-04-14 16:12 ` Dmitry Gutov
2023-04-14 16:31 ` João Távora
2023-04-14 16:54 ` Philip Kaludercic
2023-04-14 17:32 ` João Távora
2023-04-14 18:27 ` Philip Kaludercic
2023-04-14 18:39 ` João Távora
2023-04-14 19:33 ` Philip Kaludercic
2023-04-14 19:48 ` João Távora
2023-04-14 17:53 ` Eli Zaretskii
2023-04-14 18:44 ` João Távora
2023-04-14 18:51 ` Eli Zaretskii
2023-04-14 19:14 ` Dmitry Gutov
2023-04-14 19:19 ` Eli Zaretskii
2023-04-14 19:21 ` Dmitry Gutov
2023-04-14 19:30 ` Eli Zaretskii
2023-04-14 19:34 ` João Távora
2023-04-14 19:20 ` João Távora
2023-04-14 19:28 ` Eli Zaretskii
2023-04-14 19:46 ` João Távora
2023-04-14 20:04 ` Philip Kaludercic
2023-04-15 8:35 ` João Távora
2023-04-15 10:40 ` Philip Kaludercic
2023-04-15 10:44 ` João Távora
2023-04-15 12:34 ` Dmitry Gutov
2023-04-15 9:03 ` Eli Zaretskii
2023-04-15 10:24 ` João Távora
2023-04-15 10:28 ` Eli Zaretskii
2023-04-15 11:19 ` Kévin Le Gouguec
2023-04-15 12:33 ` Dmitry Gutov
2023-04-15 13:36 ` João Távora
2023-04-15 16:53 ` Philip Kaludercic
2023-04-15 21:16 ` Kévin Le Gouguec
2023-04-16 10:23 ` João Távora
2023-04-16 20:46 ` Dmitry Gutov
2023-04-16 21:54 ` João Távora
2023-04-17 2:30 ` Eli Zaretskii
2023-04-17 2:24 ` Eli Zaretskii
2023-04-18 1:25 ` Dmitry Gutov
2023-04-18 11:44 ` João Távora
2023-04-18 20:38 ` Dmitry Gutov
2023-04-18 20:56 ` João Távora
2023-04-18 21:06 ` Dmitry Gutov
2023-04-18 21:15 ` João Távora
2023-04-18 21:20 ` Dmitry Gutov
2023-04-19 12:05 ` Eli Zaretskii
2023-04-19 13:04 ` João Távora
2023-04-19 13:35 ` Eli Zaretskii
2023-04-19 14:04 ` João Távora
2023-04-19 16:02 ` Eli Zaretskii
2023-04-19 16:17 ` João Távora
2023-04-19 15:48 ` Dmitry Gutov
2023-04-19 16:10 ` Eli Zaretskii
2023-04-19 16:23 ` João Távora
2023-04-19 16:50 ` Eli Zaretskii
2023-04-19 17:27 ` João Távora
2023-04-19 18:00 ` Eli Zaretskii
2023-04-19 18:27 ` João Távora
2023-04-19 18:48 ` Eli Zaretskii
2023-04-19 17:23 ` Dmitry Gutov
2023-04-19 17:53 ` Eli Zaretskii
2023-04-18 12:57 ` Stability of core packages (was: Not easy at all to upgrade :core packages like Eglot) Eli Zaretskii
2023-04-18 14:02 ` João Távora
2023-04-18 14:47 ` Eli Zaretskii
2023-04-18 15:45 ` João Távora
2023-04-18 16:19 ` Eli Zaretskii
2023-04-18 17:49 ` João Távora
2023-04-18 21:19 ` Dmitry Gutov
2023-04-18 18:56 ` Jim Porter
2023-04-18 19:21 ` Eli Zaretskii
2023-04-18 19:36 ` Jim Porter
2023-04-19 11:55 ` Eli Zaretskii
2023-04-19 8:50 ` João Távora
2023-04-19 12:13 ` Dr. Arne Babenhauserheide
2023-04-19 17:03 ` Eli Zaretskii
2023-04-19 17:21 ` João Távora
2023-04-19 18:07 ` Eli Zaretskii
2023-04-19 18:14 ` Dmitry Gutov
2023-04-19 18:32 ` Eli Zaretskii
2023-04-19 19:33 ` João Távora
2023-04-20 4:26 ` tomas
2023-04-19 19:39 ` Dmitry Gutov
2023-04-19 19:46 ` João Távora
2023-04-19 20:50 ` Dmitry Gutov
2023-04-19 20:57 ` João Távora
2023-04-19 21:58 ` Jim Porter
2023-04-19 22:29 ` João Távora
2023-04-19 22:42 ` Jim Porter
2023-04-19 22:58 ` João Távora
2023-04-19 22:06 ` Dmitry Gutov
2023-04-19 22:21 ` Jim Porter
2023-04-19 22:27 ` Dmitry Gutov
2023-04-19 22:43 ` Jim Porter
2023-04-20 10:02 ` bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot Eli Zaretskii
2023-04-20 10:31 ` João Távora
2023-04-20 11:49 ` Eli Zaretskii
2023-04-20 11:53 ` João Távora
2023-04-20 12:14 ` Eli Zaretskii
2023-04-20 13:39 ` Dmitry Gutov
2023-04-20 13:56 ` João Távora
2023-04-20 14:25 ` João Távora
2023-04-20 14:31 ` Dmitry Gutov
2023-04-20 14:40 ` João Távora
2023-04-21 0:22 ` Dmitry Gutov
2023-04-20 14:49 ` Eli Zaretskii
2023-04-20 15:03 ` João Távora
2023-04-20 14:51 ` Philip Kaludercic
2023-04-20 14:30 ` Dmitry Gutov
2023-04-20 14:25 ` Eli Zaretskii
2023-04-20 18:08 ` Robert Pluim
2023-04-20 18:24 ` Philip Kaludercic
2023-04-20 18:53 ` João Távora
2023-04-24 7:48 ` Robert Pluim
2023-04-24 8:57 ` João Távora
2023-04-24 9:38 ` Robert Pluim
2023-04-24 11:43 ` João Távora
2023-04-24 13:01 ` Robert Pluim
2023-04-24 13:08 ` Eli Zaretskii
2023-04-24 13:12 ` Robert Pluim
2023-04-24 20:36 ` Dmitry Gutov
2023-04-24 22:45 ` João Távora
2023-04-21 0:50 ` Dmitry Gutov
2023-04-21 6:37 ` Eli Zaretskii
2023-04-21 10:19 ` Dmitry Gutov
2023-04-21 11:05 ` Eli Zaretskii
2023-04-21 23:12 ` Dmitry Gutov
2023-04-22 0:57 ` Dmitry Gutov
2023-04-22 8:33 ` Eli Zaretskii
2023-04-22 10:30 ` Dmitry Gutov
2023-04-22 11:11 ` Eli Zaretskii
2023-04-22 11:24 ` Dmitry Gutov
2023-04-22 11:29 ` Dmitry Gutov
2023-04-22 12:01 ` Eli Zaretskii
2023-04-22 12:00 ` Eli Zaretskii
2023-04-22 12:14 ` Dmitry Gutov
2023-04-22 12:24 ` Eli Zaretskii
2023-04-22 23:46 ` Dmitry Gutov
2023-04-23 6:39 ` Eli Zaretskii
2023-04-23 11:58 ` Dmitry Gutov
2023-04-23 13:02 ` Eli Zaretskii
2023-04-23 13:11 ` Dmitry Gutov
2023-04-23 14:24 ` Eli Zaretskii
2023-04-23 21:53 ` Dmitry Gutov
2023-04-24 11:58 ` Eli Zaretskii
2023-04-24 23:45 ` Dmitry Gutov
2023-04-25 7:47 ` Eli Zaretskii
2023-04-25 12:08 ` Dmitry Gutov
2023-04-25 12:12 ` João Távora
2023-04-25 12:43 ` Eli Zaretskii
2023-04-25 18:35 ` Dmitry Gutov
2023-04-26 23:05 ` Dmitry Gutov
2023-04-27 5:41 ` Eli Zaretskii
2023-04-27 9:00 ` Dmitry Gutov
2023-04-27 10:44 ` Eli Zaretskii
2023-04-27 23:51 ` Dmitry Gutov
2023-04-28 5:19 ` Eli Zaretskii
2023-05-04 23:58 ` Dmitry Gutov
2023-05-05 5:04 ` Eli Zaretskii
2023-05-05 5:41 ` Philip Kaludercic
2023-05-05 13:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-05 14:05 ` Eli Zaretskii
2023-05-06 1:02 ` Dmitry Gutov
2023-04-23 13:05 ` Philip Kaludercic
2023-04-23 13:09 ` Dmitry Gutov
2023-04-22 0:57 ` João Távora
2023-04-22 11:38 ` Dmitry Gutov
2023-04-22 12:12 ` João Távora
2023-04-22 8:26 ` Eli Zaretskii
2023-04-22 10:48 ` Dmitry Gutov
2023-04-22 11:20 ` Eli Zaretskii
[not found] ` <f32d7008-ea39-a9d7-8224-2c5b969236b7@gutov.dev>
[not found] ` <CALDnm53vPnODxpv_=nvOHRjLX-PfhyTS0MFudR0qZ3Pa-Lw-AQ@mail.gmail.com>
2023-04-19 23:25 ` Stability of core packages (was: Not easy at all to upgrade :core packages like Eglot) Dmitry Gutov
2023-04-20 0:13 ` João Távora
2023-04-20 1:13 ` Dmitry Gutov
2023-04-20 1:49 ` João Távora
2023-04-20 2:04 ` Dmitry Gutov
2023-04-19 19:15 ` João Távora
2023-04-20 9:38 ` Eli Zaretskii
2023-04-20 9:48 ` João Távora
2023-04-20 11:47 ` Eli Zaretskii
2023-04-20 12:00 ` João Távora
2023-04-20 12:16 ` Eli Zaretskii
2023-04-20 12:24 ` João Távora
2023-04-19 17:35 ` John Yates
2023-04-19 17:42 ` João Távora
2023-04-19 18:02 ` Eli Zaretskii
2023-04-19 18:04 ` Jim Porter
2023-04-19 18:34 ` Eli Zaretskii
2023-04-19 19:35 ` Jim Porter
2023-04-20 9:49 ` Eli Zaretskii
2023-04-19 19:40 ` Dr. Arne Babenhauserheide
2023-04-20 6:02 ` Eli Zaretskii
2023-04-29 5:21 ` Stability of core packages emacs
2023-04-29 6:26 ` Eli Zaretskii
2023-04-29 21:47 ` Mohsen BANAN
2023-04-30 6:21 ` Eli Zaretskii
2023-04-30 9:07 ` Philip Kaludercic
2023-04-30 13:12 ` Corwin Brust
2023-05-07 5:58 ` Mohsen BANAN
2023-05-05 4:36 ` David Masterson
2023-05-05 4:56 ` David Masterson
[not found] ` <878re3bdj6.fsf@penguin>
2023-05-05 4:59 ` David Masterson
2023-04-19 12:55 ` Stability of core packages (was: Not easy at all to upgrade :core packages like Eglot) Eli Zaretskii
2023-04-19 13:18 ` João Távora
2023-04-19 13:44 ` Eli Zaretskii
2023-04-19 14:13 ` João Távora
2023-04-18 22:10 ` Dmitry Gutov
2023-04-19 8:34 ` João Távora
2023-04-19 12:47 ` Eli Zaretskii
2023-04-19 18:22 ` Jim Porter
2023-04-19 18:37 ` Eli Zaretskii
2023-04-19 19:32 ` Jim Porter
2023-04-19 22:51 ` Lynn Winebarger
2023-04-20 13:47 ` history of ELPA packages and dependencies (was: Stability of core packages (was: Not easy at all to upgrade :core packages like Eglot)) Lynn Winebarger
2023-04-20 13:58 ` Stability of core packages (was: Not easy at all to upgrade :core packages like Eglot) Lynn Winebarger
2023-04-19 19:25 ` Dmitry Gutov
2023-04-19 19:40 ` João Távora
2023-04-20 9:47 ` Eli Zaretskii
2023-04-20 13:03 ` Dmitry Gutov
2023-04-20 14:03 ` Eli Zaretskii
2023-04-20 14:22 ` Dmitry Gutov
2023-04-20 14:42 ` Eli Zaretskii
2023-04-20 15:30 ` Dmitry Gutov
2023-04-20 15:49 ` Eli Zaretskii
2023-04-20 17:26 ` Stability of core packages Philip Kaludercic
2023-04-20 18:46 ` Eli Zaretskii
2023-04-20 21:25 ` Stability of core packages (was: Not easy at all to upgrade :core packages like Eglot) Dmitry Gutov
2023-04-21 14:12 ` Lynn Winebarger
2023-04-19 12:31 ` What is :core? (was: Stability of core packages (was: Not easy at all to upgrade :core packages like Eglot)) Lynn Winebarger
2023-04-19 12:57 ` João Távora
2023-04-19 13:03 ` Eli Zaretskii
2023-04-14 13:40 ` bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot Eli Zaretskii
2023-04-14 16:04 ` Dmitry Gutov
2023-04-14 17:43 ` Eli Zaretskii
2023-04-14 17:47 ` Dmitry Gutov
2023-04-14 17:59 ` Eli Zaretskii
2023-04-22 23:37 ` Dmitry Gutov
2023-04-23 13:02 ` Philip Kaludercic
2023-04-23 20:56 ` Dmitry Gutov
2023-04-25 12:24 ` Philip Kaludercic
2023-05-01 2:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-13 16:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-13 15:14 ` Philip Kaludercic
2023-04-13 15:59 ` Eli Zaretskii
2023-04-13 16:13 ` Dmitry Gutov
2023-04-13 19:14 ` Philip Kaludercic
2023-04-14 10:56 ` Eli Zaretskii
2023-04-14 16:40 ` Philip Kaludercic
2023-04-15 8:37 ` Eli Zaretskii
2023-04-15 10:41 ` Philip Kaludercic
2023-04-15 10:56 ` Eli Zaretskii
2023-04-15 11:37 ` Philip Kaludercic
2023-04-15 11:43 ` Eli Zaretskii
2023-04-15 13:21 ` Philip Kaludercic
2023-04-15 13:51 ` Eli Zaretskii
2023-04-15 17:14 ` Philip Kaludercic
2023-04-15 17:37 ` Eli Zaretskii
2023-04-15 18:19 ` Philip Kaludercic
2023-04-15 18:37 ` Eli Zaretskii
2023-04-16 13:45 ` Philip Kaludercic
2023-04-16 15:12 ` Eli Zaretskii
2023-04-16 10:44 ` João Távora
2023-04-16 14:23 ` Kévin Le Gouguec
2023-04-12 20:10 ` Philip Kaludercic [this message]
2023-04-13 5:49 ` Eli Zaretskii
2023-04-12 15:49 ` Dmitry Gutov
2023-04-12 15:59 ` Eli Zaretskii
2023-04-12 16:29 ` João Távora
2023-04-12 20:50 ` Dmitry Gutov
2023-04-12 15:45 ` Dmitry Gutov
2023-04-11 18:54 ` Eli Zaretskii
2023-04-11 20:28 ` João Távora
2023-04-12 5:51 ` Eli Zaretskii
2023-04-12 9:18 ` João Távora
2023-04-12 9:53 ` Eli Zaretskii
2023-04-12 12:37 ` João Távora
2023-04-12 13:20 ` Philip Kaludercic
2023-04-12 16:54 ` Eli Zaretskii
2023-04-11 19:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-11 20:05 ` João Távora
2023-04-11 21:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-12 7:34 ` Philip Kaludercic
2023-04-12 5:44 ` Eli Zaretskii
2023-04-12 7:44 ` Philip Kaludercic
2023-04-12 8:10 ` Eli Zaretskii
2023-04-12 14:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-11 21:14 ` Dmitry Gutov
2023-04-12 9:34 ` João Távora
2023-04-12 15:38 ` Dmitry Gutov
2023-04-08 7:10 ` Eli Zaretskii
2023-04-08 9:09 ` João Távora
2023-04-08 14:51 ` Ihor Radchenko
2023-04-08 15:23 ` João Távora
2023-04-08 15:31 ` Ihor Radchenko
2023-04-08 18:10 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pm88kgj9.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=62720@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--cc=larsi@gnus.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.