From: Arun Isaac <arunisaac@systemreboot.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Alex Kost <alezost@gmail.com>, 27491-done@debbugs.gnu.org
Subject: bug#27491: Indentation issue in emacs
Date: Mon, 03 Jul 2017 00:46:56 +0530 [thread overview]
Message-ID: <eea15999.AEEAMvGltBEAAAAAAAAAAAPOBbcAAAACwQwAAAAAAAW9WABZWUav@mailjet.com> (raw)
In-Reply-To: <87y3s970gh.fsf@elephly.net>
Ricardo Wurmus writes:
> Alex Kost <alezost@gmail.com> writes:
>
>> Arun Isaac (2017-06-27 11:44 +0530) wrote:
>>
>>> Ok, fixed! :-)
>>>
>>> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=2482c02f3b23b2490a6647e0717cf8a4ccf3f6a8
>>>
>>> However, I think this is a hack, and the better solution would be to
>>> actually fix the underlying indentation issue. But, I am too lazy to
>>> find out how. :-P
>>
>> I'm not sure what you mean by a "fix". This is an Emacs issue, and it
>> was there since... I don't know, always. Moreover, I don't think it's a
>> bug; it's just how Emacs finds a beginning of the top-level sexp – it
>> "sees" a leading parenthesis on a line and it considers it to be a
>> beginning of the sexp.
>
> I consider this a bug. Surely Emacs could do better here — especially
> since this is a lisp mode!
>
> @Arun, would you like to report this as a bug to the Emacs developers?
Sure, I'll do that.
prev parent reply other threads:[~2017-07-02 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 21:05 bug#27491: Indentation issue in emacs Arun Isaac
2017-06-26 18:27 ` Alex Kost
2017-06-27 6:14 ` Arun Isaac
[not found] ` <8bc87dab.AEAAMA4zZSgAAAAAAAAAAAO2CsUAAAACwQwAAAAAAAW9WABZUffQ@mailjet.com>
2017-06-28 12:35 ` Alex Kost
2017-06-28 13:13 ` Arun Isaac
2017-06-30 19:13 ` Ricardo Wurmus
2017-07-02 19:16 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eea15999.AEEAMvGltBEAAAAAAAAAAAPOBbcAAAACwQwAAAAAAAW9WABZWUav@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=27491-done@debbugs.gnu.org \
--cc=alezost@gmail.com \
--cc=rekado@elephly.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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).