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: Mon, 15 Dec 2014 18:55:05 +0100 Organization: Linux Private Site Message-ID: <87siggx0g6.fsf@Gertrud.fritz.box> References: <20141205123549.GA29331@thyrsus.com> <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> <87388jz1ss.fsf@Gertrud.fritz.box> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1418666216 1677 80.91.229.3 (15 Dec 2014 17:56:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 15 Dec 2014 17:56:56 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 15 18:56:49 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 1Y0Zt3-0002Wx-NO for ged-emacs-devel@m.gmane.org; Mon, 15 Dec 2014 18:56:49 +0100 Original-Received: from localhost ([::1]:41285 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y0Zt3-0005x1-DZ for ged-emacs-devel@m.gmane.org; Mon, 15 Dec 2014 12:56:49 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54041) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y0Zrl-0004pX-LE for emacs-devel@gnu.org; Mon, 15 Dec 2014 12:55:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y0Zrf-0001hs-D3 for emacs-devel@gnu.org; Mon, 15 Dec 2014 12:55:29 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:40435) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y0Zrf-0001hL-5k for emacs-devel@gnu.org; Mon, 15 Dec 2014 12:55:23 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Y0Zrd-0001p9-5g for emacs-devel@gnu.org; Mon, 15 Dec 2014 18:55:21 +0100 Original-Received: from p54b7ff63.dip0.t-ipconnect.de ([84.183.255.99]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Dec 2014 18:55:21 +0100 Original-Received: from Stromeko by p54b7ff63.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Dec 2014 18:55:21 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 58 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: p54b7ff63.dip0.t-ipconnect.de User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:XEZjaiqK1gHwU03224K1lfauRCI= 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:180171 Archived-At: Richard Stallman writes: > If you send me a list of the current simple markup characters, > I could make some proposals. The simple markup is *bold*, =verbatim=, ~code~, /italic/ +strike-through+ and _underline_. The actual rules are a bit more complicated since some of that is costumizable for historical reasons. The last section in the Org syntax document says this: --8<---------------cut here---------------start------------->8--- Text Markup Text markup follows the pattern: PRE MARKER CONTENTS MARKER POST PRE is a whitespace character, (, { ~’~ or a double quote. It can also be a beginning of line. MARKER is a character among * (bold), = (verbatim), / (italic), + (strike-through), _ (underline), ~ (code). CONTENTS is a string following the pattern: BORDER BODY BORDER BORDER can be any non-whitespace character excepted ~,~, ~’~ or a double quote. BODY can contain contain any character but may not span over more than 3 lines. BORDER and BODY are not separated by whitespaces. CONTENTS can contain any object encountered in a paragraph when markup is “bold”, “italic”, “strike-through” or “underline”. POST is a whitespace character, -, ., ~,~, :, !, ?, ~’~, ), } or a double quote. It can also be an end of line. PRE, MARKER, CONTENTS, MARKER and POST are not separated by whitespace characters. All of this is wrong if org-emphasis-regexp-components or org-emphasis-alist are modified. This should really be simplified and made persistent (i.e. no defcustom allowed). Otherwise, portability and parsing are jokes. Also, CONTENTS should be anything within code and verbatim emphasis, by definition. — ngz --8<---------------cut here---------------end--------------->8--- > I agree that we should not go overboard on this. It might be good for > 10 common constructs to have character pairs to designate them, while > using Texinfo-like format with braces for the rest of the constructs. I imagine that to look a lot like digraphs and trigraphs... Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra