No redirects are processed correctly in shell-to-batch conversion.

[rburkey2005]

When converting a shell script to a batch file, no redirect is processed correctly. For example, my shell script contains the redirects

...command1... &> /dev/null
...command2... > module.v
...command3... < module.v

As I understand it, these should be converted in the batch file to

...command1... > NUL 2>&1
...command2... > module.v
...command3... < module.v

Instead, they are converted to

...command1...
REM UNKNOWN: {"type":"Redirect","op":{"text":">","type":"great"},"file":{"text":"/dev/null","type":"Word"}}
...command2... REM UNKNOWN: {"type":"Redirect","op":{"text":">","type":"great"},"file":{"text":"module.v","type":"Word"}}
...command3... REM UNKNOWN: {"type":"Redirect","op":{"text":"<","type":"less"},"file":{"text":"module.v","type":"Word"}}

I have tried this both with and without a space between the redirection operator and the file to/from which redirection is supposed to occur. This happens on Linux Mint 21.3.

For what it's worth, my original shell script is attached, though renamed with a .txt extension, since attachments with the extension .sh are not allowed by the issue-tracker: simulateModuleII.txt

[rburkey2005]

Workarounds can be applied that considerably simplify the manual rework on a batch file generated from a shell script that uses such redirects. Perhaps the workarounds could be built into the converter even if the redirects themselves cannot be handled properly.

Prior to conversion of the shell script to a batch file, the following substitutions are made:

• ">>" is replaced by "_PGG_ " (notice the trailing space)
• "&>" is replaced by "_PAG_ "
• "2>&1" is replaced by "_P2GA1_ "
• "<" is replaced by "_PL_ "
• ">" is replaced by "_PG_ "
• "/dev/null" is replaced by "NUL"

After conversion to a batch file, the following substitutions are made in the batch file:

• "_PGG_" is replaced by ">>"
• "_PAG_" is left as-is to be dealt with by the coder, or perhaps replaced by "2>&1 >".
• "_P2GA1_" is replaced by "2>&1".
• "_PL_" is replaced by "<"
• "_PG_" is replaced by ">"
• "NUL" is left as-is, because it's already correct. (If surrounded by quotes, perhaps the quotes need to be removed.)

I'm sure that there are plenty of other special cases that could be handled, but these should cover the vast bulk of cases encountered in actual practice.

[daniel-sc]

@rburkey2005 would you like to give it a try and make a PR?

[rburkey2005]

@daniel-sc I'm not sure what you're asking. If you're asking whether I'd like to actually do the work myself to implement it, alas no. The backlog on my own project is so big that lending a hand on other projects isn't in the cards, I'm afraid.