You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was testing yash vs ./shell from a restored version of my CS account, and this is what I got:
(begins with running yash)
eric@omnix ~/programs/homedir/etheller/cs252/lab3/lab3-src
$ grep "wildcard" *.cc
grep: *.cc: No such file or directory
eric@omnix ~/programs/homedir/etheller/cs252/lab3/lab3-src
$ ./shell
# eric at omnix in /home/eric/programs/homedir/etheller/cs252/lab3/lab3-src
$ grep "wildcard" *.cc
command.cc: * Takes a pointer to a directory, and a wildcard-containing
command.cc: //printf("\"%s\" has a wildcard!\n", arg)
As we see above, YaSh failed to do wildcard expansion where ./shell succeeded. However, the expansion appeared to work for the 1st argument in other tests.
The text was updated successfully, but these errors were encountered:
@Retera the underlying issue here is the fact that yash currently cannot handle wildcards with a quote near them.
echo * works, echo ~/* * works, but, unfortunately, echo "${HOME}"/* * will not. There's some issue with the grammar here. Maybe you want to take a look?
I was testing yash vs ./shell from a restored version of my CS account, and this is what I got:
(begins with running yash)
As we see above, YaSh failed to do wildcard expansion where ./shell succeeded. However, the expansion appeared to work for the 1st argument in other tests.
The text was updated successfully, but these errors were encountered: