all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: juri@jurta.org, emacs-pretest-bug@gnu.org
Subject: Re: Info-build-node-completions has an extra `*' node
Date: Tue, 19 Feb 2008 10:45:41 -0500	[thread overview]
Message-ID: <E1JRUf7-0001Rd-UB@fencepost.gnu.org> (raw)
In-Reply-To: <001201c87255$68d3b270$9eb22382@us.oracle.com> (drew.adams@oracle.com)

    Hmm. Really? I don't see it in my copy of Emacs 20:

     In GNU Emacs 20.7.3 (i386-*-nt5.1.2600)
      of Thu Dec 21 2000 on buffy
     configured using `configure NT'

    It doesn't show up in *Completions*, and if I type `g * RET' it says [No
    match].

That surprises me, since I recall this feature is very old.
I think it goes back to PDP10 Emacs.

Perhaps it was broken or missing from GNU Emacs for a while.





  reply	other threads:[~2008-02-19 15:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-17 22:25 Info-build-node-completions has an extra `*' node Drew Adams
2008-02-17 22:34 ` Drew Adams
2008-02-17 23:05   ` Bastien
2008-02-17 23:22   ` Juri Linkov
2008-02-17 23:53     ` Bastien Guerry
2008-02-18  0:27       ` Juri Linkov
2008-02-18  0:56         ` Bastien Guerry
2008-02-18 23:54           ` Juri Linkov
2008-02-19  0:48             ` Bastien
2008-02-21 19:24               ` Drew Adams
2008-02-18  0:02     ` Drew Adams
2008-02-18  0:29       ` Juri Linkov
2008-02-18  0:54         ` Bastien Guerry
2008-02-18  1:27         ` Drew Adams
2008-02-18  3:37           ` Miles Bader
2008-02-18  4:12             ` David De La Harpe Golden
2008-02-18 11:56               ` Bastien Guerry
2008-02-18 23:55             ` Juri Linkov
2008-02-18 17:31           ` Richard Stallman
2008-02-18 17:40             ` Drew Adams
2008-02-19 15:45               ` Richard Stallman [this message]
2008-02-19 21:35                 ` Stefan Monnier
2008-02-20  3:23                 ` Drew Adams

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1JRUf7-0001Rd-UB@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=juri@jurta.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.