From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Wiki updates, more people on #sup
Date: Sat, 05 Apr 2008 17:04:34 -0700 [thread overview]
Message-ID: <1207440240-sup-2556@south> (raw)
In-Reply-To: <18635-64358@sneakemail.com>
Reformatted excerpts from Guarded Identity's message of 2008-03-28:
> One thing to note about these configurations are that I'm relying on
> other tools to solve problems rather than asking William to "improve"
> Sup.
That's what makes you a good user. :)
> However, regarding [2], I guess I wish that contact tab-complete could
> be customizable (say to hook into ldbdq).
I've just added an extra-contact-addresses hook. Try parsing some lbdbq
output in that.
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-04-06 0:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 15:54 Guarded Identity
2008-04-06 0:04 ` William Morgan [this message]
2008-04-07 17:19 ` Grant Hollingworth
2008-04-07 18:00 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1207440240-sup-2556@south \
--to=wmorgan-sup@masanjin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox