Closed GoogleCodeExporter closed 9 years ago
I'm not sure if Kris intended the "sh wmiirc" to be runnable under dash. Try
bash.
Original comment by sun...@gmail.com
on 23 Feb 2011 at 7:30
He did.
See for example changeset 2668:a41c27c7d8be.
Original comment by skwi...@googlemail.com
on 23 Feb 2011 at 7:35
Same problem with bash here.
I suppose the reason is that the default code in wmiirc,
local_events | wi_events
will execute `wi_events' in a subshell, and that `wi_events' stores settings in
a shell-scoped space (so they're immediately lost after exiting the subshell).
When replacing the line with
local_events >/tmp/localEvents$$
wi_events < /tmp/localEvents$$
rm -f /tmp/localEvents$$
everything works fine.
In version 3.9.2, this problem did not exist (so I lost all custom key settings
when switching to -hg).
BTW, there's a similar problem with $HOME/.wmii-hg/wmiirc_local: The `status'
function is also called as part of a pipe, and that means that if `status'
needs to preserve information over multiple invocations then this requires
really ugly workarounds (as opposed to simply storing that information in some
shell variable).
Adding a simple "show-average-network-bandwidth-over-last-3-seconds" status
field with that almost drove me nuts...
So it would be really useful if execution of `local_events' and `status' in a
subshell could be avoided somehow.
Original comment by a...@fractal9.net
on 5 Jun 2011 at 3:11
Original comment by sun...@gmail.com
on 19 Sep 2011 at 8:24
local_events is deprecated. wmiirc_local.sh should simply call wi_events itself
since it now supports multiple invocations. That line was an inadequately
tested stopgap compatibility measure.
Original comment by maglion...@gmail.com
on 19 Sep 2011 at 8:30
This issue was closed by revision ec047f6f9b26.
Original comment by maglion...@gmail.com
on 19 Sep 2011 at 8:39
Original issue reported on code.google.com by
skwi...@googlemail.com
on 23 Feb 2011 at 8:37