From: Jay Mendoza <jayzer@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: [sup-talk] phantom unread messages & address book autocomplete
Date: Tue, 15 Dec 2009 18:24:01 -0600 [thread overview]
Message-ID: <1260922380-sup-33@orion> (raw)
I've been using sup for a few weeks now and just have a couple of
questions.
I seem to run into an issue of having at least one elusive unread
message from time to time. It appears in Unread, Inbox, Attachments, and
Killed, but no amount of $ or @ seems to remedy the situation. Searching
for is:unread turns up nothing, and none of the labels with which the
message is marked will display anything, either. Is there a better way
to track this down? I'm using sup 0.9.1/xapian.
Is there a trick to getting autocomplete to work for email addresses in
the To: field? I've only ever seen it work on two addresses (and one was
my own), and even then, not very consistently. It almost seems like I've
had to have use the address once before during the session for it to
work properly. Maybe this is the desired behavior, but I feel like I'm
missing something here.
--
Jay
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next reply other threads:[~2009-12-16 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 0:24 Jay Mendoza [this message]
2009-12-16 0:35 ` Edward Z. Yang
2009-12-16 5:43 ` Jay Mendoza
2009-12-19 18:44 ` 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=1260922380-sup-33@orion \
--to=jayzer@gmail.com \
--cc=sup-talk@rubyforge.org \
/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