From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 12583@debbugs.gnu.org, 'Le Wang' <l26wang@gmail.com>
Subject: bug#12583: latest org-mode changes exposes bug in `comment-forward'in newcomment.el
Date: Sat, 06 Oct 2012 12:48:40 -0400 [thread overview]
Message-ID: <jwvzk3zmtve.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8A74257275DC479D86CE39485F0D5FB7@us.oracle.com> (Drew Adams's message of "Sat, 6 Oct 2012 09:37:48 -0700")
>> > For my own use, I wonder whether I should be calling `c-n-v' before
>> > I make use of `comment-search-forward'.
>> Yes, you should.
> OK, thanks. Please consider providing specific guidelines about this,
> somewhere.
I think the guideline "commands that use comment-* functions should call
c-n-v first" is a good approximation.
> OK, so it was only for a transition. Presumably that means that some
> of those autoloads will be removed at some point.
Except that I don't know how to mark obsolete the auto-loading of
a variable, so the transition would be just as abrupt now as it would
have been then.
I guess we can remove autoloads one at a time and see when
someone screams.
Stefan
next prev parent reply other threads:[~2012-10-06 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 11:07 bug#12583: latest org-mode changes exposes bug in `comment-forward' in newcomment.el Le Wang
2012-10-06 12:49 ` Stefan Monnier
2012-10-06 15:53 ` bug#12583: latest org-mode changes exposes bug in `comment-forward'in newcomment.el Drew Adams
2012-10-06 16:12 ` Stefan Monnier
2012-10-06 16:37 ` Drew Adams
2012-10-06 16:48 ` Stefan Monnier [this message]
2012-10-06 16:57 ` Drew Adams
2012-10-06 17:07 ` Stefan Monnier
2012-10-06 17:12 ` Drew Adams
2012-10-07 0:48 ` Stefan Monnier
2012-10-07 2:51 ` Drew Adams
2012-10-23 2:18 ` Chong Yidong
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=jwvzk3zmtve.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=12583@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=l26wang@gmail.com \
/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).