Joined: April 2006
||Posted: May 24 2008,20:46
|Quote (malanrich @ May 24 2008,19:16)|
|Success! Thanks to jpeters for the tips on preserving the options file. I'm writing from glinks now, and all my configuration settings remain intact. |
The only glitch is getting the mydsl menu to boot glinks from the right directory (I think). There's a glinks executable (glinks.app) in the mydsl directory. That, and the glinks entry in the mydsl menu, executes a glinks that seems to be without any configuration at all--just a glinks gui. But the glinks executable in the opts/glinks directory calls up the right one with all my settings. It's some kind of path problem that I'll figure out.
Meanwhile, I'm happy with what I've got working. Thanks for the help.
Edit the options (homepage, etc) directly from the /.links/options
file and it will work. For some reason, changes from within the program aren't writing to the file. The mydsl menu is correctly loading the program from /opt/glinks/links -g
EDIT: It does work correctly, but you have to "save options" in the "setup" menu after changing them.
Note: This is a handy little browser. Besides being 1/3 the size of FF, the virtual memory difference is huge: FF 33124, Glinks 3760.