all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arnaud Daby-Seesaram <ds-ac@nanein.fr>
To: help-guix@gnu.org
Subject: Installing info manuals without cluttering my profile.
Date: Wed, 16 Oct 2024 10:26:58 +0200	[thread overview]
Message-ID: <87v7xs1mi5.fsf@nanein.fr> (raw)

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

Hi,

I am trying to install more manuals (info pages), without installing
associated packages in my profile.

My first idea was to use a home service to overwrite INFOPATH.  However,
I do not think that it is sufficient.  For example, the following
commands show unexpected `(top)' nodes.

--8<---------------cut here---------------start------------->8---
INFOPATH=$(guix build emacs)/share/info info # Empty (top).

info -d "$(guix build haunt)/share/info"     # No haunt in (top).
--8<---------------cut here---------------end--------------->8---


An alternative (that I prefer to avoid) would be to write packages that
would copy the info manuals of the packages I need.


Motivation:

I currently use direnv+manifests to setup work environments in different
directories.  However, the info-mode of Emacs is easily lost (the `top'
node is generated with the first INFOPATH the info-mode sees).

This can be annoying when switching profiles, so I would like to add all
info pages that are relevant for me by altering INFOPATH
home-profile-wide.


Best regards,

-- 
Arnaud

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 857 bytes --]

             reply	other threads:[~2024-10-16 11:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-16  8:26 Arnaud Daby-Seesaram [this message]
2024-10-16 18:33 ` Installing info manuals without cluttering my profile Tobias Geerinckx-Rice
2024-10-16 18:39   ` Tobias Geerinckx-Rice
2024-10-17  7:57   ` Arnaud Daby-Seesaram

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=87v7xs1mi5.fsf@nanein.fr \
    --to=ds-ac@nanein.fr \
    --cc=help-guix@gnu.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/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.