From: walt <w41ter@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Anyone else having a problem with bash?
Date: Thu, 9 Jul 2015 05:41:38 -0700 [thread overview]
Message-ID: <20150709054138.5c3f7074@a6> (raw)
In-Reply-To: 20150709124824.10f75958@hactar.digimed.co.uk
On Thu, 9 Jul 2015 12:48:24 +0100
Neil Bothwick <neil@digimed.co.uk> wrote:
> On Thu, 09 Jul 2015 13:38:43 +0200, Stephan Müller wrote:
>
> > As a wild guess into the blue, it could be related to readline. As I
> > see gentoo's bash uses the standalone readline from coreutils, while
> > the original bash source maintains an own trimmed version of
> > readline.. just a thought
>
> In that case, re-emerging Bash with USE="-readline" should get rid of
> the problem.
>
> <smug>I can't test it myself as a use a superior shell to Bash</smug>
I just re-emerged bash with -readline and the ebuild ignored me,
apparently because I have the ncurses flag enabled. I suppose I could
try disabling ncurses too, but I have no idea what to expect from that
so I'll wait and hope for wisdom to strike me like a bolt of lightening.
prev parent reply other threads:[~2015-07-09 12:42 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 17:01 [gentoo-user] Anyone else having a problem with bash? walt
2015-07-06 17:18 ` Alexander Kapshuk
2015-07-06 19:07 ` [gentoo-user] " »Q«
2015-07-06 20:43 ` Alex Thorne
2015-07-06 14:09 ` Bill Kenworthy
2015-07-08 4:44 ` Jc García
2015-07-08 5:00 ` Anton Shumskyi
2015-07-08 7:00 ` Alan McKinnon
2015-07-08 9:06 ` Florian Gamböck
2015-07-08 9:28 ` Stephan Müller
2015-07-08 10:08 ` Florian Gamböck
2015-07-08 10:13 ` Joerg Schilling
2015-07-08 10:40 ` Florian Gamböck
2015-07-08 10:53 ` Joerg Schilling
2015-07-08 0:48 ` walt
2015-07-08 7:15 ` Florian Gamböck
2015-07-08 13:10 ` Todd Goodman
2015-07-08 13:46 ` Florian Gamböck
2015-07-08 10:17 ` Nikos Chantziaras
2015-07-08 10:29 ` Joerg Schilling
2015-07-09 11:38 ` [gentoo-user] " Stephan Müller
2015-07-09 11:48 ` Neil Bothwick
2015-07-09 12:01 ` Gevisz
2015-07-09 12:07 ` [gentoo-user] " Nikos Chantziaras
2015-07-09 12:20 ` Gevisz
2015-07-09 16:07 ` Neil Bothwick
2015-07-09 17:45 ` Gevisz
2015-07-09 17:54 ` Neil Bothwick
2015-07-09 23:34 ` Nikos Chantziaras
2015-07-09 23:36 ` Nikos Chantziaras
2015-07-09 23:54 ` wraeth
2015-07-10 5:29 ` Franz Fellner
2015-07-10 8:16 ` Neil Bothwick
2015-07-10 15:00 ` Gevisz
2015-07-10 17:39 ` Nikos Chantziaras
2015-07-10 22:18 ` Marc Joliet
2015-07-11 10:22 ` Nikos Chantziaras
2015-07-11 10:39 ` Marc Joliet
2015-07-11 20:56 ` Martin Vaeth
2015-07-12 16:52 ` Nikos Chantziaras
2015-07-12 17:01 ` Neil Bothwick
2015-07-12 22:35 ` Martin Vaeth
2015-07-11 5:53 ` Martin Vaeth
2015-07-11 11:04 ` covici
2015-07-11 20:47 ` Martin Vaeth
2015-07-13 9:21 ` Joerg Schilling
2015-07-13 9:30 ` Peter Humphrey
2015-07-10 6:06 ` Martin Vaeth
2015-07-10 6:18 ` Martin Vaeth
2015-07-10 8:35 ` Neil Bothwick
2015-07-10 15:31 ` Martin Vaeth
2015-07-13 9:39 ` Joerg Schilling
2015-07-13 14:00 ` Martin Vaeth
2015-07-13 15:03 ` Joerg Schilling
2015-07-13 9:27 ` Joerg Schilling
2015-07-13 13:55 ` Martin Vaeth
2015-07-13 14:40 ` Joerg Schilling
2015-07-09 12:19 ` Nikos Chantziaras
2015-07-09 12:24 ` wraeth
2015-07-09 12:37 ` Nikos Chantziaras
2015-07-09 14:46 ` wraeth
2015-07-10 11:46 ` wraeth
2015-07-11 22:21 ` walt
2015-07-09 12:41 ` walt [this message]
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=20150709054138.5c3f7074@a6 \
--to=w41ter@gmail.com \
--cc=gentoo-user@lists.gentoo.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