--xHFwDpU9dbj6ez1V
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Rocco Rutte <[EMAIL PROTECTED]>, 2002-06-07 23:49 -0400:
> Hi,
>=20
> * Andre Berger [02-06-08 04:45:05 +0200] wrote:
> > How can I view inline images like
>=20
> > --begin example--
>=20
> > begin 666 car30001.jpg
> > M_]C_X `02D9)1@`!`0```0`!``#_X2'317AI9@``24DJ``@````(``\!`@`6
> > [snip]
> > ;<17D$:2OL,:D@G/\ZZ>!BR\G-,*U&5'=3DW/_9
> > `
> > end
>=20
> > --end example--
>=20
> > in mutt-nntp (Orjan's patch)? I tried to pipe the message
> > to xv and the like but it seems those image viewers don't
> > recognoze the STDIN.  Probably my setup...
>=20
> Ever tried uudecode(1)? You can just pipe the article
> through it and should get the files. Maybe you want to
> use a short shell script as a wrapper which also sets=20
> the download directory for your ware^H^H^Hfiles.
>=20
> If you clean the directory up afterwards, you can use=20
> the output of ls to call your image viewer.
>=20
> It could look similar to:
>=20
>   #!/bin/sh
>   dir=3D"$HOME/tmp/downloads/warez"
>   cd $dir
>   uudecode -c && xv `ls $dir/*.jpg`
>=20
> HTH,
> Cheers, Rocco

It did. Though my uudecode doesn't support the -c flag. So my
solution is:

macro pager \cV "<decode-copy>/tmp/nntp.temp<enter>y<shell-escape>uudeview =
-i -b -p /tmp/ -d /tmp/nntp.temp && gqview /tmp/ && rm /tmp/nntp.temp\n" "B=
ilder ansehen (Inline)"

which makes a decoded copy /tmp/nntp.temp,
calls uudeview (which decodes everything it can w/o asking into /tmp/),
calls gqview (an image viewer) on /tmp/ so that I can see/save/whatever
images in /tmp,
and finally removes the decoded msg /tmp/nntp.temp

Thank you very much

-Andre

--xHFwDpU9dbj6ez1V
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9AaWGWkhBtALlJZ0RAtP/AKC5tJJ02Hoiao5xOsQGn26OIlyPfwCeJ/Em
dLbc8xyr3KrshHOY2c5U7rw=
=QTht
-----END PGP SIGNATURE-----

--xHFwDpU9dbj6ez1V--

Reply via email to