I'm jwgc-beta4 on FreeBSD. I find that jwgc does not seem to
properly receive "composing" messages from other Jabber clients,
nor does it seem to send them when I use jwrite.
I tried editing my jwgc.desc to add a print statement to the $event
== "composing" && $body == "" test, but this appears never to be
triggered, even if I remove the $body == "" above it. I verified
with tcpdump that the composing messages are being received
(using Fire as the client on the other end), but jwgc doesn't seem
to actually do anything with them.
I also expected jwrite to send a composing message when not
using the -n option, but it did not. It should do this when you start
to write a message. The Zephyr zwrite command does something
similar (sends a PING opcode), and both allows other users to
know you're about to send them a message (something Jabber has
built-in), but also allows zwrite to fail immediately if the user is
not logged in. With the current jwrite behavior, you won't know
until after you've sent the message, which can be annoying.
I think jwrite should send each recipient a composing event when
you first start to type, unless the -n option is passed. This would
match the behavior of zwrite, and what I think most people would
Log in to post a comment.