Re: \nonstopmode does not work

2006-07-05 Thread Andre Poenitz
On Tue, Jul 04, 2006 at 02:05:12PM +0200, Enrico Forestieri wrote: > > Leave it out. Letting vim read settings from files of unknown source is a > > security risk, so it is disabled by default, and we should not encourage > > people to switch this on. I guess it is similar with emacs. > > I cannot

Re: \nonstopmode does not work

2006-07-04 Thread Joost Verburg
Enrico Forestieri wrote: I installed LyX using the installer by Joost to test them on a pure win32 environment. They work provided that the patch I posted earlier in this thread is applied to dvipost. I'll include this patch in the next version of the installer. Joost

Re: \nonstopmode does not work

2006-07-04 Thread Enrico Forestieri
On Tue, Jul 04, 2006 at 12:48:55PM +0200, Jean-Marc Lasgouttes wrote: > > "Bo" == Bo Peng <[EMAIL PROTECTED]> writes: > > Bo> Attached are my versions of the configure.py patch. I use r""" """ > Bo> to improve readability. I also replace \t with spaces in the > Bo> original 1.5 patch, which is

Re: \nonstopmode does not work

2006-07-04 Thread Enrico Forestieri
On Tue, Jul 04, 2006 at 01:24:45PM +0200, Georg Baum wrote: > Jose' Matos wrote: > > > On Tuesday 04 July 2006 11:34, Enrico Forestieri wrote: > >> Ops, forgot to ":set expandtab" in vim. Why not put a > >> "# vim: set et ts=4 sw=4:" line at the end of python scripts? > > > > I am not against s

Re: \nonstopmode does not work

2006-07-04 Thread Georg Baum
Jose' Matos wrote: > On Tuesday 04 July 2006 11:34, Enrico Forestieri wrote: >> Ops, forgot to ":set expandtab" in vim. Why not put a >> "# vim: set et ts=4 sw=4:" line at the end of python scripts? > > I am not against such a change. :-) > The same applies for emacs settings although we are

Re: \nonstopmode does not work

2006-07-04 Thread Jose' Matos
On Tuesday 04 July 2006 11:34, Enrico Forestieri wrote: > Ops, forgot to ":set expandtab" in vim. Why not put a > "# vim: set et ts=4 sw=4:" line at the end of python scripts? I am not against such a change. :-) The same applies for emacs settings although we are using the emacs default setti

Re: \nonstopmode does not work

2006-07-04 Thread Jean-Marc Lasgouttes
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes: Bo> Attached are my versions of the configure.py patch. I use r""" """ Bo> to improve readability. I also replace \t with spaces in the Bo> original 1.5 patch, which is not allowed now. Bo> Please confirm that they still work under windows. Bo If

Re: \nonstopmode does not work

2006-07-04 Thread Enrico Forestieri
On Tue, Jul 04, 2006 at 12:03:54AM -0500, Bo Peng wrote: > Attached are my versions of the configure.py patch. I use r""" """ to > improve readability. Indeed, they're more readable. > I also replace \t with spaces in the original > 1.5 patch, which is not allowed now. Ops, forgot to ":set exp

Re: \nonstopmode does not work

2006-07-03 Thread Bo Peng
Attached are my versions of the configure.py patch. I use r""" """ to improve readability. I also replace \t with spaces in the original 1.5 patch, which is not allowed now. Please confirm that they still work under windows. Bo Index: lib/configure.py

Re: \nonstopmode does not work

2006-07-03 Thread Bo Peng
The attached patches for 1.4.x and 1.5.x work for me. Please test. -writeToFile('a b.tex', r'\nonstopmode\message{working^^J}' ) -if ''.join(cmdOutput(LATEX + ' "a b"')).find('working') != -1: +writeToFile('a b.tex', r'\message{working^^J}' ) +if os.name == 'nt': + latex_out

Re: \nonstopmode does not work

2006-07-03 Thread Enrico Forestieri
On Mon, Jul 03, 2006 at 11:28:19PM +0200, Jean-Marc Lasgouttes wrote: > > "Bo" == Bo Peng <[EMAIL PROTECTED]> writes: > > >> The solution would be to have some temp file which does \input{"a > >> b"} (is that what we are checking?), just like we do for the cygwin > >> check. > > Bo> Can we ju

Re: \nonstopmode does not work

2006-07-03 Thread Enrico Forestieri
On Mon, Jul 03, 2006 at 10:29:20PM +0200, Jean-Marc Lasgouttes wrote: > >>>>> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes: > > Bo> Hi, Enrico, JMarc, Configure.py stops at checkTeXAllowSpace, so > Bo> \nonstopmode does not work as expected

Re: \nonstopmode does not work

2006-07-03 Thread Jean-Marc Lasgouttes
> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes: >> The solution would be to have some temp file which does \input{"a >> b"} (is that what we are checking?), just like we do for the cygwin >> check. Bo> Can we just restore to -interaction=nonstopmode for now? Actually, Bo> if this option works,

Re: \nonstopmode does not work

2006-07-03 Thread Bo Peng
The solution would be to have some temp file which does \input{"a b"} (is that what we are checking?), just like we do for the cygwin check. Can we just restore to -interaction=nonstopmode for now? Actually, if this option works, I do not see a reason to try a wrapper file. Bo

Re: \nonstopmode does not work

2006-07-03 Thread Jean-Marc Lasgouttes
>>>>> "Bo" == Bo Peng <[EMAIL PROTECTED]> writes: Bo> Hi, Enrico, JMarc, Configure.py stops at checkTeXAllowSpace, so Bo> \nonstopmode does not work as expected. This is why I did not fix this instance of nonstopmode in my patch :) I suspected something

\nonstopmode does not work

2006-07-03 Thread Bo Peng
Hi, Enrico, JMarc, Configure.py stops at checkTeXAllowSpace, so \nonstopmode does not work as expected. Any idea? Bo % latex 'a b.tex' This is TeX, Version 3.14159 (Web2C 7.4.5) ! I can't find file `a'. <*> a b.tex Please type another input file name: X ! I