GNU bug report logs - #63189
28.2; Shell commands doesn't get executed after command that use stdin.

Previous Next

Full log

Message #11 received at 63189 <at> debbugs.gnu.org (full text, mbox):

From: Новогодняя Ёлка
 <gamemode1.459 <at> gmail.com>
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: "63189 <at> debbugs.gnu.org" <63189 <at> debbugs.gnu.org>
Subject: Re: bug#63189: 28.2; Shell commands doesn't get executed after
 command that use stdin.
Date: Mon, 1 May 2023 12:18:28 +0300

[Message part 1 (text/plain, inline)]

> Can you confirm that the commands
> echo start
> sleep 1
> echo end
> have the same effect?

No, it works as it should. Same with true command.
It's just commands that read from the standard input behave that way. (pacman, apt, etc)
1. Create a file named ~/a.sh with content
read -p "Continue (y/n)?" choice
2. chmod +x ~/a.sh
3. emacs -q
4. M-x shell
5. echo start
~/a.sh
echo end

The result is
~ > echo start
~/a.sh
echo end
echo start
start
~ > ~/a.sh
Continue (y/n)?y
y
~ >

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.