From: Philip Kaludercic <philipk@posteo.net>
To: Feng Shu <tumashu@163.com>
Cc: 59087@debbugs.gnu.org
Subject: bug#59087: 29.0.50; package-vc-update error
Date: Wed, 16 Nov 2022 12:59:44 +0000 [thread overview]
Message-ID: <87k03vnjgf.fsf@posteo.net> (raw)
In-Reply-To: <877czvcaz3.fsf@163.com> (Feng Shu's message of "Wed, 16 Nov 2022 20:58:24 +0800")
Feng Shu <tumashu@163.com> writes:
> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Feng Shu <tumashu@163.com> writes:
>>
>>> Philip Kaludercic <philipk@posteo.net> writes:
>>>
>>>> Feng Shu <tumashu@163.com> writes:
>>>>
>>>>> Philip Kaludercic <philipk@posteo.net> writes:
>>>>>
>>>>>> Thank you for all these stack traces, I have managed to reproduce and
>>>>>> resolve all the mistakes -- at least on my end. The new state is still
>>>>>> on scratch/package-vc-fixes.
>>>>>>
>>>>>
>>>>> Ok, new info :-)
>>>>>
>>>>> 1. package-vc-update is unusable when first run emacs.
>>>>
>>>> Unusable in what sense? The command is not auto-loaded, so you need to
>>>>
>>>> M-x load-library RET package-vc RET
>>>>
>>>> first.
>>>
>>> Yes, I mean command is not auto-loaded :-)
>>
>> Do you think we should make it such? The command is strictly speaking
>> not necessary, because package-update does the same thing.
>
> If so, package-update is enough.
I will add a comment in the docstring to clarify this point.
next prev parent reply other threads:[~2022-11-16 12:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 2:33 bug#59087: 29.0.50; package-vc-update error Feng Shu
2022-11-14 11:32 ` Philip Kaludercic
2022-11-15 1:52 ` Feng Shu
2022-11-15 9:48 ` Philip Kaludercic
2022-11-16 0:46 ` Feng Shu
2022-11-16 8:20 ` Philip Kaludercic
2022-11-16 9:22 ` Feng Shu
2022-11-16 9:51 ` Philip Kaludercic
2022-11-16 12:03 ` Feng Shu
2022-11-16 12:20 ` Philip Kaludercic
2022-11-16 12:01 ` Feng Shu
2022-11-16 12:18 ` Philip Kaludercic
2022-11-16 12:58 ` Feng Shu
2022-11-16 12:59 ` Philip Kaludercic [this message]
2022-11-17 0:43 ` Feng Shu
2022-11-17 15:54 ` Philip Kaludercic
2022-11-18 0:43 ` Feng Shu
2022-11-18 9:53 ` Philip Kaludercic
2022-11-18 11:48 ` Feng Shu
2022-11-18 3:31 ` Feng Shu
2022-11-18 9:55 ` Philip Kaludercic
2022-11-18 11:47 ` Feng Shu
2022-11-18 11:52 ` Feng Shu
2022-11-18 15:22 ` Philip Kaludercic
2022-11-19 4:59 ` Feng Shu
2022-11-19 7:28 ` Philip Kaludercic
2022-11-19 10:01 ` Feng Shu
2022-11-19 10:52 ` Philip Kaludercic
2022-11-19 5:06 ` Feng Shu
2022-11-16 16:22 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-16 16:29 ` Philip Kaludercic
2022-11-17 1:44 ` Feng Shu
2022-11-15 2:08 ` Feng Shu
2022-11-15 5:51 ` Feng Shu
2022-11-19 5:10 ` Feng Shu
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=87k03vnjgf.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=59087@debbugs.gnu.org \
--cc=tumashu@163.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).