actually,
no they do not.
I cannot edit the .bash_profile, because the edit command indicates that
there is no such file or directory.
The echo option, while terrific produced no changes i. e. when I run
lynx
I am still taken to the uniform location, which now produces an error
because google learned of the
theoldgnews.com
Service shutting it down.
As I just told Tim, *should* and reality do not always match.
his option would have been amazing, if it actually worked.
Frankly I great deal of list traffic would have been avoided if the answer
you suggest below, i. e. there is no command line option without
creating an alias first had been shared...as I have no interest in
creating an alias.
On Sun, 17 Nov 2019, dan d. wrote:
Multiple ways were offered not involving lynx.cfg.
The only strickly command line approach is to include an url after any lynx
optionss.
If one wants to avoid doing this each time lynx is used, one of the other
methodds offered will work.
On Sat, 16 Nov 2019, Karen Lewellen wrote:
folks,
i. do. not. want. to. make. this. change. in lynx.cfg...at all!
How hard is that to understand?
I asked for *command line* not all the ways I might screw up another
person's setup.
On Fri, 15 Nov 2019, Bela Lubkin wrote:
Karen Lewellen wrote:
since this is not my system,
I have no idea where the lynx.cfg file is.
While in Lynx, hit 'o' for options. Near the very bottom is a line,
View the file lynx.cfg.
Following the 'lynx.cfg' link, you see a rendition of the active
portions of your lynx.cfg. Near the top of that is a comment:
#Your primary configuration /path/to/system/lynx.cfg
====
We can reduce that somewhat. 'LYNXCFG:/' is the URL used in that
'lynx.cfg' link; we can dump that from the shell:
$ lynx -dump LYNXCFG:/ | grep primary.config
#Your primary configuration [4]/path/to/system/lynx.cfg
One way to make use of this:
$ cd $HOME
$ echo 'INCLUDE:/path/to/system/lynx.cfg' > .lynx_cfg
$ echo 'STARTFILE:https://www.xyz.abc' >> .lynx_cfg
$ lynx -cfg $HOME/.lynx_cfg ### opens www.xyz.abc
This uses lynx.cfg's INCLUDE command to include the system lynx.cfg by
reference. That way it will keep up with any changes the system
administrator might make (as long as they don't replace the lynx binary
with one compiled to look in a different location). Setting STARTFILE
*after* the INCLUDE ensures that your setting overrides the system's.
Now all you need is one of the various alias techniques mentioned by
others...
Bela<
_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
--
XB
_______________________________________________
Lynx-dev mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lynx-dev
