From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Philipp Stephani" <p.stephani2@gmail.com>,
"Noam Postavsky" <npostavs@gmail.com>,
43329@debbugs.gnu.org, "João Távora" <joaotavora@gmail.com>
Subject: bug#43329: 28.0.50; Incorrect indentation for variables starting with `def' in let form
Date: Wed, 13 Oct 2021 21:23:33 +0200 [thread overview]
Message-ID: <877deg3f0q.fsf@gnus.org> (raw)
In-Reply-To: <87een5h9u8.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 13 Sep 2020 19:20:47 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> So 34 in-tree functions that start with "def", but an unknown number of
> macros. That's not a lot, and I think we should add indent specs to all
> of them, including the macros.
I've now gone through all the functions that have names that start with
"def" and marked the ones that should have `defun' indent explicitly.
I'll do the macros next, and then we can remove the heuristic.
This will change how out-of-tree code indents, though. This can be
fixed by out-of-tree packages doing markup, but is there some way we can
make the transition kinder? (I don't think so, though.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-13 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 10:10 bug#43329: 28.0.50; Incorrect indentation for variables starting with `def' in let form Philipp Stephani
2020-09-11 10:26 ` Lars Ingebrigtsen
2020-09-11 16:35 ` Noam Postavsky
2020-09-12 11:57 ` Lars Ingebrigtsen
2020-09-12 15:48 ` Stefan Monnier
2020-09-13 12:44 ` Lars Ingebrigtsen
2020-09-13 15:24 ` Stefan Monnier
2020-09-13 17:20 ` Lars Ingebrigtsen
2021-10-13 19:23 ` Lars Ingebrigtsen [this message]
2021-10-18 8:00 ` bug#43329: bug#33301: 27.0.50; broken elisp indentation for non-definition symbols starting with "def.." 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877deg3f0q.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43329@debbugs.gnu.org \
--cc=joaotavora@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--cc=p.stephani2@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 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.