[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Texmacs-dev] /bin/sh vs. /bin/bash in Ubuntu

From: Joris van der Hoeven
Subject: Re: [Texmacs-dev] /bin/sh vs. /bin/bash in Ubuntu
Date: Sat, 25 Apr 2009 22:18:10 +0200
User-agent: Mutt/1.5.9i

On Wed, Apr 22, 2009 at 12:34:16PM +0200, Andrea Gamba wrote:
> Dear Joris,
> can you fix also the old  /bin/sh - /bin/bash problem, that still 
> hampers the use of external mathematical programs in Ubuntu 8.10? See:
> https://launchpad.net/ubuntu/+source/texmacs/+bug/58498
> and also:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497020
> https://savannah.gnu.org/bugs/?18519
> https://bugs.launchpad.net/ubuntu/+source/texmacs/+bug/181315
> https://bugs.launchpad.net/ubuntu/+source/texmacs/+bug/70655
> I know there was a long discussion about it. At the end of the story, I 
> think there are two easy solutions:
> 1) change /bin/sh -> /bin/bash in the first row of all shell scripts in 
> /usr/local/libexec/TeXmacs/bin/, that should still be good for all 
> distributions;

This /bin/sh issue comes up every now and then; a pain.
In principle, as long as we no not use any bash-specific stuff,
then we probably should stick to /bin/sh.

Andrey, do you remember the previous conclusions on this subject?

> 2) do it in a distribution-dependent way, i.e. only for the Ubuntu and 
> Debian package (although the problem is only in Ubuntu, there is usually 
> a single package for both.)
> Other solutions are more complicated.
> Apart from the /bin/sh - /bin/bash problem:
> The Octave plugin hangs TeXmacs at start. The fix is to change 
> tm-start.oct and .octaverc in  
> /usr/local/share/TeXmacs/plugins/octave/octave/ as follows:
> gset -> __gnuplot_set__
> LOADPATH=[[...,LOADPATH]] -> addpath([[...]])
> PS1=... -> PS1(...)
> PS2=... -> PS2(...)
> to take into account changes in the Octave script language (that are 
> listed by typing "new" at the Octave prompt). See:
> https://bugs.launchpad.net/ubuntu/+source/texmacs/+bug/181315
> Unfortunately, the list of broken plugins (at least in Ubuntu) is not 
> exhausted here. I would like to contribute to improve the situation, is 
> it ok to go on posting plugin-related patches here?

Sure, if you have any patches for these problems, I will apply them.

Thanks, Joris

reply via email to

[Prev in Thread] Current Thread [Next in Thread]