From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Logic error found in mailcap.el (was: Unable to change mailcap entry.)
Date: 24 Apr 2000 02:27:51 -0400 [thread overview]
Message-ID: <2nd7ngxbbs.fsf@tiger.jia.vnet> (raw)
In-Reply-To: Lloyd Zusman's message of "24 Apr 2000 01:37:26 -0400"
>>>>> "Lloyd" == Lloyd Zusman <ljz@asfast.com> writes:
Lloyd> My guess is that the solution should be either that ...
Lloyd> ... one or more of the `(nreverse passed)' calls should be
Lloyd> removed from within the `mailcap-mime-info' function in
Lloyd> `mailcap.el'
Lloyd> ... or that one or more of the `(car passed)' calls should be
Lloyd> `(car (last passed))' in this `mailcap-mime-info' function
Lloyd> ... or that the final line of the `mailcap-add-mailcap-entry'
Lloyd> in this same file should be changed to read:
Lloyd> (setcdr old-major (cons (cdr old-major) (cons minor info)))))))))
Lloyd> ... or perhaps something else along these same lines which would cause
Lloyd> newly added entries to not be skipped
Lloyd> Thoughts?
Another problem is that Gnus builtin mailcap overrides ~/.mailcap and
others. I don't think this is right.
My suggestion is removing the nreverse calls, parsing mailcap file
backwards, and adjusting the file order in mailcap-parse-mailcaps.
BTW, the default mailcap file order for ms-windows is reversed.
--
Shenghuo
next prev parent reply other threads:[~2000-04-24 6:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-24 1:33 Unable to change mailcap entry Lloyd Zusman
2000-04-24 5:37 ` Logic error found in mailcap.el (was: Unable to change mailcap entry.) Lloyd Zusman
2000-04-24 6:27 ` Shenghuo ZHU [this message]
2000-04-24 14:36 ` Lars Magne Ingebrigtsen
2000-04-24 19:47 ` Shenghuo ZHU
2000-04-24 20:04 ` Lloyd Zusman
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=2nd7ngxbbs.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/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).