Brad hat gesagt: // Brad wrote:
> i think the original proposal was that /etc/environment would only contain
> name=value pairs. Each shell would parse this file (via a script in
> /etc/profile or whatever default) to insert all those pairs into the
> shell's environment. This way, /etc/environment would work with any shell
> instead of just bash.
There is this in Xsession:
# If /etc/environment is present, source it. It's useful to put default
# environment settings in this file, and then source it both here and in
if [ -f /etc/environment ]; then
But if you just put:
in /etc/environment $PAGER gets set, but not "export"ed (or "setenv"ed).
The result is useless, unless you do a "export PAGER" again in /etc/profile or
I would like to have those settings in one file and /etc/environment
seems a natural place. Maybe a wrapper for the shell would be a
solution. The wrapper should scan /etc/environment for NAME=value pairs
and then it should do an "for NAME in $FOUND_NAMES; do export NAME;done"
or the eqivalent with "setenv".
Just "source"ing /etc/environment does not work, or does it?
Frank Barknecht ____ ______ ____ __ trip\ \ / /wire ______
/ __// __ /__/ __// // __ \ \/ / __ \\ ___\
/ / / ____/ / / / // ____// /\ \\ ___\\____ \
/_/ /_____/ /_/ /_//_____// / \ \\_____\\_____\