unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Aaron Jensen <aaronjensen@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 54702@debbugs.gnu.org
Subject: bug#54702: 29.0.50; ruby-mode indentation: endless methods
Date: Fri, 16 Dec 2022 11:24:23 -0500	[thread overview]
Message-ID: <CAHyO48wJqJf8T7ZWS_55Tmtic09T_JjtSEsG660=i_vu2LXZOg@mail.gmail.com> (raw)
In-Reply-To: <0d8a9e9d-2c8f-6282-63da-e4af020fea8d@yandex.ru>

On Fri, Dec 16, 2022 at 11:15 AM Dmitry Gutov <dgutov@yandex.ru> wrote:
>
> On 16/12/2022 15:12, Aaron Jensen wrote:
> > On Fri, Dec 16, 2022 at 7:31 AM Dmitry Gutov <dgutov@yandex.ru> wrote:
> >>
> >> Right, thanks. See the attached updated patch.
> >
> > That works. I found another inconsistency related to the other issue I
> > just opened:
> >
> > def foo(
> >        baz,
> >        bar
> > ) = what
> >
> > def foo(
> >        baz,
> >        bar
> >      )
> >    hello
> > end
> >
> > I don't know who is savage enough to do a multi-line endless method
> > like that, but when it's done the closing paren should probably be
> > consistent w/ the regular method closing paren.
>
> Thank you, savage indeed.
>
> Okay, here's an alternative version -- this was a pain to implement.
>
> Would be much easier if we just decided to change the args indentation
> without support for the current one.

It works for me w/ that example.

You won't find me resisting getting rid of the old way. Lining up
against the method name is a fairly clear UX issue, in my opinion. I
don't know that it's something I see outside of Emacs, and my guess is
that it was influenced by Lisp rather than being influenced by Ruby
and its community.

Aaron





  reply	other threads:[~2022-12-16 16:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  2:03 bug#54702: 29.0.50; ruby-mode indentation: endless methods Aaron Jensen
2022-04-27  2:44 ` Dmitry Gutov
2022-04-27 23:58   ` Aaron Jensen
2022-12-16  0:33     ` Dmitry Gutov
2022-12-16  5:07       ` Aaron Jensen
2022-12-16 12:31         ` Dmitry Gutov
2022-12-16 12:40           ` Dmitry Gutov
2022-12-16 14:49             ` Eli Zaretskii
2022-12-18 12:06               ` Dmitry Gutov
2022-12-18 15:42                 ` Aaron Jensen
2022-12-16 13:12           ` Aaron Jensen
2022-12-16 16:15             ` Dmitry Gutov
2022-12-16 16:24               ` Aaron Jensen [this message]
2022-12-16 17:49                 ` Dmitry Gutov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHyO48wJqJf8T7ZWS_55Tmtic09T_JjtSEsG660=i_vu2LXZOg@mail.gmail.com' \
    --to=aaronjensen@gmail.com \
    --cc=54702@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).