unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Texinfo Mode:  node-based movement functions.
Date: Mon, 08 Nov 2004 17:40:48 -0500	[thread overview]
Message-ID: <jwvsm7kotta.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1041108182144.333A-100000@acm.acm> (Alan Mackenzie's message of "Mon, 8 Nov 2004 20:09:09 +0000 (GMT)")

>> Why worry about keybindings?  Why not just set beginning-of-defun-function
>> (or page-delimiter)?
> (i) The beginning-of-defun-function mechanism is broken in 21.3 - the
> COUNT argument is not passed through to b-o-d-f.

But you won't retroactively change texinfo.el for Emacs-21.3 anyway, so this
shouldn't be a consideration.  Either it's fixed in Emacs-CVS and you can
use it for Emacs-CVS's texinfo.el or it's not fixed in which case you should
get it fixed first.  AFAIK it is fixed.

> Why not enhance the meaning of page-delimiter?  It should be either a
> regexp, as at present, or a cons cell like ("\\(^\\)@node" . 1), where
> the "1" means "the page boundary is at (match-beginning 1)"?  Even
> better, ("^@node" . 0) would leave point at (match-beginning 0), the
> _start_ of the regexp.  Perhaps, even, (regexp . -1) could mean
> (match-end 1).

And how do you specify the case of "\f\\|@node" ?
Nah... just make it possible to use a function and be done with it.


        Stefan

  reply	other threads:[~2004-11-08 22:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-06 12:40 Texinfo Mode: node-based movement functions Alan Mackenzie
2004-11-06 15:04 ` Alan Mackenzie
2004-11-06 21:52 ` Robert J. Chassell
2004-11-07 13:55   ` Alan Mackenzie
2004-11-07 23:52     ` Robert J. Chassell
2004-11-07  3:37 ` Richard Stallman
2004-11-08 14:47 ` Stefan
2004-11-08 20:09   ` Alan Mackenzie
2004-11-08 22:40     ` Stefan Monnier [this message]
2004-11-09 11:14   ` 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=jwvsm7kotta.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=emacs-devel@gnu.org \
    /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).