From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jporterbugs@gmail.com, philipk@posteo.net, 62720@debbugs.gnu.org,
joaotavora@gmail.com, larsi@gnus.org, monnier@iro.umontreal.ca
Subject: bug#62720: 29.0.60; Not easy at all to upgrade :core packages like Eglot
Date: Sat, 22 Apr 2023 13:48:41 +0300 [thread overview]
Message-ID: <d8f44ecf-6100-5f74-54b9-07bb78053037@gutov.dev> (raw)
In-Reply-To: <835y9o2uh2.fsf@gnu.org>
On 22/04/2023 11:26, Eli Zaretskii wrote:
>> The above scenarios (package-install or (use-package eglot :ensure t))
>> when ~/.emacs.d/elpa is empty, result in the very latest Eglot being
>> installed when using Emacs 28. And will result in something different
>> with Emacs 29 (not the latest version). That's not nothing: the CI
>> scripts will have to be updated, and the user instructions for reporting
>> problems will have to be made more complicated as well. Some
>> possibilities will simply be gone (the user won't be able to upgrade
>> Eglot to the very latest by deleting it from ~/.emacs.d/elpa and calling
>> package-install, for example). This *is* a non-backward compatible
>> change from the perspective of Eglot's maintainer.
>
> We were talking about users installing and updating packages. The CI
> scenario doesn't belong here. It is also much less important one
> (test suites are always required to chase the changes in development).
>
> Let's not complicate an already complicated set of issues by bringing
> up unimportant secondary use cases.
You asked. I relayed what's already been said on the matter by Joao.
>> I, personally, don't really buy this kind of argument, but I figured you
>> might. After all, it's rather in line with reasoning we've seen voiced
>> around these parts many times ("X has worked this way for Y years, let's
>> never change it from now on"). Classic https://xkcd.com/1172/.
>
> If you allude to my reasoning, then it is never that simplistic, and
> always considers each case separately, not "by analogy".
Of course that's a simplification. Hence the "might" anyway.
>> Either way would be fine, IMO, as long as the behavior is logical and
>> matches documentation. But having a separate command to upgrade now lets
>> us fix it separately without worry of breaking something more globally.
>
> Except that, based on what we have (see below) ,we don't really have
> an "upgrade" operation, we only have "install" and "delete"
> (i.e. "uninstall"). So maybe we should preserve that, to minimize
> problems and user surprise/confusion.
We do. We have commands for upgrading, both in "list-packages", and used
interactively. Which do the thing of installing the new version and
removing the old one.
Which is what upgrading means in various tools, e.g. 'apt'.
>>> In interactive invocation, package-upgrade calls completing-read with
>>> its 4th argument non-nil, so you cannot select a package which is not
>>> in the collection returned by package--updateable-packages. What I
>>> meant above is to allow that collection to include built-in packages
>>> as optional behavior. I just tried invoking package-update for ElDoc,
>>> and I get "No match" after typing "eldoc" to its prompt, although
>>> eldoc version 1.14.0 is in the list presented by list-packages as
>>> "available".
>>
>> That's what I imagined: adding a new optional argument to
>> package--updateable-packages which would include builtins in the result.
>>
>> And only pass it when called from package-upgrade.
>>
>> Hopefully that's the kind of optional that you meant.
>
> Yes, something like that. Presumably activated by the same new option
> introduced for package-installed.
Okay, then it's something different, and you didn't answer my question.
>>>>>> 'package-update' is an
>>>>>> interactive function which itself it called from only one place:
>>>>>> 'package-update-all', and since the plan is to improve both, we can make
>>>>>> sure they only do what we ask of them: package-update will upgrade
>>>>>> builtins when invoked directly, and package-update-all will upgrade them
>>>>>> only when the builtin has been upgraded before (making it not a builtin
>>>>>> anymore), or a new user option is set.
>>>>>
>>>>> This is one possibility, and it might make sense to some users. But I
>>>>> don't think we can be sure it will make sense to an overwhelming
>>>>> majority of the users.
>>>>
>>>> Hence the user option?
>>>
>>> Which one? Are you suggesting to add a new one? If so, why not use
>>> the one we already added, package-install-upgrade-built-in?
>>
>> The user option I was thinking of would probably be called a little
>> shorter: package-upgrade-built-in. And it would only affect the upgrader
>> commands.
>
> We could rename the existing option, if the name is the problem.
> Otherwise, I don't see why we would need two separate options: they do
> the same job and have the same meaning from the user's POV.
The name is a problem, yes. What could also be a problem is a user that
customizes this option to have package-update update builtin packages (a
reasonable behavior that should be on by default anyway), will also
automatically have change the behavior of package-install to be more
surprising (install an already installed package).
Further, if we have a user option affect package-update, we'll have to
alter package-update-all and package-manu-mark-for-update in the same
patch (otherwise we'll have more nonsense on our hands). Whereas the
first version I sent is more minimal.
>> All this is to say, the first step (upgrading Eglot to the version from
>> ELPA) will be less user-friendly compared to the other UIs we have. But
>> it's probably manageable, especially if documented well.
>
> I don't see why it would be less user-friendly.
The same reason we do have commands with "upgrade" in their names,
rather than force everybody to use the "install" and "delete" ones.
>> My point here, however, is that commit 580d8278c5f48 improved the
>> situation to a lesser degree that some people here might have expected.
>
> One again: commit 580d8278c5f48 solved precisely the problem which
> opened this bug report, nothing more, nothing less.
It doesn't seem like the originator of the report agrees with that.
>> But we can conclude that we do have two different installation actions:
>>
>> - package-install which will install the latest version of a package,
>> but only if it's not installed;
>> - package-menu-mark-install, which will mark a specific version for
>> installation, disregarding whether some earlier version is already
>> installed; the previous version will remain installed still.
>
> Which is again a breaking behavior change, AFAIU. Is this a good idea
> so late in the development of Emacs 29?
The above is not a breaking change, it's how things work already. And
have been working for quite a while.
>> But even if we decide that we want to eliminate that split, doing *that*
>> would really be a breaking change. I don't have a reasonable plan to
>> present for doing that in Emacs 29, so far.
>
> There's no "split". What I wanted to point out is that we don't seem
> to have a clear vision of these two commands, since they are confusing
> intertwined. In fact, one could argue that package-upgrade in its
> current form is simply a convenience shortcut for "delete old and
> install new".
What should an upgrade command do, in your opinion, if not "delete old
and install new"?
next prev parent reply other threads:[~2023-04-22 10:48 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 [this message]
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
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=d8f44ecf-6100-5f74-54b9-07bb78053037@gutov.dev \
--to=dmitry@gutov.dev \
--cc=62720@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joaotavora@gmail.com \
--cc=jporterbugs@gmail.com \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
/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.