[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lynx-dev patch to spawn extra lynx's

From: Richard E. Hawkins
Subject: Re: lynx-dev patch to spawn extra lynx's
Date: Wed, 15 Sep 1999 17:21:33 -0500

Klaus Kalled,

>But since you'll have to "jump" anyway (I don't think spearate patches
>for 2.8.1 -> 2.8.2 are available anywhere, and even if they were it would
>be a pain to apply them) just jump to the current latest full lynx2.8.3dev.9.



The code I patched is all either a) obsolete, or b) gone :)

But there may now be a cleaner way to do this--more in keeping with my 
original thinking.  Ideally, the existing run_external should run the 

  xterm -e "lynx <theulr> &"

(for unix & X). Thsi shoudl probably be user definable if for no other 
reason than to allow automatically choosing huge letters rather than 
normal for the xterm.

I've noticed that external programs are *not* sent to the background 
when launched, but rather that lynx waits for them. Is there some 
particular reason for this?  In a windowed environment, spawning seems 
more natural.

Another change I found is that BUTTON2 is now used to pop up a menu. I 
had assumed that I'd use button 2 just to keepin line with netscape and 
mosaic. What should I try to attach this behavior to?  Can I use  a 
double-clicked button?

Anyway, I see the behavior as:

1) get_mouse_link, just as if button 1 were pressed
2) get the url.  If I'm reading things right (my c is more than a 
little rusty), then if mouse_link has a value other than -1, there is a 
link, and i can find the url in links[mouse_link].something.   is that 
something "target"?
3) concatenate     xterm -e \"lynx     &links[mouse_link].target    \" &
4) send this concatenated string to LYSystem

Am I on track?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]