`guix home import` doesn't quote aliases properly

  • Open
  • quality assurance status badge
Details
2 participants
  • Attila Lendvai
  • Attila Lendvai
Owner
unassigned
Submitted by
Attila Lendvai
Severity
normal
A
A
Attila Lendvai wrote on 1 Apr 13:18 +0200
(name . bug-guix@gnu.org)(address . bug-guix@gnu.org)
-fjyp6sHcs3Atk40lT6VlGjwyMWyNgtXQZ-LiDh04-ZXqAmUmME1Dbf8z215BPKe3SBFRZsLKfIpLofDLqsdrOs2Ru-Ud5kTn78TZR46ltI=@lendvai.name
as reported on #guix on 2024-04-01:


the following alias (a default in ubuntu) is not quoted properly:

notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"

which leads to an error when opening a new terminal after a `guix home reconfigure`.

a discussion of this alias:


--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“What you do speaks so loud I cannot hear what you say.”
— Ralph Waldo Emerson (1803–1882)
A
A
Attila Lendvai wrote on 28 Sep 20:47 +0200
(address . 70125@debbugs.gnu.org)(name . Attila Lendvai)(address . attila@lendvai.name)
87setj39ac.fsf@lendvai.name
Toggle quote (4 lines)
> as reported on #guix on 2024-04-01:
>
> https://logs.guix.gnu.org/guix/2024-04-01.log#121908

copying for reference from the paste:

(home-bash-configuration
(aliases '(("alert" . "notify-send --urgency=low -i \"$([ $? = 0 ] && echo terminal || echo error)\" \"$(history|tail -n1|sed -e '\\''s/^\\s*[0-9]\\+\\s*//;s/[;&|]\\s*alert$//'\\'')\"")
)))

<#secure method=pgpmime mode=sign>
--
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“I do not think that it is possible to give any meaningful definition of anarchy by which it could exist but currently does not. Anarchists are not those who wish that there be anarchy, but those who reason along anarchist lines about what there currently is, what there was and what could there possibly be.”
— Zsolt Felföldi
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 70125@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 70125
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch