Mail Archives: djgpp/1997/04/10/13:09:09
On Tue, 8 Apr 1997, Dave Pearson wrote:
> BTW Eli, I know you've given warnings about hacking the DJGPP.ENV file
> before but I also think that that file is one of the great features of
> the whole DJGPP "environment". Having the avility to specify environment
> variables on a pre-exe bases makes it so flexible.
If you have read the docs which explains the syntax of that file and
feel that you know enough to go and change it, you are free to do so.
The point is that changing that file should be the last resort,
because its defaults are well-thought and changing them without
understanding enough about how the DJGPP programs work together may
break too many things.
As you might already know, Microsoft platforms don't make running Unix
tools an easy job. A lot of people who participated in DJGPP
development put a lot of efforts into making DJGPP ports work together
in harmony, by figuring out many gory details and setting things up in
a way that those details are transparently taken care of.
Unfortunately, some people take this seamless operation for granted,
change the defaults and then come back crying that things don't work.
You can guess who is then called upon to make things work for them (or
to be cursed, as the case may be).
> > If this makes trouble, I can suggest ways to work around them.
>
> Yeah, I'd love to hear any suggestions. I guess re-binding C-z to run
> 'bash -logon' would be one way to go?
Set SUSPEND=c:/bin/bash -login. This variable, if set, overrides
$SHELL, but only for `M-x suspend-emacs'; `M-x compile' will still use
$SHELL. You can then either unset SHELL or set it to just `bash' with
no -login.
Another possibility is to set the DJSYSFLAGS environment variable; it
is described in the library reference, under `system'. But I think
the $SUSPEND feature is better.
- Raw text -