Sponsored Content
Top Forums Shell Programming and Scripting Grep behaves diffrent upon printf or echo output Post 302920922 by sea on Monday 13th of October 2014 03:51:11 PM
Old 10-13-2014
Grep behaves diffrent upon printf or echo output

Hello

I want to check whether certain arguments were passed to the script, and when those are, not doing a log entry.
If those arguments are not passed, always do a log entry (*new call*).

What currently i have is this:
Code:
	echo "${@}"|grep -q \\-[Lih] || \
		tui-log -e "$LOG" "\r---- New call $$ ----"

Which upon these 2 commands, produces these lines within the logfiles:
Code:
vhs -h ; vhs -L

With echo i have the expected output:
Code:
21:42:46         Show Help
21:42:46         Show Logfile
21:42:49         Show Help
21:42:49         Show Logfile

However, as soon i change echo to become printf, it produces this (not wanted):
Code:
---- New call 17388 ----
21:44:19         Show Help

---- New call 17423 ----
21:44:19         Show Logfile

In addition i wanted to use [[:space:]]\\-[Lih], but i assume that is another issue?
I've tried quoting the regex, but still fails.

System:
Code:
export LC_ALL=C ; uname -r ; echo "--" ; $SHELL --version
3.16.3-200.fc20.x86_64
--
GNU bash, version 4.2.51(1)-release (x86_64-redhat-linux-gnu)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>

This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Any ideas?
Thank you in advance
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

diffrent results between command line and scripted grep

When I type a command at the command line it supplies one result and the exact same command in a script egrep '^01|^02|^03|^04' file > fileout count = 29353 same count in the script yields a count of 23492 is there any reason this could be happening. (1 Reply)
Discussion started by: r1500
1 Replies

2. UNIX for Dummies Questions & Answers

How do I output or echo NONE if grep does not find anything?

I am performing a grep command and I need to know how to echo "NONE" or "0" to my file if grep does not find what i am looking for. echo What i found >> My_File grep "SOMETHING" >> My_File I am sure this is easy, I am sort of new at this! Thanks (2 Replies)
Discussion started by: jojojmac5
2 Replies

3. Shell Programming and Scripting

advanced echo/printf

I want to print a colored line using bash. I want to print: Smtp status where "Smtp status" will be in yellow and will be in green. Thanks. (2 Replies)
Discussion started by: proactiveaditya
2 Replies

4. Shell Programming and Scripting

\n in ksh using echo & printf

#!/usr/bin/ksh var1="Hi World" var2="Morning" var3=$(echo "$var1" \n "$var2") echo $var3 var3=$(printf "$var1 \n $var2") echo $var3 Output Any way to get in my $var3 ? (7 Replies)
Discussion started by: dahlia84
7 Replies

5. Shell Programming and Scripting

printf/echo in a second script

This may be little confusing. I have Script1, which pulls data from the system and creates another script(lets say script2). While I run script1 I need to add printf/echo statements for script2, so that when I run script2 I see those statement. eg: script1 765 printf " display frame-$1 timeoffset... (2 Replies)
Discussion started by: miltonrods
2 Replies

6. Solaris

Diffrent output in cron jobs

Hi, I have issue with cron. When i run script manually output is fine but when i add it to cron output file is not as same. both file attach some junk charecter comming in cron output. thanx Jignesh (5 Replies)
Discussion started by: jkmistry
5 Replies

7. Shell Programming and Scripting

Managing output... echo or printf?

Hello script guru's as i write more and more code i always block at managing output... either writing to standard out, writing to files via std out (log, temp file, etc). Don't get me wrong 99% of the time it DOES the job but maybe there is more efficient. I'm writing a small script to... (2 Replies)
Discussion started by: maverick72
2 Replies

8. Linux

Availability: echo vs. printf?

Hello, For some reason i dont remember, i currently believe (but beeing unsure) that printf is available on more diffrent systems (unix, bsd, linux, ??) than echo is. Could someone please enlighten me, whether this is true or not? Thank you PS: I just found pages about the diffrences of... (3 Replies)
Discussion started by: sea
3 Replies

9. Shell Programming and Scripting

Copy-pasted code behaves diffrent

Heyas I'm currently attempting to apply the code of tui-select to tui-list. That is because tui-list simply made a 1 string list, while tui-select uses dynamicly up to 3 strings per line. Anyway, so i copy pasted the code, and just made the changes marked with red.... Know that both scripts... (2 Replies)
Discussion started by: sea
2 Replies

10. Shell Programming and Scripting

Grep echo awk print all output on one line

Hello, I've been trying to find the answer to this with Google and trying to browse the forums, but I haven't been able to come up with anything. If this has already been answered, please link me to the thread as I can't find it. I've been asked to write a script that pulls a list of our CPE... (51 Replies)
Discussion started by: rwalker
51 Replies
SVK::Command::Log(3)					User Contributed Perl Documentation				      SVK::Command::Log(3)

NAME
SVK::Command::Log - Show log messages for revisions SYNOPSIS
log DEPOTPATH log PATH log -r N[:M] [DEPOT]PATH OPTIONS
-r [--revision] ARG : ARG (some commands also take ARG1:ARG2 range) A revision argument can be one of: "HEAD" latest in repository {DATE} revision at start of the date NUMBER revision number NUMBER@ interpret as remote revision number NUM1:NUM2 revision range Unlike other commands, negative NUMBER has no meaning. -l [--limit] REV : stop after displaying REV revisions -q [--quiet] : Don't display the actual log message itself -x [--cross] : track revisions copied from elsewhere -v [--verbose] : print extra information --xml : display the log messages in XML format --filter FILTER : select revisions based on FILTER --output FILTER : display logs using the given FILTER DESCRIPTION
Display the log messages and other meta-data associated with revisions. SVK provides a flexible system allowing log messages and other revision properties to be displayed and processed in many ways. This flexibility comes through the use of "log filters." Log filters are of two types: selection and output. Selection filters determine which revisions are included in the output, while output filters determine how the information about those revisions is displayed. Here's a simple example. These two invocations produce equivalent output: svk log -l 5 //local/project svk log --filter "head 5" --output std //local/project The "head" filter chooses only the first revisions that it encounters, in this case, the first 5 revisions. The "std" filter displays the revisions using SVK's default output format. Selection filters can be connected together into pipelines. For example, to see the first 3 revisions with log messages containing the string 'needle', we might do this svk log --filter "grep needle | head 3" //local/project That example introduced the "grep" filter. The argument for the grep filter is a valid Perl pattern (with any '|' characters as '|' and '' as '\'). A revision is allowed to continue to the next stage of the pipeline if the revision's log message matches the pattern. If we wanted to search only the first 10 revisions for 'needle' we could use either of the following commands svk log --filter "head 10 | grep needle" //local/project svk log -l 10 --filter "grep needle" //local/project You may change SVK's default output filter by setting the SVKLOGOUTPUT environment. See svk help environment for details. Standard Filters The following log filters are included with the standard SVK distribution: Selection : grep, head, author Output : std, xml For detailed documentation about any of these filters, try "perldoc SVK::Log::Filter::Name" where "Name" is "Grep", "Head", "XML", etc.. Other log filters are available from CPAN <http://search.cpan.org> by searching for "SVK::Log::Filter". For details on writing log filters, see the documentation for the SVK::Log::Filter module. perl v5.10.0 2008-08-04 SVK::Command::Log(3)
All times are GMT -4. The time now is 12:37 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy