Re: w3mimgdisplay use?
- To: mutt-users@xxxxxxxx
- Subject: Re: w3mimgdisplay use?
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Fri, 9 Nov 2007 17:18:24 -0600
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date:from:to:subject:message-id:references:mime-version:content-type:in-reply-to; q=dns/txt; s=default; bh=pY2pcD3ZCPS96ol3otIy0EDjyL4=; b=IDTBQNgEywr7m3hShf8aDVz+6bP4YcsQoDPtlKjA6R7TFwIZaNNCztCDJQYNIhXPK3dde3IedHzkQASk2PP3AVM8gxdIrM9+vK3ys+l8bGJWTHnQGTecIAPKoiBhqc60679U/5HkghD25G8uaCQ+RnsLGeKWnfGJvJulLba9cbA=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=Ycn0wJGiV+LfJgZFFt3wNmJOLZoy6PpYT6zmR+fKombEY1k4eHaWs4zGvHbf0l2L00EdTDia/GbFCHsPafcfZE5oX5qedR9iA7VtJvIdcDMC8J/sBDixBEHcstT5QB5xCHrY9YdKVM9OUsE9T0+mFd14RduQ/m7etexG2KxXpoI=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:User-Agent;
- In-reply-to: <20071109211613.GE20630@xxxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- References: <20071109211613.GE20630@xxxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.17 (2007-11-08)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday, November 9 at 03:16 PM, quoth Kyle Wheeler:
>And I *believe* the command to display an image looks something like
>this:
>
> echo '0;1;2;3;4;5;6;7;8;9;./test.jpg' | w3mimgdisplay
AHA! I figured it out by dissecting the X-Face patch by Tamo. For
posterity, here's how you do it:
echo -e '2;3;\n0;1;0;0;0;0;0;0;0;0;./test.jpg\n4;\n3; | w3mimgdisplay
Now, I'm not 100% sure WHY it works or what the other commands are in
there for, but it does work.
>P.S. Yes, I know that w3mimgdisplay has to be a persistent process,
>so the echo line up there won't *quite* work... but I'm still stumped
>as to what the correct behavior is.
That's not true: it does not have to be a persistent process. It's
just that w3m uses it as a persistent process to handle scrolling
around without needing to keep fork()/exec()'ing all the time.
This all said, while it's nifty and all, w3m is a nicer *viewer*
because it handles all the scrolling and such.
However... this may be useful for viewing images *inline* (if they're
small enough)... time to play around! :)
~Kyle
- --
You cannot reason a person out of a position he did not reason himself
into in the first place.
-- Jonathan Swift
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFHNOq/BkIOoMqOI14RAlrnAJ9vCxqI6YupAcUp0jDqN/VQS/iu9gCg6lhv
xnR+NH+KUK+ABQFmsaRdrJ0=
=Mqho
-----END PGP SIGNATURE-----