From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: Upcoming loss of usability of Emacs source files and Emacs. Date: Sun, 28 Jun 2015 22:28:37 +0200 Message-ID: <87381bzife.fsf@gnu.org> References: <20150615142237.GA3517@acm.fritz.box> <87y4jkhqh5.fsf@uwakimon.sk.tsukuba.ac.jp> <557F3C22.4060909@cs.ucla.edu> <5580D356.4050708@cs.ucla.edu> <87si9qonxb.fsf@gnu.org> <5581C29E.1030101@yandex.ru> <558D6A3D.1070706@yandex.ru> <877fqnzpno.fsf@gnu.org> <5590493C.8000007@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1435523352 24991 80.91.229.3 (28 Jun 2015 20:29:12 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 28 Jun 2015 20:29:12 +0000 (UTC) Cc: Paul Eggert , rms@gnu.org, emacs-devel@gnu.org, Stefan Monnier , acm@muc.de, stephen@xemacs.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 28 22:29:02 2015 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 1Z9JCH-0007r1-Vp for ged-emacs-devel@m.gmane.org; Sun, 28 Jun 2015 22:29:02 +0200 Original-Received: from localhost ([::1]:39822 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9JCH-0007vb-Hh for ged-emacs-devel@m.gmane.org; Sun, 28 Jun 2015 16:29:01 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54262) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9JC4-0007vI-Ss for emacs-devel@gnu.org; Sun, 28 Jun 2015 16:28:49 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z9JBy-0005cK-Hw for emacs-devel@gnu.org; Sun, 28 Jun 2015 16:28:48 -0400 Original-Received: from out3-smtp.messagingengine.com ([66.111.4.27]:52459) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9JBy-0005cD-Bj for emacs-devel@gnu.org; Sun, 28 Jun 2015 16:28:42 -0400 Original-Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 076B72045C for ; Sun, 28 Jun 2015 16:28:42 -0400 (EDT) Original-Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Sun, 28 Jun 2015 16:28:42 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=7WRhbIvePy+WGnM 25V5MNy2oNiw=; b=c29f8ORxXVhyFIfEjQxBITv6HRXUpj24Li6FI8Ly0+mXfnk CwiP3oQ2rgVS6YuTfPU+XkpZCT646TKuPEgbiKMcrKL2HpOktsWi7Z3umdvbHf9k DpAuiX8y1srn+aa+deHZqnENiVCajetxhB96ajsKHgxPDiqtiIgpK+S8nmng= X-Sasl-enc: qtjITXtHCc/lMpqmRSWU12AAO0Jrozi5nIBBsfX3m0DJ 1435523321 Original-Received: from thinkpad-t440p (unknown [2.160.147.237]) by mail.messagingengine.com (Postfix) with ESMTPA id CFABB6800DA; Sun, 28 Jun 2015 16:28:39 -0400 (EDT) Mail-Followup-To: Dmitry Gutov , Stefan Monnier , acm@muc.de, stephen@xemacs.org, Paul Eggert , rms@gnu.org, emacs-devel@gnu.org In-Reply-To: <5590493C.8000007@yandex.ru> (Dmitry Gutov's message of "Sun, 28 Jun 2015 22:21:32 +0300") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 66.111.4.27 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:187625 Archived-At: Dmitry Gutov writes: > On 06/28/2015 08:52 PM, Tassilo Horn wrote: > >> For example, I've seen uses of =E2=B8=A2foo=E2=B8=A5 for marking up sour= ce code >> snippets. That seems pretty unambiguous (although you can never be >> sure), and as long you can type it easily and display it however >> suits you best, it's as good as anything else. > > If we're prepared to change the markup radically, it would be better > to use something like a tilde character, which is both ASCII and very > rare in our docstrings. That wasn't really meant as a suggestion. I just wanted to ask why not use some extremely rare paired characters if unambiguity is the main point and we have some convenient input method anyhow. That simply typing a key which has the exact letter on it is even better is obvious. >> BTW: On a related note: I don't get why *Help* buffers display quotes >> at all when they are already displayed with a face that makes them >> distinguishable from "normal" text and are clickable. > > Not the same thing. We only linkify the names of already-loaded (or > autoloaded) functions and variables. > > Whereas we also use the quotes for other cases, like key sequences > (`C-h k') and arbitrary `symbols' (for example when describing > possible values of a variable or a function argument). Ok, right. Basically, what I meant to say is that @kbd{} in texinfo and `...' in elisp docstrings is markup which says that's a keybinding/symbol/code snippet. I don't see why this would imply that it needs to be displayed with quote characters, it just needs to be displayed as something "non-prose-y." Bye, Tassilo