From: Kaushal Modi <kaushal.modi@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Help Gnu Emacs mailing list <help-gnu-emacs@gnu.org>
Subject: Re: Thanks Re: Global keymap not found
Date: Sat, 10 Oct 2015 08:02:26 -0400 [thread overview]
Message-ID: <CAFyQvY24U-S2zZFiNLGNZH9hbxYGf60R0GnsKrtDM=bS59VSxg@mail.gmail.com> (raw)
In-Reply-To: <87d1wnxe4w.fsf@web.de>
To add to the `C-x C-e` method, the below will do the same if the user is
not already in an Info buffer,
C-h i g (emacs) Easy Customization
If the user is already in an Info buffer, they need to just do
g (emacs) Easy Customization
In any info node, the node name is copied using `w`, "(emacs) Easy
Customization" in above case.
Of course, if the user is not familiar with info nodes and navigating them,
they should first start with `C-h i h`. That will launch the info manual on
how to use info.
On Oct 10, 2015 5:33 AM, "Michael Heerdegen" <michael_heerdegen@web.de>
wrote:
> Albrecht Mehl <AlbrechtMehl.spamgrab@iesy.net> writes:
>
> > - The chapters in the manual are numerated within the text. So
> > they should be in the table of context as well. People
> > write 'Look at 49.1' e.g. and one wonders where this is.
>
> Providing such a reference is not nice. You can find it via isearch
> (C-s) nonetheless, which in info is not limited to the current manual
> page but spans the whole complete manual.
>
> A certain kink of standard is to write references to the manual like
> this:
>
> (info "(emacs) Easy Customization") (1)
>
> This is actually a piece of Elisp code, so you can e.g. put the cursor
> after it and hit C-x C-e to get to the page.
>
> You can produce (1) and insert it into the kill-ring conveniently from
> within the info viewer via typing M-0 w, and then paste it into any
> message.
>
>
> Regards,
>
> Michael.
>
>
>
prev parent reply other threads:[~2015-10-10 12:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 8:03 Global keymap not found Albrecht Mehl
2015-10-07 8:46 ` Marco Wahl
2015-10-07 9:28 ` Michael Heerdegen
[not found] ` <mailman.45.1444210137.916.help-gnu-emacs@gnu.org>
2015-10-07 11:19 ` Marco Wahl
2015-10-07 15:01 ` Tassilo Horn
2015-10-07 15:12 ` Drew Adams
2015-10-08 6:27 ` Albrecht Mehl
2015-10-08 8:53 ` Michael Heerdegen
[not found] ` <mailman.7.1444294440.4386.help-gnu-emacs@gnu.org>
2015-10-08 14:36 ` Thanks " Albrecht Mehl
2015-10-08 14:46 ` Loris Bennett
2015-10-08 15:08 ` Michael Heerdegen
[not found] ` <mailman.69.1444347042.4386.help-gnu-emacs@gnu.org>
2015-10-09 9:13 ` Marco Wahl
2015-10-08 17:09 ` Drew Adams
2015-10-09 9:07 ` Albrecht Mehl
2015-10-09 20:12 ` Tassilo Horn
2015-10-09 20:21 ` Emanuel Berg
2015-10-09 20:18 ` Emanuel Berg
2015-10-09 20:45 ` Drew Adams
2015-10-10 9:09 ` Eli Zaretskii
2015-10-10 9:32 ` Michael Heerdegen
2015-10-10 12:02 ` Kaushal Modi [this message]
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='CAFyQvY24U-S2zZFiNLGNZH9hbxYGf60R0GnsKrtDM=bS59VSxg@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.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).