From: Alex Kost <alezost@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 27491@debbugs.gnu.org
Subject: bug#27491: Indentation issue in emacs
Date: Mon, 26 Jun 2017 21:27:07 +0300 [thread overview]
Message-ID: <87tw32bo5g.fsf@gmail.com> (raw)
In-Reply-To: <cd1b87c9.AEAAL8sI7CsAAAAAAAAAAAPNlMMAAAACwQwAAAAAAAW9WABZUCW6@mailjet.com> (Arun Isaac's message of "Mon, 26 Jun 2017 02:35:52 +0530")
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
next prev parent reply other threads:[~2017-06-26 18:28 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 [this message]
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
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=87tw32bo5g.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=27491@debbugs.gnu.org \
--cc=arunisaac@systemreboot.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).