[4172] in testers
discuss with readline
daemon@ATHENA.MIT.EDU (Camilla R Fox)
Wed Jun 2 23:31:08 1999
Message-Id: <199906030330.XAA07400@x15-cruise-basselope.mit.edu>
To: testers@MIT.EDU
Date: Wed, 02 Jun 1999 23:30:56 -0400
From: Camilla R Fox <cfox@MIT.EDU>
So the 8.3 discuss client has readline stuff added to the ss library
which it uses. I tried to write a configuration file, and it isn't
behaving as I expect.
My .inputrc contains:
set editing-mode vi
$if application == discuss
"show": "print"
$endif
The vi editing mode works as expected, and doesn't seem to affect
anything else.
Without the conditional, the macro doesn't work as expected; anytime an
s is typed, no matter what character follows it, the s as well as the
next few characters gets eaten, and never appear. If I type "show" in
it's entirety, I do however get it's expansion instead.
From the readline man page:
> In the second form, "keyseq":function-name or macro, keyseq
> differs from keyname above in that strings denoting an
> entire key sequence may be specified by placing the sequence
> within double quotes. Some GNU Emacs style key escapes can
> be used, as in the following example.
(people I've asked don't seem to think that this should work, so it's
possible that I am completely confused in my reading of the man page)
My other problem is that the conditional doesn't work; I've tried
several variations, such as "$if discuss" (as per the example in the
man page) and "$if application=discuss". However, in each case it
evaluates to false inside the discuss client. If I add an $else
clause, that gets evaluated instead.
If this sort of thing worked, it would be nice if there were mention of
it in the discuss man page. In it's current state, that seems
unnecessary. It's certainly a low priority, given that it's an added
feature, albeit a very useful one.
