Re: [wmii] Enviroment

Georg Göri wrote:
> Kris Maglione schrieb:
>>
>> You'll have to be more specific. What happens to bash? What else has
>> problems?
>>
> I think its a bash problem, I am using gentoo and I am having bugs
> while emerge runs.
> The error
> "/usr/lib64/portage/bin/filter-bash-environment.py: Argument list too long
> /usr/lib64/portage/bin/ebuild.sh: line 1444: /bin/sed: Argument list too
> long
> /usr/lib64/portage/bin/ebuild.sh: line 1791: /bin/bzip2: Argument list
> too long
> "
> occurs and this error is described in gentoo bug #190128.
>
> I doesn't have this problem when i run emerge without this strange wmii
> enviroment on a normal console(tty).
>> zsh, for some odd reason, unsets all of the fn# variables. If you
>> *must* unset them, add something like this to wi_runcmd:
>>
>> fn `{env | 9 sed -n 's/^fn#([^=]+).*/\1/p'}
>>
> What is the wi_runcmd?? I don't found this on my system.
>
>

wi_runcmd is a shell function.

It replaces run_command, also lots of functions was renamed, wi_menu,
wi_tags

wi_runcmd() {
         if [ "$1" = -t ]; then
             shift
             set -- wihack -tags $(wmiir read /tag/sel/ctl | sed 1q) "$*"
         fi
         eval exec $* &
}

See /usr/local/bin/wmii.rc (plan9)
     /usr/local/bin/wmii.sh (sh)

I use wmii-hg2294

See you!

-- 
Ruben Gonzalez Arnau
GPG key: 0x08AF5CD4 http://www.websbarcelona.com/ruben/0x08AF5CD4.asc