On 2/7/07, Michael Gerz <[EMAIL PROTECTED]> wrote:
Has this patch been applied in the mean-time?
Apparently so.
--
John C. McCabe-Dansted
PhD Student
University of Western Australia
Has this patch been applied in the mean-time?
Michael
Georg Baum schrieb:
John McCabe-Dansted wrote:
On 1/30/07, Georg Baum
<[EMAIL PROTECTED]> wrote:
I don't understand why we need to create an absolute path here:
Because in 1.5.0svn (but not 1.4.4svn) we get:
Assertion t
On 2/1/07, Georg Baum <[EMAIL PROTECTED]> wrote:
Am Mittwoch, 31. Januar 2007 12:34 schrieb John McCabe-Dansted:
> So, what do you think of the patch below:?
It does not apply. Please send one against current svn, and as attachment
please, then it is easier for me to apply.
Its easier for me
Am Mittwoch, 31. Januar 2007 12:34 schrieb John McCabe-Dansted:
> So, what do you think of the patch below:?
It does not apply. Please send one against current svn, and as attachment
please, then it is easier for me to apply.
Georg
John McCabe-Dansted wrote:
>
> On 1/30/07, Georg Baum
> <[EMAIL PROTECTED]> wrote:
>> I don't understand why we need to create an absolute path here:
>
> Because in 1.5.0svn (but not 1.4.4svn) we get:
> Assertion triggered in lyx::support::FileName::FileName(const
> std::string&) by failing
Jean-Marc Lasgouttes wrote:
>> "José" == José Matos <[EMAIL PROTECTED]> writes:
>
> José> Any objection to apply this patch to trunk?
>
> The second part is fine, the first looks bad:
>
> @@ -1145,8 +1145,8 @@
> busy(true);
>
> // get LaTeX-Filename
> - string const name = getLate
> "José" == José Matos <[EMAIL PROTECTED]> writes:
José> Any objection to apply this patch to trunk?
The second part is fine, the first looks bad:
@@ -1145,8 +1145,8 @@
busy(true);
// get LaTeX-Filename
- string const name = getLatexName(false);
string const
On Sunday 28 January 2007 4:36:22 am John McCabe-Dansted wrote:
> On 1/23/07, John McCabe-Dansted <[EMAIL PROTECTED]> wrote:
> > ChkTex does not create .tex file before running chktex, causing "could
> > not run chktex successfully" error.
>
> This is caused by runChkTeX outputting the .tex file to
