Awesome, thanks!
ma 29. lokak. 2018 klo 13.57 Ilkka Virta (itvi...@iki.fi) kirjoitti:
> On 29.10. 12:40, Ricky Tigg wrote:
> > Actual result:
> >
> > $ curl https://www.startpage.com
> > (...) [yk@localhost ~]$
>
> The shell just prints the prompt where ever the cursor was left. That's
> quite
On Mon, 29 Oct 2018 11:40:54 +0100, Ricky Tigg wrote:
> Component: bash.x86_64 4.4.23-5.fc29 @fedora
>
> To reproduce,: execute 'curl https://www.startpage.com'.
>
> Actual result:
>
> $ curl https://www.startpage.com
> (...) [yk@localhost ~]$
>
> Expected result:
>
> $ curl
Component: bash.x86_64 4.4.23-5.fc29 @fedora
To reproduce,: execute 'curl https://www.startpage.com'.
Actual result:
$ curl https://www.startpage.com
(...) [yk@localhost ~]$
Expected result:
$ curl https://www.startpage.com
(...)
[yk@localhost ~]$
On Sun, Oct 28, 2018 at 09:30:00PM -0400, Chet Ramey wrote:
> That doesn't work for the same reason as discussed in
> http://lists.gnu.org/archive/html/bug-bash/2018-03/msg00074.html.
> It's unlikely that someone will set his umask to 400 and expect no ill
> effects, but I suppose it's better not
On 29.10. 12:40, Ricky Tigg wrote:
Actual result:
$ curl https://www.startpage.com
(...) [yk@localhost ~]$
The shell just prints the prompt where ever the cursor was left. That's
quite common, the only exception I know is zsh, which moves the cursor
to the start of line if the previous
