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: [Emacs-diffs] master 9ffb6ce 5/5: Quoting fixes in lisp/international and lisp/leim Date: Wed, 2 Sep 2015 14:16:28 +0300 Message-ID: <55E6DA8C.1030403@yandex.ru> References: <20150831061236.27796.57762@vcs.savannah.gnu.org> <55E3F434.2060507@yandex.ru> <55E496DC.1030608@cs.ucla.edu> <877foas9jh.fsf@gmail.com> <55E5FD79.3060309@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1441192603 19393 80.91.229.3 (2 Sep 2015 11:16:43 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 2 Sep 2015 11:16:43 +0000 (UTC) Cc: Paul Eggert , Oleh Krehel , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 02 13:16:42 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 1ZX61w-00069h-Vw for ged-emacs-devel@m.gmane.org; Wed, 02 Sep 2015 13:16:41 +0200 Original-Received: from localhost ([::1]:36524 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZX61w-0004F8-HU for ged-emacs-devel@m.gmane.org; Wed, 02 Sep 2015 07:16:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37915) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZX61t-0004Es-TB for emacs-devel@gnu.org; Wed, 02 Sep 2015 07:16:38 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZX61r-0002eL-6K for emacs-devel@gnu.org; Wed, 02 Sep 2015 07:16:37 -0400 Original-Received: from mail-wi0-x236.google.com ([2a00:1450:400c:c05::236]:34977) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZX61q-0002dn-Uo for emacs-devel@gnu.org; Wed, 02 Sep 2015 07:16:35 -0400 Original-Received: by wicge5 with SMTP id ge5so36886652wic.0 for ; Wed, 02 Sep 2015 04:16:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=iGyU9of3uwgBTO5j7Wzfsz/8l1tvS7rjtwNWkDw/JGo=; b=c43H/sQ2SkA4EJOFI05g+UknGvyTWjejANrNBlJk0zrlRWhUnLqDJzfbgxH38lb7hB 5zUWX6Pxr0PLLyHmHLSr/Mn/ZWPBUy7fbnZiQlc8UZkm5m+uzVBMxyjI257GbRz93C+O WP8hMpecjRJ+gBDI+CodgZqIZ7ECh7CZNdurd0iR9Mq7E68DzhfXd/5eUtSlO9dneYM7 l7tmOorg5cKkUatS967Xw2Sn0xw6v4pU/zBJ5W7SCvTsfJcEeBjfZ8+z2IFD1E9iSUid /e3Zp82V3lsJGuRsyUX7seN3gDhlCfKzOV5c9DSzPJIv/2XAZ6JBsQi1zU5sOSiVsurZ 1FJw== X-Received: by 10.194.122.97 with SMTP id lr1mr39081769wjb.26.1441192593887; Wed, 02 Sep 2015 04:16:33 -0700 (PDT) Original-Received: from [10.9.0.103] (nat.webazilla.com. [78.140.128.228]) by smtp.googlemail.com with ESMTPSA id k12sm31929439wjw.4.2015.09.02.04.16.32 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 02 Sep 2015 04:16:32 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Thunderbird/40.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::236 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:189456 Archived-At: On 09/02/2015 05:34 AM, Stefan Monnier wrote: > W.r.t ambiguity, the main problem I see is that we currently can never > be sure that when we see a ` followed by a ' the two actually form a pair. > A human usually can tell, but a program can't get it right 100% of the time. Okay. But then, there's no problem in using the same quoting for key sequences, aside from the quote-matching algorithm. >> We might also want to support code snippets like `(progn (foo bar foo))'. >> At least, elisp-completion-at-point relies on snippets being quoted >> that way now. We can detect these using paired parens. > > Not sure I want to go down that road. What about `(foo 'a 'b)' ? That, too. At least if this quote-matching logic is implemented in Elisp, forward-sexp can take care of skipping the spaces. > AFAIK it's not very common (yet?) to quote code that way, and I'm not > sure we want to get into the habit of quoting it that way. I could see > the need/advantage of quoting code reliably, but I don't think `...' is > a good way to do it. If we take after Markdown (because why not?), it has two methods of quoting code: one for inline code (also used for references), and one for code blocks (on separate lines). It might be a good idea to also have just one quoting method for inline code. But if you have a better idea for quoting code, that's fine, too.