From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id CFwsKW4QoF+ocQAA0tVLHw (envelope-from ) for ; Mon, 02 Nov 2020 13:58:06 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id UF4YJW4QoF9qAwAA1q6Kng (envelope-from ) for ; Mon, 02 Nov 2020 13:58:06 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 27327940148 for ; Mon, 2 Nov 2020 13:58:06 +0000 (UTC) Received: from localhost ([::1]:58704 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kZaLU-0005Bk-JE for larch@yhetil.org; Mon, 02 Nov 2020 08:58:04 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:58566) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kZaKl-00052e-4S for emacs-orgmode@gnu.org; Mon, 02 Nov 2020 08:57:19 -0500 Received: from mail-pl1-x62e.google.com ([2607:f8b0:4864:20::62e]:46362) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kZaKj-00056l-0J for emacs-orgmode@gnu.org; Mon, 02 Nov 2020 08:57:18 -0500 Received: by mail-pl1-x62e.google.com with SMTP id g11so334985pll.13 for ; Mon, 02 Nov 2020 05:57:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:subject:date:in-reply-to:message-id :mime-version; bh=/UbN0hOqjZdcFSpgNIMs1yrzaxE1XSqX3MHZhtDq6Lc=; b=APhf+FY6YAgXjZffsjsoB+gJhAjdX14y2Na3aIsyShFLS3QBqr2AMqPuixqSfZt2hu p4YFtKHKGVPpa677Yy/HKTplwXNCLQJRUG/B6B9r6TejZu6bku0Q7Lga82WrRmT5XhuT Wl8SgUkwye6+rxAYfAVjMFdr2Il7t0DIbsP3J2tOokh2gB7OmA+Uom4uj44GI70XqnFt Yr7EcAzH87VAyVlKSVKjOowbwpmrGM2FX1WZmHz/8j6btflrUUGdmEI1WQtI51+9cYr2 4/aHnMq7hJChccn4CwQ7Ql+6ktr4qPVxQcubZj6eK5DKuLE0KEzsWXMrj3cuV2a15N09 bHAg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:subject:date :in-reply-to:message-id:mime-version; bh=/UbN0hOqjZdcFSpgNIMs1yrzaxE1XSqX3MHZhtDq6Lc=; b=tCyraXUcJJTpyVLA5j0r0OjMwVr3xpdnr25bYmKbJ8MCyprXxb4UwdJRdIXWZXlqt5 wJPqo+BoLBLkQ4j8cXwKVgoyMgZ5lI3R3tustbdtt6fVpvnBynM/yb0iGhz9BD2YB9Y4 5AKs2hhNkIVwCen4CqNCMtQmRn5W5qoAaRMqX5X9ik24+aYvbPE0UF4pCJwjs5cfIS9y +KNLTlNDmkUnWIENSWvXXUsageulpkmE8AZt7TrIP/TrR6J9Picp2kiYDGku6ONmBVED 8XtRtqpPlbY/EvdV6Oa3Kv2IkxiyzJ00etJInPstOHqCDzGafsPq34XUkiI+w0nfAcnl Mz7Q== X-Gm-Message-State: AOAM532p3fp2gsgdGmQ9JAHyARSbz+IBJqOVwyb0DYjrln6mYqByIKs9 HLzr8/Xfdv0ez2+59CLDkFxoX3uDZo4= X-Google-Smtp-Source: ABdhPJw9JZ8+XjL2iB9fc0YSGq9BfGcEwM9MDUuQjVeGaimIbf3fAucGs3PoaRG9PGpHw3qxSy7lGg== X-Received: by 2002:a17:902:b108:b029:d6:82d8:f0d5 with SMTP id q8-20020a170902b108b02900d682d8f0d5mr21044955plr.45.1604325434657; Mon, 02 Nov 2020 05:57:14 -0800 (PST) Received: from localhost (180-150-91-8.b4965b.per.nbn.aussiebb.net. [180.150.91.8]) by smtp.gmail.com with ESMTPSA id c127sm14411569pfc.115.2020.11.02.05.57.12 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Nov 2020 05:57:14 -0800 (PST) References: <20201101161317.GA6609@maokai> <87imaoekrz.fsf@web.de> <39fb1f8d-4407-9359-ad14-72ae7841fda9@grinta.net> <87tuu85djy.fsf@gmail.com> User-agent: mu4e 1.4.13; emacs 27.1 From: TEC To: emacs-orgmode@gnu.org Subject: Re: Thoughts on the standardization of Org Date: Mon, 02 Nov 2020 21:43:27 +0800 In-reply-to: Message-ID: <87sg9r6evd.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed Received-SPF: pass client-ip=2607:f8b0:4864:20::62e; envelope-from=tecosaur@gmail.com; helo=mail-pl1-x62e.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=APhf+FY6; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.71 X-TUID: JXJU8a2PYrUD Daniele Nicolodi 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.