This time with the patch ;)
Soeren
Kayvan>> On Thu, Jul 11, 2002 at 08:01:25PM +0200, Soeren Pietsch wrote:
>>> Kayvan>> It seems fine, except that I am concerned about checking for the exact
>>> Kayvan>> string CYGWIN_NT-5.0
>>>
>>> Kayv
Kayvan> On Thu, Jul 11, 2002 at 08:01:25PM +0200, Soeren Pietsch wrote:
>> Kayvan>> It seems fine, except that I am concerned about checking for the exact
>> Kayvan>> string CYGWIN_NT-5.0
>>
>> Kayvan>> What happens with the ``uname -s'' s
Kayvan>> It seems fine, except that I am concerned about checking for the exact
Kayvan>> string CYGWIN_NT-5.0
Kayvan>> What happens with the ``uname -s'' string changes to CYGWIN_NT-5.1?
Kayvan>> I think it might be better to have a case statement there:
Kayvan>> sysname=`uname -s`
Kayvan>> cas
Kayvan> It seems fine, except that I am concerned about checking for the exact
Kayvan> string CYGWIN_NT-5.0
Kayvan> What happens with the ``uname -s'' string changes to CYGWIN_NT-5.1?
Kayvan> I think it might be better to have a case statement there:
Kayvan> sysname=`uname -s`
Kayvan> case "$sy
Kayvan> On Tue, Jul 09, 2002 at 05:21:07PM +0200, Jean-Marc Lasgouttes wrote:
>> >>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes:
>>
>> >>>>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writ
>>>>>> "Soeren" == Soeren Pietsch <[EMAIL PROTECTED]> writes:
Soeren>> Hi, I had a bit of a problem with the lyx configure script on
Soeren>> a cygwin environment. The following check only works if the sh
Soeren>> shell points to the bash sh
Herbert> Soeren Pietsch wrote:
>> No it is not! See my few lines below. Perhaps if I read your patch
>> right you should just use return (RemoveExtension(orig_file));
>> instead of my way returning the file with extension.
>> This simply checks whether the user su
Herbert> Soeren Pietsch wrote:
>>>>>>>>"Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
>>>>>>>>
>>
>> Herbert>> Jean-Marc Lasgouttes wrote:
>>
>>>>>>>>>>"Herbert
>> "Herbert" == Herbert Voss <[EMAIL PROTECTED]> writes:
Herbert>> Jean-Marc Lasgouttes wrote:
"Herbert" == Herbert Voss <[EMAIL PROTECTED]>
writes:
Herbert>> there is a bug in current cvs. With the attached patch all
Herbert>> (e)ps/pdf-files are exported to latex
Dekel> On Wed, Jun 26, 2002 at 06:39:19PM +0200, Andre Poenitz wrote:
>> On Wed, Jun 26, 2002 at 05:25:45PM +0100, Angus Leeming wrote:
>> > I think that LaTeX falls over if there is space /between/ keys:
>> > key1, key2, key3
>>
>> I think it does. I seem to remember Konni complaining about
Hi,
Agnus could you tell why we need the following?
2001-08-01 Angus Leeming <[EMAIL PROTECTED]>
* insetcite.C (latex): Paranoia check. Make sure that there is no
whitespace between the citation keys.
// Paranoia check: make sure that there is no whitespace in here
string content;
Herbert> at this time only the File->Export->Latex works in your way, all
Herbert> filenames are exported without extension.
Herbert> LyX do not need an extension to recognize the correct file-format.
Herbert> it maybe an option to pass _all_ files without the extension to
Herbert> latex.
Herbert>
Hi,
I noticed a difference how the filename in different converters
handled.
In the epstoxpm converter $$i points to the original file in the
source directory. In the epstopdf converter $$i points to a temporary
file. Why this difference? If I wrote my own converter I have no
chance to get the pa
Hi,
I had a bit of a problem with the lyx configure script on a cygwin
environment.
The following check only works if the sh shell points to the bash
shell.
### Adjust PATH for Win32 (Cygwin)
if test "x$OSTYPE" = xcygwin; then
echo "configure: cygwin detected; path correction"
srcdir=`cygpat
Juergen> It's the same for the indented paragraphs also. We droped that too and it
doesn't
Juergen> seem someone wants it back (appart from me as I think it's pretty usefull,
but one
Juergen> can always use an office software ;)
he you are not the only one! But one can always drop LyX in favor
15 matches
Mail list logo
