* Peter Vereshagin <pe...@vereshagin.org> [12-03-12 10:33]:
> 2012/12/03 09:28:17 -0500 Patrick Shanahan <p...@opensuse.org> => To 
> tmux-users@lists.sourceforge.net :
> PS> > TA> [Adding back tmux-users@ to Cc list.  Please don't cull it next 
> time.]
> PS> > 
> PS> > thought I did. No X-Mailing-List comes here so mutt's 'list-reply' 
> doesn't
> PS> > work.
> PS> > 
> PS> 
> PS> odd, it works for me and I don't even have tmux listed as "subscribe" or
> PS> "list".  mutt-1.5.21 on openSUSE Tumbleweed
> 
> Then it was Cc'ed to me and the X-Mailing-List wasn't added by the sender.

>From my history of this list it appears Mr. Adams posts *directly* to the
OP and cc's the list, usually.  I do not understand that approach as
pervious experience indicates list postings "should go to the list" unless
the OP specifically requests to be cc'd.
 
> PS> nor do I see the necessity to cc: list posts unless an individual
> PS> requests an *additional* copy ???
> 
> Depends.

His cc problem is his configuration of mutt.  He can make cc'ing
automatical even if the cc: header is removed/stripped.  And if he uses
"group-reply", normally bound to 'g' in mutt, existance of the header
would not affect his manner of posting and would not require changing his
.muttrc.  The post would be to the poster and cc the list as he presently
appears to prefer.

-- 
(paka)Patrick Shanahan       Plainfield, Indiana, USA      HOG # US1244711
http://wahoo.no-ip.org        Photo Album: http://wahoo.no-ip.org/gallery2
http://en.opensuse.org                           openSUSE Community Member
Registered Linux User #207535                    @ http://linuxcounter.net

------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
BUILD Helping you discover the best ways to construct your parallel projects.
http://goparallel.sourceforge.net
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users

Reply via email to