From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>,
zimoun <zimon.toutoune@gmail.com>
Cc: 51755@debbugs.gnu.org
Subject: [bug#51755] [PATCH 1/1] gnu: proof-general: Adjust autoloads for Emacs.
Date: Sun, 21 Nov 2021 20:07:48 +0100 [thread overview]
Message-ID: <6aab24bab9512e0957e33256a3addf1076a9d012.camel@gmail.com> (raw)
In-Reply-To: <8735npwdvr.fsf@nicolasgoaziou.fr>
Hi,
Am Sonntag, den 21.11.2021, 19:40 +0100 schrieb Nicolas Goaziou:
> > + (add-after 'install 'allow-subfolders-autoloads
> > + (lambda* (#:key outputs #:allow-other-keys)
> > + (let ((out (assoc-ref outputs "out")))
> > + ;; Make it visible by Emacs
> > + (copy-file "proof-general.el"
> > + (string-append out ,base-directory
> > + "/proof-general-
> > autoloads.el")))))))))
>
> So, IIUC, the above is basically a hack: you disguise the main file
> into an autoloads file because no autoloads file is generated from
> the code base? If so, this might deserve a longer comment, IMO.
On a related note, what would be so bad about having to (require
'proof-general) interactively? Alternatively, we could in an after-
unpack phase add autoload cookies to the source file or write our own
autoloads altogether. WDYT?
next prev parent reply other threads:[~2021-11-21 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 19:26 [bug#51755] [PATCH 0/1] Fix ProofGeneral (emacs front-end for Coq) zimoun
2021-11-10 19:37 ` [bug#51755] [PATCH 1/1] gnu: proof-general: Adjust autoloads for Emacs zimoun
2021-11-21 18:40 ` Nicolas Goaziou
2021-11-21 19:07 ` Liliana Marie Prikler [this message]
2021-11-21 20:15 ` Nicolas Goaziou
2021-11-21 21:11 ` zimoun
2021-11-22 18:22 ` bug#51755: " Nicolas Goaziou
2021-11-21 22:17 ` [bug#51755] " zimoun
2021-11-19 12:27 ` [bug#51755] [PATCH 0/1] Fix ProofGeneral (emacs front-end for Coq) zimoun
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6aab24bab9512e0957e33256a3addf1076a9d012.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=51755@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=zimon.toutoune@gmail.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/guix.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).