tag:blogger.com,1999:blog-6111725723134762877.post4575953751153111238..comments2022-11-16T05:32:23.171-08:00Comments on XMLSH: When are sequences too much ?Anonymoushttp://www.blogger.com/profile/06155161084044858311noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6111725723134762877.post-5074559104129094712010-03-08T06:32:12.184-08:002010-03-08T06:32:12.184-08:00I've implemented a more invasive change, check...I've implemented a more invasive change, checked in but not released yet.<br />This reverts the default behaviour for sequences to expand to multiple arguments, but allows direct control of each expression by using {expr}.<br />Example<br /><br />set $(ls) # sets multiple args<br />set {$(ls)} # sets 1 arg as a sequence<br />set <[1,2,3]> # sets 3 args<br />set {<[1,2,3]>} # sets 1 arg as sequence of 3Anonymoushttps://www.blogger.com/profile/06155161084044858311noreply@blogger.comtag:blogger.com,1999:blog-6111725723134762877.post-86698709265986707082010-03-07T08:18:50.923-08:002010-03-07T08:18:50.923-08:00I'm experimenting with a non-invasive partial ...I'm experimenting with a non-invasive partial solution for this problem. Its not a general solution but might be useful enough to be sufficient. <br /><br />I added a -E (or -expand) option to set.<br />This tells set that it should expand (flatten) all sequences into individual XdmItme's for each positional parameter.<br />Example<br /><br />set $(ls) # sets $1 to be a sequence of file names<br /><br /><br />set -E -- $(ls) # sets $1...$N to be individual file namesAnonymoushttps://www.blogger.com/profile/06155161084044858311noreply@blogger.com