unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs Lisp code formatting
Date: Mon, 08 Nov 2021 10:59:33 +0200	[thread overview]
Message-ID: <86bl2v3tvu.fsf@mail.linkov.net> (raw)
In-Reply-To: <87r1brekup.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 07 Nov 2021 22:06:54 +0100")

>> Oh, I thought it works like 'pp-buffer' - just by adding/removing newlines
>> (because everything else is handled by 'indent-sexp').
>
> Since we're being passed a sexp, I thought it would be easier to just
> work on the sexp instead of inserting it into the buffer and then
> partially re-parse it to get at the symbol properties.  pp-buffer
> doesn't have that problem, since it basically doesn't care about any of
> that.

BTW, it seems the new pp-emacs-lisp-code is not yet used to pp
the variable values by 'C-h v'?  Especially, hook's lambdas/closures
could benefit from prettier printing.



  reply	other threads:[~2021-11-08  8:59 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
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 [this message]
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=86bl2v3tvu.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --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).