unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ralf Angeli <angeli@caeruleus.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Autoloading comment-forward
Date: Mon, 09 Jul 2007 20:55:29 +0200	[thread overview]
Message-ID: <87bqel4db2.fsf@neutrino.caeruleus.net> (raw)
In-Reply-To: <jwvsl7zypak.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 08 Jul 2007 09:55:39 -0400")

* Stefan Monnier (2007-07-08) writes:

>> Oh, okay.  Thanks for the hint.  Is this documented somewhere?  Should
>> it be done everytime `comment-forward' is called?
>
> Once is enough: It simply should be called at some point after the major
> mode is set but before internal functions such as comment-forward are used.

Okay.

>> I saw that other functions in newcomment.el call
>> `comment-normalize-vars' themselves.  Would it make sense if
>> `comment-forward' did the same (and was autoloaded)?
>
> Could be.  What kind of situation do you have in mind where this is useful?

I'm not sure I understand the question.  AUCTeX uses `comment-forward'
to skip empty or commented lines when traversing LaTeX macro arguments.
So for me `comment-forward' is not so much an internal function of
newcomment.el but rather one which is useful for other parts of Emacs or
packages like AUCTeX.  That's also why I think it makes sense for it to
be autoloaded.

Anyway, I will put a call to `comment-normalize-vars' into the
compatibility function for `comment-forward' in AUCTeX before
`comment-forward' is actually called (if available).  This will get rid
of the issue.  And the call to `comment-forward' in RefTeX has actually
only been present in my local copy.  RefTeX actually uses a different
mechanism for skipping over comments.

-- 
Ralf

  reply	other threads:[~2007-07-09 18:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 19:20 Autoloading comment-forward Ralf Angeli
2007-07-07  1:34 ` Stefan Monnier
2007-07-07  6:24   ` Ralf Angeli
2007-07-08 13:55     ` Stefan Monnier
2007-07-09 18:55       ` Ralf Angeli [this message]
2007-07-09 19:51         ` Stefan Monnier
2007-07-09 20:01           ` Ralf Angeli
2007-07-10  2:55             ` Stefan Monnier
2007-07-10 22:01               ` Richard Stallman
2007-07-11  2:26                 ` Stefan Monnier
2007-07-11 21:03                   ` Richard Stallman
2007-07-12  3:17                     ` Stefan Monnier
2007-07-12 21:23                       ` Richard Stallman
2007-07-07 20:47 ` Richard Stallman

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=87bqel4db2.fsf@neutrino.caeruleus.net \
    --to=angeli@caeruleus.net \
    --cc=emacs-devel@gnu.org \
    --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).