From: Pascal Fleury <fleury@google.com>
To: Skip Collins <skip.collins@gmail.com>
Cc: Bastien <bzg@gnu.org>, emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Export arrays for 'sh' code blocks when using bash
Date: Wed, 23 Apr 2014 16:13:22 +0200 [thread overview]
Message-ID: <CACc7+8YT_2Orcj4-+HyKODp2zM+YqJ3=McGNApO_UMDXG=f-3A@mail.gmail.com> (raw)
In-Reply-To: <CABUh-75CxYdwms_oqo_8JBdm+hueC7b0S79bkh72292PfNp7Fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Hi,
Yes that is a test I added, and did not think of older versions of bash
(have not used bash3 in quite a long time :-)
Actually, if we have bash3, then we should not use the associative arrays
at all, but fallback to the lists.
Will give it a go.
--paf
On Wed, Apr 23, 2014 at 3:51 PM, Skip Collins <skip.collins@gmail.com>wrote:
> On Tue, Apr 22, 2014 at 5:22 PM, Bastien <bzg@gnu.org> wrote:
> > Mhh... okay then, thanks for mentioning it.
>
> The stackoverflow link contains what appears to be a good workaround
> that functions in old and new versions of bash. Perhaps Pascal Fleury
> could modify the org code to avoid using 'declare -A' when bash
> version < 4.
>
--
--paf
[-- Attachment #2: Type: text/html, Size: 1199 bytes --]
next prev parent reply other threads:[~2014-04-23 14:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 10:26 Export arrays for 'sh' code blocks when using bash Pascal Fleury
2014-03-27 17:43 ` Eric Schulte
2014-03-27 22:52 ` Pascal Fleury
2014-03-29 19:37 ` Eric Schulte
2014-04-06 23:25 ` Pascal Fleury
2014-04-11 2:38 ` Eric Schulte
2014-04-11 9:33 ` Bastien
2014-04-14 8:48 ` Pascal Fleury
2014-04-15 3:35 ` Eric Schulte
2014-04-15 11:15 ` Pascal Fleury
2014-04-22 14:47 ` Skip Collins
2014-04-22 15:37 ` Bastien
2014-04-22 17:19 ` Skip Collins
2014-04-22 20:59 ` Bastien
2014-04-22 21:04 ` Skip Collins
2014-04-22 21:09 ` Skip Collins
2014-04-22 21:22 ` Bastien
2014-04-23 13:51 ` Skip Collins
2014-04-23 14:13 ` Pascal Fleury [this message]
2014-04-23 16:31 ` Skip Collins
2014-04-24 1:23 ` Eric Schulte
2014-04-24 7:44 ` Pascal Fleury
2014-04-22 21:15 ` Bastien
2014-04-15 3:37 ` Eric Schulte
2014-04-15 15:37 ` Nick Dokos
2014-04-17 6:31 ` Bastien
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='CACc7+8YT_2Orcj4-+HyKODp2zM+YqJ3=McGNApO_UMDXG=f-3A@mail.gmail.com' \
--to=fleury@google.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=skip.collins@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).