On Tue, Jun 06, 2006 at 10:03:47AM +0200, Juergen Spitzmueller wrote:
> Enrico Forestieri wrote:
>
> > It is unlikely that the problem is related to that particular piece
> > of code as Edwin is using the 1.5 version and the user the 1.4 version,
> > most probably. I think this is a MSYS bash fail
On Tuesday 06 June 2006 09:03, Juergen Spitzmueller wrote:
> (I can't, my knowledge to Python is limited to dead parrots).
You are in the right path to enlightenment. ;-)
> Jürgen
--
José Abílio
Enrico Forestieri wrote:
> It is unlikely that the problem is related to that particular piece
> of code as Edwin is using the 1.5 version and the user the 1.4 version,
> most probably. I think this is a MSYS bash failure as both versions
> work ok with the cygwin bash.
OK, thanks for the enlight
On Sun, Jun 04, 2006 at 06:27:11PM +0200, Juergen Spitzmueller wrote:
> Enrico Forestieri wrote
> > Please, don't fix what is not broken...
>
> I certainly won't fix it (my knowledge on shell scripting is close to zero,
> so
> thanks for your explanations).
> Note, however, that something *is*
Enrico Forestieri wrote
> Please, don't fix what is not broken...
I certainly won't fix it (my knowledge on shell scripting is close to zero, so
thanks for your explanations).
Note, however, that something *is* broken. The script crashes on Edwins box
(and we have a similar report from a window
On Sun, Jun 04, 2006 at 01:59:28PM +0200, Juergen Spitzmueller wrote:
> Edwin Leuven wrote:
> > > Edwin, does the situation improve if you change that?
> >
> > i have different script here (that looks ok):
>
> Fine. So my suspicion was basically right. You'll send a patch, won't you?
Please, don
On Sun, Jun 04, 2006 at 01:33:41PM +0200, Edwin Leuven wrote:
> Juergen Spitzmueller wrote:
> > if test -z "$COMSPEC" || test -z "$ComSpec"; then SEP=':'; else SEP=';'; fi
> >
> > Edwin, does the situation improve if you change that?
>
> i have different script here (that looks ok):
It is exact
On Sun, Jun 04, 2006 at 01:18:37PM +0200, Juergen Spitzmueller wrote:
> Edwin Leuven wrote:
> > > It looks like the script fails (sh crashes), so that it has to be
> > > re-run everytime. You should investigate why it cashes on windows.
> >
> > yeah, but time is probably better spent getting rid o
Juergen Spitzmueller wrote:
Edwin Leuven wrote:
it's the script that's in trunk: i didn't touch it (dunno anything about
shell scripting...)
I see. But does it solve your problem?
no, i had the problem with this in the first place...
If so, it should probably be backported
to branch.
i s
Edwin Leuven wrote:
> it's the script that's in trunk: i didn't touch it (dunno anything about
> shell scripting...)
I see. But does it solve your problem? If so, it should probably be backported
to branch.
Jürgen
Juergen Spitzmueller wrote:
Edwin Leuven wrote:
Edwin, does the situation improve if you change that?
i have different script here (that looks ok):
Fine. So my suspicion was basically right. You'll send a patch, won't you?
it's the script that's in trunk: i didn't touch it (dunno anything a
Edwin Leuven wrote:
> > Edwin, does the situation improve if you change that?
>
> i have different script here (that looks ok):
Fine. So my suspicion was basically right. You'll send a patch, won't you?
Jürgen
Juergen Spitzmueller wrote:
if test -z "$COMSPEC" || test -z "$ComSpec"; then SEP=':'; else SEP=';'; fi
Edwin, does the situation improve if you change that?
i have different script here (that looks ok):
DOSISH=no
case `uname -s` in
CYGWIN*|Cygwin*|cygwin*)
# MikTeX's kpsewhich says "kp
Edwin Leuven wrote:
> > It looks like the script fails (sh crashes), so that it has to be
> > re-run everytime. You should investigate why it cashes on windows.
>
> yeah, but time is probably better spent getting rid of the script
> altogether.
In the meantime I had a quick look at the script. I d
Jean-Marc Lasgouttes wrote:
It looks like the script fails (sh crashes), so that it has to be
re-run everytime. You should investigate why it cashes on windows.
yeah, but time is probably better spent getting rid of the script
altogether.
(let's hope that bo reads this thread...)
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> (2) The output you see on the console, however, is from
Juergen> scripts/TeXFiles.sh that creates a list of all available
Juergen> cls/sty/bst/bib files, using kpsewhich again. The info is
Juergen> used by the TeXInfo dia
Edwin Leuven wrote:
> inserting a bib is very slow (qt4/windows)
What means slow and when is it slow (while opening the dialog or after
applying?)
> any idea what is going on here?
Two possibilities (dependig on the answer to the question above):
(1)
If you add or delete a bib file, Buffer::up
17 matches
Mail list logo
