all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Aaron Jensen <aaronjensen@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Dmitry Gutov <dmitry@gutov.dev>, 64589@debbugs.gnu.org
Subject: bug#64589: 30.0.50; smie-config-guess can break ruby indentation
Date: Thu, 19 Oct 2023 23:39:55 -0400	[thread overview]
Message-ID: <CAHyO48zEe7N6jaFFG_7tjb-LZ5xQa2WGrv2P6Z5=Lvc6PJejLA@mail.gmail.com> (raw)
In-Reply-To: <jwv1qdq6nxk.fsf-monnier+emacs@gnu.org>

On Thu, Oct 19, 2023 at 10:15 PM Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>
> > Perhaps we'll simply end up documenting that it doesn't work for all SMIE
> > modes, just for some. And dtrt-indent will have a whitelist.
>
> It's definitely the case that it's a "best effort" kind of tool, which
> makes assumptions that don't always hold.
> Using it unconditionally like `dtrt-indent` does seems ... optimistic,
> but I'll take it as a compliment :-)
>
>
>         Stefan
>

Just to double check, the thing I found odd was that it broke some
indentation, but not all. I don't know anything about how it works or
what its impact is, but it wasn't like it disabled indentation across
the board. It just made much of the indentation stop working or break
in subtle ways.

This is what smie-config-buffer-local ends up as: ((-5 :elem basic 2))

Thanks,

Aaron





      reply	other threads:[~2023-10-20  3:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13  4:20 bug#64589: 30.0.50; smie-config-guess can break ruby indentation Aaron Jensen
2023-10-19 20:05 ` Dmitry Gutov
2023-10-19 21:41   ` Aaron Jensen
2023-10-19 23:29     ` Dmitry Gutov
2023-10-20  2:15       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-20  3:39         ` Aaron Jensen [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

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

  git send-email \
    --in-reply-to='CAHyO48zEe7N6jaFFG_7tjb-LZ5xQa2WGrv2P6Z5=Lvc6PJejLA@mail.gmail.com' \
    --to=aaronjensen@gmail.com \
    --cc=64589@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.