unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Schierl <schierlm-usenet@gmx.de>
Subject: Re: helpex.el 0.2 --- useful extensions for the C-h prefix
Date: Mon, 26 Jan 2004 20:43:13 +0100	[thread overview]
Message-ID: <bv3qkk$o0r4b$3@ID-39741.news.uni-berlin.de> (raw)
In-Reply-To: jwvfze911ky.fsf-monnier+gnu.emacs.help@asado.iro.umontreal.ca

Hmm, unannounced Followup-To. Is that best current practice here in
gnu.*?

Stefan Monnier <monnier@iro.umontreal.ca> wrote:

>> Is there a good solution for the Info-goto-node "problem" as well?
>
>IIRC, the goto-node code in CVS does completion within the parenthesese,
>but it does not do completion of the node name afterwards (this requires
>looking inside the Info file and I didn't bother writing it up).
>
>> IOW: If you have an info file called "foo" with a node "Bar Baz" (e.g.
>> "(elisp)Regular Expressions"), can you type
>
>> C-h i g (foo)Bar SPC Baz RET
>
>> while p-c-m is enabled, *without* making Emacs barf about no
>> completion when hitting SPC?
>
>I haven't used p-c-m in a while and I use C-a SPC 

Do you mean C-q SPC?

>to insert a space, so
>I wouldn't know.  If it works without p-c-m, then it's a bug in p-c-m,
>otherwise it's a misfeature.

It's most likely a bug in p-c-m. On the other hand, without p-c-m,
when you hit TAB twice after entered the full file name (e.g.
"(emacs)"), you first get "[Complete, but not unique]" and on the
second try "[No completions]". Maybe that's irritating p-c-m.

Michael
-- 
"New" PGP Key! User ID: Michael Schierl <schierlm@gmx.de>
Key ID: 0x58B48CDD    Size: 2048    Created: 26.03.2002
Fingerprint:  68CE B807 E315 D14B  7461 5539 C90F 7CC8
http://home.arcor.de/mschierlm/mschierlm.asc

  parent reply	other threads:[~2004-01-26 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <buhb0j$hu8n8$2@ID-39741.news.uni-berlin.de>
2004-01-20 17:16 ` helpex.el 0.2 --- useful extensions for the C-h prefix Stefan Monnier
2004-01-21 19:36   ` Michael Schierl
2004-01-21 20:44     ` Stefan Monnier
2004-01-22 19:20       ` Kevin Rodgers
2004-01-26 19:43       ` Michael Schierl [this message]
2004-01-26 22:02         ` Stefan Monnier

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='bv3qkk$o0r4b$3@ID-39741.news.uni-berlin.de' \
    --to=schierlm-usenet@gmx.de \
    --cc=schierlm@gmx.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.
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).