Custom Query (116 matches)
Results (52 - 54 of 116)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #147 | jgross@mit.edu | andersk@mit.edu | fixed | colorztext should force recomputation of message fmttext |
| Description |
Currently the colorztext option strips colors from the message when it is received, so changing it after the fact doesn’t do what you expect. |
|||
| #148 | jesstess@mit.edu | duplicate | misleading text for sender on zwrite to multiple people without -C | |
| Description |
If I 'zwrite leonidg ternus', I see -> Zephyr sent to leonidg 12:56 (Jessica)
Test
even though both leonidg and ternus received the zephyr. The text implies that only leonidg received it. Tested using whatever barnowl is on dr-wily: dr-wily:~> which barnowl /mit/barnowl/arch/i386_deb50/bin/barnowl |
|||
| #161 | kevinr@mit.edu | fixed | commands in startup which request input fail oddly | |
| Description |
If I put, at the end of my ~/.owl/startup, a command which requests user input, eg. jabberlogin kevinr@free-dissociation.com (which doesn't do Kerberos authentication; it asks for a password), when I run BarnOwl, it appears to work (or at least doesn't error visibly). I don't see the "you're now logged into kevinr@free-dissociation.com/owl" message, though, so I get suspicious and run it again by hand. This results in the error: [Error] Error in connect: error not-authorized That's odd, it never even asked for my password! So in a fit of insanity (technical definition) I run it again, and *this* time it asks me for my password and lets me log into Jabber successfully. It used to be that including that line at the end of my startup file would cause the password prompt to appear and accept input when I started BarnOwl. We should either return to that behavior or completely prohibit input-requesting commands in the startup file. |
|||
