[Lynx-dev] lynx configuration precedence

2019-11-17 Thread Jude DaShiell
If a user has a lynx.cfg file in their home directory or in /home/.lynx
will lynx automatically use their configuration file rather than the
system's /etc/lynx.cfg file?  If not, such a modification to lynx in some
future version may be worth doing.  System administrators could put
lynx.cfg in /etc/skel and have that put into new accounts automatically
when created that way.



--


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


[Lynx-dev] A note on shellworld.

2019-11-17 Thread Karen Lewellen

David,
It is my understanding that the shellworld admin has personal reasons for 
not  allowing the creation of new accounts.  His father was profoundly ill 
for  some time as an example.
The last time I sent a perspective client in their direction, I was told 
that unless the person is rather self sufficient, they were unlikely to 
create  anything new for them.

granted contacting the admin,
admin at shellworld dot net,
would be far more direct than seeking marketing information on the web.
Karen


On Sun, 17 Nov 2019, David Woolley wrote:


On 17/11/2019 22:04, Tim Chase wrote:

 However asking the system admin to modify the system-wide lynx.cfg
 file*will*  impact all other Shellworld users.  Using any of the
 methods recommended in this thread are exactly the way to prevent
 this.



I wonder how long shellworld has to live.  I completely failed to find any 
current marketing page for it, and people have said, here, that they have 
failed to get accounts created.


The Wayback Machine suggests that it hasn't been marketed for over ten years, 
although it does seem to have been intended as a blind users' system, rather 
than a power users' one.  The last page captured that wasn't empty or invalid 
seems to be October 2007, and it was blank by December that year.


I assume they are not taking on new users and will close when the number 
remaining drops sufficiently.


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev




___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Chime Hart
Hi David-and-All, I just looked-and-there are around 22 user names here on 
Shellworld, including some with more than 1 account. Certainly an amount of 
annual income from even that many accounts is nothing to sneeze at.
O-and-David, speaking of the Wayback Machine, I was never able to accomplish 
this in Lynx. I wanted to go back before the New York Times-and-most other 
NewsPapers added javascript so I couldn't get to their printer friendly pages. 
But if I tried following a link, it took me to a current page. Thanks so much in 
advance

Chime


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread David Woolley

On 17/11/2019 22:04, Tim Chase wrote:

However asking the system admin to modify the system-wide lynx.cfg
file*will*  impact all other Shellworld users.  Using any of the
methods recommended in this thread are exactly the way to prevent
this.



I wonder how long shellworld has to live.  I completely failed to find 
any current marketing page for it, and people have said, here, that they 
have failed to get accounts created.


The Wayback Machine suggests that it hasn't been marketed for over ten 
years, although it does seem to have been intended as a blind users' 
system, rather than a power users' one.  The last page captured that 
wasn't empty or invalid seems to be October 2007, and it was blank by 
December that year.


I assume they are not taking on new users and will close when the number 
remaining drops sufficiently.


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Tim Chase
On 2019-11-17 16:37, Karen Lewellen wrote:
> Big picture goal for whom?

You wanted to set your default start-page to a particular URL without
needing to enter it every time:

On 2019-11-15 17:52, Karen Lewellen wrote:
> The idea is to change this default homepage, not just simply visit
> a new site once.
On 2019-11-15 19:45, Karen Lewellen wrote:
> the goal is a permanent change to the default one.

This thread gave you multiple ways to do this:

- manually start lynx with the desired homepage URL on the
  command-line, possibly simplified with an alias/function

- create a lynx.cfg file and use "lynx -cfg=$HOME/.lynx.cfg" possibly
  simplified with an alias/function (which is what I detailed and has
  the longest-term flexibility and extensibility)

- exporting the WWW_HOME either each time your shell starts up or in
  your shell start-up file


On 2019-11-17 16:37, Karen Lewellen wrote:
> I am asking the admin here to make the change for me, end of story.

You were also clear (and rudely condescending to those trying to help)
about not wanting to modify the system lynx.cfg:

On 2019-11-16 22:53, Karen Lewellen wrote:
>   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.

However asking the system admin to modify the system-wide lynx.cfg
file *will* impact all other Shellworld users.  Using any of the
methods recommended in this thread are exactly the way to prevent
this.

-tim



___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Karen Lewellen

Big picture  goal for whom?
As it is my goal, and I state otherwise, I am unsure why you  choose to 
claim this is my goal.

This issue is moot, and I consider the thread to be closed.
I am asking the admin here to make the change for me, end of story.



On Sun, 17 Nov 2019, Tim Chase wrote:


The big picture goal is to create a local/user-specific lynx.cfg file
in your home directory.  This can be as minimal as that one
"STARTFILE" line produced by the `echo` command, and then start lynx
using that config file.

You can use a text-editor to create/edit the ~/.lynx.cfg file and
append the line

 STARTFILE:https://ca.yahoo.com/news

at the bottom.  Alternatively you can use "echo" to append the file
(creating it if it doesn't already exist):

 $ echo "STARTFILE:https://ca.yahoo.com/news"; >> ~/.lynx.cfg

With that local/user-specific config file available, you can then
start lynx manually using that config file:

 $ lynx -cfg=$HOME/.lynx.cfg

but typing that whole thing every time gets tedious.  So to avoid
that tedium, you want to let your shell know that when you type
"lynx" (or "ly" or whatever short-hand you want) that you really mean
"every time I type `lynx`, pretend that I added -cfg=$HOME/.lynx.cfg
after it".  You can do this with an alias or with a function though
the function is a bit more flexible. This would be created in one of
your shell startup files. However the exact syntax and file-names for
that startup file depend on the shell you're using. That's why I'm
interested in the output of

 $ basename $SHELL

to make sure which shell you're running.  In all liklihood, it's
"bash" in which case it would also help for you to provide the output
of

 $ ls ~/.bash*

If that output includes a .bash_aliases file, that's the best place
to put an alias/function.  Otherwise, you can just append it to your
.bashrc (which would most likely be among the output).

However your shell could also be any of a number of common
alternatives like sh, ash, dash, zsh, ksh, csh, tcsh, fish, or yet
others.  Each one has its own configuration files and making sure
that the edit takes place in the right one is essential to ensuring
that the alias/function gets created properly.

But then once you have the alias/function in your local start-up
file, every time you type "lynx" (or "ly" or whatever short-hand you
prefer), it will start with your preferred configuration.

-tim


On 2019-11-17 14:10, Karen Lewellen wrote:

Tim,
*should* is an interesting concept.  What should  be does not
always translate into what is.
For example,
Your echo line below is a fantastic example of the kind of command
line idea I have been seeking the entire time.
However, because there are   about ten different  lynx.cfg files in
the home directory of my site hosted here on shellworld, running it
did not produce any changes.
I got no errors, meaning  likely something was changed, just not
the lynx.cfg file governing  my karenlewellen.com workspace hosted
at shellworld.
still, it was at least the sort of  solution I desired, a simple
command line  that could be run without editing altering or
changing anything else.
As I said to rick,  that he has done something himself in no way
translates to  the approximately 7 billion others sharing our world.
Karen


On Sun, 17 Nov 2019, Tim Chase wrote:


There are system-level config files which you should be able to
read but not modify.  There are also user-level config files
which you are expected to be able to read and modify to make your
life easier.

Yes, you can manually specify a config file every time on the
command line, or specify the start-URL on the command-line every
time, or establish environment variables every time you log in,
or define a function/alias everytime you log in.

But the purpose of creating local/user-level config files is for
your own conveneince.  So that when you type "lynx" (or "ly" or
whatever short-hand abbreviation you want), it does exactly what
*you* want (within the software's limitations) every time.

As David mentions, if your Shellworld account allows you to modify
system-level config files, that would impact everybody on the
system and be a big security issue.  But I suspect that the
administrator left permissions as their defaults and so you can't
change the site-wide settings as a mere user.  But you can copy
the lynx.cfg file -- either from your system /etc/lynx.cfg or
/usr/local/etc/lynx.cfg or downloading a copy from the internet
-- to your home directory, modify it to your satisfaction, and
then instruct lynx to use that config file instead.  For your
purposes, you might even be able to just use "echo" to put the
one line in a file without any text editor:

 $ echo 'STARTFILE:https://example.com' >> ~/.lynx.cfg

if you want to start at example.com

You then modify your *local* (not system-wide) shell configuration
file to create the command you use to override that config file:

 $ echo 'lynx() { command lynx -cfg ~/.lynx.cfg "$@" ; }' >>
~/.bashrc

or wh

Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Tim Chase
The big picture goal is to create a local/user-specific lynx.cfg file
in your home directory.  This can be as minimal as that one
"STARTFILE" line produced by the `echo` command, and then start lynx
using that config file.

You can use a text-editor to create/edit the ~/.lynx.cfg file and
append the line

  STARTFILE:https://ca.yahoo.com/news

at the bottom.  Alternatively you can use "echo" to append the file
(creating it if it doesn't already exist):

  $ echo "STARTFILE:https://ca.yahoo.com/news"; >> ~/.lynx.cfg

With that local/user-specific config file available, you can then
start lynx manually using that config file:

  $ lynx -cfg=$HOME/.lynx.cfg

but typing that whole thing every time gets tedious.  So to avoid
that tedium, you want to let your shell know that when you type
"lynx" (or "ly" or whatever short-hand you want) that you really mean
"every time I type `lynx`, pretend that I added -cfg=$HOME/.lynx.cfg
after it".  You can do this with an alias or with a function though
the function is a bit more flexible. This would be created in one of
your shell startup files. However the exact syntax and file-names for
that startup file depend on the shell you're using. That's why I'm
interested in the output of

  $ basename $SHELL

to make sure which shell you're running.  In all liklihood, it's
"bash" in which case it would also help for you to provide the output
of

  $ ls ~/.bash*

If that output includes a .bash_aliases file, that's the best place
to put an alias/function.  Otherwise, you can just append it to your
.bashrc (which would most likely be among the output).

However your shell could also be any of a number of common
alternatives like sh, ash, dash, zsh, ksh, csh, tcsh, fish, or yet
others.  Each one has its own configuration files and making sure
that the edit takes place in the right one is essential to ensuring
that the alias/function gets created properly.

But then once you have the alias/function in your local start-up
file, every time you type "lynx" (or "ly" or whatever short-hand you
prefer), it will start with your preferred configuration.

-tim


On 2019-11-17 14:10, Karen Lewellen wrote:
> Tim,
> *should* is an interesting concept.  What should  be does not
> always translate into what is.
> For example,
> Your echo line below is a fantastic example of the kind of command
> line idea I have been seeking the entire time.
> However, because there are   about ten different  lynx.cfg files in
> the home directory of my site hosted here on shellworld, running it
> did not produce any changes.
> I got no errors, meaning  likely something was changed, just not
> the lynx.cfg file governing  my karenlewellen.com workspace hosted
> at shellworld.
> still, it was at least the sort of  solution I desired, a simple
> command line  that could be run without editing altering or
> changing anything else.
> As I said to rick,  that he has done something himself in no way 
> translates to  the approximately 7 billion others sharing our world.
> Karen
> 
> 
> On Sun, 17 Nov 2019, Tim Chase wrote:
> 
> > There are system-level config files which you should be able to
> > read but not modify.  There are also user-level config files
> > which you are expected to be able to read and modify to make your
> > life easier.
> >
> > Yes, you can manually specify a config file every time on the
> > command line, or specify the start-URL on the command-line every
> > time, or establish environment variables every time you log in,
> > or define a function/alias everytime you log in.
> >
> > But the purpose of creating local/user-level config files is for
> > your own conveneince.  So that when you type "lynx" (or "ly" or
> > whatever short-hand abbreviation you want), it does exactly what
> > *you* want (within the software's limitations) every time.
> >
> > As David mentions, if your Shellworld account allows you to modify
> > system-level config files, that would impact everybody on the
> > system and be a big security issue.  But I suspect that the
> > administrator left permissions as their defaults and so you can't
> > change the site-wide settings as a mere user.  But you can copy
> > the lynx.cfg file -- either from your system /etc/lynx.cfg or
> > /usr/local/etc/lynx.cfg or downloading a copy from the internet
> > -- to your home directory, modify it to your satisfaction, and
> > then instruct lynx to use that config file instead.  For your
> > purposes, you might even be able to just use "echo" to put the
> > one line in a file without any text editor:
> >
> >  $ echo 'STARTFILE:https://example.com' >> ~/.lynx.cfg
> >
> > if you want to start at example.com
> >
> > You then modify your *local* (not system-wide) shell configuration
> > file to create the command you use to override that config file:
> >
> >  $ echo 'lynx() { command lynx -cfg ~/.lynx.cfg "$@" ; }' >>
> > ~/.bashrc
> >
> > or whatever your local shell-configuration file is depending on
> > your shell. Again, would be helpful to kno

Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Karen Lewellen

Chime,
i do not need to see all of my bookmarks
that is not my stated goal whatsoever.



On Sun, 17 Nov 2019, Chime Hart wrote:

Well Karen, if you have bookmarks enabled, you can just type from a 
commandline

lynx -book
You will then see all your bookmarks, which like any other page, you can type 
a link number or arrow-and-highlight an item.
Now probably back on Firday I inquired if there were a way of invoking an 
actual bookmark from a commandline? As an example if I want to go to bookmark 
145, are their ways of doing that? Thanks so much in advance

Chime




___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Chime Hart

Well Karen, if you have bookmarks enabled, you can just type from a commandline
lynx -book
You will then see all your bookmarks, which like any other page, you can type a 
link number or arrow-and-highlight an item.
Now probably back on Firday I inquired if there were a way of invoking an actual 
bookmark from a commandline? As an example if I want to go to bookmark 145, are 
their ways of doing that? Thanks so much in advance

Chime


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Karen Lewellen

My goal is to use
ca.yahoo.com/news
as my startfile.
As I have several hundred bookmarks, how does using the bookmark page 
produce the result I desire?




On Sun, 17 Nov 2019, dan d. wrote:



I just rememberd another way using command line only to have an alternative 
start page.  Fromm the lynx hlp page:

-book use the bookmark page as the startfile (off)

Here from the info lynx file additional info:

-book  use  the bookmark page as the startfile.  The default or command
 line startfile is still set for the  Main  screen  command,  and
 will be used if the bookmark page is unavailable or blank.
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
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev



___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev



--
XB




___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Karen Lewellen

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
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev



___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev



--
XB




___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Chime Hart
Well Karen, I remember the many times I was able to work with folks over the 
phone, who knew their way around. While I am not archiving these messages, maybe 
if Rick or another expert could guide you live, I think you would finally have 
success. While I am not actually volunteering Rick, I know for many years he was 
ahead of myself in a Unix World. Anyway, I sincerely hope some1 can assist you 
in real time

Chime


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Karen Lewellen

Tim,
*should* is an interesting concept.  What should  be does not  always 
translate into what is.

For example,
Your echo line below is a fantastic example of the kind of command line 
idea I have been seeking the entire time.
However, because there are   about ten different  lynx.cfg files in the 
home directory of my site hosted here on shellworld, running it did not 
produce any changes.
I got no errors, meaning  likely something was changed, just not the 
lynx.cfg file governing  my karenlewellen.com workspace hosted at 
shellworld.
still, it was at least the sort of  solution I desired, a simple command 
line  that could be run without editing altering or changing anything 
else.
As I said to rick,  that he has done something himself in no way 
translates to  the approximately 7 billion others sharing our world.

Karen


On Sun, 17 Nov 2019, Tim Chase wrote:


There are system-level config files which you should be able to read
but not modify.  There are also user-level config files which you are
expected to be able to read and modify to make your life easier.

Yes, you can manually specify a config file every time on the command
line, or specify the start-URL on the command-line every time, or
establish environment variables every time you log in, or define a
function/alias everytime you log in.

But the purpose of creating local/user-level config files is for your
own conveneince.  So that when you type "lynx" (or "ly" or whatever
short-hand abbreviation you want), it does exactly what *you* want
(within the software's limitations) every time.

As David mentions, if your Shellworld account allows you to modify
system-level config files, that would impact everybody on the system
and be a big security issue.  But I suspect that the administrator
left permissions as their defaults and so you can't change the
site-wide settings as a mere user.  But you can copy the lynx.cfg
file -- either from your system /etc/lynx.cfg or
/usr/local/etc/lynx.cfg or downloading a copy from the internet -- to
your home directory, modify it to your satisfaction, and then instruct
lynx to use that config file instead.  For your purposes, you might
even be able to just use "echo" to put the one line in a file without
any text editor:

 $ echo 'STARTFILE:https://example.com' >> ~/.lynx.cfg

if you want to start at example.com

You then modify your *local* (not system-wide) shell configuration
file to create the command you use to override that config file:

 $ echo 'lynx() { command lynx -cfg ~/.lynx.cfg "$@" ; }' >> ~/.bashrc

or whatever your local shell-configuration file is depending on your
shell. Again, would be helpful to know the output of

 $ basename $SHELL

to know which shell you're in.

Once you've configured these two things, invoking lynx should give
you the settings you want every time without needing to re-type them.

The local/user-level configuration files are there specifically to
make each user's life easier, without impacting other users on the
same system.

I'm still hoping I could get a Shellworld account so I can test some
of these things to give you a more targeted reply, but I've not heard
back from the admin on any of the occasions I've tried emailing them.

-tim

On 2019-11-16 22:39, Karen Lewellen wrote:

because this is not my service I wish to tamper with config files
as little  as possible.
If there is not a command line only method to accomplish this task,
much like  the -useragent one, then never mind.
thanks for all the ideas but  again  I am not interested in
altering lynx.cfg in any fashion.
Karen


On Fri, 15 Nov 2019, Tim Chase wrote:


Karen,

You can combine Thorsten's advice to use "-cfg=FILENAME" with my
previous shell-alias suggestion, which is what I've done in the
past to specify a local config file.  With that in place, you can
set your default home-page in your local lynx config file (say,
~/.lynx.cfg)

 echo "STARTFILE:https://example.com"; >> ~/.lynx.cfg

and then have your function/alias specify the config file:

 lynx() { command lynx -cfg=$HOME/.lynx.cfg "$@" ; }

I happen to like the TEXTFIELDS_NEED_ACTIVATION:TRUE set in my
.cfg file too, so this is how I get that behavior every time.

-tim


On 2019-11-15 22:56, Thorsten Glaser wrote:

Karen Lewellen dixit:


I am seeking a command line method  to override the site  listed
as the homepage for lynx regularly,  i. e. the page that appears
if i just entre lynx.


Then don’t enter just lynx ;-)

Otherwise, you can override the homepage in the lynx.cfg file.
Since you’re on a shellserver you cannot do that system-wide,
but you can copy the system-wide one into your home directory
and use the -cfg=FILENAME option to point to the changed file.


The idea is  to change this  default homepage, not just simply
visit a new site once.


But the “homepage” is only shown if you don’t tell it a site
to visit when starting.

It’s probably easiest to make an alias, something like this:

echo "alias 'ly=lynx http://the.new.start.site'

Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Karen Lewellen

Rick,
One thing unique to the human condition is individual skill based on 
experience.  Just because you have done something does not translate that 
every single child born of woman can do the same. 
Making such  is a matter of opinion  with which I disagree having tried at 
least 
one   suggestion.
Trying to save the  www_home parameter locked me into something  that kept 
producing a  > from which I could not exit.

Karen


On Sat, 16 Nov 2019, Rick Lewis wrote:


Karen,
I hope you have saved all of the suggestions. They will allow you to do what 
you want without affecting anyone else on the system.
I've done these things myself. They work, and will achieve what you want.
--
Rick

-Original Message-
From: Lynx-dev [mailto:lynx-dev-bounces+ricklew=shellworld@nongnu.org] On 
Behalf Of Karen Lewellen
Sent: Saturday, November 16, 2019 8:05 PM
To: Halaasz Saandor 
Cc: lynx-dev@nongnu.org
Subject: Re: [Lynx-dev] changing lynx default homepage from the comand line?

do you mind providing the exact command?
karen


On Sat, 16 Nov 2019, Halaasz Saandor via Lynx-dev wrote:


2019/11/15 18:26 ... Larry Hynes via Lynx-dev:

 If you can set the WWW_HOME environment variable, lynx will use that as
 the startfile.


I use this method, although I have complete control of my "lynx.cfg".

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev




___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev




___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread dan d.

I just rememberd another way using command line only to have an alternative 
start page.  Fromm the lynx hlp page:

-book use the bookmark page as the startfile (off)

Here from the info lynx file additional info:

-book  use  the bookmark page as the startfile.  The default or command
  line startfile is still set for the  Main  screen  command,  and
  will be used if the bookmark page is unavailable or blank.
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
> > Lynx-dev@nongnu.org
> > https://lists.nongnu.org/mailman/listinfo/lynx-dev
> >
>
> ___
> Lynx-dev mailing list
> Lynx-dev@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/lynx-dev
>

-- 
XB

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread dan d.

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
> > Lynx-dev@nongnu.org
> > https://lists.nongnu.org/mailman/listinfo/lynx-dev
> >
>
> ___
> Lynx-dev mailing list
> Lynx-dev@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/lynx-dev
>

-- 
XB

___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread Tim Chase
There are system-level config files which you should be able to read
but not modify.  There are also user-level config files which you are
expected to be able to read and modify to make your life easier.

Yes, you can manually specify a config file every time on the command
line, or specify the start-URL on the command-line every time, or
establish environment variables every time you log in, or define a
function/alias everytime you log in.

But the purpose of creating local/user-level config files is for your
own conveneince.  So that when you type "lynx" (or "ly" or whatever
short-hand abbreviation you want), it does exactly what *you* want
(within the software's limitations) every time.

As David mentions, if your Shellworld account allows you to modify
system-level config files, that would impact everybody on the system
and be a big security issue.  But I suspect that the administrator
left permissions as their defaults and so you can't change the
site-wide settings as a mere user.  But you can copy the lynx.cfg
file -- either from your system /etc/lynx.cfg or
/usr/local/etc/lynx.cfg or downloading a copy from the internet -- to
your home directory, modify it to your satisfaction, and then instruct
lynx to use that config file instead.  For your purposes, you might
even be able to just use "echo" to put the one line in a file without
any text editor:

  $ echo 'STARTFILE:https://example.com' >> ~/.lynx.cfg

if you want to start at example.com

You then modify your *local* (not system-wide) shell configuration
file to create the command you use to override that config file:

  $ echo 'lynx() { command lynx -cfg ~/.lynx.cfg "$@" ; }' >> ~/.bashrc

or whatever your local shell-configuration file is depending on your
shell. Again, would be helpful to know the output of

  $ basename $SHELL

to know which shell you're in.

Once you've configured these two things, invoking lynx should give
you the settings you want every time without needing to re-type them.

The local/user-level configuration files are there specifically to
make each user's life easier, without impacting other users on the
same system.

I'm still hoping I could get a Shellworld account so I can test some
of these things to give you a more targeted reply, but I've not heard
back from the admin on any of the occasions I've tried emailing them.

-tim

On 2019-11-16 22:39, Karen Lewellen wrote:
> because this is not my service I wish to tamper with config files
> as little  as possible.
> If there is not a command line only method to accomplish this task,
> much like  the -useragent one, then never mind.
> thanks for all the ideas but  again  I am not interested in
> altering lynx.cfg in any fashion.
> Karen
> 
> 
> On Fri, 15 Nov 2019, Tim Chase wrote:
> 
> > Karen,
> >
> > You can combine Thorsten's advice to use "-cfg=FILENAME" with my
> > previous shell-alias suggestion, which is what I've done in the
> > past to specify a local config file.  With that in place, you can
> > set your default home-page in your local lynx config file (say,
> > ~/.lynx.cfg)
> >
> >  echo "STARTFILE:https://example.com"; >> ~/.lynx.cfg
> >
> > and then have your function/alias specify the config file:
> >
> >  lynx() { command lynx -cfg=$HOME/.lynx.cfg "$@" ; }
> >
> > I happen to like the TEXTFIELDS_NEED_ACTIVATION:TRUE set in my
> > .cfg file too, so this is how I get that behavior every time.
> >
> > -tim
> >
> >
> > On 2019-11-15 22:56, Thorsten Glaser wrote:  
> >> Karen Lewellen dixit:
> >>  
> >>> I am seeking a command line method  to override the site  listed
> >>> as the homepage for lynx regularly,  i. e. the page that appears
> >>> if i just entre lynx.  
> >>
> >> Then don’t enter just lynx ;-)
> >>
> >> Otherwise, you can override the homepage in the lynx.cfg file.
> >> Since you’re on a shellserver you cannot do that system-wide,
> >> but you can copy the system-wide one into your home directory
> >> and use the -cfg=FILENAME option to point to the changed file.
> >>  
> >>> The idea is  to change this  default homepage, not just simply
> >>> visit a new site once.  
> >>
> >> But the “homepage” is only shown if you don’t tell it a site
> >> to visit when starting.
> >>
> >> It’s probably easiest to make an alias, something like this:
> >>
> >> echo "alias 'ly=lynx http://the.new.start.site'" >>~/.bashrc
> >>
> >> Then typing ly will start lynx with the other start page.
> >> Easier than doing the config dance, unless you need that anyway.
> >>
> >> bye,
> >> //mirabilos
> >> --
> >> FWIW, I'm quite impressed with mksh interactively. I thought it
> >> was much *much* more bare bones. But it turns out it beats the
> >> living hell out of ksh93 in that respect. I'd even consider it
> >> for my daily use if I hadn't wasted half my life on my zsh
> >> setup. :-) -- Frank Terbeck in #!/bin/mksh
> >>
> >> ___
> >> Lynx-dev mailing list
> >> Lynx-dev@nongnu.org
> >> https://lists.nongnu.org/mailman/listinfo/lyn

Re: [Lynx-dev] changing lynx default homepage from the comand line?

2019-11-17 Thread David Woolley

On 17/11/2019 03:48, Karen Lewellen wrote:
i do not know where the lynx.cfg file is located.  I imagine this is 
wise to prevent accidents with  individuals  making changes.


If the service makes it possible for individuals to change a shared 
configuration file, they have very severe security issues and you 
shouldn't be using them.  The file should be easy to find, and should be 
write protected against ordinary users.



___
Lynx-dev mailing list
Lynx-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lynx-dev