From: Drew Adams <drew.adams@oracle.com>
To: Andy Moreton <andrewjmoreton@gmail.com>, 25030@debbugs.gnu.org
Subject: bug#25030: 25.1; Unexpected indentation and syntax-highlighting in `emacs-lisp-mode'
Date: Sun, 18 Mar 2018 14:32:16 -0700 (PDT) [thread overview]
Message-ID: <11b10aaf-d454-4c83-b775-e45f2d250c37@default> (raw)
In-Reply-To: <868taptb26.fsf@gmail.com>
> This may not be a bug, but it is certainly a mis-feature.
>
> Warning should be reserved for syntax which may have unintended or
> surprising semantics. Indentation that does not follow a convention is
> not wrong either systacically or semantically.
>
> Please remove this broken mis-feature.
I agree that warnings are not for such things. Emacs too
often uses "warnings" for things that are not warnings.
On the other hand, I do appreciate this highlighting, though
at first I didn't think I would. I think a different face
should be used for this - this is *warning* about anything.
That would let users control whether it is actually highlighted
(e.g., by resetting the face attributes to nil).
This is a duplicate of bug #18163, BTW. And the thread
repeats that one...
next prev parent reply other threads:[~2018-03-18 21:32 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
2018-03-18 19:53 ` Andy Moreton
2018-03-18 21:32 ` Drew Adams [this message]
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=11b10aaf-d454-4c83-b775-e45f2d250c37@default \
--to=drew.adams@oracle.com \
--cc=25030@debbugs.gnu.org \
--cc=andrewjmoreton@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.