all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: Einar Largenius <jaadu@lysator.liu.se>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Missing built-in commands
Date: Wed, 22 Nov 2023 05:12:33 +0300	[thread overview]
Message-ID: <87cyw2cz8u.fsf@gmail.com> (raw)
In-Reply-To: <87sf4z3qum.fsf@lysator.liu.se> (Einar Largenius's message of "Tue, 21 Nov 2023 19:16:23 +0100")

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

Hello Einar,

Einar Largenius <jaadu@lysator.liu.se> writes:

> I use guix on a foreign distro and the version of bash provided by guix seems
> to have many builtin commands missing.
>
> If I run /usr/bin/bash I have no issues and can use guix and everything else
> without issue, but if I run ~/.guix-profile/bin/bash (or just bash) from my
> terminal I get errors like these:
>
>     bash: shopt: progcomp: invalid shell option name
>     bash: shopt: progcomp: invalid shell option name
>     bash: complete: command not found
>     bash: complete: command not found
>     #... and so on
>
> Other builtin commands like help also seems to be missing. Some input commands
> also don't work, instead printing things like ^P or ^N when trying to browse
> history.

What ~/.guix-profile/bin/bash points to? See:

    readlink -f ~/.guix-profile/bin/bash

If it's ‘bash-minimal’, then try the ‘bash’ package insted, e.g.:

    guix package --remove bash-minimal
    guix package --install bash


Oleg.

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

  reply	other threads:[~2023-11-22  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-21 18:16 Missing built-in commands Einar Largenius
2023-11-22  2:12 ` Oleg Pykhalov [this message]
2023-11-22 18:21   ` Einar Largenius

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=87cyw2cz8u.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=jaadu@lysator.liu.se \
    /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.