From mint-bounce@lists.fishpool.fi Sun Dec 19 19:56:55 2004 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <7BECFCC4-51EF-11D9-8640-000D9356BAEE@epfl.ch> Content-Type: text/plain; charset=US-ASCII; format=flowed To: mint@lists.fishpool.fi From: =?ISO-8859-1?Q?Philipp_Donz=E9?= Subject: [MiNT] XaAES: Bug in shel_write? Date: Sun, 19 Dec 2004 19:55:00 +0100 X-Mailer: Apple Mail (2.619) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: philipp.donze@epfl.ch Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-1.0 tagged_above=-50.5 required=3.8 tests=BAYES_00 X-Spam-Level: Hi, While debugging a little GEMJing demo application I realized that shel_write(SWM_LAUNCH, GEMAPP, CL_PARSE, path, arg) has an odd behaviour under current XaAES version: It changes the current working directory of the parent process to point to the directory of the launched child process. I don't think this behaviour is documented somewhere. (Tell me if I'm wrong.) At the moment I can't test with other AES replacements, as I've only MagiC and XaAES installed. regards Philipp