From: Thierry Volpiatto <thievol@posteo.net>
To: akater <nuclearspace@gmail.com>
Cc: contovob@tcd.ie, mattiase@acm.org, larsi@gnus.org, 9622@debbugs.gnu.org
Subject: bug#9622: [PATCH] Re: bug#9622: 23.3; flet indentation
Date: Thu, 30 Sep 2021 16:04:11 +0000 [thread overview]
Message-ID: <875yuiyrr8.fsf@posteo.net> (raw)
In-Reply-To: <87y27em61q.fsf@gmail.com> (akater's message of "Thu, 30 Sep 2021 15:33:53 +0000")
akater <nuclearspace@gmail.com> writes:
> Thierry Volpiatto <thievol@posteo.net> writes:
>
>> Note that using `common-lisp-indent-function` as `lisp-indent-function` in
>> emacs-27.2 make `cl-flet` and friends indent properly, with a few more
>> settings for `cl-loop` indentation it is perfect, did I miss something?
>
> In general, the languages are different and rules should be expected to
> be different. cl- indenter takes care of #(..) and so on which is
> meaningless in Elisp.
>
> I also think common-lisp-indent-function should not attempt to indent
> cl- stuff and likewise lisp-indent-function should not indent plain flet
> and so on because plain ones are “officially deprecated”.
>
> It would make more sense to have a generic sexp indenter and
> dialect-specific indenters that inherit from it. But inheritance
> practices in Emacs is in terrible shape: inheritance mechanisms have
> been reinvented in incompatible ways since forever.
Thanks for explanations, make sense.
--
Thierry
next prev parent reply other threads:[~2021-09-30 16:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <504153FB-8633-4755-A91A-DF5DD64E6FAA@acm.org>
2021-09-28 3:01 ` bug#9622: 23.3; flet indentation akater
2021-09-28 5:23 ` Lars Ingebrigtsen
2021-09-28 10:11 ` Mattias Engdegård
2021-09-28 10:35 ` Mattias Engdegård
2021-09-28 16:39 ` akater
2021-09-29 18:12 ` bug#9622: [PATCH] " akater
2021-09-30 6:37 ` Lars Ingebrigtsen
2021-09-30 8:05 ` Mattias Engdegård
2021-09-30 13:06 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-30 13:41 ` Lars Ingebrigtsen
2021-09-30 13:57 ` akater
2021-10-01 11:27 ` Lars Ingebrigtsen
2021-10-09 7:26 ` akater
2021-10-09 11:23 ` Lars Ingebrigtsen
2021-10-28 19:23 ` akater
2021-10-28 21:53 ` Lars Ingebrigtsen
2021-09-30 14:52 ` Mattias Engdegård
2021-09-30 15:11 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-30 15:23 ` Thierry Volpiatto
2021-09-30 15:33 ` akater
2021-09-30 16:04 ` Thierry Volpiatto [this message]
2021-09-30 15:25 ` Mattias Engdegård
2021-09-30 15:56 ` akater
2021-09-30 19:28 ` miha--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-30 23:23 ` akater
2021-11-08 1:13 ` Michael Heerdegen
2021-11-08 6:18 ` bug#9622: [PATCH] " akater
2021-11-08 6:38 ` Lars Ingebrigtsen
2021-11-08 6:38 ` akater
2021-11-08 6:53 ` Lars Ingebrigtsen
2021-11-08 9:36 ` akater
2021-11-09 3:25 ` Lars Ingebrigtsen
2021-11-08 16:30 ` Michael Heerdegen
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=875yuiyrr8.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=9622@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=nuclearspace@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).