From: Reiner Steib <reinersteib+gmane@imap.cc>
To: <ding@gnus.org>, emacs-devel@gnu.org
Subject: Re: doc-view and mailcap
Date: Wed, 05 Dec 2007 21:02:57 +0100 [thread overview]
Message-ID: <v9y7c8ucy6.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87bq95mp2b.fsf@member.fsf.org> (Tassilo Horn's message of "Wed, 05 Dec 2007 11:08:28 +0100")
[ Adding ding again. Tassilo, please don't strip ding as long as
this thread is closely related to Gnus. Thanks. ]
On Wed, Dec 05 2007, Tassilo Horn wrote:
> Juri Linkov <juri@jurta.org> writes:
>>> PDF, PostScript and DVI files are usually A4 (or letter) paper sized
>>> documents. Displaying them in the article buffer doesn't seem useful
>>> to me. My personal preference would be a new Emacs frame.
>>
>> Large images get attached to the messages already, and Gnus displays
>> them inline just fine.
At least by default it doesn't display them inline, see
`mm-inline-large-images'. I toggled it and tried to view a wide image
(the frame is 80 chars wide). I couldn't figure out how to view the
right hand side part of the image conveniently. The best I could
think of was `scroll-left'. (I used `i image' in the Emacs manual.)
> But the difference is that the images are just there and can be
> displayed immediately whereas pdfs and such have to be converted first.
Good point.
> I don't think it would be good to unconditionally start a conversion run
> if a document is attached with disposition type `inline'.
I don't think any MUA in the wild sends PDFs as disposition=inline (of
course you can do with Gnus).
> And if the user has to type a key first to start the conversion and
> inline the images I cannot see a big benefit.
>
>> I think when the disposition type is `inline' we should try to display
>> it inline in the same article buffer if possible.
>
> I think it wouldn't be hard to add a function to doc-view that inserts
> the images into the current buffer, but we'd loose (or have to
> re-implement) all those nice features like searching or image-scrolling.
I'd suggest to implement viewing in an extra buffer first. I think
it's not worth the trouble to implement inline display in the article
buffer. But if someone wants to do it...
>> Could you also look at the problem of moving mailcap.el and its
>> related files out of Gnus?
Which are the related files? (mailcap.el doesn't require any other
packages after my changes.)
>> It seems an appropriate directory for them is `lisp/mail' or
>> `lisp/net'. Do you see a better directory?
I don't have a strong opinion on this.
[ IIRC, Miles should be back soon, so hopefully the change are synced
within a couple of days. ]
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-12-05 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87bqbhkhc6.fsf@baldur.tsdh.de>
[not found] ` <E1IfLIC-0004SH-4t@fencepost.gnu.org>
[not found] ` <87bqb8rmk2.fsf@jurta.org>
[not found] ` <E1IhEtn-0001rE-AI@fencepost.gnu.org>
[not found] ` <87ejfwgf5k.fsf@jurta.org>
[not found] ` <E1Ihrne-0001NZ-Nl@fencepost.gnu.org>
[not found] ` <m2lka22757.fsf@cam.ac.uk>
[not found] ` <E1Ii14Z-0002OH-9C@fencepost.gnu.org>
[not found] ` <m2tzoqxd1x.fsf@cam.ac.uk>
[not found] ` <E1IiFpq-0003Jp-AC@fencepost.gnu.org>
[not found] ` <v9sl49pfdx.fsf_-_@marauder.physik.uni-ulm.de>
[not found] ` <877ills6b4.fsf@jurta.org>
[not found] ` <v9ve94lvyr.fsf@marauder.physik.uni-ulm.de>
[not found] ` <v9zlx2q6ma.fsf@marauder.physik.uni-ulm.de>
[not found] ` <877ik5b6k4.fsf@member.fsf.org>
[not found] ` <87prxqb79u.fsf@fastmail.fm>
[not found] ` <v9k5ny5h5g.fsf@marauder.physik.uni-ulm.de>
[not found] ` <87ir3gog1j.fsf@jurta.org>
[not found] ` <v9d4to443q.fsf@marauder.physik.uni-ulm.de>
[not found] ` <87tzmzmpst.fsf@jurta.org>
[not found] ` <87sl2ierzl.fsf@member.fsf.org>
2007-12-04 18:22 ` Reiner Steib
2007-12-04 22:45 ` Juri Linkov
[not found] ` <87bq95mp2b.fsf@member.fsf.org>
2007-12-05 20:02 ` Reiner Steib [this message]
2007-12-05 22:45 ` Juri Linkov
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=v9y7c8ucy6.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.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;
as well as URLs for NNTP newsgroup(s).