dash.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joachim Breitner <mail@joachim-breitner.de>
To: dash@vger.kernel.org
Subject: dash drops exported bash functions
Date: Wed, 10 Feb 2016 16:18:53 +0100	[thread overview]
Message-ID: <1455117533.18345.59.camel@joachim-breitner.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1027 bytes --]

Dear dash developers,

a change in 0.5.8, very likely this one
http://git.kernel.org/cgit/utils/dash/dash.git/commit/?id=46d3c1a614f11f0d40a7e73376359618ff07abcd
broke the exporting of bash shell functions via the environment.

The attached script shows the breakage, as it outputs

$ ./exporttest.sh 
exportest called ()
Setting up environment
Calling myself
exportest called (1)
function foo successfully called
Calling myself directly
exportest called (2)
function foo successfully called
Calling myself via dash
exportest called (3)
/tmp/exporttest.sh: Zeile 33: foo: Kommando nicht gefunden.
Done

Exporting bash functions via the environment might be a rarely used
feature, but it is used in practice, unfortunately (otherwise I
wouldn’t have noticed this).

Thanks,
Joachim

-- 
Joachim “nomeata” Breitner
  mail@joachim-breitner.de • https://www.joachim-breitner.de/
  XMPP: nomeata@joachim-breitner.de • OpenPGP-Key: 0xF0FBF51F
  Debian Developer: nomeata@debian.org


[-- Attachment #1.2: exporttest.sh --]
[-- Type: application/x-shellscript, Size: 523 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-02-10 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-10 15:18 Joachim Breitner [this message]
2016-02-10 15:54 ` dash drops exported bash functions Eric Blake
2016-02-10 16:31   ` Joachim Breitner
2016-02-11  3:53 Makarius
2016-02-11 12:15 ` Makarius
2016-02-11 13:40   ` Makarius
2016-02-11 14:19     ` Olof Johansson
2016-02-11 14:30       ` Makarius
2016-02-11 14:46         ` Stephane Chazelas

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1455117533.18345.59.camel@joachim-breitner.de \
    --to=mail@joachim-breitner.de \
    --cc=dash@vger.kernel.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.
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 NNTP newsgroup(s).