From: Michael Brand <michael.ch.brand@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: link abbreviation with multiple params, e. g. for geo locations
Date: Fri, 14 Jun 2013 22:13:42 +0200 [thread overview]
Message-ID: <CALn3zojO==XDKV-_LW2qH0=1DtWUkhAHZ0HTeLoOkb8n4rwTWw@mail.gmail.com> (raw)
In-Reply-To: <878v2c8sja.fsf@gmail.com>
Hi Eric
On Fri, Jun 14, 2013 at 8:18 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
>> The :session is only to have more than one call which works for
>> emacs-lisp source blocks. Am I doing something wrong or is this a bug?
>
> Sessions are not supported in every language. Shell code blocks do
> *not* support sessions (or rather it looks like someone started to
> implement session support, but never completed it).
Good to know. It is high on my wishlist. I often take notes about
shell and utilities and just a few days ago I planned to improve by
using, well, babel source blocks. Now I know that I have to use some
workaround. What about :var dummy_name?
#+NAME: unicode_normal_form_c
#+HEADER: :var dummy_name="workaround to get different result blocks"
#+BEGIN_SRC sh :shebang #!/bin/sh :eval no :exports code
printf 'a\xcc\x88' | od -Ax -tx1
printf 'a\xcc\x88' | iconv -f UTF-8-MAC -t UTF-8 | od -Ax -tx1
printf 'a\xcc\x88' | iconv -f UTF-8-MAC -t UTF-8 2>&1 > /dev/null
echo "(`uname`, `date +%Y-%m-%d`)"
#+END_SRC
- OS X (implementation of iconv by Apple, not e. g. MacPorts):
#+CALL: unicode_normal_form_c[:results output verbatim :eval
no-export :exports results](dummy_name="osx")
#+RESULTS: unicode_normal_form_c[:results output verbatim :eval
no-export :exports results](dummy_name="osx")
: 0000000 61 cc 88
: 0000003
: 0000000 c3 a4
: 0000002
: (Darwin, 2013-06-14)
- GNU/Linux:
#+CALL: unicode_normal_form_c[:results output verbatim :eval
no-export :exports results](dummy_name="gnu")
#+RESULTS: unicode_normal_form_c[:results output verbatim :eval
no-export :exports results](dummy_name="gnu")
: 000000 61 cc 88
: 000003
: 000000
: iconv: conversion from `UTF-8-MAC' is not supported
: Try `iconv --help' or `iconv --usage' for more information.
: (Linux, 2013-06-14)
Is there a better workaround or would you accept :var dummy_name for
my ERT that I mentioned?
And how can I break the long lines #+CALL into multiple lines staying
near their individual #+CALL line, when moving header arguments
into #+BEGIN_SRC and its #+HEADERs is not possible for cases where
variety in the values of header arguments between calls or between
call and #+BEGIN_SRC is necessary?
Michael
next prev parent reply other threads:[~2013-06-14 20:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 17:03 link abbreviation with multiple params, e. g. for geo locations Michael Brand
2013-05-29 16:14 ` Michael Brand
2013-06-05 17:19 ` Michael Brand
2013-06-06 17:01 ` Eric Schulte
2013-06-07 14:53 ` Michael Brand
2013-06-07 15:18 ` Eric Schulte
2013-06-07 19:16 ` Michael Brand
2013-06-07 19:54 ` Vitalie Spinu
2013-06-08 18:05 ` Eric Schulte
2013-06-08 18:52 ` Vitalie Spinu
2013-06-08 19:21 ` Eric Schulte
2013-06-14 17:54 ` Michael Brand
2013-06-14 18:18 ` Eric Schulte
2013-06-14 20:13 ` Michael Brand [this message]
2013-06-19 9:39 ` Michael Brand
2013-06-07 20:10 ` Achim Gratz
2013-06-08 18:03 ` Eric Schulte
2013-06-09 7:56 ` Michael Brand
2013-06-09 8:07 ` Michael Brand
2013-06-09 19:18 ` Eric Schulte
2013-06-09 20:32 ` Michael Brand
2013-06-11 13:12 ` Eric Schulte
-- strict thread matches above, loose matches on Subject: below --
2013-05-05 15:06 Michael Brand
2013-05-06 7:06 ` Christian Moe
2013-05-06 18:42 ` Michael Brand
2013-05-06 22:29 ` Christian Moe
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='CALn3zojO==XDKV-_LW2qH0=1DtWUkhAHZ0HTeLoOkb8n4rwTWw@mail.gmail.com' \
--to=michael.ch.brand@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.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.
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).