Awesome, thanks for the super fast fix :)
e.
On Thu, Mar 27, 2014 at 7:26 PM, Chet Ramey wrote:
> On 3/27/14 3:40 AM, Egmont Koblinger wrote:
> > Hi,
> >
> > Type a multiline command, and press ^C.
> >
> > bash-4.2: The new prompt appeared below the complete multiline command.
> >
> > bash-4.
On 3/27/14 3:40 AM, Egmont Koblinger wrote:
> Hi,
>
> Type a multiline command, and press ^C.
>
> bash-4.2: The new prompt appeared below the complete multiline command.
>
> bash-4.3: The new prompt appears right under the previous prompt,
> overwriting parts of the aborted command line and le
Egmont Koblinger writes:
> Sorry, I wasn't clear enough.
>
> By "multiline" I mean a simple command that is so long (e.g. takes so many
> parameters) that it cannot fit into a single line. (You reach the right
> margin of your terminal and keep on typing.)
I can reproduce that, and the subsequen
Sorry, I wasn't clear enough.
By "multiline" I mean a simple command that is so long (e.g. takes so many
parameters) that it cannot fit into a single line. (You reach the right
margin of your terminal and keep on typing.)
On Thu, Mar 27, 2014 at 8:50 AM, Chris Down wrote:
> Egmont Koblinger w
Egmont Koblinger writes:
> Type a multiline command, and press ^C.
>
> bash-4.2: The new prompt appeared below the complete multiline command.
>
> bash-4.3: The new prompt appears right under the previous prompt,
> overwriting parts of the aborted command line and leaving garbage after the
> ne
