From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Upcoming loss of usability of Emacs source files and Emacs. Date: Sun, 28 Jun 2015 23:36:34 +0300 Message-ID: <55905AD2.4090406@yandex.ru> 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> <87381bzife.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1435523839 31853 80.91.229.3 (28 Jun 2015 20:37:19 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 28 Jun 2015 20:37:19 +0000 (UTC) To: Stefan Monnier , acm@muc.de, stephen@xemacs.org, Paul Eggert , rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 28 22:37:13 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 1Z9JKD-0003cE-BG for ged-emacs-devel@m.gmane.org; Sun, 28 Jun 2015 22:37:13 +0200 Original-Received: from localhost ([::1]:39836 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9JKC-0000xM-ID for ged-emacs-devel@m.gmane.org; Sun, 28 Jun 2015 16:37:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:56025) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9JK0-0000xC-89 for emacs-devel@gnu.org; Sun, 28 Jun 2015 16:37:01 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z9JJr-0001Hq-LO for emacs-devel@gnu.org; Sun, 28 Jun 2015 16:36:59 -0400 Original-Received: from mail-wi0-x22e.google.com ([2a00:1450:400c:c05::22e]:34019) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z9JJr-0001G9-EL; Sun, 28 Jun 2015 16:36:51 -0400 Original-Received: by wicnd19 with SMTP id nd19so82938436wic.1; Sun, 28 Jun 2015 13:36:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=RcV9zgaERlb6+jmbpk3jl1wj7WUCpUs6BiqBkzp4qSc=; b=QoUzpaEBU56MSrZo7De6tD+LDYClyFrJXNFM+9o0N9Bg+KNAID8TeTSrUX3YXllJIF 67DCrOZtUj6i3DcPquB7OPE5ZAY8sLDmiRq+vLXTkEEDQcaUSPTgaeyiycKiM+w89s4H nEf2XeqRRrAZ2KASGzzIateHIBhGHV4+Y5Fsip1XuvHT0vBwbcv+NIibSdK79Pn1WNId ceRrTDFsEoYF4aWYR9wa4lXq/mxlPXlJoNgzBu79ALhbc0WfuI7yTJvF8EXvINdQG2Mh yxEk0vO1BEPsg+m9zMcStnfC4zEG9mLPNEBGP6Ma1mBm1GbZA0nn5aLAfnoJ82ufcC1i OOWg== X-Received: by 10.194.5.74 with SMTP id q10mr21995736wjq.27.1435523799315; Sun, 28 Jun 2015 13:36:39 -0700 (PDT) Original-Received: from [192.168.1.2] ([82.102.93.54]) by mx.google.com with ESMTPSA id n8sm8856438wiy.19.2015.06.28.13.36.38 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 28 Jun 2015 13:36:39 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 In-Reply-To: <87381bzife.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::22e 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:187626 Archived-At: On 06/28/2015 11:28 PM, Tassilo Horn wrote: > 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. I would understand it if it was meant as a sarcastic remark. We don't have a convenient input method for ⸢ and ⸥ and I'd prefer not to have a need for it anyway (nor for similar characters). > 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." Yes, we might want to at least provide an option to display them differently (that has been brought up before, by yours truly). Handling the quotes in font-lock should make implementing that easy enough.