From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Jai Vetrivelan <jaivetrivelan@gmail.com>, 54474@debbugs.gnu.org
Subject: [bug#54474] [PATCH 0/6] gnu: emacs-xyz: Add info manuals of packages
Date: Mon, 21 Mar 2022 09:22:24 +0100 [thread overview]
Message-ID: <e4364c4275fce5d99ddf55d4010688755b6cf7c5.camel@gmail.com> (raw)
In-Reply-To: <2170eb1a448af6aa90b3f69ad39707dbf9d40867.camel@gmail.com>
Am Sonntag, dem 20.03.2022 um 18:03 +0530 schrieb Jai Vetrivelan:
> I noticed that a few packages had info manuals in their repositories,
> but they were not installed by Guix. This patch series updates the
> existing definions to add those Info manuals, and adds a few similar
> packages.
>
> 1) The .info files were generated from .org files in the repository
> and I attempted to install them through this command:
>
> "emacs --batch --eval=(require 'ox-texinfo) --eval=(find-file
> \"README.org\") --eval=(org-texinfo-export-to-info)"
>
> Is there a better way for this?
There is emacs-batch-eval in (guix build emacs-utils), which is already
part of the emacs-build-system imports. This currently appears to only
affect six packages, but if that's a trend we might want to offer a
build phase for it. Note that the default include regexp already
contains "\\.info$", so you only need to build it.
> 2) modus-themes is a part of emacs (since v28 iirc), would the info
> manual of emacs-modus-themes take precedence of the info manual
> provided with emacs?
That'd probably depend on the ordering. I'm not sure if installing
modus-themes on top of 28 is even expected, but whatever floats your
boat, I guess.
Cheers
next parent reply other threads:[~2022-03-21 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2170eb1a448af6aa90b3f69ad39707dbf9d40867.camel@gmail.com>
2022-03-21 8:22 ` Liliana Marie Prikler [this message]
2022-03-20 13:15 [bug#54474] [PATCH 0/6] gnu: emacs-xyz: Add info manuals of packages Jai Vetrivelan
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=e4364c4275fce5d99ddf55d4010688755b6cf7c5.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=54474@debbugs.gnu.org \
--cc=jaivetrivelan@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 external index
https://git.savannah.gnu.org/cgit/guix.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.