On Mon, Dec 12, 2011 at 11:27:50PM +0100, Dominique Michel wrote:
> Le Mon, 12 Dec 2011 18:19:55 +,
> Thomas Adam a écrit :
>
> > On Mon, Dec 12, 2011 at 05:39:38PM +, Thomas Adam wrote:
> > > On Mon, Dec 12, 2011 at 06:32:03PM +0100, Dominique Michel wrote:
> > > > I can list the current
Le Mon, 12 Dec 2011 18:19:55 +,
Thomas Adam a écrit :
> On Mon, Dec 12, 2011 at 05:39:38PM +, Thomas Adam wrote:
> > On Mon, Dec 12, 2011 at 06:32:03PM +0100, Dominique Michel wrote:
> > > I can list the current values of all environment variables with
> > > the command env. Will it be po
On Mon, Dec 12, 2011 at 05:39:38PM +, Thomas Adam wrote:
> On Mon, Dec 12, 2011 at 06:32:03PM +0100, Dominique Michel wrote:
> > I can list the current values of all environment variables with the
> > command env. Will it be possible to do something similar?
>
> No, but I can easily add it.
D
On Mon, Dec 12, 2011 at 06:32:03PM +0100, Dominique Michel wrote:
> I can list the current values of all environment variables with the
> command env. Will it be possible to do something similar?
No, but I can easily add it.
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in m
Le Mon, 12 Dec 2011 11:02:00 +,
Thomas Adam a écrit :
> But people are forever asking me *why*, and it's because shoving
> information in the environment is global to processes created from
> FVWM within the same process group. Hence, that information is both
> publicly viewable and potentia
Hello,
So I've recently been doing a bunch of FVWM things off-list with a few
people who've asked for my help, and in doing so I've finally scratched an
itch which I've long-since been bemoaning but not really suggested a better
alternative for, until now...
I don't like SetEnv -- or rather, I do
