[Braber01]

I'm currently making a twitter shell for my own amusment here is the code:

#!/bin/bash
#Twitter.sh
#Revised making use of Twitter and Twitter's api using a shell prompt 
#That looks like "twitter> "

clear
echo "Login to Twitter..."
echo
echo "Twitter Username?"
read -p "twitter> " USER
echo
echo "Twitter Password?"
read -sp "twitter> " PASS

echo "Welcome to the Twitter shell."
echo "What do you want to do?"
CMD=""

while [ "$CMD" != "bye" ];
do
	 read -p "twitter> " CMD
	 echo
	 if [ "$CMD" == "show" ]; then
		  echo "not programmed yet"
	 elif [ "$CMD" == "update" ]; then
		  echo "Update your status to...?"
		  read -p "twitter> " STATUS
		  curl -u "$USER":"$PASS" -d status="$STATUS" http://twitter.com/statuses/uptade.xml > /dev/null
		 echo "Status updated"
	 elif [ "$CMD" == "bye" ]; then
		  clear
	 else
		echo "not an option"
	 fi
done

How do i get rid of the report that /dev/null prints out? I don't want the user of the application to see it

[Braber01]

adding the command clear did it

[snoj]

/dev/null prints something? I thought /dev/null just was a place to pipe things when you didn't want or need them sticking around.

Could it be that you're not redirecting (like STDERR) all output from curl?

[Braber01]

snoj, on 19 Dec, 2009 - 12:45 PM, said:

/dev/null prints something? I thought /dev/null just was a place to pipe things when you didn't want or need them sticking around.

Could it be that you're not redirecting (like STDERR) all output from curl?

well when i tried

curl -u "$USER":"$PASS" -d status="$STATUS" http://twitter.com/statuses/update.xml | /dev/null 

it prints:
bash: dev/null: No such file or directory
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
101 2125 100 2003 0 122 2501 152 --:--:-- --:--:-- --:--:-- 3464

and i got the same thing using the '>' symbol so i just added a clear after it and everythings is allright.

[no2pencil]

You shouldn't pipe /dev/null, you use /dev/null as a dumping ground for output that you don't want to see. It's about data pipes, Standard in, out, and error. If you only wish to see the errors, then you pipe standard out to /devl/null & the same with if you only wish to see standard out, you'd pipe standard error to /dev/null, lastly if you wish to see no output, just pipe all output to /dev/null.

For example 1 is stdout stream & 2 is the stderr stream :

ls /root/ 2> /dev/null # errors are piped to /dev/null & not seen on standard out

[Braber01]

no2pencil, on 19 Dec, 2009 - 10:52 PM, said:

You shouldn't pipe /dev/null, you use /dev/null as a dumping ground for output that you don't want to see. It's about data pipes, Standard in, out, and error. If you only wish to see the errors, then you pipe standard out to /devl/null & the same with if you only wish to see standard out, you'd pipe standard error to /dev/null, lastly if you wish to see no output, just pipe all output to /dev/null.

For example 1 is stdout stream & 2 is the stderr stream :

ls /root/ 2> /dev/null # errors are piped to /dev/null & not seen on standard out

I've tried this trick using both

curl -u "$USER":"$PASS" -d status="$STATUS" http://twitter.com/statuses/update.xml  1> /dev/null

curl -u "$USER":"PASS" -d status="$STATUS" http://twitter.com/statuses/update.xml 2>/dev/null

and

curl -u "$USER":"$PASS" -d status="$STATUS" http://twitter.com/statuses/update.com 3> /dev/null

and NONE of them have worked any advice???

no2pencil, on 19 Dec, 2009 - 10:52 PM, said:

You shouldn't pipe /dev/null, you use /dev/null as a dumping ground for output that you don't want to see. It's about data pipes, Standard in, out, and error. If you only wish to see the errors, then you pipe standard out to /devl/null & the same with if you only wish to see standard out, you'd pipe standard error to /dev/null, lastly if you wish to see no output, just pipe all output to /dev/null.

For example 1 is stdout stream & 2 is the stderr stream :

ls /root/ 2> /dev/null # errors are piped to /dev/null & not seen on standard out

I've tried this trick using both

curl -u "$USER":"$PASS" -d status="$STATUS" http://twitter.com/statuses/update.xml  1> /dev/null

curl -u "$USER":"PASS" -d status="$STATUS" http://twitter.com/statuses/update.xml 2>/dev/null

and

curl -u "$USER":"$PASS" -d status="$STATUS" http://twitter.com/statuses/update.com 3> /dev/null

and NONE of them have worked any advice???

[no2pencil]

Braber01, on 20 Dec, 2009 - 04:41 PM, said:

any advice???

Yes.

Use CURL correctly Don't suppress the output at the command prompt, use CURL with --silent.

[Braber01]

no2pencil, on 21 Dec, 2009 - 08:56 PM, said:

Braber01, on 20 Dec, 2009 - 04:41 PM, said:

any advice???

Yes.

Use CURL correctly Don't suppress the output at the command prompt, use CURL with --silent.

cURL asks me for a password each time i tried to use the --silent or the -s flag I know this is a bad way of programming but I'm new to linux and I'm going to stick with what works for me thanks anyway