GNU bug report logs -
#40059
lisp-mode indentation not aligned vertically
Previous Next
Reported by: Spenser Truex <lists <at> spensertruex.com>
Date: Sat, 14 Mar 2020 04:57:01 UTC
Severity: normal
Tags: moreinfo, unreproducible
Done: Stefan Kangas <stefan <at> marxist.se>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Sun, 03 May 2020 03:13:08 +0200
with message-id <87r1w13job.fsf <at> stefankangas.se>
and subject line Re: bug#40059: lisp-mode indentation not aligned vertically
has caused the debbugs.gnu.org bug report #40059,
regarding lisp-mode indentation not aligned vertically
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
40059: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40059
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
This code sample demonstrates what I consider to be a bug in the
lisp-mode indentation.
Here is a very simple example:
(:a :b
:c
:d
:e)
Here it is in an actual use case (defining Common Lisp packages)
(defpackage :example
(:use :cl)
;; Here is the weird part:
(:export :thing1
:thing2
:thing3
:thing4
:thing5))
A sane, non-buggy indentation would be this:
(defpackage :example
(:use :cl)
;; These are aligned vertically:
(:export :thing1
:thing2
:thing3
:thing4
:thing5))
This seems to be primarily caused by the keyword argument as the first
element of the unquoted list.
This is especially an issue if using aggressive formatting like
aggressive indent mode. <https://github.com/Malabarba/aggressive-indent-mode/issues/122>
--
Spenser Truex
spensertruex.com
SFSU Computer Science
[Message part 3 (message/rfc822, inline)]
martin rudalics <rudalics <at> gmx.at> writes:
>> Here is my M-x version
>> GNU Emacs 27.0.90 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.14) of 2020-03-07
>
> Have you tried with emacs -Q?
More information was requested, but none was given within 6 weeks, so
I'm closing this bug. It was already tagged unreproducible.
If this is still an issue, please reply to this email (use "Reply to
all" in your email client) and we can reopen the bug report.
Best regards,
Stefan Kangas
This bug report was last modified 5 years and 73 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.