From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Adam Sokolnicki Newsgroups: gmane.emacs.bugs Subject: bug#16182: Date: Fri, 20 Dec 2013 13:44:32 +0100 Message-ID: References: <874n66byoo.fsf@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e01182c7ec934e604edf6a339 X-Trace: ger.gmane.org 1387543516 12285 80.91.229.3 (20 Dec 2013 12:45:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 20 Dec 2013 12:45:16 +0000 (UTC) To: 16182@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Dec 20 13:45:20 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1VtzSB-00069A-FO for geb-bug-gnu-emacs@m.gmane.org; Fri, 20 Dec 2013 13:45:19 +0100 Original-Received: from localhost ([::1]:49245 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtzSB-0002S5-5D for geb-bug-gnu-emacs@m.gmane.org; Fri, 20 Dec 2013 07:45:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34333) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtzS2-0002OS-5k for bug-gnu-emacs@gnu.org; Fri, 20 Dec 2013 07:45:16 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VtzRv-0002xZ-QD for bug-gnu-emacs@gnu.org; Fri, 20 Dec 2013 07:45:10 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:45666) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VtzRv-0002xC-NY for bug-gnu-emacs@gnu.org; Fri, 20 Dec 2013 07:45:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1VtzRu-0008Lm-HR for bug-gnu-emacs@gnu.org; Fri, 20 Dec 2013 07:45:03 -0500 X-Loop: help-debbugs@gnu.org In-Reply-To: <874n66byoo.fsf@yandex.ru> Resent-From: Adam Sokolnicki Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 20 Dec 2013 12:45:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 16182 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 16182-submit@debbugs.gnu.org id=B16182.138754347732042 (code B ref 16182); Fri, 20 Dec 2013 12:45:02 +0000 Original-Received: (at 16182) by debbugs.gnu.org; 20 Dec 2013 12:44:37 +0000 Original-Received: from localhost ([127.0.0.1]:59684 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VtzRU-0008Kh-2X for submit@debbugs.gnu.org; Fri, 20 Dec 2013 07:44:36 -0500 Original-Received: from mail-oa0-f52.google.com ([209.85.219.52]:41339) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1VtzRR-0008KX-AD for 16182@debbugs.gnu.org; Fri, 20 Dec 2013 07:44:34 -0500 Original-Received: by mail-oa0-f52.google.com with SMTP id h16so2710798oag.25 for <16182@debbugs.gnu.org>; Fri, 20 Dec 2013 04:44:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=zFvke6gbVKS0g9g9UNfYDqVTC2RGJEYhfAKtoIhxU+A=; b=nuzY6tvWVq09xfMNVCFAKSga0c3QsQJR4om0azfLnkcojntRuGdH9YKbZkY0Ci7L5+ zZk7qFuvWyjTcOtucncYey2xCliVxBJceNumXLsRlbGXbzoi4NPwTSw6nzeTHvmfKhN5 rwH/CFtfW9InwQ02OZJfnfupn+1ZZsIiJylA1/gKmXA0xCwTon24B+1u8Zyl+3xMQap6 kEKsekj08jg78x6h0kZkJqvBteQZg2mMiNy8xMrP+c3v4iosrxNf9EK6QGzCHqRTKlOb Qf6KqdKKVYZch8SpPAxuJwPwOpyXRW/ZwKZnRv5v9YnPCW5HzZfgAMPQfVUqmcOysE7x gIyg== X-Received: by 10.60.33.7 with SMTP id n7mr6109310oei.25.1387543472451; Fri, 20 Dec 2013 04:44:32 -0800 (PST) Original-Received: by 10.182.105.200 with HTTP; Fri, 20 Dec 2013 04:44:32 -0800 (PST) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:82281 Archived-At: --089e01182c7ec934e604edf6a339 Content-Type: text/plain; charset=ISO-8859-1 >> When I'm breaking line on argument list it's >> because the line is too long. With indentation to the opened paren the >> line stays long despite breaking the line. > > Like Stefan suggests, if the opened paren is immediately followed by a > newline, the arguments will be indented less (but still indented by > additional two columns, compared to the beginning of the statement). I did not think about it before. It makes sense. >> I think this is how vim indents ruby code by default. > If that's true, could you point to: > > * Some other open source project or two using this style. > > * Some tutorial or step-by-step instruction for me to test this > indentation in Vim. Do I need to install anything apart from the > > base > distribution? > Suppose I have the snippet of code typed out. What do I press next? Actually that's not true. I was wrong. Sorry for the confusion. >> I you ask me emacs can only support the indentation to the beginning >> of the statement. > > I don't think it's sufficient, by itself. > > Take this example: > > current_user.statuses.find(params[:id]).update({ > user: current_user, > text: params[:status] > }) > > Suppose `update' accepted a second argument, and we wanted to pass it > here, on the next line after the hash. Which column would it be indented > to? 0? Yes it's not sufficient. --089e01182c7ec934e604edf6a339 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 
 
>> When I'm breaking line o=
n argument list it's
>> because the line is too long. With indentation to the opened paren=
 the
>> line stays long despite breaking the line.
>
> Like Stefan suggests, if the opened paren is immediately followed by a
> newline, the arguments will be indented less (but still indented by
> additional two columns, compared to the beginning of the statement).

I did not think about it before. It makes sense.

>> I think this is how vim indents ruby code by default.

> If that's true, could you point to:
>
> * Some other open source project or two using this style.
>
> * Some tutorial or step-by-step instruction for me to test this
>   indentation in Vim. Do I need to install anything apart from the >=
; > base
>   distribution?
>   Suppose I have the snippet of code typed out. What do I press next?

Actually that's not true. I was wrong. Sorry for the confusion.

>> I you ask me emacs can only support the indentation to the beginni=
ng
>> of the statement.
>
> I don't think it's sufficient, by itself.
>
> Take this example:
>
> current_user.statuses.find(params[:id]).update({
>   user: current_user,
>   text: params[:status]
> })
>
> Suppose `update' accepted a second argument, and we wanted to pass=
 it
> here, on the next line after the hash. Which column would it be indent=
ed
> to? 0?

Yes it's not sufficient.
=A0



--089e01182c7ec934e604edf6a339--