all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: gfp <gfp@posteo.at>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: help-guix@gnu.org
Subject: Re: finding the right path
Date: Tue, 19 Nov 2024 17:31:20 +0000	[thread overview]
Message-ID: <685c3ae0-a38c-480b-b455-dbf82e39b81b@posteo.at> (raw)
In-Reply-To: <87frnnclir.fsf@lease-up.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2999 bytes --]

Hi Felix,

thanks for your help

I installed ps-print package in Emacs,
but it does not work.
It says, you do need to install ghostscript.
That's why I am dealing with ghostscript.

> 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.

This is exactly my question.
I don't know where Guix System installed my ghostscript package.
How can I find out this?
What are the commands to find out where I installed a package?

thanks for help

Gottfried



Am 19.11.24 um 16:04 schrieb Felix Lechner:
> 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/



[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2451 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]

  reply	other threads:[~2024-11-19 19:36 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
2024-11-19 17:31   ` gfp [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=685c3ae0-a38c-480b-b455-dbf82e39b81b@posteo.at \
    --to=gfp@posteo.at \
    --cc=felix.lechner@lease-up.com \
    --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.