From: Andreas Schwab <schwab@linux-m68k.org>
To: Arash Esbati <arash@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 52038@debbugs.gnu.org
Subject: bug#52038: Completion for user mailcap entries
Date: Sun, 02 Oct 2022 10:59:44 +0200 [thread overview]
Message-ID: <874jwmmwhr.fsf@linux-m68k.org> (raw)
In-Reply-To: <868rlymxbk.fsf@gnu.org> (Arash Esbati's message of "Sun, 02 Oct 2022 10:41:51 +0200")
On Okt 02 2022, Arash Esbati wrote:
> diff --git a/lisp/net/mailcap.el b/lisp/net/mailcap.el
> index aa0c172655..a0355f876b 100644
> --- a/lisp/net/mailcap.el
> +++ b/lisp/net/mailcap.el
> @@ -303,9 +303,9 @@ mailcap-mime-data
> Which looks like:
> -----------------
> ((\"application\"
> - (\"postscript\" . <info>))
> + (\"postscript\" <info>))
> (\"text\"
> - (\"plain\" . <info>)))
> + (\"plain\" <info>)))
>
> Where <info> is another assoc list of the various information
> related to the mailcap RFC 1524. This is keyed on the lowercase
>
> The way I understand it the 2nd assoc list isn't a dotted pair where
> <info> contains dotted pairs.
This is wrong. <info> is a list that is the cdr of the containing list.
In the definition of mailcap-mime-data the <info> list is spliced into
its parent, since you can always write '(a . (b c)) as '(a b c).
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-10-02 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 13:03 bug#52038: Completion for user mailcap entries Arash Esbati
2022-09-24 13:39 ` Lars Ingebrigtsen
2022-10-01 7:21 ` Arash Esbati
2022-10-01 10:12 ` Lars Ingebrigtsen
2022-10-01 13:21 ` Lars Ingebrigtsen
2022-10-02 8:41 ` Arash Esbati
2022-10-02 8:59 ` Andreas Schwab [this message]
2022-10-02 9:58 ` Arash Esbati
2022-10-02 10:05 ` Andreas Schwab
2022-10-02 11:21 ` Arash Esbati
2022-10-02 12:08 ` Andreas Schwab
2022-10-02 12:13 ` Lars Ingebrigtsen
2022-10-02 13:02 ` Arash Esbati
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=874jwmmwhr.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=52038@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.