Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • is it possible to use uq(); with a replacement string defined with --rpl? For example, in this case, is it possible to do something like this: parallel --rpl "{var} s/var/Var/; uq();" myprogram {1 var} {2} :::: variables.txt ::: My*.txt Commented Apr 23, 2021 at 12:16
  • 1
    @IsoBar Almost. ... {1var} ... (no space between 1 and var) Commented Apr 23, 2021 at 17:07
  • @OleTange - might you consider an option where replacement strings are not quoted at all. IMO quoting is gratuitous and makes assumptions that are not always correct about the environment in which the string is to appear. I would argue that the default should be not to quote them, but it is too late, and you will at least want to be backwards compatible if you were to take my suggestion. Commented Sep 2, 2021 at 17:39
  • @malcook The non-quoting by default was one of the most annoying thing I found about xargs: I was bitten by this more than once. With uq I have yet to see examples where this is not sufficient. Commented Sep 2, 2021 at 20:57
  • 1
    @OleTange - I guess each to their own.... I find that parallel 's quoting presents an issue especially since it only quotes a parameter if it "thinks" quoting will be needed using its own idiosyncratic rules. Personally, I'd much rather quote or escape as appropriate to the context (for a shell, for a url) when required rather than strip them using the {= crufty perl escape syntax =} (which you introduced at my suggestion, thank you very much). So, my Q stands: "might you consider an option where replacement strings are not quoted at all". Commented Sep 3, 2021 at 22:10