From: Po Lu <luangruo@yahoo.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Björn Bidar" <bjorn.bidar@thaodan.de>,
eliz@gnu.org, stefankangas@gmail.com, emacs-devel@gnu.org
Subject: Re: Should Emacs declare itself as being able to open all the text/* mimetypes?
Date: Wed, 20 Sep 2023 20:23:26 +0800 [thread overview]
Message-ID: <87o7hxrq2p.fsf@yahoo.com> (raw)
In-Reply-To: <87il858563.fsf@localhost> (Ihor Radchenko's message of "Wed, 20 Sep 2023 11:17:40 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Other source code files might though. For example,
>
> $ xdg-mime query filetype src/js.rs
> text/rust
RFC6838 does not incorporate text/rust AFAICT.
next prev parent reply other threads:[~2023-09-20 12:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87v8d66r7l.fsf@localhost>
[not found] ` <CADwFkmmr=9DpCXDqgh_z+EFJPAvmchJfzuzReWM9z=T63oC2NA@mail.gmail.com>
[not found] ` <CADwFkm=AejxJ2saoH37Eo_OLRXKT7BALZM7NF4V_c3vQGXUiyA@mail.gmail.com>
[not found] ` <87led53q0c.fsf@thaodan.de>
[not found] ` <CADwFkmm9SOp5Cx4MsHkSs9NVq9-aDAy8uu8MUPbY2RZnWQRx3Q@mail.gmail.com>
[not found] ` <87fs3bkho4.fsf@localhost>
[not found] ` <835y47g2b2.fsf@gnu.org>
[not found] ` <zaqt9p.s16mth.rtvd7y-qmf@thaodan.de>
[not found] ` <874jjrk48q.fsf@localhost>
[not found] ` <87cyyfwqs5.fsf@yahoo.com>
2023-09-19 11:14 ` Generic Elisp mechanism to declare file/URI handlers for Emacs (was: bug#65469: [PATCH] * etc/emacsclient.desktop: Make Emacs default application for org-protocol) Ihor Radchenko
2023-09-19 11:44 ` Generic Elisp mechanism to declare file/URI handlers for Emacs Po Lu
2023-09-19 13:06 ` Ihor Radchenko
2023-09-19 13:25 ` Po Lu
2023-09-20 9:26 ` Ihor Radchenko
2023-09-20 9:57 ` Po Lu
2023-09-20 11:17 ` Should Emacs declare itself as being able to open all the text/* mimetypes? (was: Generic Elisp mechanism to declare file/URI handlers for Emacs) Ihor Radchenko
2023-09-20 12:23 ` Po Lu [this message]
2023-09-20 12:38 ` Should Emacs declare itself as being able to open all the text/* mimetypes? Ihor Radchenko
2023-09-19 13:46 ` Generic Elisp mechanism to declare file/URI handlers for Emacs Eli Zaretskii
2023-09-19 13:56 ` Ihor Radchenko
2023-09-20 11:15 ` Eli Zaretskii
2023-09-19 16:28 ` Generic Elisp mechanism to declare file/URI handlers for Emacs (was: bug#65469: [PATCH] * etc/emacsclient.desktop: Make Emacs default application for org-protocol) Jim Porter
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=87o7hxrq2p.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=bjorn.bidar@thaodan.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
--cc=yantar92@posteo.net \
/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).