From: Lars Ingebrigtsen <larsi@gnus.org>
To: Campbell Barton <ideasman42@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs Lisp code formatting
Date: Thu, 04 Nov 2021 06:47:47 +0100 [thread overview]
Message-ID: <878ry4jwu4.fsf@gnus.org> (raw)
In-Reply-To: <b29c65fb-6f0b-e727-b4e1-4faa9c2ec374@gmail.com> (Campbell Barton's message of "Thu, 4 Nov 2021 11:31:40 +1100")
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.
> 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.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-11-04 5:47 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 [this message]
2021-11-04 6:51 ` Campbell Barton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878ry4jwu4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=ideasman42@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.