Re: Attachments with command line invocation?

guenther <[email protected]>
Newsgroups gmane.comp.gnome.ximian.user
Message-ID <1104511752.9946.26.camel@delta>
On Thu, 2004-12-30 at 15:41 -0500, Ken Mandelberg wrote:
> I've tried both of
> 
>  evolution "mailto:?to=km&attachment=/etc/hosts"
>  evolution "mailto:?to=km&attachment=%2Fetc%2Fhosts"
> 
> on evolution 1.4.6, and nothing gets attached. I just get a compose
> window with the To: header filled in.
> 
> What am I missing?

Sorry, I haven't noticed you are still running Evo 1.4...

I'm not sure on that version, cause I haven't used it for about a year
or so. Anyway, according to my archive this should work with even older
versions and the "attach" string, rather than "attachment". Try

  evolution "mailto:foo@bar?attach=/path/to/attach"

(copy'n'paste from the archive) or with "to" explicitly set

  evolution "mailto:?to=foo@bar&attach=/path/to/attach"

Does this work?

...guenther


> On Tue, 2004-12-28 at 11:10, guenther wrote:
> > > Is it possible to invoke evolution in composition mode with
> > > attachments supplied from the command line? I noticed that I can
> > > invoke it with a "mailto:" url and supply header info and body, but
> > > not attachments.
> > 
> > Yes, this is possible.
> > 
> > $ evolution "mailto:?to=address&cc=address&attachment=/path/to/file"
> > 
> > Both 'attach' as well as 'attachment' do work. Be sure to url-encode the
> > string and use quotes to properly escape the & char.
> > 
> > Evolution should use the same method as Mozilla, AFAIK.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}

_______________________________________________
Users maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.