From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Bastien Guerry Newsgroups: gmane.emacs.devel Subject: Re: Org mode and Emacs Date: Wed, 30 Aug 2023 10:11:37 +0200 Message-ID: <874jkh54qu.fsf@bzg.fr> References: <83msyemjx8.fsf@gnu.org> <871qfpoij6.fsf@gnu.org> <87fs45ivyo.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22878"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: "Jose E. Marchesi" , Eli Zaretskii , rms@gnu.org, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 30 10:12:39 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qbGJa-0005go-Vt for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Aug 2023 10:12:39 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qbGIk-0006z0-0R; Wed, 30 Aug 2023 04:11:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbGIh-0006hW-OB for emacs-devel@gnu.org; Wed, 30 Aug 2023 04:11:43 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbGIg-0000JM-5B; Wed, 30 Aug 2023 04:11:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=qzrMzUp/jgc/IuQ8TzdItC1mFXGyQ2FZAkk6tvWQr0s=; b=FbBolqov7cClrhn43E9b GDCefuZ0ewu/I8PXsLEic5BmSGkPqvxKQUJrMRtcIU9IhZzjh5zOXofJN0/h3SL+bmEqjzH/sT/9T Oh+sSLP9fC+AwY8MJ0bJDhk1a0zY1GyDfz5NGB80V+vuVpGRnQtj+/8MjZGMzQUWRVY4b2hEYkLio ZuBcqKirnN0LpPN1YSh1xL9Fo6bgRlETa20cxVV0m9VgictPu9iYE7OyJU4QAgl4XnUplCx31rSyI SRTVK/RqB/HWlRpn2/xRKTL9eO9TjFdKPlq2lpYGc8Ns2gCKKtN3+y0rn3i1wxbmjubSl+z76LKw4 uYvhLlbLyMsNjw==; In-Reply-To: <87fs45ivyo.fsf@localhost> (Ihor Radchenko's message of "Sat, 26 Aug 2023 16:56:15 +0000") X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:309533 Archived-At: Ihor Radchenko writes: > That's what we plan to add to Org. Not just because of this > discussion; Why? Where can I find this discussion? If the main reasons for supporting inline markup like @NAME{CONTENT} (or similar) are the current fontification shortcomings, I'm skeptic. The .org falls in the category of lightweight markup formats and I believe it should stick close to this definition. That is, natively support *bold*, /emphasis/, etc. without adding heavy more constructs like @NAME{CONTENT} -- even optionnally. If we need to support @defn{FUNCTION} for .texi export, what about considering ~~FUNCTION~~ ? Using two chars at the beg and end is a natural extension of the current markup syntax and should spare us some ambiguity that we have with one-char constructs. > there are other reasons why we want such custom inline markup. Thanks for pointing at these discussions. -- Bastien Guerry