response checker in a script

Multi tool use
Multi tool use

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I have following response checker in a script:



#!/bin/bash

test_fn()

WARNFILE=$1
echo
echo "--- BEGIN ---"
cat $WARNFILE
echo "--- END ---"
echo

while true; do
 read -r -n 1 -p "Continue? [y/n]: " REPLY
 case $REPLY in
 [yY]) break ;;
 [nNqQ]) echo;exit ;;
 *) printf "33[31m%s33[0mn" " invalid input: $REPLY"
 esac
done


test_fn /tmp/warning


it works fine...



$ ./test.sh

--- BEGIN ---
test warning
--- END ---

Continue? [y/n]: a invalid input: a
Continue? [y/n]: s invalid input: s
Continue? [y/n]: d invalid input: d
Continue? [y/n]: w invalid input: w
Continue? [y/n]: s invalid input: s
Continue? [y/n]: q
$


...until I change line:



test_fn /tmp/warning


with line:



test_fn /tmp/warning | tee -a /tmp/logfile


then, it scrambles lines:



$ ./test.sh

--- BEGIN ---
test warning
Continue? [y/n]: --- END ---

aContinue? [y/n]: invalid input: a
sContinue? [y/n]: invalid input: s
dContinue? [y/n]: invalid input: d
fContinue? [y/n]: invalid input: f
q
$


Anyone could please tell why it works so?




bash shell-script tee




share|improve this question


















  • 4




    It's because read is writing the prompt to stderr but you are only redirecting stdout to tee I think; that results in the original stderr getting intermixed with the teed stdout. Try test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile
    – steeldriver
    Mar 24 at 13:29










  • @steeldriver, indeed, you are absolutely right, thank you.
    – DonJ
    Mar 24 at 17:42















up vote
0
down vote

favorite












I have following response checker in a script:



#!/bin/bash

test_fn()

WARNFILE=$1
echo
echo "--- BEGIN ---"
cat $WARNFILE
echo "--- END ---"
echo

while true; do
 read -r -n 1 -p "Continue? [y/n]: " REPLY
 case $REPLY in
 [yY]) break ;;
 [nNqQ]) echo;exit ;;
 *) printf "33[31m%s33[0mn" " invalid input: $REPLY"
 esac
done


test_fn /tmp/warning


it works fine...



$ ./test.sh

--- BEGIN ---
test warning
--- END ---

Continue? [y/n]: a invalid input: a
Continue? [y/n]: s invalid input: s
Continue? [y/n]: d invalid input: d
Continue? [y/n]: w invalid input: w
Continue? [y/n]: s invalid input: s
Continue? [y/n]: q
$


...until I change line:



test_fn /tmp/warning


with line:



test_fn /tmp/warning | tee -a /tmp/logfile


then, it scrambles lines:



$ ./test.sh

--- BEGIN ---
test warning
Continue? [y/n]: --- END ---

aContinue? [y/n]: invalid input: a
sContinue? [y/n]: invalid input: s
dContinue? [y/n]: invalid input: d
fContinue? [y/n]: invalid input: f
q
$


Anyone could please tell why it works so?




bash shell-script tee




share|improve this question


















  • 4




    It's because read is writing the prompt to stderr but you are only redirecting stdout to tee I think; that results in the original stderr getting intermixed with the teed stdout. Try test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile
    – steeldriver
    Mar 24 at 13:29










  • @steeldriver, indeed, you are absolutely right, thank you.
    – DonJ
    Mar 24 at 17:42













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have following response checker in a script:



#!/bin/bash

test_fn()

WARNFILE=$1
echo
echo "--- BEGIN ---"
cat $WARNFILE
echo "--- END ---"
echo

while true; do
 read -r -n 1 -p "Continue? [y/n]: " REPLY
 case $REPLY in
 [yY]) break ;;
 [nNqQ]) echo;exit ;;
 *) printf "33[31m%s33[0mn" " invalid input: $REPLY"
 esac
done


test_fn /tmp/warning


it works fine...



$ ./test.sh

--- BEGIN ---
test warning
--- END ---

Continue? [y/n]: a invalid input: a
Continue? [y/n]: s invalid input: s
Continue? [y/n]: d invalid input: d
Continue? [y/n]: w invalid input: w
Continue? [y/n]: s invalid input: s
Continue? [y/n]: q
$


...until I change line:



test_fn /tmp/warning


with line:



test_fn /tmp/warning | tee -a /tmp/logfile


then, it scrambles lines:



$ ./test.sh

--- BEGIN ---
test warning
Continue? [y/n]: --- END ---

aContinue? [y/n]: invalid input: a
sContinue? [y/n]: invalid input: s
dContinue? [y/n]: invalid input: d
fContinue? [y/n]: invalid input: f
q
$


Anyone could please tell why it works so?




bash shell-script tee




share|improve this question














I have following response checker in a script:



#!/bin/bash

test_fn()

WARNFILE=$1
echo
echo "--- BEGIN ---"
cat $WARNFILE
echo "--- END ---"
echo

while true; do
 read -r -n 1 -p "Continue? [y/n]: " REPLY
 case $REPLY in
 [yY]) break ;;
 [nNqQ]) echo;exit ;;
 *) printf "33[31m%s33[0mn" " invalid input: $REPLY"
 esac
done


test_fn /tmp/warning


it works fine...



$ ./test.sh

--- BEGIN ---
test warning
--- END ---

Continue? [y/n]: a invalid input: a
Continue? [y/n]: s invalid input: s
Continue? [y/n]: d invalid input: d
Continue? [y/n]: w invalid input: w
Continue? [y/n]: s invalid input: s
Continue? [y/n]: q
$


...until I change line:



test_fn /tmp/warning


with line:



test_fn /tmp/warning | tee -a /tmp/logfile


then, it scrambles lines:



$ ./test.sh

--- BEGIN ---
test warning
Continue? [y/n]: --- END ---

aContinue? [y/n]: invalid input: a
sContinue? [y/n]: invalid input: s
dContinue? [y/n]: invalid input: d
fContinue? [y/n]: invalid input: f
q
$


Anyone could please tell why it works so?





bash shell-script tee





share|improve this question













share|improve this question




share|improve this question








edited Mar 24 at 13:19









Jeff Schaller

31.2k846105




31.2k846105










asked Mar 24 at 12:55









DonJ

768




768







  • 4




    It's because read is writing the prompt to stderr but you are only redirecting stdout to tee I think; that results in the original stderr getting intermixed with the teed stdout. Try test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile
    – steeldriver
    Mar 24 at 13:29










  • @steeldriver, indeed, you are absolutely right, thank you.
    – DonJ
    Mar 24 at 17:42













  • 4




    It's because read is writing the prompt to stderr but you are only redirecting stdout to tee I think; that results in the original stderr getting intermixed with the teed stdout. Try test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile
    – steeldriver
    Mar 24 at 13:29










  • @steeldriver, indeed, you are absolutely right, thank you.
    – DonJ
    Mar 24 at 17:42








4




4




It's because read is writing the prompt to stderr but you are only redirecting stdout to tee I think; that results in the original stderr getting intermixed with the teed stdout. Try test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile
– steeldriver
Mar 24 at 13:29




It's because read is writing the prompt to stderr but you are only redirecting stdout to tee I think; that results in the original stderr getting intermixed with the teed stdout. Try test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile
– steeldriver
Mar 24 at 13:29












@steeldriver, indeed, you are absolutely right, thank you.
– DonJ
Mar 24 at 17:42





@steeldriver, indeed, you are absolutely right, thank you.
– DonJ
Mar 24 at 17:42











1 Answer
1






active

oldest

votes

















up vote
1
down vote



accepted










To convert a comment to an answer:



read -p writes the prompt to stderr; in order to get the results in-line for tee, pipe the function's stderr to stdout before the tee with:



test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile


To demonstrate read's behavior:



$ read -p "my prompt: " >/dev/null
my prompt: hi
$ read -p "my prompt: " 2>/dev/null
hi





share|improve this answer




















    Your Answer







    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    convertImagesToLinks: false,
    noModals: false,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );








     

    draft saved


    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f433261%2fresponse-checker-in-a-script%23new-answer', 'question_page');

    );

    Post as a guest

















    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    1
    down vote



    accepted










    To convert a comment to an answer:



    read -p writes the prompt to stderr; in order to get the results in-line for tee, pipe the function's stderr to stdout before the tee with:



    test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile


    To demonstrate read's behavior:



    $ read -p "my prompt: " >/dev/null
    my prompt: hi
    $ read -p "my prompt: " 2>/dev/null
    hi





    share|improve this answer
























      up vote
      1
      down vote



      accepted










      To convert a comment to an answer:



      read -p writes the prompt to stderr; in order to get the results in-line for tee, pipe the function's stderr to stdout before the tee with:



      test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile


      To demonstrate read's behavior:



      $ read -p "my prompt: " >/dev/null
      my prompt: hi
      $ read -p "my prompt: " 2>/dev/null
      hi





      share|improve this answer






















        up vote
        1
        down vote



        accepted







        up vote
        1
        down vote



        accepted






        To convert a comment to an answer:



        read -p writes the prompt to stderr; in order to get the results in-line for tee, pipe the function's stderr to stdout before the tee with:



        test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile


        To demonstrate read's behavior:



        $ read -p "my prompt: " >/dev/null
        my prompt: hi
        $ read -p "my prompt: " 2>/dev/null
        hi





        share|improve this answer












        To convert a comment to an answer:



        read -p writes the prompt to stderr; in order to get the results in-line for tee, pipe the function's stderr to stdout before the tee with:



        test_fn /tmp/warning 2>&1 | tee -a /tmp/logfile


        To demonstrate read's behavior:



        $ read -p "my prompt: " >/dev/null
        my prompt: hi
        $ read -p "my prompt: " 2>/dev/null
        hi






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 28 at 0:46









        Jeff Schaller

        31.2k846105




        31.2k846105






















             

            draft saved


            draft discarded


























             


            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f433261%2fresponse-checker-in-a-script%23new-answer', 'question_page');

            );

            Post as a guest
































































            m11955TQ VCRJHOUQ9G aeIJ FYka3 PS,3hOU4SyyExN mKsTwyqhoyx4VlrIIjLYIhYiT4CcM3r209fYc
            -
            qN7fzc,PCAfPEHQGfvzKPYdTzvvQ83tmpGY,GG,3tkx z,I,xZ,cOF2CtI bdv G5 6GS48Uu9aB39 Ag Ol

            Popular posts from this blog

            How to check contact read email or not when send email to Individual?

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
            Read more

            How many registers does an x86_64 CPU actually have?

            Image
            Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
            Read more

            Displaying single band from multi-band raster using QGIS

            Image
            Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
            Read more