Re: Better piped text support
On Fri, May 14, 2004 at 07:26:21PM +0200, Jens Paulus wrote:
> On Fri, May 14, 2004 at 19:04:20 +0900, TAKAHASHI Tamotsu wrote:
> > On Fri, May 14, 2004 at 12:35:13AM +0200, Jens Paulus wrote:
> > > The command $mutt -s <subject> -i - add@ress < textfile.txt
> > > should make mutt open the editor with the piped text in the buffer or
> > > open the compose menu with the content of textfile.txt as first
> > > attachment. If there is a patch for that, please let me know.
> >
> > No patch.
> > "mutt -i /dev/stdin < text.txt" works here (FreeBSD and zsh).
>
> this does not work here with Solaris and csh. This works just like
> piping the text to mutt without the -i option, that means the message is
> sent directly.
I didn't know that mutt allowed piped text.
I only did "echo foo|mutt -s sbj -i /dev/stdin -e 'set editor=true' add@ress"
and post it. Sorry for the wrong post.
If mutt accepts piped text for direct sending, you can't
make mutt accept piped text for also -i/-a option, apparently.
> > If /dev/stdin does not work, you use a wrapper script
> > (cat>tmpfile;mutt -i tmpfile).
>
> This is possible but I think it should work directly.
But this is the only way to do it because mutt already
uses piping for other purpose.
--
tamo