From: TEC <tecosaur@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Thoughts on the standardization of Org
Date: Mon, 02 Nov 2020 21:43:27 +0800 [thread overview]
Message-ID: <87sg9r6evd.fsf@gmail.com> (raw)
In-Reply-To: <dbe93479-44a4-7319-851c-c21fb160d028@grinta.net>
Daniele Nicolodi <daniele@grinta.net> writes:
> On 02/11/2020 10:02, TEC wrote:
>> I think there are absolutely some benefits for Org users. I am
>> personally interested in registering Org as an IANA MIME type.
>
> I don't think that registering Org as IANA MIME type will have
> the
> consequences you hope it has.
Hmmm. I'm glad you've brought this up. I wouldn't want to put in
hours
of effort for a unlikely benefit.
My hope is that registering org as an IANA MIME type will cause it
to
trickle down into individual MIME registries.
The benefit I see here is Org being able to be treated more as a
'first
class' plaintext format --- like I see markdown being treated
today.
Open a ".md" file in Ocular and you see a nice rendered version (I
use
this as a general, not specific example).
Then, if we can package Emacs into an LSP client, we can provide a
very
well-featured Org experience to dozens of editors, and the
"text/*"
association will be important to ensure that Org files are opened
in
those text editors.
For people who use editors like VSCode, being able to send an Org
file
and have it open in VSCode will likely prompt them to install an
extension that provides support for .org files...
This may be a bit unrealistic, and I'm hugely appreciative of any
effort
to inform me of any aspects that I may be overlooking.
> Finally, even if you get your attachment automatically tagged as
> "text/org", the receiving side needs to have a mime type handler
> configured to display it. As far as I know, not even Emacs (on
> the
> platforms that allow it) registers itself as an handler for any
> MIME
> type. Therefore, what you get, assuming that the mail client on
> the
> other side behaves correctly and uses "text/*" as a fallback for
> "text/org" is that your attachment will be displayed in a
> generic text
> editor.
1. Could Emacs change to register itself as a text/org handler?
2. See above for why I don't think that opening it in a generic
text
editor would necessarily be a bad idea.
> I send Org files as "text/plain" (often even using ".txt"
> extension to
> avoid confusion on the receiving side) and I think this is the
> best
> choice as it puts the least burden on the receiving side to
> consume the
> content and it is displayed inline by most email clients.
This seems like a good idea, thanks for sharing it!
> I don't think that registering "text/org" with the IANA will
> have the
> consequences that you hope it has.
Thanks for highlighting some potential pitfalls that I haden't
considered. As outlined above, in light of your comments I still
see
this being potentially beneficial/worth the effort, but you've
opened my
eyes to some complications that I was previously unaware of.
Thank you,
Timothy.
next prev parent reply other threads:[~2020-11-02 13:58 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 0:22 Thoughts on the standardization of Org Asa Zeren
2020-11-01 0:40 ` Dr. Arne Babenhauserheide
2020-11-01 3:08 ` Asa Zeren
2020-11-01 4:23 ` Pankaj Jangid
2020-11-01 7:54 ` Tim Cross
2020-11-01 2:28 ` Tim Cross
2020-11-01 3:39 ` Pankaj Jangid
2020-11-02 12:39 ` Eric S Fraga
2020-11-02 14:22 ` Greg Minshall
2020-11-02 14:56 ` Eric S Fraga
2020-11-02 15:23 ` Russell Adams
2020-11-02 15:31 ` TEC
2020-11-02 15:48 ` Eric S Fraga
2020-11-02 16:27 ` Carsten Dominik
2020-11-02 22:05 ` Tim Cross
2020-11-03 3:29 ` Greg Minshall
2020-11-01 5:20 ` Tom Gillespie
2020-11-01 10:25 ` Dr. Arne Babenhauserheide
2020-11-01 10:28 ` TEC
2020-11-01 18:02 ` Jack Kamm
2020-11-01 16:03 ` Asa Zeren
2020-11-01 17:27 ` Dr. Arne Babenhauserheide
2020-11-01 17:29 ` TEC
2020-11-01 18:43 ` Asa Zeren
2020-11-01 6:24 ` TEC
2020-11-01 16:13 ` Russell Adams
2020-11-01 19:46 ` Daniele Nicolodi
2020-11-01 23:10 ` Dr. Arne Babenhauserheide
2020-11-02 8:37 ` Daniele Nicolodi
2020-11-02 9:02 ` TEC
2020-11-02 11:04 ` Daniele Nicolodi
2020-11-02 13:43 ` TEC [this message]
2020-11-07 21:20 ` Jean Louis
2020-11-09 14:04 ` Maxim Nikulin
2020-11-09 15:57 ` Daniele Nicolodi
2020-11-09 15:59 ` Jean Louis
2020-11-10 16:19 ` Maxim Nikulin
2020-11-10 20:22 ` Jean Louis
2020-11-10 23:08 ` Tom Gillespie
2020-11-11 0:00 ` Tim Cross
2020-11-09 21:46 ` Tim Cross
2020-11-09 22:45 ` Emails are not safe - " Jean Louis
2020-11-10 4:13 ` Greg Minshall
2020-11-10 4:49 ` Tim Cross
2020-11-10 7:12 ` Greg Minshall
2020-11-10 16:29 ` Maxim Nikulin
2020-11-10 20:35 ` Jean Louis
2020-11-10 22:30 ` Tim Cross
2020-11-11 5:03 ` Jean Louis
2020-11-11 6:40 ` Tim Cross
2020-11-27 16:49 ` Maxim Nikulin
2020-11-27 17:16 ` Jean Louis
2020-11-11 17:10 ` Maxim Nikulin
2020-11-11 17:34 ` Jean Louis
2020-11-12 3:39 ` Greg Minshall
2020-11-11 3:49 ` Greg Minshall
2020-11-02 9:53 ` Dr. Arne Babenhauserheide
2020-11-02 1:17 ` Ken Mankoff
2020-11-02 8:12 ` Russell Adams
2020-11-02 9:57 ` Dr. Arne Babenhauserheide
2020-11-03 8:24 ` David Rogers
2020-11-03 12:14 ` Ken Mankoff
2020-11-03 12:27 ` Russell Adams
2020-11-03 13:00 ` Eric S Fraga
2020-11-03 13:31 ` Ken Mankoff
2020-11-03 15:03 ` Eric S Fraga
2020-11-03 20:27 ` TEC
2020-11-03 14:38 ` Devin Prater
2020-11-03 22:03 ` David Rogers
-- strict thread matches above, loose matches on Subject: below --
2020-11-01 13:34 Gustav Wikström
2020-11-01 18:39 Asa Zeren
2020-11-03 22:30 Asa Zeren
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sg9r6evd.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.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/org-mode.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).