all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 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: Tue, 13 Mar 2018 21:49:47 -0400	[thread overview]
Message-ID: <877eqfxw78.fsf@gmail.com> (raw)
In-Reply-To: <CAArVCkQRs3FhD6GPfpYZaWyP7aH8oONQ_Q=HoRO0Pvdok0DYAQ@mail.gmail.com> (Philipp Stephani's message of "Sun, 27 Nov 2016 20:38:42 +0000")

tags 25030 + wontfix
quit

Philipp Stephani <p.stephani2@gmail.com> writes:

> 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.

Since there's been no further movement on this, I'm closing as wontfix.





  reply	other threads:[~2018-03-14  1:49 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
2018-03-14  1:49   ` Noam Postavsky [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877eqfxw78.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=25030@debbugs.gnu.org \
    --cc=bauer.klaus.dieter@gmail.com \
    --cc=p.stephani2@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.