From: Paul Pogonyshev <pogonyshev@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57494@debbugs.gnu.org
Subject: bug#57494: `package-install' no longer byte-compiles files of installed packages
Date: Thu, 1 Sep 2022 13:00:41 +0200 [thread overview]
Message-ID: <CAG7Bpap6ZPTLuOj-xwGDKepnqnJY5Op_GhcdpqSgnWx=_e-74Q@mail.gmail.com> (raw)
In-Reply-To: <87o7vzz9lj.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
By the way, wouldn't it be nice if Emacs included the Git commit somewhere,
at least in unstable versions? In the output it can be seen only
incidentally, because it is included in `configure --prefix ...'. And it's
actually not even guaranteed it is correct.
Paul
On Thu, 1 Sept 2022 at 12:13, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Paul Pogonyshev <pogonyshev@gmail.com> writes:
>
> > Here is the output of `report-emacs-bug':
> >
> > In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, X toolkit, cairo
> version 1.16.0,
> > Xaw3d scroll bars)
> > System Description: Debian GNU/Linux 11 (bullseye)
> >
> > Configured using:
> > 'configure
> >
> --prefix=/nix/store/fam04cbjqrwhvzg2j35pabikpgf0a9k1-emacs-snapshot-a1Fa3d24
> > --disable-build-details --with-modules'
>
> Well, that looks pretty similar to mine... but it's referring to
> a1Fa3d24, which is a version from March? Can you try testing with the
> current trunk instead?
>
[-- Attachment #2: Type: text/html, Size: 1424 bytes --]
next prev parent reply other threads:[~2022-09-01 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 17:29 bug#57494: `package-install' no longer byte-compiles files of installed packages Paul Pogonyshev
2022-08-31 10:15 ` Lars Ingebrigtsen
2022-08-31 11:27 ` Paul Pogonyshev
2022-09-01 10:12 ` Lars Ingebrigtsen
2022-09-01 10:37 ` Paul Pogonyshev
2022-09-01 11:44 ` Lars Ingebrigtsen
2022-09-01 11:00 ` Paul Pogonyshev [this message]
2022-09-01 11:40 ` Eli Zaretskii
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='CAG7Bpap6ZPTLuOj-xwGDKepnqnJY5Op_GhcdpqSgnWx=_e-74Q@mail.gmail.com' \
--to=pogonyshev@gmail.com \
--cc=57494@debbugs.gnu.org \
--cc=larsi@gnus.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 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.