From: sup-talk@gurski.org (Michael Gurski)
Subject: [sup-talk] Excluding a certain name and/or email from being auto-added to people.txt?
Date: Mon, 12 Nov 2007 22:29:11 -0500 [thread overview]
Message-ID: <1194923879-sup-1418@ln> (raw)
In-Reply-To: <1194918770-sup-9170@bdawg>
Excerpts from Brendan O'Connor's message of Mon Nov 12 20:56:22 -0500 2007:
> I feel lame for asking a question without a patch fixing it and adding 5 new
> features :) but was wondering: is there a way to exclude a particular email
> address from having names being added to it? i have emails from a bug tracking
> system (JIRA) that puts various person names but always with the same email
> address <issues at bla.com> which ends up getting saved in ~/.sup/people.txt and
> then sup displays all emails from issues at bla.com based on the people.txt name
> instead of the individual names on the emails. I think being able to say
> "never auto-save for emails matching a certain regex" is the right solution but
> not sure...
I'd have to agree. Certain sites like linkedin.com, as well as some
web-to-mailinglist gateways (notably the ruby on rails list) do the
same thing. Worse, the gateways periodically get spam that isn't
trapped anywhere, and so now all mail from that address shows up as
being from <reallylongspamtext> <reallylongspamtext>. Since sup's the
only client I've used that caches the name fields, this is the first
I've run into this particular problem...
--
Michael A. Gurski (opt. [first].)[last]@pobox.com http://www.pobox.com/~[last]
1024R/39B5BADD PGP: 34 93 A9 94 B1 59 48 B7 17 57 1E 4E 62 56 45 70
1024D/1166213E GPG: 628F 37A4 62AF 1475 45DB AD81 ADC9 E606 1166 213E
4096R/C0B4F04B GPG: 5B3E 75D7 43CF CF34 4042 7788 1DCE B5EE C0B4 F04B
Views expressed by the host do not reflect the staff, management or sponsors.
next prev parent reply other threads:[~2007-11-13 3:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 1:56 Brendan O'Connor
2007-11-13 3:29 ` Michael Gurski [this message]
2007-11-14 7:04 ` 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=1194923879-sup-1418@ln \
--to=sup-talk@gurski.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