|
| From: | Walter Ian Kaye |
| Subject: | Re: [Lynx-dev] "can't access startfile" |
| Date: | Sun, 29 Oct 2006 17:37:57 -0800 |
Walter Ian Kaye dixit:You're telling me I should never start lynx via a URL?No, I'm telling you to add that line to /etc/lynx.cfg and be happy.
Oh, you mean that acts as a secondary "backup"?
If you're starting it with an URI, and that one doesn't exist, you're doing something wrong anyway.
It does exist. See below.At 11:23a -0500 10/29/2006, Thomas Dickey didst inscribe upon an electronic papyrus:
On Sun, 29 Oct 2006, Eduardo Chappa wrote:*** Thomas Dickey (address@hidden) wrote in the Lynx list on Oct 28,...::) > > > just because it can't find a page. This causes loss of session :) > > > data and wastes people's time and patience. :) > > :) > > As the session is empty, I don't see how there can be any session :) > > data to lose! :) > :) > There's lots. Cookies, Lynx options that don't get saved to disk, :) > other web pages in cache, URL history -- all that data. Lynx quits, :) > it's all gone. :) :) What session data is actually present if you cannot go to the _start_ :) page? As I understand your comment, none of that applies. I believe that the main point in the original message is that an error like "page is not accesible, you made a mistake in your spelling", or so, should not cause Lynx to quit. It is perfectly reasonable to allow lynx tolynx didn't quit: lynx didn't _start_. There was no session to save.
OK, this is where the misunderstanding is. Lynx is *already* running, perhaps for days or weeks even; I hit the BACK key while disconnected from the 'Net, and Lynx gave me the finger and quit. Usually Lynx lets me go back and displays the cached page, but sometimes it doesn't and instead tries to access the URL itself -- no, I did not hit ^R; I know better than that -- and then gives me that error message and quits.
We on the same "page" now?
| [Prev in Thread] | Current Thread | [Next in Thread] |