From: Philipp Stephani <p.stephani2@gmail.com>
To: Klaus-Dieter Bauer <bauer.klaus.dieter@gmail.com>, 25030@debbugs.gnu.org
Subject: bug#25030: 25.1; Unexpected indentation and syntax-highlighting in `emacs-lisp-mode'
Date: Sun, 27 Nov 2016 20:38:42 +0000 [thread overview]
Message-ID: <CAArVCkQRs3FhD6GPfpYZaWyP7aH8oONQ_Q=HoRO0Pvdok0DYAQ@mail.gmail.com> (raw)
In-Reply-To: <CANtbJLEtLvA76RM5sJGofNGq14KbeqkX6_7Dkq5aB55iVJtrZA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
Klaus-Dieter Bauer <bauer.klaus.dieter@gmail.com> schrieb am Sa., 26. Nov.
2016 um 00:13 Uhr:
> Hello!
>
> In `emacs-lisp-mode', the counting of the nesting level of forms seems
> to be broken in some subtle way. Consider e.g.
>
> (form
> (
> ) WEIRD HIGHLIGHT
> x) ;; Unexepected Indentation
>
> It looks like "WEIRD HIGHLIGHT" is wrongly highlighted as junk after a
> surplus closing parenthesis, and the subsequent form is also weirdly
> indented.
>
>
This is working as intended (i.e. not a bug). Lisp-mode explicitly tests
for this. When you hover over the highlighted part, you get a tooltip
"Hidden behind deeper element; move to another line?"
While not a syntax error, there's such a strong convention to avoid such
formatting that the Lisp modes warn unconditionally about it.
[-- Attachment #2: Type: text/html, Size: 2463 bytes --]
next prev parent reply other threads:[~2016-11-27 20:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 23:12 bug#25030: 25.1; Unexpected indentation and syntax-highlighting in `emacs-lisp-mode' Klaus-Dieter Bauer
2016-11-27 20:38 ` Philipp Stephani [this message]
2018-03-14 1:49 ` Noam Postavsky
2018-03-18 19:53 ` Andy Moreton
2018-03-18 21:32 ` Drew Adams
2018-03-19 23:53 ` Noam Postavsky
2018-03-20 0:23 ` Andy Moreton
2018-03-20 1:35 ` Drew Adams
2018-03-20 2:14 ` Noam Postavsky
2018-03-20 12:55 ` Andy Moreton
2018-03-22 2:38 ` Noam Postavsky
2022-02-12 8:54 ` bug#25030: elisp: highlighting of unexpected indentation should use separate face from highlight of error functions 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='CAArVCkQRs3FhD6GPfpYZaWyP7aH8oONQ_Q=HoRO0Pvdok0DYAQ@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=25030@debbugs.gnu.org \
--cc=bauer.klaus.dieter@gmail.com \
/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).