We use cookies to ensure you have the best browsing experience on our website. Please read our cookie policy for more information about how we use cookies.
Loading...
  1. Practice
  2. Linux Shell
  3. Bash
  4. A Personalized Echo
  5. Discussions

A Personalized Echo

Sort 25 Discussions, By:

votes

  • Netherheld + 5 comments

    Why is the read syntax the only correct answer to this question? Why not the $1 alternative?

    • mbrito + 0 comments

      agree

    • cli__ + 0 comments

      The input comes from stdin, not comand line arguments

    • panchito + 0 comments

      Humm, thanks, didn't know this only correct answere i did also it with $1 with no success .. theses tests are limited

    • dukemaneesh + 0 comments

      read name echo "Welcome Dan"

    • dave00ster + 0 comments

      Agreed. I don't understand why they had to write "script which accepts" instead of "script which reads.

  • michi7x7 + 0 comments

    hehe :)

    printf "Welcome "
cat

  • x0r19x91 + 2 comments
    sed -r 's/(.*)/Welcome \1/g'
    • Cristiana + 1 comment

      Hi! I'm new to this. Can you please explain a bit this command?

      • x0r19x91 + 1 comment

        I'm capturing the contents of stdin using (.*) regexp which can be referenced using \1 where \1 refers to 1st captured group and then prepending the text with "Welcome".
        The syntax is s/[text]/[replacement]/

        • Cristiana + 0 comments

          Got it. Thanks!

    • zzmmss + 0 comments

      new to shell, very incredible

  • sakthipitchaiah + 3 comments

    here is the answer:

    read name
echo "Welcome $name"
    • dread1 + 0 comments
      [deleted]
    • dread1 + 1 comment
      echo "Welcome $(</dev/stdin)"

      will also work

      • mmshaban + 1 comment

        Can you explain this a bit, please?

        • SomuSysAdmin + 1 comment

          Whenever you use something like `$(command) in bash, you're creating a new sub-shell for that command. The input is obtained in that subshell, and the output replaces the entire $(command)` section in the original shell. Essentially think of it like executing a command first and then putting the ouput in place of the bracketed section.

          Now, </dev/stdin is just redirecting the input from the subshell. So, whatever is entered in the subshell (sample inputs from the test-cases) gets sent (and replaces) $(</dev/stdin).

          • mmshaban + 0 comments

            Nice.. Thanks..

    • kiyana_ahmadi + 0 comments

      I wrote exactly the same thing but it keeps saying it's wrong !!

  • aadi2203 + 3 comments

    I have a tick in every test case but when retunr back to the bash tutorials page it doesnt show thus question as fully solved?

    • vivmbbsHackerRank Admin + 1 comment

      checking this; it's a bug on our end. will fix

      • apachebeard + 0 comments

        bug still not fixed

    • dheerajHackerRank Admin + 1 comment

      Hi @aadi2203,

      can you please check now? It will be fixed.

      • varunchopra + 0 comments

        3 years and it still hasn't been fixed.

    • brahanmadhav + 0 comments

      same here :(

  • cloaked1 + 0 comments
    xargs -I ^ echo "Welcome" ^

  • itsvvishnu + 0 comments
    str1="Welcome " 
read test
echo $str1 $test

  • h1184869170 + 0 comments

    One new solution: sed -r 's/\w+/Welcome &/g'

  • mleite + 1 comment

    the input parameter comes from stdin, not from comand line arguments

    in this case, this code is wrong:

    #!/bin/sh
echo "Welcome $1

    but this works well:

    #!/bin/sh
echo "Welcome "`cat -`
    • pssasadraw + 0 comments

      Can you explain the cat and the '-'.

  • geetuvaddeboina + 0 comments

    read name echo "welcome($name)"

Load more conversations