From: Andy Moreton <andrewjmoreton@gmail.com>
To: 25030@debbugs.gnu.org
Subject: bug#25030: 25.1; Unexpected indentation and syntax-highlighting in `emacs-lisp-mode'
Date: Tue, 20 Mar 2018 12:55:48 +0000 [thread overview]
Message-ID: <vz1woy6c3e3.fsf@gmail.com> (raw)
In-Reply-To: <CANtbJLEtLvA76RM5sJGofNGq14KbeqkX6_7Dkq5aB55iVJtrZA@mail.gmail.com>
On Mon 19 Mar 2018, Noam Postavsky wrote:
> Drew Adams <drew.adams@oracle.com> writes:
>
>>> I disagree. The interpreter and byte compiler do not care about the
>>> indentation style that you choose for your code: the syntax and
>>> semantics are unaffected.
>>>
>>> Style choices should not produce warnings. An indication that code layout
>>> is following an unusual style may be useful, but it should be optional, and
>>> it should not use the warning face (it should have a separate face that can
>>> be customised independently of the warning face).
>>
>> What Andy said. This has nothing to do with byte-compiling
>> (or interpreting, for that matter).
>
> I don't understand why you guys are all of a sudden talking about
> byte-compiling.
The point is that the unusual code layout does not cause any problems for
elisp code, and it does not matter if the code is interpreted or
byte-compiled: the result is the same, namely that indentation style has
no effect on the meaning of the code.
AndyM
next prev parent reply other threads:[~2018-03-20 12:55 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
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 [this message]
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=vz1woy6c3e3.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=25030@debbugs.gnu.org \
/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.