unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Mackenzie <acm@muc.de>
Cc: Dmitry Gutov <dgutov@yandex.ru>, Justine Tunney <jart@google.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	17978@debbugs.gnu.org
Subject: bug#17978: 24.3; forward-paragraph broken with javadocs
Date: Thu, 10 Feb 2022 09:23:22 +0100	[thread overview]
Message-ID: <87y22j9ll1.fsf@gnus.org> (raw)
In-Reply-To: <20140713132301.GA4056@acm.acm> (Alan Mackenzie's message of "Sun, 13 Jul 2014 13:23:01 +0000")

Alan Mackenzie <acm@muc.de> writes:

> With all due respect to the OP, the purpose of C-{ and C-} is to move
> between paragraphs, not blank lines.  Or, alternatively, in CC Mode, a
> line which contains only a comment prefix is considered to be blank.
>
> The motivation for this is to be able to move by paragraphs in large
> comments, such are frequently found at the beginning of source files.
> Sometimes, comments for individual functions are also quite sizeable.
> And of course, as already mentioned, filling should do the Right Thing
> inside comments.  If backward-paragraph (and forward-paragraph) were to
> be redefined not to handle comment prefices specially, the facility to
> move by paragraphs inside large comments (when the comment prefix is
> non-null) would be lost.
>
> I don't think we should change things here.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

Skimming this bug report, it sounds like this is working as designed, so
I'm therefore closing this bug report.  If further work should be done
here, please respond to the debbugs address and we'll reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-02-10  8:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09 17:53 bug#17978: 24.3; forward-paragraph broken with javadocs Justine Tunney
2014-07-09 19:26 ` Stefan Monnier
2014-07-09 21:11   ` Justine Tunney
2014-07-09 22:28     ` Stefan Monnier
2014-07-09 23:40       ` Justine Tunney
2014-07-10  3:06         ` Stefan Monnier
2014-07-11  6:54           ` Dmitry
2014-07-11  7:46             ` Dmitry
2014-07-11 13:51               ` Stefan Monnier
2014-07-13  0:48                 ` Dmitry Gutov
2014-07-13 13:23                   ` Alan Mackenzie
2022-02-10  8:23                     ` Lars Ingebrigtsen [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=87y22j9ll1.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=17978@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=dgutov@yandex.ru \
    --cc=jart@google.com \
    --cc=monnier@iro.umontreal.ca \
    /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).