unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Felix Lechner via <help-guix@gnu.org>
To: gfp <gfp@posteo.at>
Cc: help-guix@gnu.org
Subject: Re: finding the right path
Date: Tue, 19 Nov 2024 07:04:44 -0800	[thread overview]
Message-ID: <87frnnclir.fsf@lease-up.com> (raw)
In-Reply-To: <9d85a378-6e08-476e-8736-89ac5eeb9699@posteo.at> (gfp@posteo.at's message of "Mon, 18 Nov 2024 16:01:06 +0000")

Hi Gottfried,

On Mon, Nov 18 2024, gfp wrote:

> What is now the right path

In Guix, programs can be found in four places:

1. In the store.  That is where packages are "installled," but the paths
are cumbersome.  They involve a gibberish of characters known as
cryptographic hashes.  In Guix, we use those paths only when referring
from one package to another.  That's how multiple versions of the same
thing can co-exist on Guix at the same time.  It's also why Guix is so
stable.

2. In your home profile (~/.guix-home/profile).  Those are symbolic
links into the store.  The profile itself is actually in the store
itself ("ls -al ~/.guix-home/profile" in Bash but not in Eshell) which
then links to the final location.  Guix is all about managing those
links.

3. In temporary profiles, which are in ~/.cache/guix/profiles.  They are
created by commands like 'guix shell'.

4. If you use "Guix System" as I do, links to the programs you installed
are aggregated in the system profile, which is located in
/run/current-system/profile.

An environment variable called GUIX_ENVIRONMENT tracks your active
profiles and, with proper configuration in your shell, should set PATH
so that all programs are found without paths.

In other words, you (or any programs that inherits PATH) should be able
to type just "gv".

With that in mind, I would first try to get rid of pr-path-alist
altogether.

> (require 'printing)
>     (setq pr-path-alist
> 	    '((unix      "." "~/bin" ghostview mpage PATH)
> 	      (ghostview "$HOME/bin/gsview-dir")
> 	      (mpage     "$HOME/bin/mpage-dir")
> 	      ))

If that does not work, I would use the paths in the home or system
profile, depending on where you installed ghostview and, if it's in both
places, which version you would like to use.

As a side note, I personally had better luck with the ps-print package
that is described here. [1] Locally, it uses my default printer, which I
configured in CUPS (localhost:631) and probably set to default with
'lpoptions' as described here. [2]

Kind regards
Felix

[1] https://www.emacswiki.org/emacs/PrintingFromEmacs
[2] https://arkit.co.in/set-default-printer-linux-command/


  reply	other threads:[~2024-11-19 15:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-18 16:01 finding the right path gfp
2024-11-19 15:04 ` Felix Lechner via [this message]
2024-11-19 17:31   ` gfp
2024-11-19 19:36     ` Felix Lechner via
2024-11-19 21:04       ` gfp

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=87frnnclir.fsf@lease-up.com \
    --to=help-guix@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=gfp@posteo.at \
    /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.
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).