(This is all after doing "set -o vi")
In previous versions of bash, I could do the following keys: / ^ foo
and it would find the most recent command that starts with foo. This is all as
expected.
However, in bash 5.0 beta (self-compiled), this doesn't work. It always leaves
the
cursor line e
Alright, so it seems PS1 is causing the problem. I removed the line from
~/.bashrc file and the shell is behaving normal again. Thanks for pointing
that out and apologies for the noise.
Kind regards,
Valentin
On Wed, Dec 12, 2018 at 8:56 PM Valentin Bajrami
wrote:
> Hi guys and thanks for the
Hi guys and thanks for the quick reply. I think Greg had a good point
there mentioning my PS1. I have it slightly modified for my personal needs
but this is happening even though I run bash with --norc flag
A piece of my ~/.bashrc file is as follows:
color_enabled() {
local -i colors=$(tput
On 12/12/18 11:36 AM, Valentin Bajrami wrote:
> While playing around a bit with dotglob and nullglob the following testcase
> seem to fail when cd'ing to a non existing directory. The shell seems to
> hang there and sending a SIGINT isn't having much effect.
>
> f3d0r4:~$ pwd
> /home/valentin.loca
On Wed, Dec 12, 2018 at 05:36:26PM +0100, Valentin Bajrami wrote:
> f3d0r4:~$ cd ../Nonexistingdir
> bash: cd: ../Nonexistingdir: No such file or directory
> ^C
> ^C
> cd Desktop/
> f3d0r4:~/Desktop$
What's in your PS1 and PROMPT_COMMAND variables? Have you set a DEBUG
trap? Have you set an E
While playing around a bit with dotglob and nullglob the following testcase
seem to fail when cd'ing to a non existing directory. The shell seems to
hang there and sending a SIGINT isn't having much effect.
f3d0r4:~$ pwd
/home/valentin.local
f3d0r4:~$ shopt -s nullglob dotglob
f3d0r4:~$ f=(*)
f3d0
