Replies: 1 comment 2 replies
-
hi! I'm going to answer generally because I feel the pressure of posix shells users expectations. The xonsh shell is young and developed by the volunteers without strong release cycles. Current behavior of parser, threading and the logic of how it's working together were constructed for cover pretty minimal needs. So we can't say that the logic is weird we can say that the logic is on the beginner level. To push the improvement forward:
(I see that my messages has "Maintainer" label but the "maintainer" is the team during a couple of years. Don't treat my comment as a comment from owner.) |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was basically trying to do the same as lieryan here but with different constructs, and ran across some counter-intuitive behavior. I'm hoping someone here could clarify what's going on...
cd subdir &&
complain inside parens whencd subdir;
doesn't? What's different between the handling of;
and&&
? I expected both to commence thels
insidesubdir
and then restore cwd.cd subdir &&
complaining about, when in fact it's successfully changing the cwd?$()
not interpret;
as command-separators? Is the inside of$()
not "full-fledged" subprocess mode somehow? What exactly is the difference, and why is there such a difference? Is it useful for something? I expected$(cd subdir; ls)
to simply behave as ifcd subdir; ls
were typed at the top level (i.e. runscd subdir
thenls
), except that it returns the output as a string.;
-interpretation? I expected the only difference between$(())
and$()
to be whether a subshell is started.Beta Was this translation helpful? Give feedback.
All reactions