From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] skip_killed not getting set in default config
Date: Mon, 19 May 2008 21:42:57 -0700 [thread overview]
Message-ID: <1211258383-sup-445@south> (raw)
In-Reply-To: <1209555731-sup-8618@black-opal>
Reformatted excerpts from Kevin Riggle's message of 2008-04-30:
> I've just started using Sup, and I quite like it. It's always
> wonderful to discover that someone else has developed *exactly the
> software you wanted*, and done such a bang-up job of it. Thank you!
Thanks! Welcome aboard.
> I have, however, run into a few bugs. At the moment, the most notable
> one is that killed threads would show up in my inbox again, +killed
> label and all, which sort of defeats the purpose of killing them.
Yes, this has been working intermittently and I haven't gotten a chance
to look at the current breakage.
> I poked around in the source and discovered the skip_killed option,
> which inbox-mode seems to initialize to true. When I added
>
> :skip_killed: true
>
> to the end of my ~/.sup/config.yaml, which had previously been exactly
> as sup-config created it, the killed threads no longer showed up in my
> inbox.
That shouldn't have made a difference. There is a :skip_killed option in
the code, but it's not related to the configuration file. If you grep
for $config you'll see how the config file is used.
(The :skip_killed: internal flag is there only so it can be be turned
off when you're explicitly searching for killed messages.)
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-05-20 4:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 12:14 Kevin Riggle
2008-05-20 4:42 ` William Morgan [this message]
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=1211258383-sup-445@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