From: marka@pobox.com (Mark Alexander)
Subject: [sup-talk] Configurable SIG_PATTERN?
Date: Tue, 24 Mar 2009 15:21:10 -0700 [thread overview]
Message-ID: <a412e2a70903241521u726dc83ajdb75c967bee2fb44@mail.gmail.com> (raw)
Here's another little feature I'd like to see (and
maybe implement when I get the time):
I get a lot of automated messages from Bugzilla
at work, full of long lines of dashes separating
blocks of text. Sup has been interpreting
these blocks as signatures when they're within
15 (MAX_SIG_DISTANCE) lines from the end of the
message. So I hacked the SIG_PATTERN so that
only the first regexp is used. This is probably
wrong for many users, though.
I was thinking it might be nice to have
both SIG_PATTERN and MAX_SIG_DISTANCE settable
in config.yaml. Does this make sense?
next reply other threads:[~2009-03-24 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 22:21 Mark Alexander [this message]
2009-03-24 23:36 ` John Bent
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=a412e2a70903241521u726dc83ajdb75c967bee2fb44@mail.gmail.com \
--to=marka@pobox.com \
/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