On Sat, 7 Dec 2019, at 14:20, songbird wrote: > The Wanderer wrote: > > ... about various characters and then @ in particular ... > > > As far as I can see, at least on my keyboard, that pretty much just > > leaves @. It does still sometimes occur in paths and filenames, so it's > > not really ideal, but it's probably less common there than any of the > > non-special-meaning others. > > my specific use wasn't for paths or file names but text in > general which i'd previously typed in as a summary. so rarely > any special characters in there at all (other than the end of > line characters). it was always delimited by triple "'s so i > had to split that chunk to get rid of those.
On other systems I've got around this by translating the strings to a hex representation, then issued the command in hex terms, so eg instead of this = "first string" that = "new value" "c /"this"/"that"/" I've had thishex = c2x(this) ie: "666972737420737472696E67" thathex = c2x(that) ie: "6E65772076616C7565" "c /&x'"thishex"'/&x'"thathex"'/" which is to say "c /&x'666972737420737472696E67'/&x'6E65772076616C7565'/" -- Jeremy Nicoll - my opinions are my own.
