Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: weird echo output?
Top Forums Shell Programming and Scripting weird echo output? Post 302177904 by era on Monday 24th of March 2008 03:21:27 AM
Old 03-24-2008
Quote:
Code:
echo "\"$CDPERFORMER\" "
echo "\"$CDTITLE\" "
echo "\"$TRACKNUMBER\" "
echo "\"$TRACKTITLE\" "

I get:
This funny board software didn't even know how to quote the output, so I take that as additional indication that the problem is this: you have DOS carriage returns in the output.

I really wonder about your use of less inside a script. Does it bring some benefit over simply reading the file?

Quote:
Code:
CDPERFORMER=`less "$CUEFILE"|grep -B10 FILE|grep PERFORMER|sed 's/PERFORMER\ "//'|sed 's/^[ \
t]*//'|sed 's/"//'`

With all due respect, you should probably read up on sed scripting. grep | sed is almost always redundant, since sed is basically a grep on stereoids.

Code:
CDPERFORMER=`grep -B10 FILE "$CUEFILE" |
    tr -d '\015' |
    sed -n 's/^[ 	][ 	]*PERFORMER[ 	][ 	]*"\([^"]*\)*"/\1/p'`

... assuming that your repeated sed invocations were meant to remove any PERFORMER tag, remove any leading whitespace before it, and trim the double quotes around the value (and throwing in the removal of any DOS carriage returns as a bonus). Probably the first grep could also be avoided if you familiarize yourself with sed some more, but this is how far I get without even reading the manual page. (Granted, the real magic is in being able to write a proper regular expression for any given problem.) ... That's a tab and a space between the square brackets, by the way.
 

10 More Discussions You Might Find Interesting

1. AIX

Weird bootlist output

just setup a new system today - 9117 570, using HMC for console but not partitioned. I installed this system twice. the first time it started off as 5300-00, then updated to ML03. before the update, I believe I mirrored the rootvg, and then altered the bootlist, at that point, the display was... (4 Replies)
Discussion started by: davew1099
4 Replies

2. UNIX for Dummies Questions & Answers

Weird character in between echo function

Hi All, Appreciate if anyone can help. I've a script where it does echo function like this while do FILE_ARG="cu0${w}_${FILE}_${DT}.av" ORACLE_ERROR=`grep "ORA-" ${FILE_ARG}` if ]; then Func_Log_Writer "Fail! ${FILE_ARG}\n" Func_Log_Writer "Error message:... (2 Replies)
Discussion started by: agathaeleanor
2 Replies

3. Shell Programming and Scripting

format of output is weird

hi all, have a ksh script which connects to a database and runs a sql and dumps it to a '.csv' file. The problem is the result is in multiple rows with long spaces in between when it should be just a single line and this screws up the format in the '.csv' file. script is : #!/bin/ksh... (1 Reply)
Discussion started by: cesarNZ
1 Replies

4. UNIX for Dummies Questions & Answers

weird 'ls' output

Hi, Anyone knows why I can't display the contents of my directory and how to fix this? http://i50.tinypic.com/4smfth.jpg Thanks in advance for any advise. Deanne Double post. Continued here. (0 Replies)
Discussion started by: Deanne
0 Replies

5. Shell Programming and Scripting

In bash getting weird output from function ?

My script- result="" times() { echo "inside the times function" result=8 echo "Inside function $result" return $result } result=$(times) echo "the value is "$? echo "the value of result $result" when I run I get this, why the value still remain 0. $ ./func the value is 0 the value... (5 Replies)
Discussion started by: boy18nj
5 Replies

6. Shell Programming and Scripting

Traceroute script weird output

This script is giving weird output #!/bin/bash NETPATH=(`/bin/traceroute -n 4.2.2.2 | awk '{print $2}'`) for i in "${NETPATH}" do echo $i done The output: to 11.11.11.1 1.1.1.1 99.111.208.2 traceroute_test.sh traceroute_test.sh (7 Replies)
Discussion started by: thumbs
7 Replies

7. Shell Programming and Scripting

Weird tail output over ssh

Hello; Am trying to correct the formatting of tail output over ssh. Using the following code: echo "" > $FILE for BOX in $SERVERS do echo "Processing on $BOX" |tee -a $FILE echo "===============================" >> $FILE sudo ssh $BOX 'TERMINAL="vt100" /usr/bin/sh -s' <... (2 Replies)
Discussion started by: delphys
2 Replies

8. HP-UX

[Solved] Weird 'ls -l' output

Hello folks, I've found an HP-UX server with a rare 'ls -l' output. Please see the attached file. Anybody knows how can I change the output to not have this extra tabulations? Thanks in advance! (10 Replies)
Discussion started by: carpannav
10 Replies

9. UNIX for Advanced & Expert Users

Weird output from ps command

Hi Guys, I am regular Solaris user. I came across a weird problem that puzzled me. Hope you guys can help. I found that process's state(command & arguments) in two different variants of ps command is different. Can anyone explain how is this possible? bash-3.2$ ps -eLo pid,s,comm,args |... (2 Replies)
Discussion started by: brij123
2 Replies

10. Shell Programming and Scripting

Grep two files: -F flag gives weird output

Hi Members, I'm confused with grep -F option. Goal is to get all the lines from file2 that have exact gene name from gene list (file one). File one has list of genes: File two has lot more information pertinent to genes in file one: I use three following commands: 1) grep -wf gene... (9 Replies)
Discussion started by: genome
9 Replies

LEARN ABOUT DEBIAN

apsfilter-bug

APSFILTER-BUG(1)					    BSD General Commands Manual 					  APSFILTER-BUG(1)

NAME

     apsfilter-bug -- create a half-automatic bug report for apsfilter

SYNOPSIS

     apsfilter-bug

OPTIONS

     none

DESCRIPTION

     With the apsfilter-bug script you can automatically create a bug report for apsfilter(1).	A template report file is created which you can
     edit with your favourite editor ( emacs(1) by default, or whatever is entered in the environment variable EDITOR ).

     You will see a couple of lines starting with '#'; these lines will be removed before the report is sent. So if you want to use the '#' char-
     acter at the beginning of a line, just indent it with a space.

     A very important piece of the bug report is the debugging log created by aps2file(1), probably with a command like
	   aps2file -D -o /dev/null [-P...] [-Z...] [input] 2> log.txt
     Unless you don't even have a chance to create a debugging log, it is crucial for serious bug hunting.

     After you have filled in as much (useful) information as possible, you must save the file under its original name, then exit your editor.

     If you invoked apsfilter-bug by accident, or if you need some additional system information to include into the bug report, just exit your
     editor without saving the file.

NOTES

     In addition to the stuff you've edited, some more information is appended to the bug report automatically:

     apsfilter version	  7.2.6-stable
     ghostscript version  (from 'gs --version')
     system id		  (from 'uname -a')
     configure options	  --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --with-awk=/usr/bin/awk --with-sendmail=/usr/sbin/sendmail
     shell executable	  /bin/bash
     awk executable	  /usr/bin/awk
     sendmail executable  /usr/sbin/sendmail

FILES

     /usr/bin/aps2file	script to create debugging output

SEE ALSO

     apsfilter(1), aps2file(1)

BUGS

     See apsfilter software center - http://www.apsfilter.org/ - for new versions, bugfixes and known bugs.

     Please use the new tool apsfilter-bug(1) to release bug- or problem reports. It automatically presents you a form in an editor window which
     asks you some standard questions.	If you save and quit the editor session, then this report is sent automatically via e-mail to the proper
     apsfilter mailinglist.

     If apsfilter fails to print something or prints it in a way you wouldn't expect and you want to report an apsfilter error then please save
     the debugging output of one print session using the new aps2file(1) utility by typing aps2file -D -Z options file > /dev/null 2> file.debug
     and including the debugging output in the file file.debug into the edit session of the apsfilter-bug utility, so that it is included into the
     mail to the apsfilter mailinglist.

     Please note that you need to run /bin/sh (Bourne Shell), bash or a compatible shell, so that the above mentioned output redirection works.
     Under C-shell (/bin/csh) or tcsh it would't work. If you don't know, then simply make sure you use the Bournce shell by typing /bin/sh or
     bash, then you should have no problems with redirection of stdout and stderr (> /dev/null 2> file.debug).

DOCUMENTATION

     See official apsfilter homepage
     http://www.apsfilter.org/handbook.html   Apsfilter Handbook including the Frequently Asked Questions (FAQ)

USER FORUM

     Please send questions to the official apsfilter help channel apsfilter-help@apsfilter.org.  The above section BUGS and the file
     HOWTO-BUGREPORTS tells you how to report bugs.  If you want to know how to troubleshoot your apsfilter installation, please read the manpage
     aps2file(1) and apsfilter-bug(1) as well as the Apsfilter Handbook carefully.

HISTORY

     The apsfilter-bug manpage has been written by Michael LoBin <phallobst@web.de> and first appeared in apsfilter V 7.1.0.

BSD
								   Dec 26, 2001 							       BSD
All times are GMT -4. The time now is 02:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy