From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: oscarfv@telefonica.net, 23902@debbugs.gnu.org
Subject: bug#23902: 25.1.50; Strange warning on string-collate-equalp's docstring
Date: Sat, 09 Jul 2016 09:52:43 +0300 [thread overview]
Message-ID: <831t33i9qc.fsf@gnu.org> (raw)
In-Reply-To: <871t33q21e.fsf@web.de> (message from Michael Heerdegen on Fri, 08 Jul 2016 22:59:25 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: oscarfv@telefonica.net, 23902-done@debbugs.gnu.org
> Date: Fri, 08 Jul 2016 22:59:25 +0200
>
> Are the spaces before the closing comment delimiter (delimiting
> the docstring) significant?
You mean, before the closing "*/" ? No, these are not significant.
> When not, why are they used?
To keep C comments in their usual GNU C style, I suppose.
next prev parent reply other threads:[~2016-07-09 6:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 22:05 bug#23902: 25.1.50; Strange warning on string-collate-equalp's docstring Óscar Fuentes
2016-07-06 14:34 ` Eli Zaretskii
2016-07-06 15:08 ` Michael Heerdegen
2016-07-06 15:28 ` Eli Zaretskii
2016-07-06 15:46 ` Óscar Fuentes
2016-07-06 16:26 ` Eli Zaretskii
2016-07-06 17:44 ` Óscar Fuentes
2016-07-06 18:32 ` Eli Zaretskii
2016-07-09 17:06 ` Glenn Morris
2016-07-09 17:21 ` Eli Zaretskii
2016-07-09 21:36 ` Óscar Fuentes
2016-07-10 2:40 ` Eli Zaretskii
2016-07-10 3:06 ` Michael Heerdegen
2016-07-10 14:40 ` Eli Zaretskii
2016-07-06 15:55 ` Michael Heerdegen
2016-07-06 16:30 ` Eli Zaretskii
2016-07-06 16:44 ` Michael Heerdegen
2016-07-06 17:18 ` Eli Zaretskii
2016-07-06 22:49 ` Michael Heerdegen
2016-07-07 2:38 ` Eli Zaretskii
2016-07-07 21:52 ` Michael Heerdegen
2016-07-08 10:11 ` Eli Zaretskii
2016-07-08 20:59 ` Michael Heerdegen
2016-07-09 6:52 ` Eli Zaretskii [this message]
2016-07-09 17:06 ` Richard Stallman
2016-07-09 22:59 ` Michael Heerdegen
2016-07-06 15:48 ` Glenn Morris
2016-07-06 16:27 ` Eli Zaretskii
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=831t33i9qc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23902@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=oscarfv@telefonica.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.