From: Helmut Eller <eller.helmut@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Emacs Lisp code formatting
Date: Thu, 04 Nov 2021 09:39:57 +0100 [thread overview]
Message-ID: <m27ddoxqjm.fsf@gmail.com> (raw)
In-Reply-To: 23fdeb99-e042-2f59-d4e4-7f5b2dea1381@gmail.com
On Thu, Nov 04 2021, Campbell Barton wrote:
> I get the impression most elisp developers prefer to manually format
> their code and use auto-indentation.
If there isn't a decent tool to do it automatically, that would be no
surprise.
Maybe C-M-q (indent-pp-sexp) should do bit more than just indent every
line. I certainly would like it to break long lines automatically.
Or maybe code formatting could be integrated in elint.
The other obvious candidate is the byte-compiler. But the compiler seems
to be so complicated already, that nobody wants to touch it.
> Auto formatters are becoming more popular in other languages though,
> clang-format (C/C++), black (for Python)... once you're used to
> running them automatically on save, it feels like a step backwards not
> to have this feature available.
On that topic: I find it rather unsatisfactory that GNU indent doesn't
seem to be used much. Not even by the Emacs developers.
Helmut
next prev parent reply other threads:[~2021-11-04 8:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 15:27 Emacs Lisp code formatting Lars Ingebrigtsen
2021-11-02 23:31 ` Campbell Barton
2021-11-03 23:59 ` Lars Ingebrigtsen
2021-11-04 0:31 ` Campbell Barton
2021-11-04 5:47 ` Lars Ingebrigtsen
2021-11-04 6:51 ` Campbell Barton
2021-11-04 8:39 ` Helmut Eller [this message]
2021-11-04 16:51 ` Lars Ingebrigtsen
2021-11-04 23:34 ` Lars Ingebrigtsen
2021-11-06 19:01 ` Juri Linkov
2021-11-06 21:34 ` Lars Ingebrigtsen
2021-11-07 17:27 ` Juri Linkov
2021-11-07 21:06 ` Lars Ingebrigtsen
2021-11-08 8:59 ` Juri Linkov
2021-11-08 9:06 ` Lars Ingebrigtsen
2021-11-07 1:37 ` Michael Heerdegen
2021-11-07 1:45 ` Lars Ingebrigtsen
2021-11-07 2:22 ` Michael Heerdegen
2021-11-07 2:47 ` 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=m27ddoxqjm.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
/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.