unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Harald Jörg" <haj@posteo.de>,
	"Emacs Developer List" <emacs-devel@gnu.org>
Subject: Re: newline-and-indent vs. electric-indent-mode
Date: Sun, 24 Jan 2021 23:45:57 +0200	[thread overview]
Message-ID: <67c10291-6b6d-ccdc-90d0-e3e9a3967898@yandex.ru> (raw)
In-Reply-To: <jwvr1maoqoj.fsf-monnier+emacs@gnu.org>

On 24.01.2021 07:29, Stefan Monnier wrote:
>> All right, filed as bug#46064.
> 
> Thanks.
> 
>>> I think `electric-indent-mode` is annoying in any case if the
>>> indentation code disagrees with your style.
>> True, but my present complaint is about it being annoying *twice* for the
>> same line. And if it's being annoying while point is still on that line,
>> it's marginally easier to fix.
> 
> BTW, I just want to clarify that while I'm to be blamed for the current
> behavior, I'm perfectly happy if someone wants to change it.
> 
> My main goal was to consolidate all those major modes's ad-hoc
> auto-indent (typically by binding RET to `newline-and-indent`) into
> a global user config, and that's done.

I've considered what default we could change, but if we wanted to set 
electric-indent-inhibit to t by default (after resolving bug#46064), 
most/all major modes should first get electric-indent-functions similar 
to #'ruby--electric-indent-p to compensate for it, and that's a 
non-trivial effort, not to mention the change in user habits.

Though we probably could generate something based on SMIE grammar, in 
modes based on it.



  reply	other threads:[~2021-01-24 21:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 13:53 newline-and-indent vs. electric-indent-mode Harald Jörg
2021-01-22 14:49 ` Stefan Monnier
2021-01-22 15:02   ` Dmitry Gutov
2021-01-22 15:09     ` Stefan Monnier
2021-01-22 22:43       ` Dmitry Gutov
2021-01-22 22:56         ` Stefan Monnier
2021-01-22 23:00           ` Dmitry Gutov
2021-01-22 23:16             ` Stefan Monnier
2021-01-23  0:45               ` Dmitry Gutov
2021-01-23  3:16                 ` Stefan Monnier
2021-01-24  2:54                   ` Dmitry Gutov
2021-01-24  5:29                     ` Stefan Monnier
2021-01-24 21:45                       ` Dmitry Gutov [this message]
2021-01-25  1:56                   ` Madhu
2021-01-25  2:29                     ` Dmitry Gutov
2021-01-25 10:45                       ` Madhu
2021-01-25 11:59                         ` Dmitry Gutov
2021-01-25 14:36                         ` Stefan Monnier
2021-01-25 14:42                           ` Dmitry Gutov
2021-01-25 15:15                             ` Stefan Monnier
2021-01-25 20:10                               ` Rudolf Schlatte
2021-01-26  2:04                               ` Dmitry Gutov
2021-01-26  2:43                                 ` Stefan Monnier
2021-01-26 15:58                               ` martin rudalics
2021-01-25  3:33                     ` Eli Zaretskii
2021-01-22 19:33   ` Harald Jörg
2021-01-22 22:05     ` Stefan Monnier
2021-01-23  2:19       ` Harald Jörg
2021-01-23  3:29         ` Stefan Monnier
2021-01-23 16:27           ` Harald Jörg

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=67c10291-6b6d-ccdc-90d0-e3e9a3967898@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=haj@posteo.de \
    --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 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).