Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Michael Sperber <sperber@deinprogramm.de>
Cc: ding@gnus.org
Subject: Re: PATCH: Unbreak `mailcap-mailcap-entry-passes-test'
Date: Tue, 20 Oct 2015 23:25:24 +0900	[thread overview]
Message-ID: <b4mzizdy5uz.fsf@jpl.org> (raw)
In-Reply-To: <y9lmvvdep11.fsf@deinprogramm.de>

Michael Sperber <sperber@deinprogramm.de> wrote:
> Right.  However, many typical mailcap entries will not have a test
> clause.

Yes.  Moreover mailcap-mailcap-entry-passes-test seems to
support only `test -n $DISPLAY' and `test -z $DISPLAY'.

>> If your patch is applied, the `test' token will not be updated
>> whatever $DISPLAY is.

> I don't think so:

> If there's a test clause present, the same code as before runs -
> mutating the cdr as before.

> If not, the function simply returns t, as documented.  (In that case,
> there's nothing to mutate.)

I did misread the patched code, sorry.

> +    (or (not test)
> +	(progn
> 	  ...))

In the case `test' is nil, there is no `test' to be updated.
So, the patch is harmless, but it isn't necessarily worthwhile
except that it makes it a bit fast, I think.  In addition,

> * mailcap.el (mailcap-mailcap-entry-passes-test): Actually return
> non-nil if no test clause is present, as documented.

Actually the return value of the function is not used in at least
Gnus Lisp modules.

Regards,



  reply	other threads:[~2015-10-20 14:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  9:10 Michael Sperber
2015-10-20 11:11 ` Katsumi Yamaoka
2015-10-20 11:51   ` Michael Sperber
2015-10-20 14:25     ` Katsumi Yamaoka [this message]
2015-10-20 15:55       ` Michael Sperber

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=b4mzizdy5uz.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    --cc=sperber@deinprogramm.de \
    /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).