Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #11469

Re: Why does a Bash shell script write prompts followed by reads and do it right?

Path csiph.com!xmission!news.glorb.com!usenet.stanford.edu!not-for-mail
From Bob Proulx <bob@proulx.com>
Newsgroups gnu.bash.bug
Subject Re: Why does a Bash shell script write prompts followed by reads and do it right?
Date Wed, 2 Sep 2015 14:22:59 -0600
Lines 15
Approved bug-bash@gnu.org
Message-ID <mailman.421.1441225386.19560.bug-bash@gnu.org> (permalink)
References <CAAykW6m4H2sSshWNfv3mQr9q6ScKzLebqMBgEo96vRUSBY6SAQ@mail.gmail.com> <1441218426.1517.2.camel@16bits.net> <CAAykW6mnTcLA21h79YDb_4-Pv3GhG_8xBhhNcG0unzYpkfqGMQ@mail.gmail.com>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset=us-ascii
X-Trace usenet.stanford.edu 1441225386 10352 208.118.235.17 (2 Sep 2015 20:23:06 GMT)
X-Complaints-To action@cs.stanford.edu
Cc bug-bash@gnu.org
To Robert Parker <rlp1938@gmail.com>
Envelope-to bug-bash@gnu.org
Mail-Followup-To Robert Parker <rlp1938@gmail.com>, bug-bash@gnu.org
Content-Disposition inline
In-Reply-To <CAAykW6mnTcLA21h79YDb_4-Pv3GhG_8xBhhNcG0unzYpkfqGMQ@mail.gmail.com>
User-Agent Mutt/1.5.23 (2014-03-12)
X-detected-operating-system by eggs.gnu.org: GNU/Linux 3.x
X-Received-From 216.17.153.58
X-BeenThere bug-bash@gnu.org
X-Mailman-Version 2.1.14
Precedence list
List-Id Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive <http://lists.gnu.org/archive/html/bug-bash>
List-Post <mailto:bug-bash@gnu.org>
List-Help <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
Xref csiph.com gnu.bash.bug:11469

Show key headers only | View raw


Robert Parker wrote:
>         fputs(shortprompt, stdout);
>         fflush(stdin);

Uhm...  fflush'ing stdin?  That doesn't make sense.  Obviously you
meant to flush stdout.

        fputs(shortprompt, stdout);
        fflush(stdout);

That is likely the specific problem.  Unfortunately I have no time for
comments about the rest of the code.

Bob

Back to gnu.bash.bug | Previous | Next | Find similar


Thread

Re: Why does a Bash shell script write prompts followed by reads and do it right? Bob Proulx <bob@proulx.com> - 2015-09-02 14:22 -0600

csiph-web