"66-getenv" yields strange results.

I set a variable in ~/.profile
CVSEDITOR='emacs -nw'

"printenv" yields correctly: CVSEDITOR=emacs -nw

but the output of "66-getenv -x jwm" yields two lines:
CVSEDITOR=emacs
-nw

Piping to "sort" will muddle up everything, or piping to
"grep CVSEDITOR" will show an incorrect value of CVSEDITOR

This happens with all values of variables which contain blanks.


Some strange things on https://web.obarun.org/software/66-tools/v0.0.7.1/66-getenv.html

\n cannot be the default delimiter, because
"66-getenv -d \n -x jwm"
yields another output than just
"66-getenv -x jwm"
which cannot happen if I state a default value explicitly.


I suppose that the example
66-getenv "ck-launch-session" jwm
at the bottom is syntactically incorrect since it hat two arguments
contrary to one mentioned in the specification.


Finally:
sudo cat /proc//environ
cat: /proc//environ: No such file or directory
Sorry, for my late answer

So, yeah something wrong here. I need to check it and see what happens. The 66-getenv do not understand for now a variable with a space in it.
sudo cat /proc//environ
cat: /proc//environ: No such file or directory
The md file is correct, a bug exist at the translation process to html and manpage format. I will fix too.
2 months later

Powered by Obarun