1. Edita: "lang" directory problem
- Posted by Al Getz <Xaxo at aol.com> Sep 13, 2005
- 520 views
Hello (Pete), [v022] I was trying to open up Edita.exe (after bindw'ing) with another program and found that it wants the "lang" directory under the source's current directory rather than where Edita.exe is located. For example, i put Edita.exe into the Euphoria\Bin directory, and try to open it with system("Edita.exe MyFile.txt",0) and although edita does open, it opens with a language directory error saying it cant find the language file so it will use English. If i put a "lang" directory under the source file's current dir it opens fine. Trouble is, i wouldnt want to have to put a "lang" directory under every file's directory i intended to open using Edita so i think the lang directory should be under where the file 'edita.exw' or 'edita.exe' is located, or even better might be to just require having the lang *file* in the same dir as 'edita.exe' perhaps? I've done something like this with several of my programs by reading that stuff first then switching dir's if needed. It's fairly easy to change. The ini file seems to read fine. Take care, Al And, good luck with your Euphoria programming! My bumper sticker: "I brake for LED's"
2. Re: Edita: "lang" directory problem
- Posted by Pete Lomax <petelomax at blueyonder.co.uk> Sep 15, 2005
- 519 views
On Tue, 13 Sep 2005 10:15:19 -0700, Al Getz <guest at RapidEuphoria.com> wrote: >it wants the "lang" directory Thanks for reporting this. I'll try and find time to release 0.2.3 tomorrow, with all bugs reported so far fixed. >The ini file seems to read fine. Yep, "seems to". I'll leave a trace(1) active in there in case it (or the routine I just added) gets it wrong. At this point I think I'll reiterate what has been said many many times before: command_line() should always return a full path in the second element. It is unlikely to hurt any because it usually is a full path, but it would obviously be much better if it was /always/ a full path. If you run "exw test" from a dos prompt, then you get "test" in the second element, also with no indication whether it is running test, test.e, test.ex, test.exw, or whatever. Regards, Pete