Reply to the mailing list, and supply the information we requested
(the *exact output* of "type command_not_found_handle", and Pierce's
suggestion to try to duplicate the problem with command_not_found_handle
unset).
On Mon, Jun 29, 2015 at 03:04:03PM -0600, Braden Best wrote:
> Here's the same sc
Forwarding to the mailing list:
On Mon, Jun 29, 2015 at 02:28:32PM -0600, Braden Best wrote:
> Yes, the back tick is a quoting mechanism I picked up from stack exchange.
> In those sites, it highlights the text and renders it in a fixed width font.
>
> cnf handle is : command not found
>
> Also,
On Mon, Jun 29, 2015 at 09:28:11AM +0300, Pierre Gaston wrote:
> On Mon, Jun 29, 2015 at 5:54 AM, Braden Best wrote:
> > I noticed it when I tried to branch an xterm off into multiple sessions
> > and mistyped its name:
> >
> > `xter m&`
I'm assuming the backticks are NOT actually part of the com
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
