From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: 21072@debbugs.gnu.org, emacs-devel@gnu.org
Subject: bug#21072: Brave new mark-defun (and a testing tool)
Date: Thu, 16 Feb 2017 08:22:20 -0500 [thread overview]
Message-ID: <jwvzihmmfw6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87bmu2eoji.fsf@jane> (Marcin Borkowski's message of "Thu, 16 Feb 2017 05:40:33 +0100")
> Understood. Do you have then any better idea for the name of this
> function? beginning-of-defun--incomment-line-p seems to specific,
> in-comment-line-p _may_ be indeed too general.
I'll let someone else decide if it deserves a "non-prefixed" name, but
as for the name after the potential prefix, I think focusing on
"comment" is the wrong idea. Maybe `insignificant-line-p`? Or `emptyish-line-p`?
Stefan
next prev parent reply other threads:[~2017-02-16 13:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 6:01 Brave new mark-defun (and a testing tool) Marcin Borkowski
2017-02-12 7:09 ` John Wiegley
2017-02-12 10:10 ` Marcin Borkowski
2017-02-12 10:13 ` Marcin Borkowski
2017-02-12 21:29 ` John Wiegley
2017-02-13 11:00 ` Marcin Borkowski
2017-02-13 15:16 ` Dmitry Gutov
2017-02-13 15:58 ` Marcin Borkowski
2017-02-13 19:00 ` John Wiegley
2017-02-14 10:45 ` bug#21072: " Marcin Borkowski
2017-02-14 13:02 ` Dmitry Gutov
2017-02-14 19:06 ` Marcin Borkowski
2017-02-14 19:25 ` Stefan Monnier
2017-02-15 6:45 ` Marcin Borkowski
2017-02-15 7:56 ` Stefan Monnier
2017-02-15 19:18 ` Marcin Borkowski
2017-02-15 19:27 ` Stefan Monnier
2017-02-16 4:40 ` Marcin Borkowski
2017-02-16 13:22 ` Stefan Monnier [this message]
2017-02-17 8:54 ` Marcin Borkowski
2017-03-07 16:46 ` Eli Zaretskii
2017-03-29 6:34 ` Marcin Borkowski
2017-03-31 11:18 ` Marcin Borkowski
2017-04-02 22:56 ` npostavs
2017-04-07 8:25 ` Marcin Borkowski
2017-03-07 16:50 ` Dmitry Gutov
2017-03-07 16:53 ` Eli Zaretskii
2017-03-29 6:30 ` Marcin Borkowski
2017-03-29 6:30 ` Marcin Borkowski
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=jwvzihmmfw6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=21072@debbugs.gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mbork@mbork.pl \
/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).