Mail Archives: djgpp-workers/2000/10/27/19:24:15
At 10:47 AM 10/27/00 +0200, Hans-Bernhard Broeker wrote:
<Snipped>
>Actually, I think it's the other way round. For '#' _not_ to be
comment
>start, Bash has to be running in interactive mode, and the
option >allowing comments for interactive shells must be off (It's on
by >default, IIRC).
Opps. You're right, I misread that. Dyslexic of me...:)
>I.e. the only case in which I can see the original testcase behave
like
>the apparent expectation of the test script would be if Perl not only
>invoked the shell interactively, but also turned of that shell
option,
>deliberately.
>
>Either that, or the bug really is in Perl. Like, some command-line
>preprocessing that's supposed to be done, is not. Automatic quotation
>of 'echo' strings beginning with a '#' or whatever might be it.
>Without a Perl guru at hand, I have no idea what the right answer to
>that might be.
Nor I. But I'll try a simple test case in both environments (DJGPP and
Linux) and see if I can produce some more info.
<Snipped>
>Non-interactive shells will always treat # as a comment
character. >There's not even option to switch off that behaviour.
>
>If there's an error regarding interactivity status, it would have to
be >in the opposite direction.
Understood. And thank you very much for clarifying the issue.
---------------------------------------------------------
Peter J. Farley III (pjfarley AT dorsai DOT org OR
pjfarley AT banet DOT net)
- Raw text -