unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: emacs-devel@gnu.org
Subject: Re: Texinfo Mode:  node-based movement functions.
Date: Sat, 6 Nov 2004 16:52:08 -0500 (EST)	[thread overview]
Message-ID: <m1CQYTg-000UN3C@rattlesnake.com> (raw)
In-Reply-To: <Pine.LNX.3.96.1041106122151.342A-100000@acm.acm> (message from Alan Mackenzie on Sat, 6 Nov 2004 12:40:21 +0000 (GMT))


   In Texinfo Mode we have functions for moving to the beginning and end of
   a "page" (i.e. a @chapter) and for narrowing to a @chapter (together with
   its @sections).

   I think there should also be functions for moving to the beginning and
   end of an individual @node, and for narrowing to it.  ....

Why do you give a _node_ such relevance?  I am curious.  The reason is
that I have written many Texinfo documents over the past 18 years (or
more) and never needed a `goto Texinfo node command'.  If I had to go
to the node in Texinfo mode, I did a `C-s @no' or `C-r @no' and got
there.  (The search also brings up `@noindent' lines, but I ignore
them.  And clearly, most of my node-based movements have been to a
nearby node.)  Mostly, I have had to go to (and sometimes change)
content, which means going to chapters or sections.

Are you thinking of the other surface expressions besides Info that
Texinfo enables?  Certainly, nodes are published in Info, which is one
of the surface expressions.  They may be published in HTML -- I don't
know.  They are not published in a printed copy, whether using DVI,
PDF, XML, or PS.  I know that for sure, since I have to get rid of
nodes==sections that are too close to the first section of a chapter,
but should be in an Info file. (I keep the node but get rid of the
published section.)

However, a surface expression is not relevant to writing the deep
representation.  So perhaps the `goto Texinfo node commands' will be
useful to some writers.  (Fourteen ago, I wrote some
`texinfo-insert-...' commands that too few people cared about so they
were not included in the standard distribution.  However, they have
remained part of my .emacs file ever since.  I found the lack of
inclusion really weird since I use them.  Moreover, I always thought
of myself as an exemplar of the average so others should use them,
too.  Evidentally I am not such an exemplar.  Are your node movement
commands the same or are they useful by many other people?)

In any event, if you continue to develop the commands, please take
account of @ignore and the rest; they are used often by everyone.

Thank you.

-- 
    Robert J. Chassell                         
    bob@rattlesnake.com                         GnuPG Key ID: 004B4AC8
    http://www.rattlesnake.com                  http://www.teak.cc

  parent reply	other threads:[~2004-11-06 21:52 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 [this message]
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
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=m1CQYTg-000UN3C@rattlesnake.com \
    --to=bob@rattlesnake.com \
    --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).