On 05/28/2006 12:29 PM, Larry Evans wrote:
--text follows this line--
================================================================
Dear Bug Team!
The following is my response to Stephen Tumbull's post:
[snip]
> Do you get the same results (bad behavior with compile, and
the
> various values for PATH I've requested above for your usual
> environment) if XEmacs is invoked with "xemacs -vanilla"?
No! With "xemacs -vanilla", in the 'shell command toll', I get
the correct, longer value. Maybe that's the important clue!
I've discovered something else important. The problems I was
reporting did not start from invokation from an xterm. Instead,
they started from an icewm menu item. The code executed when
I pressed this item was:
prog "XEmacs21-nomule" - /bin/sh -c
"/usr/bin/xemacs21-nomule"
OTOH, when:
/usr/bin/xemacs21-nomule
is executed from a terminal, the problem with PATH disappears. I guess
the mention of "-vanilla" as a good clue was just due to me having
to invoke the command from an xterm and it was xterm invokation
which lead to the better results.