From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp code formatting Date: Mon, 08 Nov 2021 10:59:33 +0200 Organization: LINKOV.NET Message-ID: <86bl2v3tvu.fsf@mail.linkov.net> References: <87mtmmlgr6.fsf@gnus.org> <87lf23o5qh.fsf@gnus.org> <86o86x2jmk.fsf@mail.linkov.net> <87pmrdrmri.fsf@gnus.org> <86r1bsjglm.fsf@mail.linkov.net> <87r1brekup.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35660"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Nov 08 10:16:34 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mk0lV-00096t-Qs for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Nov 2021 10:16:33 +0100 Original-Received: from localhost ([::1]:49674 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mk0lU-0006Xu-Cd for ged-emacs-devel@m.gmane-mx.org; Mon, 08 Nov 2021 04:16:32 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:42052) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mk0Zq-0002d8-KT for emacs-devel@gnu.org; Mon, 08 Nov 2021 04:04:31 -0500 Original-Received: from relay11.mail.gandi.net ([217.70.178.231]:36109) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mk0Zl-0002by-9V for emacs-devel@gnu.org; Mon, 08 Nov 2021 04:04:30 -0500 Original-Received: (Authenticated sender: juri@linkov.net) by relay11.mail.gandi.net (Postfix) with ESMTPSA id 0F709100002; Mon, 8 Nov 2021 09:04:19 +0000 (UTC) In-Reply-To: <87r1brekup.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 07 Nov 2021 22:06:54 +0100") Received-SPF: pass client-ip=217.70.178.231; envelope-from=juri@linkov.net; helo=relay11.mail.gandi.net X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:279028 Archived-At: >> 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.