all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Alex <agrambot@gmail.com>, 27692@debbugs.gnu.org
Subject: bug#27692: 25.2; Indentation issue with strings in scheme mode
Date: Tue, 18 Jul 2017 22:21:31 +0530	[thread overview]
Message-ID: <ce07b297.AEQANSTVODwAAAAAAAAAAAPWRyIAAAACwQwAAAAAAAW9WABZbjyg@mailjet.com> (raw)
In-Reply-To: <CAM-tV-9Qt_GsNptNhNZVo6jsoBiXr7BGfGV+fb7O7h=rYjHgrw@mail.gmail.com>


> By the way, the standard workaround for earlier Emacs versions is to
> escape open parens in the first column, i.e.,
>
> "Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do
> \(eiusmod tempor) incididunt ut labore et dolore (magna aliqua. Ut enim
> ad)"
>
> Alternatively, you can try setting
> open-paren-in-column-0-is-defun-start to nil, although it might cause
> slower fontifying/indenting/movement in some cases.

I found this bug while working on the Guix project. And, the Guix
project has been working around this problem for a while.

See https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27491

Finally, I reported the bug here to get a proper solution because people
at Guix felt "Emacs could do better here — especially since this is a
lisp mode!"

>> Sorry for the somewhat late reply. I had to clone the emacs git repo,
>> and build it from source -- a process I have not done before.
>
> 3 days doesn't seem late to me, lot of bugs wait much longer (some for years!)

:-)





      reply	other threads:[~2017-07-18 16:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-14 13:58 bug#27692: 25.2; Indentation issue with strings in scheme mode Arun Isaac
2017-07-14 19:01 ` Alex
2017-07-17 12:17   ` Arun Isaac
2017-07-17 13:22     ` Noam Postavsky
2017-07-18 16:51       ` Arun Isaac [this message]

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=ce07b297.AEQANSTVODwAAAAAAAAAAAPWRyIAAAACwQwAAAAAAAW9WABZbjyg@mailjet.com \
    --to=arunisaac@systemreboot.net \
    --cc=27692@debbugs.gnu.org \
    --cc=agrambot@gmail.com \
    --cc=npostavs@users.sourceforge.net \
    /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.