unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Campbell Barton <ideasman42@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs Lisp code formatting
Date: Thu, 4 Nov 2021 17:51:44 +1100	[thread overview]
Message-ID: <23fdeb99-e042-2f59-d4e4-7f5b2dea1381@gmail.com> (raw)
In-Reply-To: <878ry4jwu4.fsf@gnus.org>

On 11/4/21 16:47, Lars Ingebrigtsen wrote:
> Campbell Barton <ideasman42@gmail.com> writes:
> 
>> You could scan external `require' calls, but this means parsing many
>> files to extract the information you need.
> 
> Like with indentation, I think we can assume that the source has been
> loaded.

Not sure what you mean exactly, while developing packages 
functions/macros may change, so I don't think it's reasonable to assume 
the evaluated state in emacs has loaded into memory is up to date.
In general it may be useful to auto-format code that hasn't been 
evaluated too.

>> Note that I use auto-format on save for all my packages (full
>> auto-formatting, not just auto-indent), and personally find it great,
>> but as far as I know I'm the only person doing this.
> 
> I think auto-formatting would be a more complicated thing than a pp for
> code -- it would need to preserve comments, for instance.  A pp for code
> doesn't have to worry about things like that.

For sure, even so, I think getting an initial auto-formatter working is 
a weekend project, getting all the details figured out is a bigger task 
though.

I get the impression most elisp developers prefer to manually format 
their code and use auto-indentation.

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.



  reply	other threads:[~2021-11-04  6:51 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 [this message]
2021-11-04  8:39           ` Helmut Eller
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

  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=23fdeb99-e042-2f59-d4e4-7f5b2dea1381@gmail.com \
    --to=ideasman42@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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 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).