From: James G. S. (jim) <jg...@sa...> - 2007-12-17 03:07:00
|
Dave Walton wrote: > Jim, > > Why no, as a matter of fact, I had NOT tried something like that. Nor > would I have known which var to mess with. Thanks for the tip! I'm glad you were able to provide the missing know-how to make the idea work. > > Using your Windows example as a starting point, I came up with this > batch file, which I call gramps.bat: > > ================================================== > @echo off > > REM Make changes to environment variables local to this block > setlocal > > REM Set USERPROFILE to the drive and path of this script > set USERPROFILE=%~dp0 > > REM Go to this script location for good measure > %~d0 > cd "%~p0" > > REM I don't know how to locate and start GRAMPS without hardcoding > REM the drive and path for it and Python. > C:\Python25\pythonw.exe "C:\Program Files\gramps\gramps.py" > > REM End the local environment block > endlocal > ================================================== > > When this script is run, it starts gramps with the profile set to the > drive and directory that contains the script. So you attach the drive, > double click the batch file, and gramps starts up, no matter which > letter the drive got. Assuming windows gramps and all its dependencies > are correctly installed on that computer, of course. If I knew how to > set up those on the removable drive, too, it'd be perfect. But this > path stuff was the most critical part of the problem. > > Right now I'm stuck on a loaner computer, but when I get a new one set > up I'll be able to do a *nix version, too. They'd also be good content > for a "How do I..." on the wiki. Yea! That would be great. You might also add an expanded discussion version (or footnotes) explaining the technical/syntax details. I await the educational opportunity. :-) Regards, ..jim |