From miket at ilm.com Sun Dec 3 23:47:30 2006 From: miket at ilm.com (Michael Thompson) Date: Sun, 3 Dec 2006 22:47:30 -0800 Subject: [elinks-users] elinks friendly wiki Message-ID: <20061204064730.GA14493@pandora-linux.lucasfilm.com> does such a thing exist? From jonas.fonseca at gmail.com Tue Dec 5 15:21:52 2006 From: jonas.fonseca at gmail.com (Jonas Fonseca) Date: Tue, 5 Dec 2006 23:21:52 +0100 Subject: [elinks-users] elinks friendly wiki In-Reply-To: <20061204064730.GA14493@pandora-linux.lucasfilm.com> References: <20061204064730.GA14493@pandora-linux.lucasfilm.com> Message-ID: <2c6b72b30612051421r14da84c0o807b8d27720e6fe7@mail.gmail.com> On 12/4/06, Michael Thompson wrote: > does such a thing exist? I've never personally used ELinks to edit a wiki, however I have heard about various problems related to the poor caching and encoding support of ELinks. Maybe you can share a bit more about any problems you have encountered? -- Jonas Fonseca From thomas.adam22 at gmail.com Tue Dec 5 16:30:09 2006 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Tue, 5 Dec 2006 23:30:09 +0000 Subject: [elinks-users] elinks friendly wiki In-Reply-To: <2c6b72b30612051421r14da84c0o807b8d27720e6fe7@mail.gmail.com> References: <20061204064730.GA14493@pandora-linux.lucasfilm.com> <2c6b72b30612051421r14da84c0o807b8d27720e6fe7@mail.gmail.com> Message-ID: <20061205233009.GB3331@edulinux.homeunix.org> [Bcc'ed tag at lists.linuxgazette.net for inclusion into LG at some point.] On Tue, Dec 05, 2006 at 11:21:52PM +0100, Jonas Fonseca wrote: > On 12/4/06, Michael Thompson wrote: > >does such a thing exist? > > I've never personally used ELinks to edit a wiki, however > I have heard about various problems related to the poor > caching and encoding support of ELinks. Maybe you can > share a bit more about any problems you have encountered? I am assuming more that Michael meant one that displays properly in ELinks. Of course, this is related to the limited CSS capabilities that ELinks currently has, but it's not all doom and gloom depending on the wiki engine ELinks is looking at. In my experience, Wikipedia, and other sites which use Wikimedia are the worst if only because they're very CSS-intensive -- and don't really give much, if any, consideration for people who use text-based browers or even screen-readers. If you look at the preferences page for, say, wikipedia, the best skin to choose I have found is "Classic". This reduces the rather long list of options at the end of the document (the "sidebar that wikipedia has which displays to the left-hand side in Firefox). Of course, the default theme wikipedia has displays fine -- it's just that ELinks renders the CSS part without positioning at the end of the document. Moinmoin, OTOH, is perhaps the better wiki engine that's ELinks friendly. If you look here: fvwmwiki.bu-web.de You'll note that the main options are at the top of the page instead (because ordinarily they'd appear horizontally across the page in some other browser). Since MoinMoin hides any user preferences in a separate page, and doesn't list all sorts of weirder options for you to choose from in some sort of sidebar like wikimedia does, visually, it's much nicer, IMO. Again, along similar lines is the all-perl wiki engine "UseMod" which is very Elinks friendly, since it's a very simple wiki engine: http://www.hantslug.org.uk ... is such an example. Now, you're probably going to ask what you can do in order to try and improve the look of wikipedia, aren't you? ;) The truth is there isn't a lot you can do unless you decide to script replacement operations via either Lua, Guile, Perl or Ruby. Since I've done a tiny bit of work in ELinks with Ruby that'd be my first choice. Not that it matters, of course. Perhaps the biggest thing which annoys me about wikimedia with ELinks is how wikimedia decides to link images. If you look at this, for instance: http://en.wikipedia.org/wiki/Squirrel You'll note that under section 2 there's two images, one for a squirrel (a thumbnail) and the other for an [enlarge]d version of him. I tend not to care for the enlarged one, so I'll leave that as is. You'll note though that clicking on either one of those links takes you to a meta-information page before you can get at the image. I find this annoying and so decided to link the thumbnail link directly to the image, bypassing that page. Assuming you had ELinks compiled in with Ruby support, here's how'd do that in ~/.elinks/hooks.rb `` def ELinks::pre_format_html_hook(url, html) if( url =~ /wikipedia\.org/) # Handle images. html.gsub!(/?(/,'\2'); return html end end '' I tend to leave the link for Enlarge on the page -- but there's nothing stopping you removing it at pre_formatting time, as above. If none of this is what you wanted to know, that's your own fault for not being specific enough. ;P But I hope it helps, nevertheless. -- Thomas Adam -- "Wanting to feel; to know what is real. Living is a lie." -- Purpoise Song, by The Monkees. From miket at ilm.com Tue Dec 5 21:51:36 2006 From: miket at ilm.com (Michael Thompson) Date: Tue, 5 Dec 2006 20:51:36 -0800 Subject: [elinks-users] elinks friendly wiki In-Reply-To: <20061205233009.GB3331@edulinux.homeunix.org> References: <20061204064730.GA14493@pandora-linux.lucasfilm.com> <2c6b72b30612051421r14da84c0o807b8d27720e6fe7@mail.gmail.com> <20061205233009.GB3331@edulinux.homeunix.org> Message-ID: <20061206045136.GA3355@pandora-linux.lucasfilm.com> thanks for the replies! i have a pretty major application here that is driven using elinks, and i was looking to include a wiki of some sort into it, as part of keeping all the documentation and FAQ-type stuff online in one spot, accessible via my app. the few wikis i've tried with elinks havn't worked out that well, as you can imagine ;) anyway, i will give these a go - thanks again everyone! On Tue, Dec 05, 2006 at 11:30:09PM +0000, Thomas Adam wrote: > > On Tue, Dec 05, 2006 at 11:21:52PM +0100, Jonas Fonseca wrote: > > On 12/4/06, Michael Thompson wrote: > > >does such a thing exist? > > > > I've never personally used ELinks to edit a wiki, however > > I have heard about various problems related to the poor > > caching and encoding support of ELinks. Maybe you can > > share a bit more about any problems you have encountered? > > I am assuming more that Michael meant one that displays properly in > ELinks. Of course, this is related to the limited CSS capabilities that > ELinks currently has, but it's not all doom and gloom depending on the > wiki engine ELinks is looking at. > > ... > > Moinmoin, OTOH, is perhaps the better wiki engine that's ELinks > friendly. If you look here: > > fvwmwiki.bu-web.de > > Again, along similar lines is the all-perl wiki engine "UseMod" which is > very Elinks friendly, since it's a very simple wiki engine: > > http://www.hantslug.org.uk > From thomas.adam22 at gmail.com Thu Dec 7 14:40:13 2006 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Thu, 7 Dec 2006 21:40:13 +0000 Subject: [elinks-users] elinks friendly wiki In-Reply-To: <20061206045136.GA3355@pandora-linux.lucasfilm.com> References: <20061204064730.GA14493@pandora-linux.lucasfilm.com> <2c6b72b30612051421r14da84c0o807b8d27720e6fe7@mail.gmail.com> <20061205233009.GB3331@edulinux.homeunix.org> <20061206045136.GA3355@pandora-linux.lucasfilm.com> Message-ID: <20061207214013.GA29329@edulinux.homeunix.org> On Tue, Dec 05, 2006 at 08:51:36PM -0800, Michael Thompson wrote: > thanks for the replies! i have a pretty major application here that > is driven using elinks, and i was looking to include a wiki of some > sort into it, as part of keeping all the documentation and FAQ-type > stuff online in one spot, accessible via my app. > > the few wikis i've tried with elinks havn't worked out that well, > as you can imagine ;) > > anyway, i will give these a go - thanks again everyone! I suppose I should mention that I was messing around with DoKu wiki -- that pronabably has the cleanist interface yet, as far as ELinks is concerned, and works well. ;) -- Thomas Adam -- "Wanting to feel; to know what is real. Living is a lie." -- Purpoise Song, by The Monkees. From ant at zimage.com Sat Dec 23 03:19:20 2006 From: ant at zimage.com (Phillip Pi) Date: Sat, 23 Dec 2006 02:19:20 -0800 Subject: [elinks-users] Unable to compile elinks v0.11.2 in Mac OS X 10.2.8 due to socket.c errors. In-Reply-To: <20061127163140.GB24548@diku.dk> References: <20061127101500.GF25246@alpha.zimage.com> <456AC5FF.406@norz.org> <20061127163140.GB24548@diku.dk> Message-ID: <20061223101920.GT20963@alpha.zimage.com> > > >Hello, > > > > > >It's me again. I am having problems compiling eLinks v0.11.2 in Mac OS X > > >10.2.8: > > > > > >... > > >[MAKE all] src/network > > >[MAKE all] src/network/ssl > > > [CC] src/network/ssl/socket.o > > > [CC] src/network/ssl/ssl.o > > > [LD] src/network/ssl/lib.o > > > [CC] src/network/connection.o > > > [CC] src/network/dns.o > > > [CC] src/network/progress.o > > > [CC] src/network/socket.o > > >socket.c: In function `get_pasv_socket': > > >socket.c:282: error: `socklen_t' undeclared (first use in this function) > > >socket.c:282: error: (Each undeclared identifier is reported only once > > >socket.c:282: error: for each function it appears in.) > > >socket.c:282: error: parse error before "len" > > >socket.c:300: error: `len' undeclared (first use in this function) > > >socket.c: In function `connected': > > >socket.c:456: error: `socklen_t' undeclared (first use in this function) > > >socket.c:456: error: parse error before "len" > > >socket.c:461: error: `len' undeclared (first use in this function) > > >make[2]: *** [socket.o] Error 1 > > >make[1]: *** [all-recursive] Error 1 > > >make: *** [all-recursive] Error 1 > > > > > >The whole compilation log can be found here: http://pastebin.ca/259301 > > >... > > > > > >Thank you in advance. :) > > > > > A potential explanation can be seen there: > > > > http://lists.helixcommunity.org/pipermail/common-dev/2004-May/000938.html > > Ok, here is a small patch that should fix it. > > diff --git a/configure.in b/configure.in > index ad44020..65ccc65 100644 > --- a/configure.in > +++ b/configure.in > @@ -221,6 +221,7 @@ AC_SYS_LARGEFILE > AC_TYPE_SIZE_T > AC_TYPE_OFF_T > EL_CHECK_TYPE(ssize_t, int) > +EL_CHECK_TYPE(socketlen_t, int) > EL_CHECK_SYS_TYPE(long long, HAVE_LONG_LONG, []) > EL_CHECK_SYS_TYPE(off_t, HAVE_OFF_T, []) > EL_CHECK_INT_TYPE(int32_t, HAVE_INT32_T) > > Phillip, does this work for you? Sorry for taking so long. I got a bit busy with life. :( It compiled and worked. Thanks and happy holidays. :) If you need to contact me, then e-mail me since I am going to unsubscribe from this mailing list for now. -- [Laser pulsing] "Bah. It's as easy as crushing an ant! You know, the..." [grunting] "Wh-wh-whoa! Hey, take my wallet and leave me alone!" --Mr. Burns from The Simpsons (Fraudcast News; FABF16/FABF18 episode) /\___/\ / /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site) | |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net \ _ / E-mail: philpi at earthlink.net or ant at zimage.com ( ) From rader at ginseng.hep.wisc.edu Sun Dec 24 07:51:17 2006 From: rader at ginseng.hep.wisc.edu (rader at ginseng.hep.wisc.edu) Date: Sun, 24 Dec 2006 08:51:17 -0600 Subject: [elinks-users] setting mono mode colors and difficult key bindings Message-ID: <200612241451.kBOEpHwR013986@ginseng.hep.wisc.edu> How do I set the mono color mode link color? I'm running in a green on black xterm, and would like links to be rendered in cyan instead of blue. Is it somehow possible to bind ^Tab? If I use... bind "main" "Tab" = "move-link-next" bind "main" "Ctrl-Tab = "tab-next" ...then ^Tab does "move-link-next". Is it somehow possible to bind ^C to "history-move-back"? If I use... bind "main" "Ctrl-C" = "history-move-back" ...then ^C does "really-quit". steve - - - From willmaier at ml1.net Sun Dec 24 08:08:03 2006 From: willmaier at ml1.net (Will Maier) Date: Sun, 24 Dec 2006 09:08:03 -0600 Subject: [elinks-users] setting mono mode colors and difficult key bindings In-Reply-To: <200612241451.kBOEpHwR013986@ginseng.hep.wisc.edu> References: <200612241451.kBOEpHwR013986@ginseng.hep.wisc.edu> Message-ID: <20061224150803.GA3569@lass.lfod.us> On Sun, Dec 24, 2006 at 08:51:17AM -0600, rader at ginseng.hep.wisc.edu wrote: > Is it somehow possible to bind ^Tab? If I use... > bind "main" "Tab" = "move-link-next" > bind "main" "Ctrl-Tab = "tab-next" > ...then ^Tab does "move-link-next". Terminals don't see ^Tab (since Tab is actually ^I), so they just pass Tab to elinks, AFAIK. > Is it somehow possible to bind ^C to "history-move-back"? If > I use... > bind "main" "Ctrl-C" = "history-move-back" > ...then ^C does "really-quit". I don't think elinks does any special trapping for ^C; it'll just accept it as normal (and quit, as you noticed). I can't think of a good way to get either of those bindings working, unfortunately. The first breaks because of the way terminals work, and the second would require some handling in elinks itself. -- [Will Maier]-----------------[willmaier at ml1.net|http://www.lfod.us/] From rader at ginseng.hep.wisc.edu Sun Dec 24 09:32:36 2006 From: rader at ginseng.hep.wisc.edu (rader at ginseng.hep.wisc.edu) Date: Sun, 24 Dec 2006 10:32:36 -0600 Subject: [elinks-users] setting mono mode colors and difficult key bindings In-Reply-To: <20061224150803.GA3569@lass.lfod.us> References: <200612241451.kBOEpHwR013986@ginseng.hep.wisc.edu> <20061224150803.GA3569@lass.lfod.us> Message-ID: <200612241632.kBOGWacx019225@ginseng.hep.wisc.edu> > > From: me > > Is it somehow possible to bind ^Tab? If I use... > > bind "main" "Tab" = "move-link-next" > > bind "main" "Ctrl-Tab = "tab-next" > > ...then ^Tab does "move-link-next". > From: Will Maier > Terminals don't see ^Tab (since Tab is actually ^I), so they just > pass Tab to elinks, AFAIK. But--Will!--I happen to have been plagiarizing one of _your_ elinks.conf files this morning which has... bind "main" "Ctrl-Tab" = "frame-next" [Sorry, I couldn't resist.] Yes, once upon a time I knew Tab is ^I. Forgive me for forgeting. > > Is it somehow possible to bind ^C to "history-move-back"? If > > I use... > > bind "main" "Ctrl-C" = "history-move-back" > > ...then ^C does "really-quit". > I don't think elinks does any special trapping for ^C; it'll just > accept it as normal (and quit, as you noticed). Elinks sometimes does.... install_signal_handler(SIGINT, (void (*)(void *)) sig_ctrl_c, term, 0); and eventually... set_kbd_term_event(&ev, KBD_CTRL_C, KBD_MOD_NONE); But it's not clear what's going on by glancing at the source. Rather than poke at it, I'm hoping someone who knows the source will chime in? steve - - - From kon at iki.fi Sun Dec 24 12:39:20 2006 From: kon at iki.fi (Kalle Olavi Niemitalo) Date: Sun, 24 Dec 2006 21:39:20 +0200 Subject: [elinks-users] setting mono mode colors and difficult key bindings In-Reply-To: <200612241632.kBOGWacx019225@ginseng.hep.wisc.edu> References: <200612241451.kBOEpHwR013986@ginseng.hep.wisc.edu> <20061224150803.GA3569@lass.lfod.us> <200612241632.kBOGWacx019225@ginseng.hep.wisc.edu> Message-ID: <87k60hm6c7.fsf@Astalo.kon.iki.fi> A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 188 bytes Desc: not available Url : http://linuxfromscratch.org/pipermail/elinks-users/attachments/20061224/35832b5a/attachment.bin From rader at ginseng.hep.wisc.edu Sun Dec 24 14:36:49 2006 From: rader at ginseng.hep.wisc.edu (rader at ginseng.hep.wisc.edu) Date: Sun, 24 Dec 2006 15:36:49 -0600 Subject: [elinks-users] setting mono mode colors and difficult key bindings In-Reply-To: <200612241451.kBOEpHwR013986@ginseng.hep.wisc.edu> References: <200612241451.kBOEpHwR013986@ginseng.hep.wisc.edu> Message-ID: <200612242136.kBOLanbb029468@ginseng.hep.wisc.edu> > From: me > How do I set the mono color mode link color? I'm running in > a green on black xterm, and would like links to be rendered > in cyan instead of blue. After looking into this some more I realized--da--this isn't a Elinks question. Elinks in mono color mode renders links with the terminal's bold attribute (curses SCREEN_ATTR_BOLD.) So the way to do what I want is to tell xterm to render bold in cyan... xterm -bg black -fg green -xrm 'XTerm*VT100*colorBD: cyan' > From: Kalle Olavi Niemitalo > If you do e.g. "stty intr undef" so that Ctrl-C does not give > ELinks a signal, then ELinks will handle it as a bindable key. Indeed. Thanks!! steve - - -