[Lynx-dev] user-agent headers
Quoth Robin Stern: 'Yes that header works! Am new to this woke side of internet, so a couple of questions:...' I haven't changed mine in 12 years - then again I don't experiment to try to make recalcitrant sites work, they being too few and insignificant (to me). I took my cue from Opera, which used to (still does?) have a menu of alternative choices. russell bell
[Lynx-dev] accessing washingtonpost.com
Quoth Tim: 'I event cannot open this site?' You need another user-agent header. I use: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.2) Gecko/20100115 Firefox/3.6 l_y_n_x Quoth Stefan Caunter: 'wapo site is always fast for me with lynx' What's your UA header? Even removing l_y_n_x doesn't help me. russell bell
Re: [Lynx-dev] dev.to website doesn't load, full support for HTML5?
Adding my stance, knowing others will as well. One feature I would appreciate, it might exist in the config file, but I am using a service, is an option that indeed lets you choose user agent headers. There is no such thing as most websites, individuals visit individually. still, having the ability to move back and forth between the default lynx agent, which works for most sites I visit, and an alternative that might avoid 403 errors would be helpful. So would encouraging folks not to block lynx itself, but that is another discussion. just my sickles. Kare On Tue, 2 Aug 2022, Robin Stern wrote: Yes that header works! Am new to this woke side of internet, so a couple of questions: 1) How does one select a header that works for most websites? 2) How often does one need to change this header? 3) Do pages render significantly different with different headers? Is there some header wisdom, other than putting l_y_n_x or lynx in it? On Sun, Jul 31, 2022 at 11:51:23AM -0600, rb...@alumni.caltech.edu wrote: Quoth Robin Stern: 'A buzzing developer website https://dev.to does not load in lynx,' Buzzing annoys lynxes. It works with my User-Agent header: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.2) Gecko/20100115 Firefox/3.6 l_y_n_x russell bell
Re: [Lynx-dev] dev.to website doesn't load, full support for HTML5?
Yes that header works! Am new to this woke side of internet, so a couple of questions: 1) How does one select a header that works for most websites? 2) How often does one need to change this header? 3) Do pages render significantly different with different headers? Is there some header wisdom, other than putting l_y_n_x or lynx in it? On Sun, Jul 31, 2022 at 11:51:23AM -0600, rb...@alumni.caltech.edu wrote: > Quoth Robin Stern: 'A buzzing developer website https://dev.to > does not load in lynx,' > Buzzing annoys lynxes. > It works with my User-Agent header: > > Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.2) Gecko/20100115 > Firefox/3.6 l_y_n_x > > russell bell > > >
Re: [Lynx-dev] lynx blinking after terminal window resizing
Thomas Dickey dixit:
>> I see it on Debian stable/bullseye, for example.
>
>I still don't see it with this combination.
Huh.
>The blinking that you're describing would be full-screen repainting.
Yes. I can verify that it does that in a typescript (attached).
I started lynx in an 80x24, moved the cursor down and up twice,
resized to 80x25, pressed ^R, then moved the cursor down… thrice,
I think. The pagetitle shows up several times, matching repaint.
$TERM is xterm, it happens with GNU screen as well (TERM=screen,
not the Debian “ncurses-term” madness of screen.xterm or so, as
that breaks sshing into BSD boxen).
>Perhaps it's something in your lynx configuration which is relevant.
>In my check, I used a test account which doesn't customize anything.
Hm. I’m attaching my /etc/lynx/local.cfg and /etc/lynx/lynx.lss and
~/.lynxrc files, maybe then? And ~/.Xresources as well…
bye,
//mirabilos
--
15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha
15:48⎜ also warum machen die xorg Jungs eigentlich alles
kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den
gebauten Turm selber umschmeissen durften? -- ~/.Xmodmap wonders…
typescript.gz
Description: Binary data
STARTFILE:file://localhost/~/
CHARACTER_SET:utf-8
LOCALE_CHARSET:FALSE
HTML5_CHARSETS:TRUE
ASSUME_CHARSET:utf-8
PREPEND_CHARSET_TO_SOURCE:TRUE
PREFERRED_LANGUAGE:
PREFERRED_CHARSET:utf-8
PARTIAL_THRES:3
SHOW_KB_RATE:BYTES,ETA
SHOW_CURSOR:FALSE
DEFAULT_CACHE_SIZE:512
DEFAULT_VIRTUAL_MEMORY_SIZE:25165824
SOURCE_CACHE:MEMORY
SOURCE_CACHE_FOR_ABORTED:KEEP
COLLAPSE_BR_TAGS:FALSE
COOKIE_REJECT_DOMAINS:google.com,google.de,google.at,google.ch,googleusercontent.com,dict.leo.org
PERSISTENT_COOKIES:TRUE
COOKIE_FILE:~/.etc/cookies.txt
COOKIE_SAVE_FILE:~/.etc/cookies.txt
DEFAULT_BOOKMARK_FILE:./.etc/bookmark.htm
POSITIONABLE_EDITOR:jupp
DOWNLOADER:View in less:less -f '%s':FALSE
DOWNLOADER:View in xloadimage:xloadimage -quiet '%s':FALSE:XWINDOWS
DOWNLOADER:View in mupdf:mupdf '%s':FALSE:XWINDOWS
DOWNLOADER:Spawn editor:"${VISUAL-${EDITOR-ed}}" '%s':FALSE
QUIT_DEFAULT_YES:FALSE
XLOADIMAGE_COMMAND:xloadimage -quiet %s
NESTED_TABLES: true
EXTERNAL:ftp:wget %s &:FALSE
EXTERNAL:http:wget %s &:FALSE
EXTERNAL:https:wget %s &:FALSE
EXTERNAL:http:mplayer %s:FALSE
EXTERNAL:https:mplayer %s:FALSE
PRETTYSRC_VIEW_NO_ANCHOR_NUMBERING:TRUE
XHTML_PARSING:TRUE
JUSTIFY:TRUE
TEXTFIELDS_NEED_ACTIVATION:TRUE
LEFTARROW_IN_TEXTFIELD_PROMPT:TRUE
ENABLE_LYNXRC:ASSUME_CHARSET:ON
ENABLE_LYNXRC:BAD_HTML:ON
ENABLE_LYNXRC:FORCE_COOKIE_PROMPT:ON
ENABLE_LYNXRC:FORCE_SSL_PROMPT:ON
ENABLE_LYNXRC:FTP_PASSIVE:ON
ENABLE_LYNXRC:HTML5_CHARSETS:ON
ENABLE_LYNXRC:MAKE_LINKS_FOR_ALL_IMAGES:ON
ENABLE_LYNXRC:MAKE_PSEUDO_ALTS_FOR_INLINES:ON
ENABLE_LYNXRC:NO_PAUSE:ON
ENABLE_LYNXRC:PREFERRED_ENCODING:ON
ENABLE_LYNXRC:PREFERRED_MEDIA_TYPES:ON
ENABLE_LYNXRC:RAW_MODE:ON
ENABLE_LYNXRC:SCROLLBAR:ON
ENABLE_LYNXRC:SET_COOKIES:ON
ENABLE_LYNXRC:SHOW_KB_RATE:ON
ENABLE_LYNXRC:TAGSOUP:ON
ENABLE_LYNXRC:UNDERLINE_LINKS:ON
TRACK_INTERNAL_LINKS:TRUE
GLOBAL_MAILCAP:
# $MirOS: src/gnu/usr.bin/lynx/samples/lynx.lss,v 1.7 2013/01/11 00:12:05 tg
Exp $
#
# Setting the normal and default types lets us keep (almost) the same colors
# whether the terminal's default colors are white-on-black or black-on-white.
# It is not exact since the default "white" is not necessarily the same color
# as the ANSI lightgray, but is as close as we can get in a standard way.
#
# If you really want the terminal's default colors, and if lynx is built using
# ncurses' default-color support, remove these two lines:
normal: normal: lightgray:black
default:normal: lightgray:black
# Normal type styles correspond to HTML tags.
#
# The next line (beginning with "em") means: use bold if mono, otherwise
# brightblue on
em: bold: brightblue
strong: bold: brightred
b: bold: red
i: bold: brightblue
a: bold: green
img:dim:brown
fig:normal: gray
caption:reverse:brown
hr: normal: yellow
blockquote: normal: brightblue
ul: normal: brown
address:normal: magenta
title: normal: magenta
tt: dim:brightmagenta: black
h1: bold: yellow: blue
label: normal: magenta
q: normal: yellow: magenta
small: dim:default
big:bold: yellow
sup:bold: yellow
sub:dim:gray
li: normal: magenta
code: normal: cyan
cite: normal:
Re: [Lynx-dev] why does cached page delay displaying?
wapo site is always fast for me with lynx, i paste in urls all day with UA header that they like ;) > On Aug 2, 2022, at 17:24, Tim wrote: > > I event cannot open this site? After few seconds of waiting nothing > happens. > >> On Tue Aug 2, 2022 at 11:57 PM EEST, rbell--- via Lynx-dev wrote: >>I check the news once daily. washingtonpost.com is >> particularly slow for lynx, takes seconds for a not-large page. (It's >> faster for almost all other browsers, including links.) I was puzzled >> today that articles that I saw yesterday still had short residence >> times (they include a time that a link has been up, in minutes, hours, >> days) and no new articles. I refreshed, got a new page. If lynx >> serves a page out of its cache, why does it take as long to display as >> a fresh page? The same happened at albuquerquejournal.com, which >> loads quickly. >> >> russell bell > >
Re: [Lynx-dev] why does cached page delay displaying?
I event cannot open this site? After few seconds of waiting nothing happens. On Tue Aug 2, 2022 at 11:57 PM EEST, rbell--- via Lynx-dev wrote: > I check the news once daily. washingtonpost.com is > particularly slow for lynx, takes seconds for a not-large page. (It's > faster for almost all other browsers, including links.) I was puzzled > today that articles that I saw yesterday still had short residence > times (they include a time that a link has been up, in minutes, hours, > days) and no new articles. I refreshed, got a new page. If lynx > serves a page out of its cache, why does it take as long to display as > a fresh page? The same happened at albuquerquejournal.com, which > loads quickly. > > russell bell
[Lynx-dev] why does cached page delay displaying?
I check the news once daily. washingtonpost.com is particularly slow for lynx, takes seconds for a not-large page. (It's faster for almost all other browsers, including links.) I was puzzled today that articles that I saw yesterday still had short residence times (they include a time that a link has been up, in minutes, hours, days) and no new articles. I refreshed, got a new page. If lynx serves a page out of its cache, why does it take as long to display as a fresh page? The same happened at albuquerquejournal.com, which loads quickly. russell bell
Re: [Lynx-dev] lynx blinking after terminal window resizing
On Mon, Aug 01, 2022 at 10:19:17PM +, Thorsten Glaser wrote: > Thomas Dickey dixit: > > >On Sun, Jun 12, 2022 at 03:16:40AM +0300, mark zaharov wrote: > >> here is the solution which my friend provides. He said it works well with > >> slang and this bug exists for ncurces only. > > Huh, I didn’t get that mail. > > >Perhaps this would be reproducible if the version of lynx were identified, > >as well as which platform. I don't see it using > > - xterm 372, > > - ncurses 6.1 and 6.3, > > - lynx 2.8.9rel.1 and 2.9.0dev.10 > > I see it on Debian stable/bullseye, for example. I still don't see it with this combination. The blinking that you're describing would be full-screen repainting. When I resize the screen and press ^R, subsequent cursor movement is only updating the expected link-highlighting characters. Perhaps it's something in your lynx configuration which is relevant. In my check, I used a test account which doesn't customize anything. -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature
Re: [Lynx-dev] Don't open link on left mouse click
who said anything about using the list page? That is not equal to using the / key, typing the word sign, and being taken swiftly to the active sign in link on the page. My main point about w3m though is that I have no real reason to try again since it did not pass the library's must use JavaScript door. Neither does lynx, but I can still search, quickly, the library catalog using lynx. I agree with others though, I do not use a mouse...at all, so lynx managing mouse functions is not important for me personally. On Tue, 2 Aug 2022, Robin Stern wrote: @Karen this is getting off topic. Because you are new to w3m, you are probably unaware of some goodness from it that can be inherits by lynx. Most importantly, you can display and search just the title of links by pressing Meta-m, which is Escape-m by default. It???s a way better feature than what lynx has as list page that lists the long URLs that don???t mean anything a lot of the time. On Tue, Aug 2, 2022 at 12:38 PM Karen Lewellen wrote: But lynx allows one to search the page using the slash key. why would one use tab keys when one can narrow down the link goal? granted, I just tried w3m for the first time this afternoon, not JavaScript enough for the Toronto public library, but neither is links or elinks. still, not having the slash key find option meant it took me longer to reach the link I sought. Kare On Tue, 2 Aug 2022, Robin Stern wrote: On Tue, Aug 02, 2022 at 02:15:46PM +0100, David Woolley wrote: On 02/08/2022 12:20, Mouse wrote: (a) so here's an opportunity for lynx to do better! They did it at a time when the convention of single click to select and double click to activate was a standard part of the Windows user interface. I think they took that position that selection wasn't something that people wanted to do with hypertext links, i.e., I think they thought single click activation was the better solution, for the hypertext use case. There is another important reason why its more natural for w3m and lynx to not follow the link on click. That ie because the user might then want to press '.' to open the underlying link in an external graphical browser like Firefox etc. At the moment if there is a link surrounded by other links on all of N, E, S, W directions then it is impossible to select it and press '.' to open in an external viewer. One is forced to press tab/ arrow keys multiple times to first reach to that link and then press '.'.
Re: [Lynx-dev] Don't open link on left mouse click
@Karen this is getting off topic. Because you are new to w3m, you are probably unaware of some goodness from it that can be inherits by lynx. Most importantly, you can display and search just the title of links by pressing Meta-m, which is Escape-m by default. It’s a way better feature than what lynx has as list page that lists the long URLs that don’t mean anything a lot of the time. On Tue, Aug 2, 2022 at 12:38 PM Karen Lewellen wrote: > But lynx allows one to search the page using the slash key. why would one > use tab keys when one can narrow down the link goal? > granted, I just tried w3m for the first time this afternoon, not > JavaScript enough for the Toronto public library, but neither is links or > elinks. > still, not having the slash key find option meant it took me longer to > reach the link I sought. > Kare > > > > On Tue, 2 Aug 2022, Robin Stern wrote: > > > On Tue, Aug 02, 2022 at 02:15:46PM +0100, David Woolley wrote: > >> On 02/08/2022 12:20, Mouse wrote: > >>> (a) so here's an opportunity for lynx to do better! > >> > >> They did it at a time when the convention of single click to select and > >> double click to activate was a standard part of the Windows user > interface. > >> I think they took that position that selection wasn't something that > people > >> wanted to do with hypertext links, i.e., I think they thought single > click > >> activation was the better solution, for the hypertext use case. > >> > > There is another important reason why its more natural for w3m and lynx > to not follow the link on click. That ie because the user might then want > to press '.' to open the underlying link in an external graphical browser > like Firefox etc. At the moment if there is a link surrounded by other > links on all of N, E, S, W directions then it is impossible to select it > and press '.' to open in an external viewer. One is forced to press tab/ > arrow keys multiple times to first reach to that link and then press '.'. > > > > >
Re: [Lynx-dev] Don't open link on left mouse click
But lynx allows one to search the page using the slash key. why would one use tab keys when one can narrow down the link goal? granted, I just tried w3m for the first time this afternoon, not JavaScript enough for the Toronto public library, but neither is links or elinks. still, not having the slash key find option meant it took me longer to reach the link I sought. Kare On Tue, 2 Aug 2022, Robin Stern wrote: On Tue, Aug 02, 2022 at 02:15:46PM +0100, David Woolley wrote: On 02/08/2022 12:20, Mouse wrote: (a) so here's an opportunity for lynx to do better! They did it at a time when the convention of single click to select and double click to activate was a standard part of the Windows user interface. I think they took that position that selection wasn't something that people wanted to do with hypertext links, i.e., I think they thought single click activation was the better solution, for the hypertext use case. There is another important reason why its more natural for w3m and lynx to not follow the link on click. That ie because the user might then want to press '.' to open the underlying link in an external graphical browser like Firefox etc. At the moment if there is a link surrounded by other links on all of N, E, S, W directions then it is impossible to select it and press '.' to open in an external viewer. One is forced to press tab/ arrow keys multiple times to first reach to that link and then press '.'.
Re: [Lynx-dev] Don't open link on left mouse click
On Tue, Aug 02, 2022 at 02:15:46PM +0100, David Woolley wrote: > On 02/08/2022 12:20, Mouse wrote: > > (a) so here's an opportunity for lynx to do better! > > They did it at a time when the convention of single click to select and > double click to activate was a standard part of the Windows user interface. > I think they took that position that selection wasn't something that people > wanted to do with hypertext links, i.e., I think they thought single click > activation was the better solution, for the hypertext use case. > There is another important reason why its more natural for w3m and lynx to not follow the link on click. That ie because the user might then want to press '.' to open the underlying link in an external graphical browser like Firefox etc. At the moment if there is a link surrounded by other links on all of N, E, S, W directions then it is impossible to select it and press '.' to open in an external viewer. One is forced to press tab/ arrow keys multiple times to first reach to that link and then press '.'.
Re: [Lynx-dev] Don't open link on left mouse click
On 8/2/22 10:07:02, Thorsten Glaser wrote: > Mouse dixit: > >> (b) what do "graphical browsers" have to do with lynx? > > As soon as you enable “mouse” support they do, because it then > suddenly becomes one. > > I don’t use lynx’ “mouse” support (didn’t notice it has one in > the first place) because I use the pointer in uxterm for copy > to PRIMARY or CLIPBOARD (with Shift) exclusively. This is much > more sane IMHO. There, lynx stays a text mode browser ☺ > Somewhat as MacOS from the very earliest has used Meta-C rather than Ctrl-C for Copy; a blessing because the latter has long been used for SIGINT. -- gil
Re: [Lynx-dev] Don't open link on left mouse click
Mouse dixit: >(b) what do "graphical browsers" have to do with lynx? As soon as you enable “mouse” support they do, because it then suddenly becomes one. I don’t use lynx’ “mouse” support (didn’t notice it has one in the first place) because I use the pointer in uxterm for copy to PRIMARY or CLIPBOARD (with Shift) exclusively. This is much more sane IMHO. There, lynx stays a text mode browser ☺ bye, //mirabilos -- 15:39⎜«mika:#grml» mira|AO: "mit XFree86® wär’ das nicht passiert" - muhaha 15:48⎜ also warum machen die xorg Jungs eigentlich alles kaputt? :)15:49⎜ thkoehler: weil sie als Kinder nie den gebauten Turm selber umschmeissen durften? -- ~/.Xmodmap wonders…
Re: [Lynx-dev] Don't open link on left mouse click
On 02/08/2022 12:20, Mouse wrote: (a) so here's an opportunity for lynx to do better! They did it at a time when the convention of single click to select and double click to activate was a standard part of the Windows user interface. I think they took that position that selection wasn't something that people wanted to do with hypertext links, i.e., I think they thought single click activation was the better solution, for the hypertext use case.
Re: [Lynx-dev] lynx blinking after terminal window resizing
> Perhaps this would be reproducible if the version of lynx were identified, > as well as which platform. I don't see it using > - xterm 372, > - ncurses 6.1 and 6.3, > - lynx 2.8.9rel.1 and 2.9.0dev.10 > > -- > Thomas E. Dickey > https://invisible-island.net > ftp://ftp.invisible-island.net Sorry. Sure. - foot 1.12.1, alacritty 0.10.1, - ncurses 6.3_p20220724-r0, - lynx 2.8.9_p1-r7, x86_64 Alpine linux (edge) Wayland
Re: [Lynx-dev] Don't open link on left mouse click
>> It would be nice to have a config option to specify mouse left click behavi$ > Single click link following has been the standard for graphical > browsers since the beginning and was inherited from earlier hypertext > formats, like PDF. (a) so here's an opportunity for lynx to do better! (b) what do "graphical browsers" have to do with lynx? /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTMLmo...@rodents-montreal.org / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
Re: [Lynx-dev] Don't open link on left mouse click
In w3m single click selects, double click or a single click followed by Enter also follows it. IMO for text-based interface it’s pretty well thought. Though I can see the drive to emulate GUI browser behavior, hence the ask is for a config option. On Tue, Aug 2, 2022 at 3:43 AM David Woolley wrote: > On 02/08/2022 11:18, Robin Stern wrote: > > It would be nice to have a config option to specify mouse left click > behavior (goto a link, but don't follow it), or an ability to remap MOUSE. > w3m also just selects a link on mouse click. > > Single click link following has been the standard for graphical browsers > since the beginning and was inherited from earlier hypertext formats, > like PDF. I've never seen an option to disable it on those, and yes it > difficult to select text in a link to copy it, in graphical browsers. > >
Re: [Lynx-dev] Don't open link on left mouse click
On 02/08/2022 11:18, Robin Stern wrote: It would be nice to have a config option to specify mouse left click behavior (goto a link, but don't follow it), or an ability to remap MOUSE. w3m also just selects a link on mouse click. Single click link following has been the standard for graphical browsers since the beginning and was inherited from earlier hypertext formats, like PDF. I've never seen an option to disable it on those, and yes it difficult to select text in a link to copy it, in graphical browsers.
[Lynx-dev] Don't open link on left mouse click
Hi lynx-dev, Lynx's mouse behavior is pretty sensitive. Left click on a link hightlights it, as well as follows it. I tried remapping MOUSE keymap but lynx does not allow that. It would be nice to have a config option to specify mouse left click behavior (goto a link, but don't follow it), or an ability to remap MOUSE. w3m also just selects a link on mouse click. It would be useful to have this behavior for multiple reasons, including: while screencasting from a page, one can highlight a link by simply clicking on it. Clicking around a link does select it without following, but if there are many links on a busy webpage it is not possible to click and highlight a link that is surrounded by other links on all sides. Lynx Version 2.9.0dev.10 (11 Aug 2021) libwww-FM 2.14, SSL-MM 1.4.1, OpenSSL 1.1.1q, ncurses 6.3.20211021 Built on darwin21.6.0 (Aug 2 2022 09:37:15). Best, Robin
