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: trunk r114545: * lisp/progmodes/ruby-mode.el: Fix recently added tests. Date: Tue, 08 Oct 2013 02:27:08 +0300 Message-ID: <5253434C.4010809@yandex.ru> References: <874n8tz5d9.fsf@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1381188447 31308 80.91.229.3 (7 Oct 2013 23:27:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 7 Oct 2013 23:27:27 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 08 01:27:32 2013 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 1VTKD4-0001RO-A0 for ged-emacs-devel@m.gmane.org; Tue, 08 Oct 2013 01:27:30 +0200 Original-Received: from localhost ([::1]:33909 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTKD3-0003Ho-Hd for ged-emacs-devel@m.gmane.org; Mon, 07 Oct 2013 19:27:29 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38461) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTKCv-0003GV-2n for emacs-devel@gnu.org; Mon, 07 Oct 2013 19:27:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VTKCn-0000iZ-Gy for emacs-devel@gnu.org; Mon, 07 Oct 2013 19:27:21 -0400 Original-Received: from mail-ea0-x232.google.com ([2a00:1450:4013:c01::232]:45704) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VTKCn-0000iR-A4 for emacs-devel@gnu.org; Mon, 07 Oct 2013 19:27:13 -0400 Original-Received: by mail-ea0-f178.google.com with SMTP id a15so3602738eae.37 for ; Mon, 07 Oct 2013 16:27:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=n6oeNagY3cJA214KwKer7FLgVIxKlOPIp0aDjx1iocU=; b=v7HhozlIL2lBItLyoCG+XI07BhW3grQ/wm1h5PBTOZpPMhr247IOQg8oBiEuT8qgn8 Ts/JWmkr31+imj3iTGLj83Aopvc0X95sp0YqG8BJAKKOnEe2aLJQ7wR3TwFiuWAv6IW7 XKTirqzjLMvgalw4S0mTn5aBf3wepDfCT600r8DUtuw6pmYu7p5dYfCJuLjaBko8zPHV pYdBhQEB6chY+KUwCYbaxYrGVGsYl4YkAqo1RENSzFt6Bw0cX44d3tkG/ywiYj7sdrJH Ej7izv6lDouHpGxM/OSmdAFFii1el46J4pD8H9m1OiafQCK57EEkAGtJwt5s0UZITdr9 nmdA== X-Received: by 10.15.64.1 with SMTP id n1mr53689943eex.15.1381188432281; Mon, 07 Oct 2013 16:27:12 -0700 (PDT) Original-Received: from [192.168.10.2] (93-113-74.netrun.cytanet.com.cy. [93.109.113.74]) by mx.google.com with ESMTPSA id v8sm68679299eeo.12.1969.12.31.16.00.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Oct 2013 16:27:11 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:4013:c01::232 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:163982 Archived-At: On 07.10.2013 18:22, Stefan Monnier wrote: >>> +# FIXME: is this really valid Ruby? Isn't the newline after "foo" treated as >>> +# an implicit semi-colon? >>> foo >>> .bar >> It is, I guess it's the main exception to the newline termination rule. > > Is the newline termination rule documented somewhere? All I could find > was discussions about the style, but no definitive clear definition of > when a newline is treated as a semi-colon. This is the best I'm aware of: http://whitequark.org/blog/2013/04/01/ruby-hacking-guide-ch-11-finite-state-lexer/ (search for "Line-break handling"). I don't see the exception mentioned. > Anyway, you can adjust ruby-smie--implicit-semi-p to reflect the "rule". Done, seems to work.