unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: info
Date: Thu, 30 Jan 2003 09:39:13 +0100	[thread overview]
Message-ID: <84n0lj821a.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: Pine.SUN.3.91.1030130074649.795B-100000@is

Eli Zaretskii <eliz@is.elta.co.il> writes:

> I believe this arebitrary predictability is not very useful, except in 
> those cases where the text between the two *'s is short.  As other 
> examples in this thread show, sometimes this approach is simply wrong.

First of all, if point is on a menu line, then choose that menu
item.  That much we all agree on.

Further, if point is on a line starting with whitespace and
containing some non-whitespace text, this could be a continuation
line for a menu line.

Here's an algorithm:

IF point is on a menu line
THEN
    choose that menu item
ELSE
    IF point is on a line that starts with whitespace and contains
       non-whitespace characters
    THEN
        WHILE point is on a nonblank line starting with whitespace
        DO
            move up one line
        END
        IF point is on a menu line
        THEN
            choose that menu item
        FI
    FI
FI

What do people think?
-- 
Ambibibentists unite!

  reply	other threads:[~2003-01-30  8:39 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29  1:33 info Luc Teirlinck
2003-01-29  3:53 ` info Luc Teirlinck
2003-01-29  6:29   ` info Eli Zaretskii
2003-01-29 19:57     ` info Luc Teirlinck
2003-01-30  5:46       ` info Eli Zaretskii
2003-01-29 21:17   ` info Richard Stallman
2003-01-29 17:33 ` info Eli Zaretskii
2003-01-29 20:39   ` info Luc Teirlinck
2003-01-29 23:21     ` info Luc Teirlinck
2003-01-30  5:48     ` info Eli Zaretskii
2003-01-30  8:39       ` Kai Großjohann [this message]
2003-01-30 15:11         ` info Luc Teirlinck
2003-01-30 16:30           ` info Luc Teirlinck
2003-01-30 20:02         ` info Eli Zaretskii
2003-01-30 20:51           ` info Kai Großjohann
2003-01-30 22:37           ` info Robert J. Chassell
2003-01-31  1:51             ` info Luc Teirlinck
2003-01-31 13:05               ` info Robert J. Chassell
2003-01-31 20:22                 ` info Luc Teirlinck
2003-02-01  1:22                   ` info Robert J. Chassell
2003-01-29 21:17 ` info Richard Stallman
2003-01-30  0:31   ` info Luc Teirlinck
2003-01-30  1:43     ` info Luc Teirlinck
2003-01-30  2:03       ` info Luc Teirlinck
     [not found] <84smvc2guf.fsf@lucy.is.informatik.uni-duisburg.de>
2003-01-29 14:20 ` info Eli Zaretskii
2003-01-30 15:21   ` info Richard Stallman
2003-01-30 16:21     ` info Luc Teirlinck
2003-01-31 19:20       ` info Richard Stallman
2003-02-01  1:22         ` info Luc Teirlinck
2003-02-01 22:11           ` info Richard Stallman
2003-02-02  4:59             ` info Luc Teirlinck
2003-02-02  5:44             ` info Eli Zaretskii
2003-02-02  6:09               ` info Miles Bader
2003-02-03 14:40             ` info Stefan Monnier
2003-02-03 19:00               ` info Luc Teirlinck
2003-02-03 19:16                 ` info Luc Teirlinck
2003-02-03 19:19                   ` info Luc Teirlinck
2003-02-04 15:41                 ` info Richard Stallman
2003-02-05  6:08                   ` info Eli Zaretskii
2003-02-05 20:07                     ` info Luc Teirlinck
2003-02-09  4:45                       ` info Luc Teirlinck

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=84n0lj821a.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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).