From: Atte Torri via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 67652@debbugs.gnu.org
Subject: bug#67652: Guix home - bash alias declarations order
Date: Tue, 5 Dec 2023 16:54:10 +0100 (CET) [thread overview]
Message-ID: <26318035.896827.1701791650006.JavaMail.zimbra@universite-paris-saclay.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
Hello,
I have an issue with guix home alias declarations. The aliases I declare in my home configuration always end up on top of the .bashrc file, while the documentation for the home-bash-service-type says "The aliases will be defined after the contents of the bashrc field has been put in the .bashrc file.". The following is the bash configuration I use
(service home-bash-service-type
(home-bash-configuration
(bashrc (list (local-file ".bashrc" "bashrc")))
(bash-profile (list (local-file ".bash_profile" "bash_profile")))
(bash-logout (list (local-file ".bash_logout" "bash_logout")))
(aliases '(("egrep" . "egrep --color=auto")
("fgrep" . "fgrep --color=auto")
("grep" . "grep --color=auto")
("l" . "ls -CF")
("la" . "ls -A")
("ll" . "ls -alF")
("ls" . "ls --color=auto")))))
M. TORRI Atte
PhD Student (Computer Science) at Université Paris-Saclay
Doctorant (Informatique) à l'Université Paris-Saclay
Équipe ParSys - Laboratoire Interdisciplinaire des Sciences du Numérique (LISN)
Bureau 105 - Bâtiment 650
atte.torri@universite-paris-saclay.fr | 0169153106
[-- Attachment #2: Type: text/html, Size: 6065 bytes --]
next reply other threads:[~2023-12-11 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-05 15:54 Atte Torri via Bug reports for GNU Guix [this message]
2023-12-06 21:11 ` bug#67652: Guix home - bash alias declarations order Christian Miller via Bug reports for GNU Guix
2024-02-22 4:10 ` bug#67652: [PATCH] * home/services/shells.scm (add-bash-configuration): reorder aliases (Bug#67652) Jason
2024-03-27 14:50 ` Hilton Chain via Bug reports for GNU Guix
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=26318035.896827.1701791650006.JavaMail.zimbra@universite-paris-saclay.fr \
--to=bug-guix@gnu.org \
--cc=67652@debbugs.gnu.org \
--cc=atte.torri@universite-paris-saclay.fr \
/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.