I tried it. on mouseUp set the shellCommand to "cmd.exe /u" put textDecode( shell("dir"), "UTF-16" ) end mouseUp
That does seem to double up the newlines. It looks like it works otherwise. Dar > On Aug 22, 2019, at 12:15 PM, dsc--- via use-livecode > <use-livecode@lists.runrev.com> wrote: > > The shellCommand property for Windows is "cmd.exe", not "command.com > <http://command.com/>" as described in the dictionary. > > I wonder how setting that to "cmd.exe /u" would affect this behavior. > >> On Aug 22, 2019, at 10:19 AM, Dar Scott Consulting via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> Concerning 22335... >> >> 1. I wonder if anyone uses shell() to return binary values. >> >> 2. I wonder about whether using the shellCommand property would help. >> >>> On Aug 22, 2019, at 9:37 AM, Paul Dupuis via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >>> I have filed two bug reports that are in LC905rc1 and go back to 7.0 where >>> LC functions that should deal with Unicode properly do not. >>> >>> These are: >>> https://quality.livecode.com/show_bug.cgi?id=22213 -- The "detailed files" >>> function fails for any files with Unicode in the name, returning the >>> filename with %3F (?) instead of the Unicode characters properly URL >>> encoded (they should be UFT8 encoded and then URL encoded) >>> and >>> https://quality.livecode.com/show_bug.cgi?id=22334 -- the shell command is >>> not Unicode aware in returning it's results. On OSX, the results are UTF8 >>> encoded (discovered by accident) and so an extra step is needed to text >>> decode them, but on Windows it is a complete failure and any Unicode >>> results of the command line - SHOWN 100% correctly is executed in the >>> command line - are returned NATIVE encoded, causing all Unicode characters >>> to become question marks. >>> >>> I have written work-around for both of these bugs that can be found in the >>> bug reports. My work-around for the "details files" is slow, due to >>> repeated calls to shell to fetch file properties one at a time. >>> >>> If anyone else out there has run into these bugs in your own code and >>> developed a faster work-around for the "detailed files" and would care to >>> share, I would welcome a faster fix. >>> >>> Of course, I'd welcome a fix from LiveCode, Ltd. to these bugs even more! >>> >>> _______________________________________________ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >> >> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode