all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 18 Nov 2022 09:53:46 +0000	[thread overview]
Message-ID: <875yfck2qd.fsf@posteo.net> (raw)
In-Reply-To: <87pmdlqeh0.fsf@163.com> (Feng Shu's message of "Fri, 18 Nov 2022 08:43:39 +0800")

Feng Shu <tumashu@163.com> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> Feng Shu <tumashu@163.com> writes:
>>
>>> I have found another issue:
>>>
>>> If I run package-update when emacs first start, it will show error:
>>>
>>> package-update: Symbol’s function definition is void: package-vc-update
>>
>> It appears that I had assumed package-vc-update was autoloaded, when it
>> was in fact not autoloaded.  This comes back to the question of whether
>> it is worth autoloading the function or not.
>
> Good job, a simple suggstion:
>
>  Source package ‘pyim’ installed (Version 5.2.8, Revision "16f7c3cf0736a65d8af0c8ba8396343dbd17e368").
>
> seem to too long, what about:
>
>  Source package ‘pyim’ installed (Version 5.2.8, Revision "16f7c3").

That would work too, but abbreviating commits is not always correct...

How about using `format-spec' together with a user option to format the
success messages?  E.g. you could set it do "Source package `%n'
installed (Version %v, Revision %6r)".

Then again, I don't know if this issue is that important.

> or more info:
>  
>  Source package ‘pyim’ installed (Version 5.2.8, Revision "16f7c3", Commit "commit message").

VC doesn't expose a convenient way of fetching commit messages from revisions.





  reply	other threads:[~2022-11-18  9:53 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yfck2qd.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 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.