custom shell not updated in UI

[seatrout]

When a custom shell is set up for a command (in this instance WSL on a windows machine) the main UI screen still shows the default shell — see screenshot.

[Taitava]

Thank you for your report! Good catch! 😎

I was able to reproduce this bug. I'll try to fix it in 0.20.1.

Just for the record, as you probably already noticed, even though a wrong shell is shown in the settings view, executing the shell command does use the correct shell. I'm just mentioning this in case there are other people reading this. 🙂

[seatrout]

Yes. It does matter most that the right shell is executed!

While we are at it, though, I just noticed an extra buglet: in the section underneath the window where the command is entered, the results of escaping it are displayed. And here, too, the display is not changed to reflect the (linux) shell actually in use. The special characters are still escaped with backticks, as for Windows and not \ as they should be.

[Taitava]

So, if I understood correctly, you refer to the command preview text showing incorrect escape characters (backticks instead of backslashes)? Just like in the screenshot you posted in the first post?

The command preview (and escaping characters) are actually created by a function that also produces the shell name below the preview command, so fixing the shell name should also fix the escape characters. I just need to call the function again in a situation when the shell is changed. 👍

[seatrout]

Thanks. Yes. that will clear it up.

[Taitava]

A fixed version 0.20.1 is now released

@seatrout can you test the new release, please? 🙂 If you still encouter any problems, please let me know. 👍

[seatrout]

Thank you. I will do so. In the meantime, my workaround has been to wrap complex sequences into a little PowerShell script and then run that from shell commands. All the quoting problems disappear!