From: Ryan Thompson <rct@thompsonclan.org>
To: Philipp Stephani <p.stephani2@gmail.com>, 27920@debbugs.gnu.org
Subject: bug#27920: 25.2; Elisp indentation breaks when function docstring matches "^("
Date: Wed, 02 Aug 2017 21:39:58 +0000 [thread overview]
Message-ID: <CAHCt_aZ6J=OHVFCpEzzQdiOKcLrW90qhK3+H539VrmjnFAVzGQ@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkRv_5ueihL2Yr86dfnudg5tG+p0F=+AGPPxLFsP8H_NKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
Ok, that's good to know. That page claims that Emacs "highlights confusing
opening delimiters (those that ought to be quoted) in bold red", but I'm
not seeing that in this case. Is there some setting to enable this, or is
it likely that some other elisp package I have installed is interfering
with this highlighting? Or can Emacs not catch this kind of misplaced paren
in a string?
On Wed, Aug 2, 2017 at 2:34 PM Philipp Stephani <p.stephani2@gmail.com>
wrote:
>
>
> Ryan <rct@thompsonclan.org> schrieb am Mi., 2. Aug. 2017 um 18:57 Uhr:
>
>>
>> When editing Emacs Lisp code, if I write a function whose docstring
>> contains a line beginning with an open paren, Emacs refuses to
>> auto-indent any line in the function body.
>
>
> Emacs by default doesn't accept opening parentheses in the first column
> that don't start a top-level definition. See
> https://www.gnu.org/software/emacs/manual/html_node/emacs/Left-Margin-Paren.html
> .
>
[-- Attachment #2: Type: text/html, Size: 1598 bytes --]
next prev parent reply other threads:[~2017-08-02 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 16:45 bug#27920: 25.2; Elisp indentation breaks when function docstring matches "^(" Ryan
2017-08-02 21:34 ` Philipp Stephani
2017-08-02 21:39 ` Ryan Thompson [this message]
2017-08-02 21:45 ` Glenn Morris
2017-08-04 17:24 ` Stefan Monnier
2017-11-29 2:32 ` Noam Postavsky
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='CAHCt_aZ6J=OHVFCpEzzQdiOKcLrW90qhK3+H539VrmjnFAVzGQ@mail.gmail.com' \
--to=rct@thompsonclan.org \
--cc=27920@debbugs.gnu.org \
--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 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).