Hey,
I think in this case, history_expand lib/readline/histexpand.c:905 is
invoked with hstring="b\" | echo '!'", and goes wrongly into history
expansion.
Not that I know how to fix it ;-)
cheers,
pg
On Tue, Dec 2, 2014 at 10:02 PM, wrote:
> This looks like a bug:
>
> gena@note2:~$ echo "a
On 12/02, Eduardo A. Bustamante López wrote:
On Tue, Dec 02, 2014 at 11:29:59PM +0530, Darshit Shah wrote:
On 12/02, Darshit Shah wrote:
[...]
>When I attempt to detach a running Screen session using `screen -Drr
>,session name` command, the original shell which contained the screen
>session d
gennady.kupava wrote:
> This looks like a bug:
>
> gena@note2:~$ echo "a
> > b" | echo '!'
> bash: !': event not found
> > ^C
> gena@note2:~$
>
> Is it?
>
> Gennady
IMHO it is. Confirmed in 4.3.30
This looks like a bug:
gena@note2:~$ echo "a
> b" | echo '!'
bash: !': event not found
> ^C
gena@note2:~$
Is it?
Gennady
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/2/14, 12:59 PM, Darshit Shah wrote:
>> However, when I attempted the same from a virtual Terminal instead of an
>> emulator, upon remotely detaching the screen session, my terminal
>> directly displayed a login prompt again. This leads me to bel
On Tue, Dec 02, 2014 at 11:29:59PM +0530, Darshit Shah wrote:
> On 12/02, Darshit Shah wrote:
[...]
> >When I attempt to detach a running Screen session using `screen -Drr
> >,session name` command, the original shell which contained the screen
> >session does not return to a prompt. It instead rem
On 12/02, Darshit Shah wrote:
I use GNU Screen along with Bash for my SSH sessions.
While detaching my Screen sessions I came across a weird Bash bug and
I'd like your help in debugging this issue.
When I attempt to detach a running Screen session using `screen -Drr
,session name` command, t
I use GNU Screen along with Bash for my SSH sessions.
While detaching my Screen sessions I came across a weird Bash bug and I'd like
your help in debugging this issue.
When I attempt to detach a running Screen session using `screen -Drr ,session
name` command, the original shell which contain
On Tue, Dec 02, 2014 at 03:09:23PM +0545, bijay pant wrote:
> Bash Version: 4.1
> Patch Level: 2
> Release Status: release
4.1.2 is vulnerable to shellshock. If you're going to compile from
source, you should compile a newer version with all the patches applied.
Patches for bash-4.1 are found in
On Dec 2, 2014, at 4:24 AM, bijay pant wrote:
> From: root
>
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86
From: root
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
-DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/sha
11 matches
Mail list logo