From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: robin.neatherway@gmail.com, larsi@gnus.org,
monnier@iro.umontreal.ca, 20846@debbugs.gnu.org
Subject: bug#20846: 24.4; Electric-indent-mode does not call indent-line-function after hitting RET inside a comment
Date: Fri, 28 May 2021 17:04:05 +0300 [thread overview]
Message-ID: <83y2bz6jl6.fsf@gnu.org> (raw)
In-Reply-To: <5b9559aa-f6be-f3a6-72db-05e72f7f3bdf@yandex.ru> (message from Dmitry Gutov on Fri, 28 May 2021 16:35:51 +0300)
> Cc: robin.neatherway@gmail.com, larsi@gnus.org, monnier@iro.umontreal.ca,
> 20846@debbugs.gnu.org
> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Fri, 28 May 2021 16:35:51 +0300
>
> > because my
> > reading of it is that it clearly states that auto-indentation inside
> > strings is generally impossible, and expects the implementations to
> > behave like that.
>
> Consider this from a design POV: if all indentation functions were
> supposed to return 'noindent when inside a string or comment,
> indent-for-tab-command could do that check itself and avoid calling
> indent-line-function entirely in that case.
Not if calling the function in that case was a rare exception, which
is what my interpretation of that text suggests.
> And also that #'indent-relative (the default value of
> indent-line-function) does indent inside strings and comments.
Documentation should be clear enough to not require the reader to
consider examples in order to understand it.
next prev parent reply other threads:[~2021-05-28 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 15:40 bug#20846: 24.4; Electric-indent-mode does not call indent-line-function after hitting RET inside a comment Robin Neatherway
2015-06-18 15:50 ` bug#20846: Reproduction instruction correction Robin Neatherway
2021-05-26 23:32 ` bug#20846: 24.4; Electric-indent-mode does not call indent-line-function after hitting RET inside a comment Lars Ingebrigtsen
2021-05-27 7:00 ` Eli Zaretskii
2021-05-27 23:43 ` Lars Ingebrigtsen
2021-05-28 5:49 ` Eli Zaretskii
2021-05-28 12:56 ` Dmitry Gutov
2021-05-28 13:06 ` Eli Zaretskii
2021-05-28 13:35 ` Dmitry Gutov
2021-05-28 14:04 ` Eli Zaretskii [this message]
2021-05-28 14:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-28 14:16 ` Eli Zaretskii
2021-05-29 2:26 ` Lars Ingebrigtsen
2021-05-29 13:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-05-30 4:14 ` Lars Ingebrigtsen
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=83y2bz6jl6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=20846@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=robin.neatherway@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).