* bug#27491: Indentation issue in emacs
@ 2017-06-25 21:05 Arun Isaac
2017-06-26 18:27 ` Alex Kost
0 siblings, 1 reply; 7+ messages in thread
From: Arun Isaac @ 2017-06-25 21:05 UTC (permalink / raw)
To: 27491
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.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#27491: Indentation issue in emacs
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>
0 siblings, 2 replies; 7+ messages in thread
From: Alex Kost @ 2017-06-26 18:27 UTC (permalink / raw)
To: Arun Isaac; +Cc: 27491
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#27491: Indentation issue in emacs
2017-06-26 18:27 ` Alex Kost
@ 2017-06-27 6:14 ` Arun Isaac
[not found] ` <8bc87dab.AEAAMA4zZSgAAAAAAAAAAAO2CsUAAAACwQwAAAAAAAW9WABZUffQ@mailjet.com>
1 sibling, 0 replies; 7+ messages in thread
From: Arun Isaac @ 2017-06-27 6:14 UTC (permalink / raw)
To: Alex Kost; +Cc: 27491-done
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
^ permalink raw reply [flat|nested] 7+ messages in thread
[parent not found: <8bc87dab.AEAAMA4zZSgAAAAAAAAAAAO2CsUAAAACwQwAAAAAAAW9WABZUffQ@mailjet.com>]
* bug#27491: Indentation issue in emacs
[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
0 siblings, 2 replies; 7+ messages in thread
From: Alex Kost @ 2017-06-28 12:35 UTC (permalink / raw)
To: Arun Isaac; +Cc: 27491
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#27491: Indentation issue in emacs
2017-06-28 12:35 ` Alex Kost
@ 2017-06-28 13:13 ` Arun Isaac
2017-06-30 19:13 ` Ricardo Wurmus
1 sibling, 0 replies; 7+ messages in thread
From: Arun Isaac @ 2017-06-28 13:13 UTC (permalink / raw)
To: Alex Kost; +Cc: 27491
> 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.
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#27491: Indentation issue in emacs
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
1 sibling, 1 reply; 7+ messages in thread
From: Ricardo Wurmus @ 2017-06-30 19:13 UTC (permalink / raw)
To: Arun Isaac; +Cc: Alex Kost, 27491-done
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?
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* bug#27491: Indentation issue in emacs
2017-06-30 19:13 ` Ricardo Wurmus
@ 2017-07-02 19:16 ` Arun Isaac
0 siblings, 0 replies; 7+ messages in thread
From: Arun Isaac @ 2017-07-02 19:16 UTC (permalink / raw)
To: Ricardo Wurmus; +Cc: Alex Kost, 27491-done
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.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-07-02 19:18 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
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).