Introduction
Introduction Statistics Contact Development Disclaimer Help
openurl.pl and w3m
Monday Jan 11 8:58:47 2021
------------------------------
Before I switched to weechat, I used irssi for several years, it was
really kewl to use the good old duo "screen + irssi" like the kewl
kids did.
Since I started using "tmux + weechat" I never looked back. But since
weechat was mysteriouly removed from sdf-eu I had to go back to irssi.
One of the scripts I liked the most, and I used on many occasions was
openurl.pl It grabs all the urls in the buffers and allows you to
easily open them in w3m (I am talking http links here although the
script also allows you to open ftp and mail links).
https://scripts.irssi.org/
Now that I am using it again I must say I'd really be enjoying the
script 100% if it weren't for one thing: w3m (or maybe two...)
Do not get me wrong, I like w3m, I think it is a great web browser and
pager. Put the blame on me but I feel clumpsy using it because the
keystrokes are not in my brain muscle and very often I find myself
having to use my w3m cheetsheet to use it properly.
The second problem is that w3m is hardcoded in openurl.pl (as well as
ncftp and mutt). I do not know much about perl but I guess it should
be pretty easy to use variables for these programs. I might take a
serious look at it someday and maybe improve it, but for the time
being, my lazy solution was to s/w3m/elinks/ and be done with it.
Now I can take the experience of quickly opening urls to a different
level using a text browser I really feel comfortable with and with
which I can easily store bookmarks and handle tabs like a pro ;-)
since many many elinks keystrokes are hardcoded in my brain.
Maybe hardcoding is not that bad after all ... (just joking)
______________________________________________________________________
Gophered by Gophernicus/1.6 on NetBSD/amd64 9.1
You are viewing proxied material from sdfeu.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.