From: "leo" <halloleo@noospaam.myrealbox.com>
Subject: Re: Using info manuals (was: do i need a .newrc file?)
Date: Mon, 5 Jan 2004 16:48:16 +1100 [thread overview]
Message-ID: <btatq6$29lr$1@otis.netspace.net.au> (raw)
In-Reply-To: <v9ptdzqsnv.fsf_-_@marauder.physik.uni-ulm.de>
"Reiner Steib" <4.uce.03.r.s@nurfuerspam.de> wrote in message
news:v9ptdzqsnv.fsf_-_@marauder.physik.uni-ulm.de...
> On Sun, Jan 04 2004, Kai Grossjohann wrote:
>
> I agree with Simon that this is very useful. Wouldn't it be nice if
> `clone-buffer' would be available from the menu? (If we don't find
> this command easily, how are novice users supposed to find it?) I
> couldn't find it in the info info manual (in 21.3).
uuups, now i see,that the clone-buffer advice is comen knowledge.. sorry.
one over thing which might be quite help full with muliple info buffers: the
u command with prefix doesn't alowe to leave the current file: that is very
help full if you want something like an *info elisp* buffer:
when you bind C-u u to a single key you can move up without worrying about
leaving your particular manual.
i'm thinking about a little function which generates and renames an info
buffer (maybe plus frame) and jumps straight to the appropiate
manual.something you cal call like (make-info-topic-frame "elisp").
when used again with the same string ideally it would jump to the existing
buffer, but that might be a bit hard...
cheers, leo
next prev parent reply other threads:[~2004-01-05 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2y8so7etj.fsf@bella.local>
2004-01-04 0:38 ` do i need a .newrc file? Tim McNamara
[not found] ` <m2oetk7awf.fsf@bella.local>
[not found] ` <m27k08e6lb.fsf@Stella-Blue.local>
[not found] ` <87d69zg6si.fsf@emptyhost.emptydomain.de>
[not found] ` <m2ptdzabmd.fsf@Stella-Blue.local>
[not found] ` <8765frd1f8.fsf@emptyhost.emptydomain.de>
[not found] ` <87znd3pn3q.fsf@hydra.localdomain>
2004-01-04 21:34 ` Kai Grossjohann
[not found] ` <m2d69z4eae.fsf@Stella-Blue.local>
2004-01-04 21:44 ` Kai Grossjohann
[not found] ` <iluad53shcp.fsf@latte.josefsson.org>
[not found] ` <87fzevblyl.fsf@emptyhost.emptydomain.de>
[not found] ` <v9ptdzqsnv.fsf_-_@marauder.physik.uni-ulm.de>
2004-01-05 5:48 ` leo [this message]
2004-01-04 0:54 ` Tassilo Horn
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='btatq6$29lr$1@otis.netspace.net.au' \
--to=halloleo@noospaam.myrealbox.com \
/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 NNTP newsgroup(s).