[406] in BarnOwl Developers
Re: Experience using owl as my primary jabber client
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Oct 29 18:05:48 2009
Resent-From: nelhage@mit.edu
Resent-To: barnowl-dev-mtg@charon.mit.edu
From: Sam Hartman <hartmans@MIT.EDU>
To: jesse <jesse@fsck.com>
Cc: dirty-owl-hackers@mit.edu
Date: Sun, 21 Jan 2007 17:28:41 -0500
In-Reply-To: <20070121220709.GQ2945@bestpractical.com> (jesse@fsck.com's
message of "Sun, 21 Jan 2007 17:07:10 -0500")
>>>>> "jesse" == jesse <jesse@fsck.com> writes:
jesse> On Sun, Jan 21, 2007 at 05:04:56PM -0500, Sam Hartman
jesse> wrote:
>> 2) The lack of short name support is really frustrating as is
>> the fact that you have to specify -a on jwrite if you are
>> logged into multiple accounts. I think it's far more important
>> to propose to send a message (telling the user in the prompt
>> which jid we've heuristically selected) than to require -a.
jesse> Would tab completion of jwrite addresses be a good thing
jesse> here? (I know I want it ;)
Yes, although I'm not sure it is related.
I think what you want to do is:
* see if the argument to jwrite appears as a jid or short name in any logged in roster.
* If it appears as conflicting short names that map to different jids
in different rosters probably at least give a warning.
* replace the shortname with a jid if we found a short name
* Use the account of the first roster we found the jid/short name in
* If the jid (*it cannot be a short name in this case) was in no
roster, then use the account of the first roster.
It's not clear if tab completion should be on jid, short name or both.
