Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: "E. Cartan" <eliecartan@mailworks.org>
To: sup-talk@rubyforge.org
Subject: Re: [sup-talk] index view options, use addressee instead of sender
Date: Mon, 15 Mar 2010 03:02:39 -0500	[thread overview]
Message-ID: <20100315080239.GA3905@katowice> (raw)
In-Reply-To: <20100312213707.GB3800@katowice>

Excerpts from E. Cartan's message of Fri Mar 12 2010 19:23:10 -0500 2010:
On Fri, Mar 12, 2010 at 03:37:07PM -0600, E. Cartan wrote:
 | Excerpts from Ben Walton's message of Mon Mar 01 07:38:45 -0500 2010:
 |  | Excerpts from E. Cartan's message of Mon Mar 01 19:23:10 -0500 2010:
 |  | 
 |  | >   I would like to see the messages which one sends displayed 
 |  | >   on the sup index by "addressee", instead of by "sender" 
 |  | >   (or sender replaced by "me").  Not all messages, but 
 |  | >   just the one sent by me.
 |  | 
 |  | I think there is a patch to do just this that is likely to be 
 |  | included in the next release of sup (or available now if you 
 |  | track the git  repo).  
 | 
 |    Finally yesterday I did get sup 0.11, only to realize that 
 |    I don't know how to configure the index view to display the 
 |    addressees on certain messages, nor how to modify the index
 |    view in any other way.  

   
    Actually I have just discovered today that sup 0.11 index 
    seems to do the above BY DEFAULT.  I mean, it displays 
    the addressee/recipient (between parentheses), instead 
    of the sender "(me)", in the case of of messages 
    sent by oneself.

    I am sorry for having being so confused to have asked above
    how to obtain what appears to be the default behaviour 
    of the new version of sup.  My false assumption that 
    a configuration change, or a hook were needed,
    was based on the fact that the first time I ran sup 0.11, 
    the index continued to be displayed as in older versions, 
    However today, when I started it a second time, I noticed 
    that it complained about not having ncursesw installed. 
    Having the wide character ncurses library solved my problem.

    Regards,
    Elie Cartan
   
    
    
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


      parent reply	other threads:[~2010-03-15  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-02  0:23 [sup-talk] index options, by addressee instead of by sender E. Cartan
2010-03-02  0:38 ` Ben Walton
2010-03-02  1:02   ` Rich Lane
2010-03-12 21:37   ` E. Cartan
2010-03-13  7:31     ` Michael Stapelberg
2010-03-15  8:02     ` E. Cartan [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=20100315080239.GA3905@katowice \
    --to=eliecartan@mailworks.org \
    --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