From: "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: guix home: no target of type 'home-profile' for service 'home-bash'
Date: Wed, 13 Oct 2021 09:15:48 +0200 [thread overview]
Message-ID: <874k9lfl97.fsf@ruhr-uni-bochum.de> (raw)
In-Reply-To: <87zgrel78f.fsf@gmail.com>
Hi there,
Oleg Pykhalov writes:
> Dustin Lyons <me@dustinlyons.co> writes:
>
>> I had a working guix home configuration, happily importing all of my
>> dotfiles into the guix store, but a most recent guix pull broke
>> it. […]
>
> home-bash-configuration and other service configurations accept only
> file-like objects (no strings), so to make it work you could use:
> (plain-file "bashrc" "# configuration string # another configuration
> string")
I've had a similar problem. I expected bashrc to also accept a list of
strings which will be added to bashrc since in the manual [1] it says:
> ‘bashrc’ (default: ‘()’) (type: text-config)
> List of strings or gexps, which will be added to ‘.bashrc’.
> Used for executing user’s commands at start of interactive
> shell (The shell for interactive usage started by typing
> ‘bash’ or by terminal app or any other program).
Was this behaviour somehow changed to only accept file-like objects? I
quite liked the string options because for simple aliases there is no
need for a file-like object. WDYT?
Best
Daniel
1: See info "(guix) Shells Home Services" under "Bash home service"
next prev parent reply other threads:[~2021-10-16 10:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 11:46 guix home: no target of type 'home-profile' for service 'home-bash' Dustin Lyons
2021-10-12 13:09 ` Oleg Pykhalov
2021-10-12 14:05 ` Zach Oglesby
2021-10-12 19:45 ` Dustin Lyons
2021-10-13 7:15 ` Daniel Meißner [this message]
2021-10-13 8:45 ` Oleg Pykhalov
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=874k9lfl97.fsf@ruhr-uni-bochum.de \
--to=daniel.meissner-i4k@ruhr-uni-bochum.de \
--cc=go.wigust@gmail.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.
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).