From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Emacs Lisp code formatting Date: Sun, 07 Nov 2021 22:06:54 +0100 Message-ID: <87r1brekup.fsf@gnus.org> References: <87mtmmlgr6.fsf@gnus.org> <87lf23o5qh.fsf@gnus.org> <86o86x2jmk.fsf@mail.linkov.net> <87pmrdrmri.fsf@gnus.org> <86r1bsjglm.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16757"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Nov 07 22:08:09 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 1mjpOb-0004AH-3n for ged-emacs-devel@m.gmane-mx.org; Sun, 07 Nov 2021 22:08:09 +0100 Original-Received: from [::1] (port=52552 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mjpOY-0005ea-CP for ged-emacs-devel@m.gmane-mx.org; Sun, 07 Nov 2021 16:08:06 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:44152) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mjpNW-0004yA-BY for emacs-devel@gnu.org; Sun, 07 Nov 2021 16:07:02 -0500 Original-Received: from [2a01:4f9:2b:f0f::2] (port=56824 helo=quimby.gnus.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mjpNU-0002Yu-Cl for emacs-devel@gnu.org; Sun, 07 Nov 2021 16:07:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnus.org; s=20200322; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=ERzu6WRJstdqdgBdVcSL8DF/G2ip2p+74dteGoONl10=; b=t7pYeMmG9qe1w//HsHZebI+aUK SEoW07Lc7V0xAeqJQmF5GmCgieovybYUelUdGg8BzeK//FpyiTh792Y3RWDQIDcRHkRC1oluSj+Gz S7pUIZSWO9BjXphOs8jH7UoJYCEBdI/+FxmxjTyJw26oYFb06xg5220srwezdMHkzbVA=; Original-Received: from [84.212.220.105] (helo=elva) by quimby.gnus.org with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mjpNP-0003jw-5c; Sun, 07 Nov 2021 22:06:58 +0100 X-Now-Playing: Mofaya!'s _Like One Long Dream_: "The Tank" In-Reply-To: <86r1bsjglm.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 07 Nov 2021 19:27:33 +0200") X-Host-Lookup-Failed: Reverse DNS lookup failed for 2a01:4f9:2b:f0f::2 (failed) Received-SPF: pass client-ip=2a01:4f9:2b:f0f::2; envelope-from=larsi@gnus.org; helo=quimby.gnus.org X-Spam_score_int: -35 X-Spam_score: -3.6 X-Spam_bar: --- X-Spam_report: (-3.6 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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:278988 Archived-At: Juri Linkov writes: > 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. > Would it be possible to do such a thing and keep it uncomplicated? > For example, to ensure there is no newline after if/when/unless, but insert > a newline after its condition, unless it's short enough to fit on one line, > etc. Sure, doing it that way around would produce results that could be used when editing code, too (which was not part of what I was trying to do here), but my guess is that it'd be more complicated. But I haven't tried -- if you want to rewrite the code to do it that way around, please do so. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no