From: Alan Mackenzie <acm@muc.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Geyslan G. Bem" <geyslan@gmail.com>, 22369@debbugs.gnu.org
Subject: bug#22369: 24.5; comment-style 'extra-line' doesn't correctly indent with tabs
Date: Thu, 17 Sep 2020 19:21:38 +0000 [thread overview]
Message-ID: <20200917192138.GA5562@ACM> (raw)
In-Reply-To: <87a6xonw12.fsf@gnus.org>
Hello, Lars and Geyslan.
On Thu, Sep 17, 2020 at 19:38:33 +0200, Lars Ingebrigtsen wrote:
> Alan Mackenzie <acm@muc.de> writes:
> >> May I suggest the addition of a new comment-style option that does like this?
> >> /* void main()
> >> * {
> >> * int i;
> >> * int b;
> >> * printf("format string");
> >> * }
> >> */
> > OK, because of this feature request, I'll leave the bug open. This would
> > indeed not be difficult to implement, but it'll have to be discussed on
> > the developers' mailing list.
> Was this ever discussed any further? It looks a bit odd to me...
I don't think there was any more discussion about this.
To be exact, the feature request was to have another option for
comment-style called something like bottom-extra which would add an
extra comment line at the bottom of a group, but not one at the top.
Four years on, I'm not convinced the feature is worth implementing, even
if it wouldn't be difficult. It would involve extending the spec of
comment-styles such that each entry would have EXTRA-TOP and
EXTRA-BOTTOM in place of the current EXTRA. Backward compatibility
could be had at the cost of counting the number of elements in each
entry.
One quirk the OP, Geyslan, pointed out was a possibly obtrusive space
when an empty line gets commented in comment-style extra-line, something
like:
/*
* foo();
* <=========== possibly obtrusive space.
* bar();
*/
I'm not sure whether or not this is a bug or a feature. If a bug, it
wouldn't be difficult to fix.
Geyslan, have you any more thoughts about this bug?
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2020-09-17 19:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 1:44 bug#22369: 24.5; comment-style 'extra-line' doesn't correctly indent with tabs Geyslan G. Bem
[not found] ` <mailman.2326.1452736388.843.bug-gnu-emacs@gnu.org>
2016-01-15 11:56 ` Alan Mackenzie
2016-01-15 12:11 ` Geyslan G. Bem
2020-09-17 17:38 ` Lars Ingebrigtsen
2020-09-17 19:21 ` Alan Mackenzie [this message]
2022-01-29 17:01 ` Lars Ingebrigtsen
2016-01-15 12:42 ` Alan Mackenzie
[not found] ` <20160115124231.67454.qmail@mail.muc.de>
2016-01-15 21:59 ` Geyslan G. Bem
[not found] ` <CAGG-pUQ8yN-VDKkfFq2-34PWfrpLtbSjRVXuJ_cQk8z-Edw=SQ@mail.gmail.com>
2016-01-18 11:14 ` Geyslan G. Bem
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=20200917192138.GA5562@ACM \
--to=acm@muc.de \
--cc=22369@debbugs.gnu.org \
--cc=geyslan@gmail.com \
--cc=larsi@gnus.org \
/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.