On Mon, Jun 29, 2015 at 5:54 AM, Braden Best wrote:
> Re-send:
>
>
> I noticed it when I tried to branch an xterm off into multiple sessions
> and mistyped its name:
>
> `xter m&`
>
> So after experimenting with a ton of different scenarios I've come to this
> conclusion:
>
> * both xterm and gno
Re-send:
I noticed it when I tried to branch an xterm off into multiple sessions and
mistyped its name:
`xter m&`
So after experimenting with a ton of different scenarios I've come to this
conclusion:
* both xterm and gnome-terminal crash
* a nested bash session also crashes returning me back
I noticed it when I tried to branch an xterm off into multiple sessions and
mistyped its name:
`xter m&`
So after experimenting with a ton of different scenarios I've come to this
conclusion:
* both xterm and gnome-terminal crash
* a nested bash session also crashes returning me back to the pre
Yeah. I noted that as workaround in the report... I figured if posix was
vague on this matching other shells might be better behavior.
On Jun 28, 2015 2:57 PM, "Dennis Williamson"
wrote:
>
>
> On Sat, Jun 27, 2015 at 2:48 PM, Nathan Neulinger
> wrote:
>
>> Configuration Information [Automaticall
On Sat, Jun 27, 2015 at 2:48 PM, Nathan Neulinger
wrote:
> 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-red
