GNU bug report logs - #51312
29.0.50; Indenting vectors with leading spaces errors out

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 51312 in the body.
You can then email your comments to 51312 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 29.0.50; Indenting vectors with leading spaces errors out
Date: Thu, 21 Oct 2021 05:03:53 +0200

Trying to use the newish space-after-parenthesis syntax errors out when
you hit tab on the second line:

[ :foo :zot
      :bar]

forward-sexp: Scan error: "Containing expression ends prematurely", 1, 1



In GNU Emacs 29.0.50 (build 39, x86_64-pc-linux-gnu, GTK+ Version 3.24.30, cairo version 1.16.0)
 of 2021-10-20 built on elva
Repository revision: 62591c164cd6d0b0555e11b160ffa81bd3bb010f
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
System Description: Debian GNU/Linux bookworm/sid

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #8 received at 51312 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>, "51312 <at> debbugs.gnu.org"
 <51312 <at> debbugs.gnu.org>
Subject: RE: [External] : bug#51312: 29.0.50; Indenting vectors with leading
 spaces errors out
Date: Thu, 21 Oct 2021 04:59:01 +0000

> Trying to use the newish space-after-parenthesis syntax...

Newish?  Or "some time back", as you said in emacs-devel?

Where is that convention documented?  Is it in
(elisp) Coding Conventions perhaps?  I don't have
Emacs 28, and I don't see it there in 27.2.

The only thing about parens I see in that node is
this, which really was established some time back:

 "Don't make a habit of putting close-parentheses
  on lines by themselves; Lisp programmers find
  this disconcerting."

FWIW, I'd guess that Lisp programmers might find
your newish convention disconcerting.  Is there
a community of them that use it, or is it just a
newish eureka someone had?

If the aim is just to work around poor indentation
then I'd say it's the wrong solution for that.

If the aim is just to indicate that the sexp isn't
evaluated (it's "data") then the quote or backquote
does that, no?  Doesn't seem very lispy, to me.

Just one somewhat disconcerted Lisp programmer.

Message #11 received at 51312 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Lars Ingebrigtsen <larsi <at> gnus.org>, 51312 <at> debbugs.gnu.org
Subject: Re: bug#51312: 29.0.50; Indenting vectors with leading spaces errors
 out
Date: Thu, 21 Oct 2021 11:06:23 +0200

[Message part 1 (text/plain, inline)]

> Trying to use the newish space-after-parenthesis syntax errors out when
> you hit tab on the second line:
>
> [ :foo :zot
>        :bar]
>
> forward-sexp: Scan error: "Containing expression ends prematurely", 1, 1

Can you try the attached patch?

Thanks, martin

[lisp-mode.el.diff (text/x-patch, attachment)]

Message #14 received at 51312 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 51312 <at> debbugs.gnu.org
Subject: Re: bug#51312: 29.0.50; Indenting vectors with leading spaces
 errors out
Date: Thu, 21 Oct 2021 15:09:37 +0200

martin rudalics <rudalics <at> gmx.at> writes:

> Can you try the attached patch?

Thanks; that fixes the problem.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Message #17 received at 51312 <at> debbugs.gnu.org (full text, mbox):

From: martin rudalics <rudalics <at> gmx.at>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 51312 <at> debbugs.gnu.org
Subject: Re: bug#51312: 29.0.50; Indenting vectors with leading spaces errors
 out
Date: Fri, 22 Oct 2021 11:05:09 +0200

close 51312 28.1
quit

>> Can you try the attached patch?
>
> Thanks; that fixes the problem.

Installed.  Bug closed.

martin

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.