unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Antonin Houska <ah@cybertec.at>
Cc: 26049@debbugs.gnu.org
Subject: bug#26049: 25.2; Extra lines not added to comment
Date: Mon, 06 Nov 2017 19:07:07 -0500	[thread overview]
Message-ID: <87zi7z54us.fsf@users.sourceforge.net> (raw)
In-Reply-To: <7456.1509963262@localhost> (Antonin Houska's message of "Mon, 06 Nov 2017 11:14:22 +0100")

tags 26049 fixed
close 26049 26.1
quit

Antonin Houska <ah@cybertec.at> writes:

> Subject: [PATCH] Handle single-line comments correctly (Bug#26049)
>
> * lisp/newcomment.el: the comment text had to contain at least one
> line break for the ending extra line to be added. The behavior seems
> more consistent if the end of the comment text is also considered a
> line break.
>
> While fixing this, also removed trailing white space from the comment
> initial line (/*).
>
> Copyright-paperwork-exempt: yes

Thanks, I rephrased/reformatted the message a bit and pushed to
emacs-26.

[1: db949166ec]: 2017-11-06 19:01:19 -0500
  Handle single-line comments correctly (Bug#26049)
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=db949166ecb9aeaa15aa41369a55b3ea6ceaa3b0





      reply	other threads:[~2017-11-07  0:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10 13:41 bug#26049: 25.2; Extra lines not added to comment Antonin Houska
2017-03-28  3:29 ` npostavs
2017-03-28 12:52   ` Antonin Houska
2017-03-29  2:25     ` npostavs
2017-03-29  6:54       ` Antonin Houska
2017-09-23  7:41         ` Antonin Houska
2017-09-23 14:37           ` Noam Postavsky
2017-11-06 10:14             ` Antonin Houska
2017-11-07  0:07               ` Noam Postavsky [this message]

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zi7z54us.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=26049@debbugs.gnu.org \
    --cc=ah@cybertec.at \
    /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/emacs.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).