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:14:34 +0200 Message-ID: <87msy92bh1.fsf@bzg.fr> References: <83msyemjx8.fsf@gnu.org> <871qfpoij6.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33245"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: "Jose E. Marchesi" , eliz@gnu.org, emacs-devel@gnu.org To: Richard Stallman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 30 10:14:56 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 1qbGLo-0008O0-Ej for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Aug 2023 10:14:56 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qbGLb-0006jv-Kn; Wed, 30 Aug 2023 04:14:43 -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 1qbGLa-0006a0-7y for emacs-devel@gnu.org; Wed, 30 Aug 2023 04:14:42 -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 1qbGLW-0000a1-Qm for emacs-devel@gnu.org; Wed, 30 Aug 2023 04:14: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=t5QrGTZdOZXn3YtKUy05Q+1HIe1B2zsk2pfxpCS2jqs=; b=a4roQfgGh5MAgYX0gMWs OZjS65rhOpWMVOk3gaTWs4R6ZMh/x5Z4y9P7d9GcwV98PPmeGtuJ8112AgIsTEr7yS6+jAneVRHXO LGf5K3gP/Jhc/vji1bPmCKkqA4RNeZrh4jckB+Jm4WGQj7pflEDcbsr18NU7H3lqfv+f0FXoMTd7b Jub/zP6Anr3YDE7QyDuaWT5VbUebCtanY2spxqyVJ3snZJ9Fz2hSW57P1bhzNk4flejPys2BZp1U0 Rwk1ZCMIF2I7vnv9z+cCPi0MhFqc+bdktH6DT6p/wRM0sTPOK41sv674XS53Py3VIOhsCEaYuwufe EHo00C+rX1Nehg==; In-Reply-To: (Richard Stallman's message of "Sat, 26 Aug 2023 21:32:28 -0400") 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:309535 Archived-At: Richard Stallman writes: > > "markdown-style" formats, on the contrary, generally support a closed > > set of marks that use delimited based ad-hoc syntax, such as *foo*, > > =foo=, "foo", `foo' and so on. > > The challenge is to extend Org format with an open-ended syntax that > could handle many different inline markup opertions. Yes, that's the idea behind using one-char constructs for basic inline markup (eg ~code~, /emphasis/, etc.) and two-chars constructs for more specific inline markup (eg ~~defn~~, =~defvar~=, etc.). -- Bastien Guerry