Haven't had time to dive into it yet, but love that you've added a WSL Script Function type. Some example scripts that show how to connect the current state in DO (for example, grep on current file basename and ps on input text) would be great to help us get started. I'm definitely going to implement a locate toolbar command.
The advanced command editor now allows commands to be set as WSL Script functions; similar to DOS Batch mode, this runs the command as a WSL (Bash) script. Note that WSL needs to be installed from the Windows Store.
Added CLI DOSPROMPT=wsl command to open a linux shell (assuming WSL is installed in Windows 10).
The Clipboard COPYNAMES command has a new wsl argument that copies filenames in WSL (Linux) format, e.g. instead of C:\Test it would copy /mnt/c/test.
The /mnt/ format is also understood by path fields, etc (anywhere aliases work).
Added a new WSL Command mode to the FAYT; this lets you run linux commands (providing WSL is installed under Windows 10) from the FAYT like you can already run DOS commands. By default the activation key is | (vertical bar).
It may be heretical, but as a unix convert to Windows, I would love a DO option to just replace all of the UI "backslashes" with forward slashes... I realize that DO responds the same whether I type / or , it would just be so nice to not have to be reminded with that ugly " \ " each time I type "/"
Using FAYT | to launch a command in WSL, I'm having some problems... Typing: | ps ax works just fine... I get the output that I would expect... But using a Linux shell command that is also an Opus command, I think we've got to have some form of escaping... For example, try | find . and instead of the output of the Linux find . I get the Opus Find panel... If I try to chain a | to another |... ie, find . | grep something I automatically get a File Collections page... Quickly chaining together WSL and Opus Commands is a huge, huge win... so hopefully there is a way to for these to both work well together!
Tested Clipboard COPYNAMES=wsl and haven't been able to break it so far... Works great!
Using /mnt/x/... format paths in path fields so far so good... Works great!
Using CLI DOSPROMPT=wsl is much better than the custom WSL Prompt Here that I rolled myself because it intelligently detects the current folder and whether or not a prompt can be launched there. Works great!
Even though I've done a ton of Linux shell scripting, I'm still not quire sure where to get started with WSL script functions in Opus.
Is there an easy way to pass a set of files back into a lister from the command line?
So a simple case would be:
| find . | grep partOfName | opus
Of course you could do things way more interesting than just grep for partOfName...
So is there an easy way to feed that list back into Opus? (so you would get a lister showing a collection of only the files piped in)
There's not really an easy way currently, that I can think of.
You can run Win32 programs from WSL so I guess potentially you could have a script on the Linux side that took the output from grep and then ran dopusrt /col to feed the names through to an Opus collection.
Ideally there'd be a way to pipe the output stream back to Opus but currently I don't think WSL has that ability. Even then you'd need a script on the Opus side to interpret the data and work out what to do with it.
