unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Tropin <andrew@trop.in>
To: 51918@debbugs.gnu.org
Cc: Xinglu Chen <public@yoctocell.xyz>
Subject: bug#51918: home-bash-service-type adds the defaults and aliases to the end of the file
Date: Wed, 17 Nov 2021 12:30:20 +0300	[thread overview]
Message-ID: <8735nvp1sj.fsf@trop.in> (raw)

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

Test in guix-home.sh looks correct, but it fails:
https://git.savannah.gnu.org/cgit/guix.git/tree/tests/guix-home.sh?h=5eb5c0789f34e87ee417a53ddfcfa3b6521bb337#n98

Seems something changed in home-bash-service-type, for some reason it
adds the serialized content of aliases field and guix-bashrc variable
after the content of bashrc field.

Original implementation works as expected and adds the content of bashrc
to the end of ~/.bashrc.

--8<---------------cut here---------------start------------->8---
(list
 ((@ (gnu services) service)
  (@ (gnu home-services shells) home-bash-service-type)
  ((@ (gnu home-services shells) home-bash-configuration)
   (guix-defaults? #t)
   (bashrc (list "echo hi"))))
 ((@ (gnu services) simple-service)
  'test-bash
  (@ (gnu home-services shells) home-bash-service-type)
  ((@ (gnu home-services shells) home-bash-extension)
   (bashrc (list "echo very hi")))))
--8<---------------cut here---------------end--------------->8---

https://git.sr.ht/~abcdw/rde/tree/master/item/gnu/home-services/shells.scm

-- 
Best regards,
Andrew Tropin

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

             reply	other threads:[~2021-11-17  9:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  9:30 Andrew Tropin [this message]
2021-12-19  8:45 ` bug#51918: home-bash-service-type adds the defaults and aliases to the end of the file Xinglu Chen
2021-12-30  8:26   ` Andrew Tropin

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=8735nvp1sj.fsf@trop.in \
    --to=andrew@trop.in \
    --cc=51918@debbugs.gnu.org \
    --cc=public@yoctocell.xyz \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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