emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nick Dokos <nicholas.dokos@hp.com>
To: LanX <lanx.perl@googlemail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: linking to emacs info nodes? Multiline comments?
Date: Mon, 19 Apr 2010 11:00:05 -0400	[thread overview]
Message-ID: <3776.1271689205@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from LanX <lanx.perl@googlemail.com> of "Mon, 19 Apr 2010 16:26:13 +0200." <u2pec36f5051004190726n90d16198yda9e2bc5eef2e178@mail.gmail.com>

LanX <lanx.perl@googlemail.com> wrote:


> is there an easy way to insert links to the emacs info manuals?
> 
> the following works for commands only
> 
> [[elisp:(Info-goto-emacs-command-node "Info-goto-emacs-command-node")][Info
> goto emacs command node]]
> 

Assuming you have done the standard keybindings (C-c l for org-store-link everywhere
- see section 1.3, "Activation", in the Org manual for more details):

Visit the info node of interest, do C-c l to store the link, then visit an org
file and do C-c C-l to insert the link.

Here is an example of what was inserted, when I tried the above procedure
on the indicated Info node:

[[info:org:Processing%20LaTeX%20fragments][Processing LaTeX fragments]]



> BTW: whats the recommended way to insert multi-line comments in elisp code?
> 
> ATM I'm assigning a string to a dummy variable, with the drawback that
> doublequotes are forbidden:
> 
> (setq org "
>   yadda yadda
> ")
> 

I don't understand the context (why do you have to define a variable exactly?),
but you can include double quotes in a lisp string by escaping it with a backslash:

(setq org "
 yadda \"yadda\"
")

see section 2.3.8.1, "Syntax for Strings" in the Elisp manual.

HTH,
Nick

next prev parent reply	other threads:[~2010-04-19 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 14:26 linking to emacs info nodes? Multiline comments? LanX
2010-04-19 14:52 ` Dan Davison
2010-04-19 15:00 ` Nick Dokos [this message]
2010-04-19 15:09 ` Sebastian Rose
2010-04-19 15:22   ` LanX
2010-04-20 16:12     ` Nick Dokos
2010-04-20 18:04       ` Carsten Dominik

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.orgmode.org/

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

  git send-email \
    --in-reply-to=3776.1271689205@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=lanx.perl@googlemail.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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).