unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Arash Esbati <arash@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52038@debbugs.gnu.org
Subject: bug#52038: Completion for user mailcap entries
Date: Sat, 01 Oct 2022 09:21:07 +0200	[thread overview]
Message-ID: <86h70o80ws.fsf@gnu.org> (raw)
In-Reply-To: <87czbkevs3.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 24 Sep 2022 15:39:40 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> The entries you are seeing as vnd\.ms-excel etc come from here:
>
> (defvar mailcap-mime-data
>   `(("application"
>      ("vnd\\.ms-excel"
>       (viewer . "gnumeric %s")
>
> These are regexps, and we want to specify that we're matching the "."
> character, and not the [.] character class, so we don't match
> "vndxms-excel".  That's probably overly pedantic, but...
>
> But I think this is working as designed, and I'm therefore closing this
> bug report.

Thanks for looking at this.  My impression back then was that the entry
"application/vnd.ms-excel" is coming from `mailcap-mime-data' and
"application/vnd\.ms-excel" is generated by the function
`mailcap-parse-mailcap' which is called inside `mailcap-parse-mailcaps'
where the former pushes the entries in ~/.mailcap through
`regexp-quote'.  So I think the bug is that 2 different entries are
generated for the same mime-type.  Or am I missing something?

Best, Arash





  reply	other threads:[~2022-10-01  7:21 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86h70o80ws.fsf@gnu.org \
    --to=arash@gnu.org \
    --cc=52038@debbugs.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).