unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Nils Landt <nils@landt.email>
To: Tanguy LE CARROUR <tanguy@bioneland.org>, Help Guix <help-guix@gnu.org>
Subject: Re: "Command not found" when using `home-mcron-service`
Date: Mon, 15 Jan 2024 19:11:25 +0100 (CET)	[thread overview]
Message-ID: <1486567587.248523.1705342285844@office.mailbox.org> (raw)
In-Reply-To: <170532183549.11028.8238107603508685851@bioneland.org>


> Tanguy LE CARROUR <tanguy@bioneland.org> hat am 15.01.2024 13:30 CET geschrieben:
> > If I'm correct, setting the PATH environment variable in the mcron job
> > should fix it.
> 
> You mean inside the `#~(job …)`? Sorry, but… how would you do that? 😅

Haven't tried it, but something like:

#~(job '(next-minute (range 0 60 5)) (string-append #$bash " -c \"PATH=$HOME/.guix-home/profile/bin " #$notmuch "/bin/notmuch new\""))

> And this means that I would have to do it for every single job? 🤔

Yes.

> Sounds suboptimal to me.

Agreed! Alternatively, you could install the dependent packages (like pass) in guix system, not guix home.

> So I would definitively favour a solution where the PATH is set once and
> for all by Mcron.

I'm pretty sure this does not exist for mcron.


  parent reply	other threads:[~2024-01-15 18:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15  9:38 "Command not found" when using `home-mcron-service` Tanguy LE CARROUR
2024-01-15 12:03 ` Nils Landt
2024-01-15 12:30   ` Tanguy LE CARROUR
2024-01-15 12:43     ` Tanguy LE CARROUR
2024-01-15 15:25       ` Oleg Pykhalov
2024-01-15 16:17         ` Tanguy LE CARROUR
2024-01-15 17:13           ` Oleg Pykhalov
2024-01-16  7:22             ` Tanguy LE CARROUR
2024-01-15 18:11     ` Nils Landt [this message]
2024-01-16  7:10       ` Tanguy LE CARROUR

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=1486567587.248523.1705342285844@office.mailbox.org \
    --to=nils@landt.email \
    --cc=help-guix@gnu.org \
    --cc=tanguy@bioneland.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. 
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).