OORT.jpg

OORT.jpg

[luis fernandes]

[-- Attachment #1: message body text --]
[-- Type: text/plain, Size: 42 bytes --]


Something I doodled...any possible use?


[-- Attachment #2: OORT --]
[-- Type: image/jpeg, Size: 9889 bytes --]

Re: OORT.jpg

[Per Abrahamsen]

luis fernandes <elf@ee.ryerson.ca> writes:

> Something I doodled...any possible use?

Nice concept!  Would look good on a t-shirt... ;-)

Re: OORT.jpg

[Katsumi Yamaoka]

[-- Attachment #1: Type: text/plain, Size: 433 bytes --]

>>>>> In <rjhepnzgkm.fsf@ssv2.dina.kvl.dk>
>>>>>	Per Abrahamsen <abraham@dina.kvl.dk> wrote:

> luis fernandes <elf@ee.ryerson.ca> writes:

> > Something I doodled...any possible use?

> Nice concept!  Would look good on a t-shirt... ;-)

Cool!  It can also be used for splashing the startup screen and
X-Face. :-)  The attached MIME part is message/exeternal-body
which should point to:

  /anonymous@ftp.jpl.org:/pub/tmp/oort.xpm


[-- Attachment #2: oort.xpm --]
[-- Type: message/external-body, Size: 24 bytes --]

[-- Attachment #3: Type: text/plain, Size: 91 bytes --]

By the way, does Oort Gnus support such a MIME part?
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: OORT.jpg

[Russ Allbery]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> Cool!  It can also be used for splashing the startup screen and
> X-Face. :-) The attached MIME part is message/exeternal-body which
> should point to:

>   /anonymous@ftp.jpl.org:/pub/tmp/oort.xpm

> By the way, does Oort Gnus support such a MIME part?

Worked fine for me.  :)

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>

Re: OORT.jpg

[Katsumi Yamaoka]

>>>>> In <yl8zayap23.fsf@windlord.stanford.edu> 
>>>>>	Russ Allbery <rra@stanford.edu> wrote:

> Katsumi Yamaoka <yamaoka@jpl.org> writes:

>> The attached MIME part is message/exeternal-body which

[...]

>> By the way, does Oort Gnus support such a MIME part?

> Worked fine for me.  :)

Oops!  I found my fault in my last article.  The part was
generated by SEMI MIME-Edit and I was foolish enough to add "/"
in the end of the directory name manually as follows:

Content-Type: message/external-body;
	access-type=anon-ftp;
	site="ftp.jpl.org";
	directory="/pub/tmp/";
	name="oort.xpm";
	mode=image

It causes the function `mm-extern-anon-ftp' to access

  "/anonymous@ftp.jpl.org:/pub/tmp//oort.xpm"

and Emacs will interpret it as "/oort.xpm". :-(
I'm sorry to waste the bandwidth.
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: OORT.jpg

[Lars Magne Ingebrigtsen]

luis fernandes <elf@ee.ryerson.ca> writes:

> Something I doodled...any possible use?

Nice!  For the t-shirt, perhaps?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: OORT.jpg

[luis fernandes]

    larsi> Nice!  For the t-shirt, perhaps?

Great minds think alike.

Still tweaking it, though. Expect another version...

Re: OORT.jpg

[Lars Magne Ingebrigtsen]

luis fernandes <elf@ee.ryerson.ca> writes:

> Still tweaking it, though. Expect another version...

Cool.  :-)

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Steinar Bang]

>>>>> luis fernandes <elf@ee.ryerson.ca>:

> Something I doodled...any possible use?

Doing `2 K v' on this article gives the messages
	Viewing with eeyes '%s'
	Displaying eeyes '/tmp/emm.1261299G/OORT.JPG'...
in the minibuffer, and then nothing happens.

My ~/.mailcap contains the line:
image/*; /usr/bin/xzgv %s

But that setting doesn't seem to "take".  What could I be doing wrong? 

All, ideas, hints etc. appreciated!

Thanx!


- Steinar

Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Lars Magne Ingebrigtsen]

Steinar Bang <sb@dod.no> writes:

> Doing `2 K v' on this article gives the messages
> 	Viewing with eeyes '%s'
> 	Displaying eeyes '/tmp/emm.1261299G/OORT.JPG'...
> in the minibuffer, and then nothing happens.

How about `b' -- does that do the same?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Steinar Bang]

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:

> Steinar Bang <sb@dod.no> writes:
>> Doing `2 K v' on this article gives the messages
>> 	Viewing with eeyes '%s'
>> 	Displaying eeyes '/tmp/emm.1261299G/OORT.JPG'...
>> in the minibuffer, and then nothing happens.

> How about `b' -- does that do the same?

Yup, it does.

Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Daniel Pittman]

On Sat, 26 Jan 2002, Steinar Bang wrote:
>>>>>> luis fernandes <elf@ee.ryerson.ca>:
> 
>> Something I doodled...any possible use?
> 
> Doing `2 K v' on this article gives the messages
> 	Viewing with eeyes '%s'
> 	Displaying eeyes '/tmp/emm.1261299G/OORT.JPG'...
> in the minibuffer, and then nothing happens.
> 
> My ~/.mailcap contains the line:
> image/*; /usr/bin/xzgv %s
> 
> But that setting doesn't seem to "take". What could I be doing wrong?
> 
> All, ideas, hints etc. appreciated!

Last time I looked at something like this, Gnus seemed to take the
/last/ setting it found, not the first. Check where eeyes(1) is in your
private and system mailcap files.

NB: I don't see this sort of problem at the moment, so it's only a hint.

        Daniel

-- 
The fundamental delusion of humanity is to suppose
that I am here and you are there.
        -- Yasutani Roshi

Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Kai Großjohann]

Steinar Bang <sb@dod.no> writes:

> My ~/.mailcap contains the line:
> image/*; /usr/bin/xzgv %s
>
> But that setting doesn't seem to "take".  What could I be doing wrong? 

If your .mailcap contains an image/* entry but the system mailcap
contains an image/gif entry, then the system entry will be taken for
image/gif.

I hate this.

Workaround: put image/gif, image/png, ... in .mailcap.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Steinar Bang]

>>>>> grossjoh@lothlorien.cs.uni-dortmund.de (Kai Großjohann):

> Steinar Bang <sb@dod.no> writes:
>> My ~/.mailcap contains the line:
>> 	image/*; /usr/bin/xzgv %s
>> 
>> But that setting doesn't seem to "take".  What could I be doing wrong? 

> If your .mailcap contains an image/* entry but the system mailcap
> contains an image/gif entry, then the system entry will be taken for
> image/gif.

Ah.  /etc/mailcap was full of "image/jpeg", "image/png", etc. using
eeyes (which I btw haven't installed).

> I hate this.

No, the behaviour doesn't seem logical.  Is this behaviour mandated by
the mailcap RFC?  Is it the practice of other programs using the
mailcap file (eg. Netscape)?  Or is it just the MIME library used by
Gnus? 

If it is the latter, perhaps one should file a bug report?

> Workaround: put image/gif, image/png, ... in .mailcap.

I put "image/jpeg; /usr/bin/xzgv %s" in ~/.mailcap, did
`M-x mailcap-parse-mailcaps RET', and then `2 K v' on the article, and
the Oort showed up in xzgv.

Thanx!  :-)

Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Kai Großjohann]

Steinar Bang <sb@dod.no> writes:

> No, the behaviour doesn't seem logical.  Is this behaviour mandated by
> the mailcap RFC?  Is it the practice of other programs using the
> mailcap file (eg. Netscape)?  Or is it just the MIME library used by
> Gnus? 

I raised this issue some years ago, I think (maybe only some months
ago).  But I don't remember what was the decision.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Lars Magne Ingebrigtsen]

grossjoh@lothlorien.cs.uni-dortmund.de (Kai Großjohann) writes:

>> No, the behaviour doesn't seem logical.  Is this behaviour mandated by
>> the mailcap RFC?  Is it the practice of other programs using the
>> mailcap file (eg. Netscape)?  Or is it just the MIME library used by
>> Gnus? 
>
> I raised this issue some years ago, I think (maybe only some months
> ago).  But I don't remember what was the decision.

The idea is that a more specific entry is supposed to override a more
generic entry.  If you specify image/* to be viewed by one thing, and
image/jpeg by another, the latter entry is supposed to override the
former.

However, the mailcap library is supposed to check whether the program
the entries point to is installed.  It doesn't seem to work in this
case, which is a bug.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: K v uses eeyes, even though mailcap uses xzgv

[Norbert Koch]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> The idea is that a more specific entry is supposed to override a more
> generic entry.  If you specify image/* to be viewed by one thing, and
> image/jpeg by another, the latter entry is supposed to override the
> former.

Hmm, I alwasy thought entries in the user's HOME override system
settings.  

norbert.

Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Kai Großjohann]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> The idea is that a more specific entry is supposed to override a more
> generic entry.  If you specify image/* to be viewed by one thing, and
> image/jpeg by another, the latter entry is supposed to override the
> former.

IMVHO, the user putting "image/*; xv %s" in ~/.mailcap clearly
indicates that they want to use xv for all images.

So image/* in the personal file should override the image/foo entries
in the system-wide file.

But of course, the image/foo entry in ~/.mailcap should overrade the
image/* entry there, and similar for the system-wide file.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

Re: K v uses eeyes, even though mailcap uses xzgv (Was: OORT.jpg)

[Steinar Bang]

>>>>> grossjoh@lothlorien.cs.uni-dortmund.de (Kai Großjohann):

> IMVHO, the user putting "image/*; xv %s" in ~/.mailcap clearly
> indicates that they want to use xv for all images.

> So image/* in the personal file should override the image/foo
> entries in the system-wide file.

That's the behaviour I expected.

> But of course, the image/foo entry in ~/.mailcap should overrade the
> image/* entry there, and similar for the system-wide file.

Agreed.

Re: K v uses eeyes, even though mailcap uses xzgv

[Lars Magne Ingebrigtsen]

grossjoh@lothlorien.cs.uni-dortmund.de (Kai Großjohann) writes:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
>> The idea is that a more specific entry is supposed to override a more
>> generic entry.  If you specify image/* to be viewed by one thing, and
>> image/jpeg by another, the latter entry is supposed to override the
>> former.
>
> IMVHO, the user putting "image/*; xv %s" in ~/.mailcap clearly
> indicates that they want to use xv for all images.

That's quite true.

Has this been fixed by now, or does the system-wide image/jpeg still
override the local image/*?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen

Re: K v uses eeyes, even though mailcap uses xzgv

[Kai Großjohann]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Has this been fixed by now, or does the system-wide image/jpeg still
> override the local image/*?

I think it has not been fixed, yet.  But I haven't tried in a while.
-- 
Ambibibentists unite!

Re: K v uses eeyes, even though mailcap uses xzgv

[Lars Magne Ingebrigtsen]

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

>> Has this been fixed by now, or does the system-wide image/jpeg still
>> override the local image/*?
>
> I think it has not been fixed, yet.  But I haven't tried in a while.

Before I go poking in the code, does anybody know whether this
misfeature still is in effect?

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen