From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Achim Gratz Newsgroups: gmane.emacs.devel Subject: Re: On being web-friendly and why info must die Date: Sat, 13 Dec 2014 22:18:27 +0100 Organization: Linux Private Site Message-ID: <87388jz1ss.fsf@Gertrud.fritz.box> References: <20141205123549.GA29331@thyrsus.com> <5485FC59.5030700@cs.ucla.edu> <87388p6glt.fsf@engster.org> <871to9lw6g.fsf@fencepost.gnu.org> <5486A704.6090305@cs.ucla.edu> <87k321jj4e.fsf@fencepost.gnu.org> <54876F7F.9000607@cs.ucla.edu> <87y4qfj2u9.fsf@fencepost.gnu.org> <54889A57.5060905@cs.ucla.edu> <87vbljb9f4.fsf@wanadoo.es> <54889F6D.6060408@cs.ucla.edu> <87r3w7b83a.fsf@wanadoo.es> <5488C710.3000209@cs.ucla.edu> <871to7ayv9.fsf@wanadoo.es> <5488DC0C.2070402@cs.ucla.edu> <837fxyt78a.fsf@gnu.org> <87iohiujcy.fsf@Gertrud.fritz.box> <8761dg1ykk.fsf@Gertrud.fritz.box> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1418505553 17243 80.91.229.3 (13 Dec 2014 21:19:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 13 Dec 2014 21:19:13 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 13 22:19:06 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xzu5i-0007z5-2h for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2014 22:19:06 +0100 Original-Received: from localhost ([::1]:34308 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xzu5h-0007uX-J6 for ged-emacs-devel@m.gmane.org; Sat, 13 Dec 2014 16:19:05 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:47255) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xzu5Y-0007lq-G3 for emacs-devel@gnu.org; Sat, 13 Dec 2014 16:19:03 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xzu5S-0007mZ-5l for emacs-devel@gnu.org; Sat, 13 Dec 2014 16:18:56 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:52416) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xzu5R-0007mN-VN for emacs-devel@gnu.org; Sat, 13 Dec 2014 16:18:50 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Xzu5O-0007Rj-Hd for emacs-devel@gnu.org; Sat, 13 Dec 2014 22:18:46 +0100 Original-Received: from p4ff1cd1f.dip0.t-ipconnect.de ([79.241.205.31]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 13 Dec 2014 22:18:46 +0100 Original-Received: from Stromeko by p4ff1cd1f.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 13 Dec 2014 22:18:46 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 49 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p4ff1cd1f.dip0.t-ipconnect.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:NnCu9JLSdeypJmnkiFgf3K51vDI= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:180040 Archived-At: Richard Stallman writes: > Documentation of how to write such things in Org format > is part of what is needed for Org format to be a candidate > for a GNU documentation format. Yes, but turning the tables: what exactly are the requirements for a GNU documentation format? If it turns out to be "exactly like texinfo", then any other contender would have to be leaps and bounds better in at least one or two other respects to be even considered seriously. > > For Org, it seems that macros would be the way to go unless we'd come up > > with yet another mechanism for semantic markup. > > What would this look like? The macro invocations are those things in triple curly braces in the manual section I posted. This would be a macro defintion for a macro taking no argument #+MACRO: page @@info:@page@@ while these two take arguments and the latter is using a macro within its own definition #+MACRO: markup @@info:@$1{@@$2@@info:}@@ #+MACRO: kbd {{{markup(kbd,$1)}}} These macros define output specific to the info export backend by using a so-called export snippet. You could write these directly, but doing this via macro expansion reduces the tedium somewhat. > A solution that occurs to me is to use character pair brackets, such > as _*foo*_ and _#foo#_ and *#foo#*. These would provide enough > alternatives to make the necessary distinctions. Defining new syntax for Org that doesn't collide with already existing things is not easy. In this particular case, I don't even see an advantage since the pair brackets aren't in any way self-describing, so one would have to look them up each time they need to be used. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds