From: "Sébastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [babel] Sh problem when echo'ing input data with ' inside
Date: Mon, 17 Jan 2011 23:39:43 +0100 [thread overview]
Message-ID: <80vd1n40k0.fsf@missioncriticalit.com> (raw)
In-Reply-To: 87fwsrusac.fsf@Rainer.invalid
Hi Achim and Eric,
Achim Gratz wrote:
> The script produced by babel should actually look like this:
>
> #+begin_src sh
> data=$(cat <<'BABEL_STRING'
> Num.ro du compte :;979-9500975-24;Compte Maxi
> Date valeur;R.f.rence de l'op.ration;Description;Montant de l'op.ration;Devise;Date d'op.ration;Compte de contrepartie;Nom de la contrepartie :;Communication 1 :;Communication 2 :
> 04-06-2009;A9F04NT01WK300TG;Virem. internet;420,00;EUR;04-06-2009;799-5900947-23;PAYEE ONE; ;
> 24-02-2009;A9B24NT012K4018Z;Virem. internet;-54,93;EUR;24-02-2009;799-9974005-30;ME;Eigen rekening;
> 18-05-2008;A8E19NT000S604QI;Virem. internet;-1.000,00;EUR;19-05-2008;799-8068445-18;PAYEE TWO; ;
> BABEL_STRING
> )
> echo "$data"
> #+end_src
>
> That is no indentation and the here-tag should be in quotes (otherwise the
> here-script is subject to shell expansion).
The above, from which I even removed the accentuated characters (from French),
still does not work...
Now, I can imagine it is due to Cygwin, not to Emacs/Org/Babel. Though, that's
a problem in general for the use of sh blocks from Org... under Windows, then.
- Has anyone any experience with this?
- Can some Bash user confirm what I see?
- Can some Windows user confirm this with other Unix-emulation shells (MinGW
and the like)?
> It's probably possible to do a contrived redirection and not use a variable
> to store the data, but I'm afraid I won't grok this today.
Or maybe using a real file as temporary storage? Overkill, or simply needed?
Best regards,
Seb
--
Sébastien Vauban
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode-mXXj517/zsQ@public.gmane.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2011-01-17 22:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 12:42 [babel] Sh problem when echo'ing input data with ' inside Sébastien Vauban
2011-01-17 16:24 ` Eric Schulte
2011-01-17 19:29 ` Sébastien Vauban
2011-01-17 19:54 ` Eric Schulte
2011-01-17 22:49 ` Sébastien Vauban
2011-01-17 20:00 ` Achim Gratz
2011-01-17 20:29 ` Eric Schulte
2011-01-17 21:36 ` Achim Gratz
2011-01-17 22:39 ` Sébastien Vauban [this message]
2011-01-17 22:51 ` Achim Gratz
2011-01-18 7:02 ` Sébastien Vauban
2011-01-18 9:22 ` Sébastien Vauban
2011-01-18 16:24 ` Eric Schulte
2011-01-18 17:31 ` Sébastien Vauban
2011-01-18 18:23 ` Achim Gratz
2011-01-20 19:17 ` Achim Gratz
2011-01-20 22:12 ` Sébastien Vauban
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=80vd1n40k0.fsf@missioncriticalit.com \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).