unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: 61017-done@debbugs.gnu.org
Subject: bug#61017: 29.0.60; ruby-ts-mode indents class between two lines incorrectly
Date: Wed, 25 Jan 2023 17:23:06 +0200	[thread overview]
Message-ID: <684b7942-c219-26fc-0971-6662feca9231@yandex.ru> (raw)
In-Reply-To: <CAHyO48x=6YDKegQiWCyjVhV-pRhBjf8HLXg00WCjKS=QwT0KXA@mail.gmail.com>

On 25/01/2023 16:22, Aaron Jensen wrote:
> On Tue, Jan 24, 2023 at 11:00 PM Dmitry Gutov<dgutov@yandex.ru>  wrote:
>> On 25/01/2023 02:45, Aaron Jensen wrote:
>>
>>>>>> Is it enough of an improvement?
>>>>> That seems to make indentation after an open def not happen:
>>>>>
>>>>> def foo
>>>>> bar
>>>>> end
>>>> Not sure what you mean. Is that an example with an "open def"? "end"
>>>> seems to be closing it. In the final state, it indents correctly here.
>>> Sorry, that's what I meant. If I do type exactly that and do not
>>> reindent, I end up with that though (closing with the end does not
>>> cause the previous line to reindent)
>> All right.
>>
>> But if the proposed patch doesn't make things worse for this example, we
>> might as well install it. Because this "unclosed def" case is distinct
>> from the one you filed this bug report regarding.
> Sounds good to me.

And done. Thanks for testing.






      reply	other threads:[~2023-01-25 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23  4:33 bug#61017: 29.0.60; ruby-ts-mode indents class between two lines incorrectly Aaron Jensen
2023-01-23 21:28 ` Dmitry Gutov
2023-01-24 14:17   ` Aaron Jensen
2023-01-24 18:53     ` Dmitry Gutov
2023-01-25  0:45       ` Aaron Jensen
2023-01-25  4:00         ` Dmitry Gutov
2023-01-25 14:22           ` Aaron Jensen
2023-01-25 15:23             ` Dmitry Gutov [this message]

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=684b7942-c219-26fc-0971-6662feca9231@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=61017-done@debbugs.gnu.org \
    --cc=aaronjensen@gmail.com \
    /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).