GNU bug report logs -
#27491
Indentation issue in emacs
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 27491 in the body.
You can then email your comments to 27491 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#27491
; Package
guix
.
(Sun, 25 Jun 2017 21:07:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Arun Isaac <arunisaac <at> systemreboot.net>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sun, 25 Jun 2017 21:07:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
I'm not entirely sure this is the right place to report this
bug. If I should report this bug elsewhere, please direct me.
When I indent the `emacs-which-key' package definition in
gnu/packages/emacs.scm using `indent-region', the description gets
indented wrongly. The "(or as many as space allows given your settings)"
part of the description string gets indented as though it were an
S-expression.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27491
; Package
guix
.
(Mon, 26 Jun 2017 18:28:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 27491 <at> debbugs.gnu.org (full text, mbox):
Arun Isaac (2017-06-26 02:35 +0530) wrote:
> I'm not entirely sure this is the right place to report this
> bug. If I should report this bug elsewhere, please direct me.
>
> When I indent the `emacs-which-key' package definition in
> gnu/packages/emacs.scm using `indent-region', the description gets
> indented wrongly. The "(or as many as space allows given your settings)"
> part of the description string gets indented as though it were an
> S-expression.
Here is the description of 'emacs-which-key' package.
(description "@code{emacs-which-key} is a minor mode for Emacs that
displays the key bindings following your currently entered incomplete command
(a prefix) in a popup. For example, after enabling the minor mode if you
enter C-x and wait for the default of 1 second, the minibuffer will expand
with all of the available key bindings that follow C-x (or as many as space
allows given your settings).")
What you describe happens because of this line:
(a prefix) in a popup. For example, after enabling the minor mode if you
As you see, it starts with "(" and Emacs doesn't like such things.
Commit 7c125ce02¹ fixed such descriptions 2 years ago. Perhaps it's
time to repeat this commit :-)
¹ http://git.savannah.gnu.org/cgit/guix.git/commit/?id=7c125ce02384cff462a3ed84ac77153921e1c2a5
--
Alex
Reply sent
to
Arun Isaac <arunisaac <at> systemreboot.net>
:
You have taken responsibility.
(Tue, 27 Jun 2017 06:15:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Arun Isaac <arunisaac <at> systemreboot.net>
:
bug acknowledged by developer.
(Tue, 27 Jun 2017 06:15:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 27491-done <at> debbugs.gnu.org (full text, mbox):
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
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27491
; Package
guix
.
(Wed, 28 Jun 2017 12:37:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 27491 <at> debbugs.gnu.org (full text, mbox):
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.
--
Alex
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27491
; Package
guix
.
(Wed, 28 Jun 2017 13:14:01 GMT)
Full text and
rfc822 format available.
Message #19 received at 27491 <at> debbugs.gnu.org (full text, mbox):
> 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.
Oh, my bad. I thought it was something related to guix-devel-mode or the
.dir-locals.el
> 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.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27491
; Package
guix
.
(Fri, 30 Jun 2017 19:14:01 GMT)
Full text and
rfc822 format available.
Message #22 received at 27491-done <at> debbugs.gnu.org (full text, mbox):
Alex Kost <alezost <at> 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?
I’m closing this bug, because it’s not a problem with Guix.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
Information forwarded
to
bug-guix <at> gnu.org
:
bug#27491
; Package
guix
.
(Sun, 02 Jul 2017 19:18:01 GMT)
Full text and
rfc822 format available.
Message #25 received at 27491-done <at> debbugs.gnu.org (full text, mbox):
Ricardo Wurmus writes:
> Alex Kost <alezost <at> 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.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 31 Jul 2017 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 7 years and 329 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.