From: Rich Lane <rlane@club.cc.cmu.edu>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH 01/10] open mail source files as binary
Date: Fri, 01 Jan 2010 16:48:29 -0500 [thread overview]
Message-ID: <1262382312-sup-2326@zyrg.net> (raw)
In-Reply-To: <1262382164-sup-4751@masanjin.net>
Excerpts from William Morgan's message of Fri Jan 01 16:43:13 -0500 2010:
> Reformatted excerpts from Anthony Martinez's message of 2010-01-01:
> > Especially if you use Maildir for a source, the resulting torrent of
> > warnings makes Sup a bit difficult to use.
> >
> > I've gone and reverted this diff locally for now. I suppose I could
> > also stop running sup with the -w flag...
>
> I'm happy with either wrapping that whole thing in a RUBY_VERSION test,
> or mandating that thou shalt not run sup with -w. Votes?
It doesn't sound very useful to have -w writing messages to the screen
in an ncurses app. Could you redirect stderr to a file instead? Is it
possible to do this from inside Sup?
That warning's existence annoys me. I thought it was a feature that Ruby
1.8 ignored the encoding in the mode string.
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-01-01 21:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 23:36 [sup-devel] Ruby 1.9 encoding fixes Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 01/10] open mail source files as binary Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 02/10] display_size is just size on Ruby 1.9 Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 03/10] add String#check Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 04/10] add String#ascii Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 05/10] fixup Iconv#easy_decode for Ruby 1.9 Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 06/10] add String#transcode Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 07/10] transcode output from mime-decode hook too Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 08/10] decode raw header/message to ascii before viewing Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 09/10] use header from the RMail::Message in Message#parse_header Rich Lane
2009-12-31 23:36 ` [sup-devel] [PATCH 10/10] decode header fields of enclosed messages Rich Lane
2010-01-01 20:59 ` [sup-devel] [PATCH 01/10] open mail source files as binary Anthony Martinez
2010-01-01 21:43 ` William Morgan
2010-01-01 21:48 ` Rich Lane [this message]
2010-01-01 21:57 ` William Morgan
2010-01-02 1:16 ` Anthony Martinez
2010-01-01 19:09 ` [sup-devel] Ruby 1.9 encoding fixes William Morgan
[not found] ` <1262442839-sup-7738@peray>
2010-01-03 14:48 ` William Morgan
2010-01-03 15:48 ` Nicolas Pouillard
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=1262382312-sup-2326@zyrg.net \
--to=rlane@club.cc.cmu.edu \
--cc=sup-devel@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