Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] a couple highlights in next
Date: Wed, 25 Mar 2009 09:30:04 -0700	[thread overview]
Message-ID: <1237996976-sup-379@entry> (raw)

Hi all,

Here's a summary of all the fun stuff that's currently merged into the
next branch:

- zsh completion for sup commandline commands, thanks to Ingmar
  Vanhassel. (zsh-completion)

- Undo support for many commands, thanks to Mike Stipicevic.
  (undo-manager)

- You can now remove labels from multiple tagged threads, thanks to
  Nicolas Pouillard, using the syntax -label. (multi-remove-labels)

- Sup works on terminals with transparent backgrounds (and that's fixed
  copy-and-paste for me too!), thanks to Mark Alexander.
  (default-colors)

- Pressing 'b' now lets you roll buffers both forward and backward,
  also thanks to Nicolas Pouillard. (roll-buffers)

- Duplicate messages (including messages you send to a mailing list, and
  then receive a copy of) should now have their labels merged, except
  for unread and inbox labels. So if you automatically label messages
  from mailing lists via the before-add-hook, that should work better
  for you now. (merge-labels)

- Saving message state is now backgrounded, so pressing '$' after
  reading a big thread shouldn't interfere with your life. It still 
  blocks when closing a buffer, though, so I have to make that work.
  (background-save)

- Email canonicalization, also thanks to Nicolas Pouillard. There's been
  a long-standing problem in Sup where names associated with email
  addresses are saved and reused. Unfortunately many automated systems
  like JIRA, evite, blogger, etc. will send you email on behalf of
  someone else, using the same email address but different names. The
  issue was compounded because Sup decided that longer names should
  always replace shorter ones, so receiving some spam claiming to be
  from your address but with a random name would have all sorts of crazy
  effects.
  
  This should now be fixed. The mapping is no longer maintained.
  Addresses are still stored in the index, both for search purposes,
  and for thread-index-mode. (Otherwise thread-index-mode has to reread
  the headers from the message source, which is slow.) Once
  thread-view-mode is opened, the headers must be read from the source
  anyways, so the email address is updated to the correct version.
  
  So, incoming new email should be fine. Sup will store whatever
  name is in the headers, and won't do any canonicalization.

  For older email, you can update the index manually by viewing the
  message in thread-view-mode, and forcing Sup to re-save it, e.g.
  by changing the labels and then changing them back. Marking it as
  read, and then reading it, should do the trick, at least for read
  messages.

  You can also make judicious use of sup-sync to do this for all
  messages in your index.  (dont-canonicalize-email-addresses)
-- 
William <wmorgan-sup at masanjin.net>


                 reply	other threads:[~2009-03-25 16:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1237996976-sup-379@entry \
    --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