emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Pascal Fleury <fleury@google.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: Skip Collins <skip.collins@gmail.com>, Bastien <bzg@gnu.org>,
	emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Export arrays for 'sh' code blocks when using bash
Date: Thu, 24 Apr 2014 09:44:45 +0200	[thread overview]
Message-ID: <CACc7+8YY_ChFQW01LM-GLQFu=Ek2fRA4S6BEyTgk99bSmemwQQ@mail.gmail.com> (raw)
In-Reply-To: <87oazr5xkg.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1287 bytes --]

On Thu, Apr 24, 2014 at 3:23 AM, Eric Schulte <schulte.eric@gmail.com>wrote:

> Skip Collins <skip.collins@gmail.com> writes:
>
> > On Wed, Apr 23, 2014 at 10:13 AM, Pascal Fleury <fleury@google.com>
> wrote:
> >> (have not used bash3 in quite a long time :-)
> >
> > Even OS X Mavericks uses bash 3. So it will be around for quite a long
> time.
> >
>
> I believe Bash 4 is GPLv3 and Bash 3 is GPLv2, so it is very possible
> that OSX will never upgrade to the current bash.
>
> If the fix is obvious and simple then it sounds like a win.
>
>
I think it should be. It could prod the version the very first time it
runs, and use that.


> I suppose the argument could be made that an Emacs project should not go
> out of it's way to support old versions of software which are
> potentially being used only to avoid GPLv3 licensing... but I won't make
> that argument here.
>

Even array support in ob-shell.el is a win for bash3, and as a user of Mac
OSX myself, I would not like a project like org-mode to push such pains
onto the users especially as here it is a regression for bash3 users.

I'm a bit overbooked these days, I hope you won't mind if it will take a
few more days for a fix.

--paf


>
> --
> Eric Schulte
> https://cs.unm.edu/~eschulte
> PGP: 0x614CA05D
>



-- 
--paf

[-- Attachment #2: Type: text/html, Size: 2354 bytes --]

  reply	other threads:[~2014-04-25  1:34 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
2014-04-23 16:31                                   ` Skip Collins
2014-04-24  1:23                                     ` Eric Schulte
2014-04-24  7:44                                       ` Pascal Fleury [this message]
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+8YY_ChFQW01LM-GLQFu=Ek2fRA4S6BEyTgk99bSmemwQQ@mail.gmail.com' \
    --to=fleury@google.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    --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).