emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: imaxima babel
Date: Wed, 27 Nov 2013 19:42:21 -0500	[thread overview]
Message-ID: <87fvqhl5le.fsf@gmail.com> (raw)
In-Reply-To: 87vbzdmoex.fsf@gmx.co.uk

<yggdrasil@gmx.co.uk> writes:

> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>  ...
>> Finally, and it's a nitpick: breaking lines in the middle of (info ...)
>> links prevents following them using "C-x C-e".
>>
> Actually, I never used these sort of links myself, thanks for pointing
> out how this is done! :) I moved all infolinks to footnotes to avoid the
> line breaks.
>

Just a clarification: you cannot break the *string* argument but
newlines in other places are fine:

      (info
         "(org) The Spreadsheet")

works fine, but

      (info
         "(org) The 
Spreadsheet")

does not: the second string is not the same as the first one, since it
includes a newline. OTOH, you can escape the newline:

      (info
         "(org) The \
Spreadsheet")

works fine.

The point is that all of this follows from the properties of
strings. Just go to the *scratch* buffer and evaluate some
expressions:

(string-equal "a b" "a \
b")
t

(string-equal "a b" "a 
b")
nil

-- 
Nick

  reply	other threads:[~2013-11-28  0:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 22:58 imaxima babel yggdrasil
2013-11-21 23:07 ` Rüdiger Sonderfeld
2013-11-21 23:33   ` Eric Schulte
2013-11-22 17:05     ` yggdrasil
2013-11-23 16:12       ` Eric Schulte
2013-11-26 21:53         ` yggdrasil
2013-11-27  8:54           ` Alan Schmitt
2013-11-27 23:10             ` yggdrasil
2013-11-28  0:42               ` Nick Dokos [this message]
2013-11-28  1:09               ` Thomas S. Dye
2013-11-30 10:19               ` Cannot generate latex preview images (Was: imaxima babel) Alan Schmitt
2013-11-30 12:49                 ` Cannot generate latex preview images Nicolas Goaziou
2013-12-02 10:09                   ` Alan Schmitt

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=87fvqhl5le.fsf@gmail.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.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 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).