Am Freitag, 8. Oktober 2010 schrieb Stephan Witt:
> Am 07.10.2010 um 14:42 schrieb Kornel Benko:
>
> > Am Dienstag 05 Oktober 2010 schrieb Stephan Witt:
> >> Fine. And you don't know how it got generated?
> >
> > The following does not harm here. And both
> > 1.) cmake on a used build-dir
> >
Am 07.10.2010 um 14:42 schrieb Kornel Benko:
> Am Dienstag 05 Oktober 2010 schrieb Stephan Witt:
>> Fine. And you don't know how it got generated?
>
> The following does not harm here. And both
> 1.) cmake on a used build-dir
> 2.) cmake on a fresh build-dir
> created Makefiles on lin
Am 16.09.2010 um 16:39 schrieb Pavel Sanda:
> Stephan Witt wrote:
>>
>> I have not told about that before... but at least for CVS I have problems
>> with the current state of the VCS code.
>> Unfortunately I'm bound to it here. So effectively I has to use the command
>> line interface of CVS an
Am 07.10.2010 16:41, schrieb Vincent van Ravesteijn:
GNU patch:
http://gnuwin32.sourceforge.net/packages/patch.htm
Thank you. I'll testing that out. Do you already use this program on
Windows?
regards Uwe
>> Yes, please.
>
> please check my commit.
Sorry, my mistake. All things from your commit should not have gone into
SVN: The preamble line is superfluous and misleading and we already have
a template file and once decided to have either a template or an example
file for each document classes
OK, but I don't know how to apply patches if not by using my SVN
client. What program can do this on Windows?
GNU patch:
http://gnuwin32.sourceforge.net/packages/patch.htm
Vincent
Am Dienstag 05 Oktober 2010 schrieb Stephan Witt:
> Fine. And you don't know how it got generated?
The following does not harm here. And both
1.) cmake on a used build-dir
2.) cmake on a fresh build-dir
created Makefiles on linux so, that the compile goes ok on the first run.
To q
C Morgenstern wrote:
> Thanks for the quick response! Unfortunately, that link
> you suggested is busted. But I'm sure the admins will
> sort things out shortly.
you really dont need to wait. we have many mirrors available,
see http://www.lyx.org/Download
pavel
Am Dienstag, 5. Oktober 2010 schrieb Stephan Witt:
> The 2nd build fails. But it should have failed on the 1st run too.
>
Stephan, I did not find anything fundamentally wrong. Only one idea:
We could mark the moc-files as generated. But since they are already all
explicitly mentioned in "OUTPUT" o
>
> please check my commit.
It seems fine, many thanks!
There is one comment about the layout file command. While I handled
this layout, I faced necessity to control 'line breaks' of the TeX
output.
For example, while I wanted
\begin{aug}
\author{...}
\author{...}
\end{aug}
this was imposs
Jean-Marc Lasgouttes lyx.org> writes:
>
> Le 7 oct. 10 à 07:50, C Morgenstern a écrit :
> > You should know that the ftp server (ftp.lyx.org:21)
> > is requiring a username and password, so I can't
> > download the OSX binary.
>
> I contacted the admins to fix this. In the meantime, you can use
Le 7 oct. 10 à 07:50, C Morgenstern a écrit :
You should know that the ftp server (ftp.lyx.org:21)
is requiring a username and password, so I can't
download the OSX binary.
I contacted the admins to fix this. In the meantime, you can use
http://ftp.lyx.org/
JMarc
12 matches
Mail list logo
