Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Tricky BASH quoting question
Top Forums Shell Programming and Scripting Tricky BASH quoting question Post 302790739 by Scrutinizer on Saturday 6th of April 2013 03:35:00 PM
Old 04-06-2013
@MadeInGermany:
In dash, you will get:
Code:
cannot open two words*: No such file

Also, what happens (when the shell does happen to expand wildcards in the variable in the redirect and) "$xmlLocation"* would expand to more than one file? The first would render and ambiguous redirect and the second would concatenate the content of those files and put that in a variable.

IMO this is not the place to use wild cards. it would be more reliable for example to use a for loop to expand wildcards and then use use the loop variable with proper quoting..
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Tricky script question

Hi, I'm in the midst of writing a UNIX script that sftp's files to an external host and am stuck with a problem. The problem is that the files created on my server as a order number that correlates to a sequence of directories on the remote host which is where the file should be ftp'ed. ... (3 Replies)
Discussion started by: budrito
3 Replies

2. UNIX for Dummies Questions & Answers

Tricky Quotation Question

Hi, I am at a point in my script where I defined the number of the command line parameter I would like to set a variable equal to: parameter_number=14 I would then like to set a variable equal to the correct parameter: variable=$parameter_number The issue here is that {} is required... (2 Replies)
Discussion started by: msb65
2 Replies

3. Shell Programming and Scripting

BASH quoting behavior

The block below isn't a surprise:$ ls file1 file2 file3 $ x=* $ echo $x file1 file2 file3 $ echo '$x' $x $ echo "$x" * $But I found this block a bit bewildering:$ echo $x' >' * $I'm wondering why substitution wasn't performed on the $x, since it was unquoted (as far as I can tell).... (5 Replies)
Discussion started by: na5m
5 Replies

4. Shell Programming and Scripting

quoting question

hi guys, i have a question related to quoting but i am not sure how to formulate it... lets say we want to simulate the following shell actions cd ~/project-dir ctags /home/work/folder1/*.sh /home/work/folder2/*.sh /home/work/folder3/*.sh so i make the following script buidtags.sh ... (2 Replies)
Discussion started by: aegis
2 Replies

5. Shell Programming and Scripting

Quoting issue: Trouble with bash strings in script

I can do this on the command line: sqsh -S 192.168.x.x -o tmp -U user -P fakepass -D horizon -C "\ select second_id from borrower where btype like '%wsd%' " I can also just leave the SQL at the end intact on one line .... ... However, when I throw this in a script like: $SQSH -o... (4 Replies)
Discussion started by: Bubnoff
4 Replies

6. Shell Programming and Scripting

Another tricky sed or awk question

This post is in reference to https://www.unix.com/shell-programming-scripting/137977-tricky-sed-awk-question-post302428154.html#post302428154 I am trying to go the opposite direction now: I have the following file: a,b,C,f,g a,b,D,f,g a,b,E,f,g h,i,J,k,l m,n,O,t,u m,n,P,t,u m,n,Q,t,u... (3 Replies)
Discussion started by: awayand
3 Replies

7. Shell Programming and Scripting

bash: correct quoting with find and exiv2?

Hi, I need to embed a metatag to image files which contain qrcodes, i usually do this with exiv -M "set Exif.Image.DocumentName `zbarimg -q -Sdisable -Sqrcode.enable --raw image.tif`" image.tif which works fine. However I need to do this recursivly for whole directory and subdiretory... (4 Replies)
Discussion started by: mcframe
4 Replies

8. UNIX for Dummies Questions & Answers

Tricky GREP question..

I have some large login files that I need to extract (user)@(server) from. Where it gets tricky is that there is usually more than one '@' sign on each line(although it does have a leading space if it's not part of the (user)@(server) string), I need only the (user)@(server) section, I need only... (6 Replies)
Discussion started by: Mordaris
6 Replies

9. Shell Programming and Scripting

Quoting / interface question

Hi, My first shell script is one that prints the five largest directories in a given directory. My current effort is as follows, it gives me the output I'd like, but I have to quote a globbed pathname, which seems wrong: #!/bin/sh du -hs $1 | sort -rn | head -n 5 And I must invoke... (2 Replies)
Discussion started by: aardymir
2 Replies

10. Shell Programming and Scripting

Help with Bash quoting

I am trying to write a BASH script that will prompt a user to enter a number of days, then calculate the date. My problem is the date command uses single or double quotes. For Example.. date -d "7 days" Here is an example of some same code I am trying to work through. echo "when do you... (4 Replies)
Discussion started by: javajockey
4 Replies

LEARN ABOUT DEBIAN

xml::easy::transform

XML::Easy::Transform(3pm)				User Contributed Perl Documentation				 XML::Easy::Transform(3pm)

NAME

       XML::Easy::Tranform - XML processing with a clean interface

DESCRIPTION

       The "XML::Easy::Transform::" namespace exists to contain modules that perform transformations on XML documents, or parts thereof, in the
       form of XML::Easy::Element and XML::Easy::Content nodes.

       XML::Easy is a collection of modules relating to the processing of XML data.  It includes functions to parse and serialise the standard
       textual form of XML.  When XML data is not in text form, XML::Easy processes it in an abstract syntax-neutral form, as a collection of
       linked Perl objects.  This in-program data format shields XML users from the infelicities of XML syntax.  Modules under the
       "XML::Easy::Transform::" namespace operate on XML data in this abstract structured form, not on textual XML.

       A transformation on XML data should normally be presented in the form of a function, which takes an XML::Easy::Element node as its main
       parameter, and returns an XML::Easy::Element node (or "die"s on error).	The input node and output node each represent the root element of
       the XML document (or fragment thereof) being transformed.  These nodes, of course, contain subordinate nodes, according to the structure of
       the XML data.  A reference to the top node is all that is required to effectively pass the whole document.

OTHER DISTRIBUTIONS

       CPAN distributions under this namespace are:

       XML::Easy::Transform::RationalizeNamespacePrefixes
	   Manages XML Namespaces by hoisting all namespace declarations to the root of a document.

SEE ALSO

       XML::Easy

AUTHOR

       Andrew Main (Zefram) <zefram@fysh.org>

COPYRIGHT

       Copyright (C) 2009, 2010, 2011 Andrew Main (Zefram) <zefram@fysh.org>

LICENSE

       This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.14.2							    2011-11-16						 XML::Easy::Transform(3pm)
All times are GMT -4. The time now is 05:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy