Re: Allow Lyx to find itself if symlinked.

1999-02-18 Thread Jean-Marc Lasgouttes
> "Miyata" == Miyata Shigeru <[EMAIL PROTECTED]> writes: Miyata> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote: >> I think we can use the portable versions of the auxilliary >> files. The problem is with the autoconf script itself. Miyata> I found out today that autoconf 2.13 for OS/2 uses

Re: Allow Lyx to find itself if symlinked.

1999-02-18 Thread Miyata Shigeru
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote: > I think we can use the portable versions of the auxilliary files. The > problem is with the autoconf script itself. I found out today that autoconf 2.13 for OS/2 uses auxilliary files from AC_PREFIX/share/autoconf rather than those in the current

Re: Allow Lyx to find itself if symlinked.

1999-02-15 Thread Jean-Marc Lasgouttes
> "miyata" == miyata <[EMAIL PROTECTED]> writes: miyata> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote: >> BTW, concerning OS/2, are there interesting things for OS/2 in >> autoconf 2.13? There is support for executable files suffixes >> (.exe) and such, but I do not know how to use it. It

Re: Allow Lyx to find itself if symlinked.

1999-02-14 Thread miyata
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote: > BTW, concerning OS/2, are there interesting things for OS/2 in > autoconf 2.13? There is support for executable files suffixes (.exe) > and such, but I do not know how to use it. It would be useful for > windows, too. > > And what's the status of

Re: Allow Lyx to find itself if symlinked.

1999-02-12 Thread Jean-Marc Lasgouttes
> "miyata" == miyata <[EMAIL PROTECTED]> writes: miyata> The code in question is used to locate configuration files, miyata> when LyX is *not* yet installed. This functionality is miyata> important for developers/users to test new versions miyata> (especially with developer versions). It i

Re: Allow Lyx to find itself if symlinked.

1999-02-12 Thread miyata
"Arnd Hanses" <[EMAIL PROTECTED]> wrote: > As one of the concerns was portability and with all UN*X ports usually > you have trouble with hardcoded pathnames hidden somewhere (at least on > OS/2), could it be possible to forget about executable absolute > pathname and just run it. > > On OS/2 DLL

Re: Allow Lyx to find itself if symlinked.

1999-02-12 Thread Jean-Marc Lasgouttes
> "Jan" == Jan Vroonhof <[EMAIL PROTECTED]> writes: Jan> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: >> Yes, but we already have this one in config.h. If you have no other >> objection, I can add that. Jan> I have no other "objection". It was not even an objection Jan> before. I was jus

Re: Allow Lyx to find itself if symlinked.

1999-02-11 Thread Jan Vroonhof
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > Yes, but we already have this one in config.h. If you have no other > objection, I can add that. I have no other "objection". It was not even an objection before. I was just being lazy (in the bad sense) and you see, it worked! Jan

Re: Allow Lyx to find itself if symlinked.

1999-02-11 Thread Arnd Hanses
On 10 Feb 1999 19:29:27 +0100, Lars Gullik Bj°nnes wrote: > AH> What about rewrite for > AH> system () (ANSI-C90) > >How? > >We want to get a string with the real name of the executable. Not run >it. Sorry, did not really say, what I meant. Idea was more general, if not heretic: As one of the

Re: Allow Lyx to find itself if symlinked.

1999-02-11 Thread Jean-Marc Lasgouttes
> "Jan" == Jan Vroonhof <[EMAIL PROTECTED]> writes: Jan> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: >> char LinkBuffer[512]; // Should be PATH_MAX but that needs autconf >> support >> >> What autoconf support do you need? Jan> The code snippet you quoted from GNU fileutils has the inc

Re: Allow Lyx to find itself if symlinked.

1999-02-11 Thread Jan Vroonhof
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > char LinkBuffer[512]; > // Should be PATH_MAX but that needs autconf support > > What autoconf support do you need? The code snippet you quoted from GNU fileutils has the inclusion of limits.h wrapped in an HAVE_LIMITS_H

Re: Allow Lyx to find itself if symlinked.

1999-02-11 Thread Jean-Marc Lasgouttes
> "Jan" == Jan Vroonhof <[EMAIL PROTECTED]> writes: Jan> [EMAIL PROTECTED] (Lars Gullik Bj?nnes) writes: >> Anyway to make a func in FileTools seems like a good option for >> 1.0.x. Jan> OK, I did this. Hello, I applied your patch after checking it a bit (I just added a AddPath() instead

Re: Allow Lyx to find itself if symlinked.

1999-02-11 Thread miyata
[EMAIL PROTECTED] wrote: > shows nothing on thos Solaris 2.5.1 box, that is bad sign. However > readlink must be fairly portable, you are already using it :-) > > See LyXFileDlg::Reread(), I took my use if readlink from that function. There is a hackish macro in os2_defines.h Regards,

Re: Allow Lyx to find itself if symlinked.

1999-02-10 Thread Lars Gullik Bjønnes
>> Arnd Hanses writes: AH> What about rewrite for AH> system () (ANSI-C90) How? We want to get a string with the real name of the executable. Not run it. Lgb

Re: Allow Lyx to find itself if symlinked.

1999-02-10 Thread Arnd Hanses
On 09 Feb 1999 16:22:05 +0100, Lars Gullik Bj°nnes wrote: > >> Jean-Marc Lasgouttes writes: > >[...] > JL> Another concern: how portable is readlink()? Is it commonly > JL> supported on all unices? What to do about OS/2? > >It seems to not be posix. > >I can't find out if readpath is posix, if

Re: Allow Lyx to find itself if symlinked.

1999-02-10 Thread Jan Vroonhof
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: > it. A question: is there a particular reason why you named the new > function LyXReadLink? Would ReadLink cause a particular problem? [just > that the other functions in filetools do not use that prefix] Not really apart from the fact that I dis

Re: Allow Lyx to find itself if symlinked.

1999-02-10 Thread Jean-Marc Lasgouttes
> "Jan" == Jan Vroonhof <[EMAIL PROTECTED]> writes: Jan> I am afraid I found it easier to just convert everything to Jan> LString now than to try to add up all the buffer sizes. The Code Jan> is much simpler and cleaner in this way. That's good anyway. The patch looks good. I'll test it and

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Jan Vroonhof
[EMAIL PROTECTED] (Lars Gullik Bj?nnes) writes: > Anyway to make a func in FileTools seems like a good option for 1.0.x. OK, I did this. > What should be done now is to make it safe and perhaps move the > if((isLink = fileInfo.isLink())) > stuff into FileTools.C > > [...] > > In 1.1.x we shou

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Jan Vroonhof
[EMAIL PROTECTED] (Lars Gullik Bj?nnes) writes: > v> // szBuffer is a 256 byte buffer! BOOM. > > And why not enlarge szBuffer to 512. Note. It needs to contain: Direntry + " -> " + linkpath, so it needs to be quite some more. > v> LString szFile; > v> huh? "sz = char []"? > > I don't ge

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread vroonhof
> It seems to not be posix. > > I can't find out if readpath is posix, if it is we could use that. Well, man readpath shows nothing on thos Solaris 2.5.1 box, that is bad sign. However readlink must be fairly portable, you are already using it :-) See LyXFileDlg::Reread(), I took my use if

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Lars Gullik Bjønnes
>> Jean-Marc Lasgouttes writes: >> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Jean-Marc Lasgouttes writes: Lars> [...] JL> Another concern: how portable is readlink()? Is it commonly JL> supported on all unices? What to do about OS/2? Lars> It seems to not b

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Jean-Marc Lasgouttes
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: >>> Jean-Marc Lasgouttes writes: Lars> [...] JL> Another concern: how portable is readlink()? Is it commonly JL> supported on all unices? What to do about OS/2? Lars> It seems to not be posix. Lars> I can't find out if readpath is

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Jean-Marc Lasgouttes
> "vroonhof" == vroonhof <[EMAIL PROTECTED]> writes: >> It seems to not be posix. >> >> I can't find out if readpath is posix, if it is we could use that. Jan> Well, Jan> man readpath Jan> shows nothing on thos Solaris 2.5.1 box, that is bad Jan> sign. Idem on Digital Unix 4.0. Jan> H

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Jean-Marc Lasgouttes
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: >>> Jean-Marc Lasgouttes writes: >>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > Jean-Marc Lasgouttes writes: Lars> [...] JL> Another concern: how portable is readlink()? Is it commonly JL> supported on all un

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Jan Vroonhof
[EMAIL PROTECTED] (Lars Gullik Bj?nnes) writes: > yes, perhaps it is safe, but better would be sure that we used posix > funcs. It seems to be that the whole symlink concept is not part of posix. It is however in 4.3 BSD and the single UNIX specification. Which seems to agree with fileutils, i.

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Lars Gullik Bjønnes
>> vroonhof writes: v> shows nothing on thos Solaris 2.5.1 box, that is bad sign. v> However readlink must be fairly portable, you are already using v> it :-) I realise that now... v> See LyXFileDlg::Reread(), I took my use if readlink from that v> function. Maybe moving the readlin

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Lars Gullik Bjønnes
>> Jean-Marc Lasgouttes writes: [...] JL> Another concern: how portable is readlink()? Is it commonly JL> supported on all unices? What to do about OS/2? It seems to not be posix. I can't find out if readpath is posix, if it is we could use that. Lgb

Re: Allow Lyx to find itself if symlinked.

1999-02-09 Thread Jean-Marc Lasgouttes
> "Jan" == Jan Vroonhof <[EMAIL PROTECTED]> writes: Jan> [This is my first patch to LyX, be patient with me] Hello, Of course, we are going to be patient. We need to lure more people into working on LyX :) Jan> The sysadmins here prefer the following structure, the full lyx Jan> tree under

Allow Lyx to find itself if symlinked.

1999-02-08 Thread Jan Vroonhof
[This is my first patch to LyX, be patient with me] The sysadmins here prefer the following structure, the full lyx tree under the prefix /usr/local/app/lyx/lyx-1.0.0/ and then lyx in /usr/local/bin symlinked to /usr/local/app/lyx/lyx-1.0.0/bin/lyx. They would prefer not have to the paths com