all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Theodor Thornhill <theo@thornhill.no>
Cc: casouri@gmail.com, 60322-done@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#60322: 30.0.50; [PATCH]: Search for comment at bol in prog-fill-reindent-defun
Date: Thu, 29 Dec 2022 13:12:26 +0200	[thread overview]
Message-ID: <83cz828nvp.fsf@gnu.org> (raw)
In-Reply-To: <87mt76wknp.fsf@thornhill.no> (message from Theodor Thornhill on Thu, 29 Dec 2022 11:48:10 +0100)

> From: Theodor Thornhill <theo@thornhill.no>
> Cc: 60322@debbugs.gnu.org
> Date: Thu, 29 Dec 2022 11:48:10 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> Date: Sun, 25 Dec 2022 22:54:44 +0100
> >> From:  Theodor Thornhill via "Bug reports for GNU Emacs,
> >>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >> 
> >> Attached is a small adjustment to the regex used in
> >> prog-fill-reindent-defun.  The point is that we shouldn't consider lines
> >> where comments come after actual code as inside a comment.
> >
> > Dmitry, Yuan, any comments?
> 
> This is adressed in f9a22cf78d1a7f6472b09c3046c6a7f6984bc2d2, so This
> can be closed :-)

Thanks, done.





  reply	other threads:[~2022-12-29 11:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25 21:54 bug#60322: 30.0.50; [PATCH]: Search for comment at bol in prog-fill-reindent-defun Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-29  9:02 ` Eli Zaretskii
2022-12-29 10:48   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-29 11:12     ` Eli Zaretskii [this message]
2022-12-29 16:04 ` Dmitry Gutov
2022-12-29 19:23   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-29 19:25     ` Dmitry Gutov

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=83cz828nvp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60322-done@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=theo@thornhill.no \
    /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.