[elinks-users] [ANNOUNCE] ELinks 0.11.4
Hello, Here goes the final 0.11.4 release containing mostly bug fixes and translation updates. Hopefully this will be one of the last releases of the long lived 0.11 branch that came to life back in 2006-01-01, since all the goodies in the 0.12 branch brings considerable improvements in terms of UTF-8 support etc. Below is the complete shortlog of changes since 0.11.4rc1 and the NEWS entry for this release with information about bug fixes. Adam Golebiowski (1): pl.po: Shortcut key for File/resize terminal changed from 't' to 'r'. Jonas Fonseca (5): elinks-0.11.4rc1.GIT Update Danish translation Update po files Update manpages for 0.11.4 elinks-0.11.4 Kalle Olavi Niemitalo (10): keys2doc: Change \foo\ to foo. update-man: Install manpages to srcdir, not builddir. elinks.conf.5: quoting corrections Bug 939: Documented the fix. Bug 1012: Compile with -fno-strict-overflow or -fwrapv. Bug 1014: Fix incompatible pointer type in init_perl. NEWS: mention bug 1014 Bug 1016: Avoid JSFunctionSpec. NEWS: Critical bug 674 is a duplicate of 956. NEWS: Remove the should be removed section. Miciah Dashiel Butler Masters (2): elinks.conf.5: Correct description of 'unset' directive save_textarea_file: don't return a dangling pointer if open fails Paul B. Mahol (1): Recognize Insert key on cons25 (FreeBSD console) Witold Filipczyk (7): Polish translation was updated. Mark option changed in File extensions - Add. bittorrent: Overflow occuring when a piece was rejected. fsp: Fixed a serious bug. Test whether CIA works. Test commit. pl.po: Question marks. The complete list of bug fixes since 0.11.3 (from NEWS): * critical bug 755: fix crashes due to dangling pointers to struct form_state * critical bugs 613, 714, 961: ``assertion list_empty(form_controls) failed'' * critical bug 945: don't crash if a Lua script calls e.g. error(nil) * critical bug 1003: don't crash if a smart URI rewrite template gets too few parameters * critical bug 1016: avoid JSFunctionSpec for better compatibility across versions of SpiderMonkey * critical bugs 674, 956: don't reuse pointers to SpiderMonkey objects that may have been collected as garbage. This fix causes bug 954. * CVE-2007-2027: check if the program path contains src/ before using ../po files * important Debian bug 380347: prevent a buffer overflow in entity_cache and a possible subsequent crash * major bug 788: don't read STRLEN n_a, which isn't initialized by POPpx of Perl v5.8.8 and later * fix query parsing in file: URIs for local CGI (was broken in 0.11.3) * bug 451: fix incompatible pointer type in PERL_SYS_INIT3 call * bug 691: don't look up bogus IPv4 addresses based on characters of a hostname * bug 712: GnuTLS works on https://www-s.uiuc.edu/[] * fix active and passive FTP over IPv6 * bug 938: elinks -remote no longer needs a controlling tty * bug 939: fix FSP directory listing (some compiler options left it empty) * bug 978: Python's webbrowser.open_new_tab(URL) works since now * bug 1012: compile with -fno-strict-overflow or -fwrapv if available * bug 1014: fix incompatible pointer type in Perl_sys_init3 call * minor bug 54, Debian bug 338402: don't force the terminal to 8 bits with no parity, and don't disable XON/XOFF flow control either * minor bug 951 in user SMJS: garbage-collect SMJS objects on 'File - Flush all caches' to work around their holding cache entries busy * minor bug 396: never show empty filename in the what-to-do dialog * minor bug 461: ensure contrast in blank areas, to keep the cursor visible * minor bug 928: properly display no-break spaces in a UTF-8 document if the terminal uses some other charset * minor bug 987: English spelling and grammar corrections * minor bug 1000: preserve any query and fragment when converting a file name to a file:// URL * minor: don't assume sizeof(int)==4 in bittorrent * trivial bug 947: document.html.wrap_nbsp also affects text in tables * trivial bug 997: fix unlikely stack corruption in active FTP * build bug 1002: fix ``comparison is always true due to limited range of data type'' warning on PowerPC and s390 * build bug 950: fix ``config/install-sh: No such file or directory'' on SunOS * build bug 936: fix errors about undefined off_t (autoheader incompatibility) * build bug 959: test in configure whether -lX11 works * build: update SpiderMonkey configure check Debian compatibility * build: use $(CPPFLAGS) rather than $(AM_CFLAGS) * build: disable GCC 4.2 warning about builtin_modules * build: move debian/ to contrib/debian/ * minor build bug 989: AsciiDoc 8.2.2 compatibility * minor build bug 960: fix errors in loadmsgcat.c if mmap() exists but munmap() doesn't -- Jonas Fonseca ___ elinks-users mailing list elinks-users
Re: [elinks-users] accesskey ... hotkeys for elinks webpages
Hello Nigel, Nigel Hamilton [EMAIL PROTECTED] wrote Wed, Apr 23, 2008: Hi, Does the accesskey attribute work in elinks? I have a number of forms on a page which I would like the user to submit by pressing an accesskey. It is supposed to work. It would be great if someone could provide a html snippet that shows form submission using accesskeys working. Take a look at test/tabindex.html in the ELinks repository. p.s. who is making a Programmer's IDE powered by elinks (see http://blog.thegoo.org) Interesting. :) -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Javascript Button Workaround?
Hello Drew, Drew Fisher [EMAIL PROTECTED] wrote Thu, Mar 20, 2008: I've read that Elinks has some support for Javascript. Before I tread down the path of getting everything downloaded and installed on my test machine, I was wondering if any of you have seen this type of thing before and can verify that Elinks will work? JavaScript support in ELinks is limited to very basic things, for example the DOM interface is not supported but some of the form interface (if that makes sense to you) is implemented. It is hard for me to say if it will work, so you are just going to have to try it yourself, but the odds are probably small. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Using Elinks with TinyUrl?
Seth Williamson [EMAIL PROTECTED] wrote Fri, Mar 14, 2008: On Fri, 14 Mar 2008, Jonas Fonseca wrote: Seth Williamson [EMAIL PROTECTED] wrote Thu, Mar 13, 2008: Sorry for being unclear. Try: Document +- Plain rendering +- Display URIs Actually I had gotten that far, but what's hosing me up is that there is apparently nothing in the plain rendering folder. I expand it and it shows there's no option of switch beneath it in the hierarchy. So my question is, is my version of elinks old or something? Or is this display URI's option something I'm supposed to add myself? If the latter, do I just click add and write that phrase? Sorry to take so much time over this. Hmm, this is strange. The option is not something you have to add and it has been there for ages as far as I remember. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Using Elinks with TinyUrl?
Seth Williamson [EMAIL PROTECTED] wrote Thu, Mar 13, 2008: I don't know if this may help you, but if you enable the Display URIs option for plain text rendering you can sometime make the links accessible by changing to the page source view. Sorry to be dense, but I can't seem to find this switch in the options manager. Or is it somewhere else? Sorry for being unclear. Try: Document +- Plain rendering +- Display URIs -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
[elinks-users] [ANNOUNCE] ELinks 0.11.4rc0
Hello,
Time is nearing another stable release, however, before hitting 0.11.4 a
few release candidates seems to be in order to let any last pending
changes migrate from the development branches. This release fixes a
handful of critical bugs and security issues, including CVE-2007-2027,
as well as some minor problems. You are adviced to upgrade!
Below is the complete shortlog of changes since 0.11.3. Please see the
NEWS file for a more structured list of fixes and improvements.
Jonas Fonseca (9):
elinks-0.11.3.GIT
Never show empty filename in the what-to-do dialog
Check if the program path contains src/ before using ../po files
Mention testing of po updates without installing ELinks
Fix smjs scripting #ifdefs to use CONFIG_SM_SCRIPTING
Update fuzzy messages in the Danish translation
Change elinks.or.cz references to elinks.cz
Use git tools instead of cogito for getting the build ID
elinks-0.11.4rc0
Kalle Olavi Niemitalo (91):
NEWS: List release dates, from mailing list announcements.
NEWS: Open a section for 0.11.3.GIT.
doc: More AsciiDoc compatibility.
Updated Lua scripting document.
lua_console_hook must return goto_url, not goto-url.
lua-scripting: Revised examples for Lua 5.0. And other updates.
Bug 945: Don't crash if the error message is not a string.
NEWS: mention bug 945
NEWS: Clarify that these are bug numbers.
l_pipe_read: Don't leak the old block if mem_realloc fails.
AUTHORS: add Simon Josefsson
Bug 712, ssl_set_no_tls: Disable TLS protocols for GnuTLS too.
Bug 947, u2cp_: Use UCS_NO_BREAK_SPACE instead of 0xa0.
Bug 879: New constant UCS_SOFT_HYPHEN; use where applicable.
Bugs 879, 928, 947: Specially map U+00A0 and U+00AD in translation tables.
Bug 947, set_hline: Respect wrap_nbsp also if !part-document.
NEWS: mention bugs 928, 947
Document the meaning of document_options.cp.
html_textarea: Use memmove rather than memcpy.
Revert 2d6840b9, Only set the socket protocol family on success.
NEWS: mention passive FTP over IPv6
Debian bug 380347: Prevent a buffer overflow in entity_cache.
NEWS: mention Debian bug 380347
NEWS: mention bug 396
NEWS: Use just http: instead of link:http:.
NEWS: 0.11.3.GIT _now_
NEWS: mention bug 691
Bug 788: Define n_a variables if the POPpx macro of Perl needs them.
NEWS: mention bug 788
configure.in: Advertise smb2.c to be included in ELinks 0.12.0.
NEWS: bug 788 is more severe than mere warnings
NEWS: mention CVE-2007-2027
Prepend $(top_builddir) to @INSTALL@ if it is relative.
NEWS: mention config/install-sh on SunOS
NEWS: markup changes from 0.12.GIT
NEWS: Bug 950 now has a number.
NEWS: mention the SpiderMonkey check
build: Don't use $(AM_CFLAGS) anymore. Use $(CPPFLAGS) instead.
NEWS: mention ${CPPFLAGS} vs. ${AM_CFLAGS}
Bug 461: Ensure contrast when filling with spaces.
NEWS: mention bug 461
List events in alphabetical order.
List Triggered When before Arguments in the event template.
Garbage-collect SMJS objects before flushing caches.
NEWS: mention bug 951
NEWS: add severities of bugs and sort accordingly
Revert 5a49b9f1, NEWS: mention bug 951
Revert 644908c1, Garbage-collect SMJS objects before flushing caches.
NEWS: mention query parsing in file: URIs for local CGI
Ignore src/ID and src/TAGS.
Compare screen_driver.name with strcmp, not memcmp.
NEWS: sync with 0.12.GIT
NEWS: mention bug 956 (and bug 954)
SMJS: Use JS_GetInstancePrivate where applicable.
SMJS: comment changes
Bug 755: A hack to make SMJS preserve integers as private data.
NEWS: Bug 755 was fixed.
Bug 957: Assert that the ECMAScript interpreter is not running.
Bug 957: if_assert_failed in ecmascript_put_interpreter.
Bug 960: Redefine LOADMSGCAT_USE_MMAP instead of HAVE_MMAP.
NEWS: mention bug 960
Reapply 644908c1, Garbage-collect SMJS objects before flushing caches.
Reapply 5a49b9f1, NEWS: mention bug 951
Link to gitweb at repo.or.cz, rather than pasky.or.cz.
SMJS: Fix error forms.namedItem is not a function.
Bug 936: Create stamp-h.in in autogen.sh.
Bug 936: Require Autoconf 2.61 or later.
Bug 936: Allow Autoconf 2.59 too, for elinks.cz compatibility.
NEWS: mention bug 936
NEWS: sync with 0.12.GIT
Debian bug 431211: Correct GNU GPL version in debian/copyright.
NEWS: mention bugs 613, 714, 961
NEWS: mention bug 959
configure.in: Actually the snapshots aren't daily.
Remove gettext doc excerpt until the license is sorted out.
Rewrite wiki to en.wikipedia.org, avoid server bug.
NEWS: Bug 937 is CVE-2007-5034.
Use -Wno-always-true only if $CC accepts it. GCC 4.1 doesn't
Re: [elinks-users] Unable to compile elinks v0.11.2 in Mac OS X 10.2.8 due to socket.c errors.
Laurent MONIN [EMAIL PROTECTED] wrote Mon, Nov 27, 2006: Phillip Pi wrote: 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? -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Unable to compile elinks v0.11.2 in Mac OS X 10.2.8 due to socket.c errors.
Phillip Pi [EMAIL PROTECTED] wrote Mon, Nov 27, 2006: On Mon, Nov 27, 2006 at 05:31:40PM +0100, Jonas Fonseca wrote: Laurent MONIN [EMAIL PROTECTED] wrote Mon, Nov 27, 2006: Phillip Pi wrote: 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) Oops, this should of course say socklen_t ... -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Can't compile eLinks v0.11.2
Phillip Pi [EMAIL PROTECTED] wrote Thu, Nov 23, 2006: I am having problems compiling eLinks v0.11.2 in an old Debian box with PPC (not mine). I get error: make[4]: Leaving directory `/u00/home/ant/download/elinks-0.11.2/src/document/html/parser' [CC] src/document/html/frames.o [CC] src/document/html/parser.o [CC] src/document/html/renderer.o In file included from ../../.././src/cache/cache.h:6, from renderer.c:13: ../../.././src/util/time.h:44: error: syntax error before 'n' In file included from renderer.c:13: ../../.././src/cache/cache.h:47: error: syntax error before 'off_t' Try to put the following in the start of src/util/time.h #include sys/types.h ... that is what v0.12 has there. Thank you, Jonas. I assume this will be fixed for the next version so I don't have to add this line manually. Am I correct? :) Yes, I hope to make another bugfix release for the stable branch before or after Christmass. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
[elinks-users] [ANNOUNCE] ELinks 0.11.2
Hello, A small update to the stable branch as a reaction to the recently discovered vulnerability in the SMB protocol module. Additionally, the release also contains some minor fixes. The highlights of this particular release are listed below: Jonas Fonseca: Use internal OFF_T_FORMAT instead of PRId64 Fix compilation on Minix3 Kalle Olavi Niemitalo: Bug 841, CVE-2006-5925: Prevent enabling the SMB protocol. Witold Filipczyk: Ecmascript: activate link only when onClick returns true [ I am resending this because it looks like the first one was dropped. ] -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Enter following links while searching ahead in text
Miciah Dashiel Butler Masters [EMAIL PROTECTED] wrote Fri, Jul 21, 2006: On Fri, Jul 21, 2006 at 07:45:14AM +0530, Ligesh wrote: [...] Sorry to disturb everyone, but there is a behavior in elinks that I find a bit hassling. When you are doing search ahead in text, and you press ENter, you expect the cursor to be focused on that particular word, but elinks seems to follow the nearest link. I think this is actually a spill over of similar behavior in 'search-ahead-in-links', where actually this behavior makes a lot of sense. That is, in search-ahead-in-links, it is actually proper that an Enter will make Elinks load that Url, but this behavior really hurts when you are doing search-ahead-in-text. Especially since normal editors like vim will just focus on the word. [...] THANK YOU! World, are there any objections to changing this behaviour? I object not. Well, only to the unwrapped lines. ;) You could use Esc to get out of the search dialog, but that will cause the text not to be added to the search history. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Cache problems?
. :) -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Re: Make errors on OSX
Daniel E. Macks [EMAIL PROTECTED] wrote Wed, Jun 28, 2006: Clayton Smith [EMAIL PROTECTED] said: It's pretty unusual to link all those .o into a giant .o instead of archiving them in a .a, and it also makes it harder to track down where symbols definitions actually are. So elinks-devels...why is that being done? I will try to answer you ramblings. Before the new GNU make based build system was introduced we used .a files. There was one problem with this, namely that some of these .a file had inter-dependencies when the final elinks binary was being linked together. So everytime you needed to add a new .a file you needed to randomly try to insert it into the list of .a file until you found a way that didn't conflict and errored out with undefined symbols. This was solved with not using .a files. Recursively linking things into a general $subdir/lib.o also makes it easier to add new directories and implementing conditional directory decending. Now for every directory in SUBDIRS you can just check for $subdir/lib.o and link it in if it exists. Before you could end up with .a files in every subdir and then you needed to specify that this $subdir/$subsubdir/lib.a should be linked in. If there is a portable way to link several .a files into a super .a file then that could of course also be used. If I recall correctly, I didn't (bother to ;) figure out how to do that. I'm having trouble finding clear documentation of the changes you've made from the official gettext distro. Yes, we should probably have done that. One thing I know of (apart from switching gettext to mostly use ELinks's memory management system and coding style instead of that horrible GNU one ;) is that _() will take a terminal struct as an arg. This stems from the fact that several terminals can exist, each with a different locale. It's probably not so common in practice and I don't know why we bother to support that, but it obviously has to do with ELinks instances being able to connect to each other and share cache info etc. to minimize memory usage. Here is the command that runs that actually produces the error: [EMAIL PROTECTED]/docs/downloads/elinks-0.11.1/src$ gcc -g -O2 -Wall -fno-strict-aliasing -Wno-pointer-sign -o elinks lib.o -lssl -lcrypto -ldl -lz -lbz2 -liconv /usr/bin/ld: warning multiple definitions of symbol _locale_charset lib.o definition of _locale_charset in section (__TEXT,__text) /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libiconv.dylib(localcharset.o) definition of _locale_charset There's long been a symbol with the same name in gettext (libintl) and iconv (libiconv). It usually only triggers a warning on OS X because each symbol lives in its own lib's namespace. If both definitions of the symbol wind up in the common namespace, however, there is a (fatal) collision. There might be a flag to instruct the linker to use symbols in the specific .o before those in the -l libs? The brute-force solution would be to rename the offending symbol in the elinks gettext. This would probably be the best way to finally put this warning to rest. There was talk about adding support for linking in a local gettext version but for the reason I've explained above regarding _() this will probably never happen and messing with various variables should be safe. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] elinks popen and coloured dump
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote Tue, Jun 13, 2006:
By the way, is it possible to have document colours except for visited links
(would like to have them always in yellow)
Not really, only customization of the active link is supported. You
could however try to echo a:visited { color: yellow; } into
~/.elinks/user.css and set the appropriate colors to load it. But
document colours will probably override it in most cases and we don't
support the CSS !important thing.
--
Jonas Fonseca
___
elinks-users mailing list
elinks-users@linuxfromscratch.org
http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Windows port
Alejandro Jakubi [EMAIL PROTECTED] wrote Tue, Jun 13, 2006: The freshmeat page http://freshmeat.net/projects/elinks states: [Operating System] BeOS, MacOS X, Microsoft :: Windows, Is there a Windows binary available for download? False marketing, there was presumably someone who started a win32 port. But it never got finished. You'll have to run ELinks on top of Cygwin to have it run on Windows. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] elinks popen and coloured dump
[EMAIL PROTECTED] [EMAIL PROTECTED] wrote Sun, Jun 11, 2006: Hallo! Hej, I now got stuck on trying to print in colour. Is there a way to get a somehow formatted coloured dump? (html, esc-sequenced, ...) I might be nice to have the option Save formatted and coloured document With colour I mean the colours elinks uses for displaying depending on one of the three modes. I tried to use /dev/vcs3 but the escape-sequences are not in there. Using elinks http://www.czech-language.cz/alphabet/kodovani.html cz.txt is behaving as if -dump 1 had been specified. ELinks uses isatty to detect both whether to read from stdin and whether to dump to stdout or use interactive mode. Recent ELinkses support dumping colors. Use something like: $ elinks --dump-color-mode 1 URL file where the --dump-color-mode option is aliased to the elinks.conf(5) option document.dump.color_mode, 0 is mono, 1 is 16 colors, and 2 is 256 colors (if ELinks was configured with --enable-256-colors). -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] color schemes
cga2000 [EMAIL PROTECTED] wrote Tue, Jun 06, 2006: On Tue, Jun 06, 2006 at 05:33:05AM EDT, Jonas Fonseca wrote: Someone posted a patch for something like this, using the X libraries. It never was polished to a degree where it was worth merging, tho'. Interesting. Obviously 64k or 16M different colors doesn't make much difference. None that I can see anyway. I asked the xterm maintainer how the 256-color palette was chosen but he did not give me much detail. My personal concern was that the default xterm palette has very few blues. So if you try to harmonize the contents of an xterm with for instance the default background of Window Maker (I call it WindowMaker blue) you don't find an xterm color that is anywhere near. That's when I started taking an interest in these aspects. I know next to nothing about how good it works. It has been there since I joined the project. BTW, I have a little script that prints out all the nice colors: http://jonas.nitro.dk/tmp/256.sh ... Sorry, that I was not clear. I am talking about using JavaScript for browser scripting, not document scripting. Ok. I need to add JavaScript to the list of things I must look into. I'll check and see if there is an online tutorial available somewhere. I see, that Miciah might be putting some API docs of SMJS browser scripting together. Else .js files in contrib/smjs/ should be a help. JavaScript is a fairly simple language where many things works as expected. That is, using JavaScript to define hooks that can handle stuff from the goto URL dialog or preformat the HTML source. Yes, but I do need it for page rendering as well..? Especially those home pages that have some sort of horizontal menu bar that ends up a vertical list of links in my setup? That is usually controlled by CSS (another area where ELinks is falling behind). CSS let's you define that the tag p which is otherwise a block element (that should start on a new separate line, or paragraph if you will) is instead an inline element, where multiple p tags should appear on one line. Bad description, but I hope you get the point. I have some (mostly 256 related) at http://jonas.nitro.dk/screenshots/ I had looked at these a few weeks back. I took another look while writing this and now I see things I didn't see back then. I compared those sites that are still around such as OSTG, OSDN, slashdot.. and it's obvious I'm not quite there yet.. Well, with slashdot's new design (they went away from table-based design to CSS-powered design) it looks broken in my ELinks too. :( So many difference might be because of changes to the website and ELinks lack of CSS support. Not that it makes it easier for you. Screenshots sells, I agree. Although most apps are easily downloaded, configured and installed, the first appearance by which you make the decision whether to even bother with all that may often be a screenshot. And properly more so for something as seemingly out-dated as a text-mode browser. What would be nice is to have the web pages and the screenshots. Because even if the site still exists six months from now the contents.. or even the page design.. are going to be different. Thus if the new user has the html document and the .png .. when he wants to make sure his configuration is optimal he just needs to point elinks to the web document and compare with the screenshot. He might need to change his font to the one that was used when the the screenshot was taken but otherwise it should be pretty painless? Yes, this would guard against deceptive screenshots like the /. screenshot above. I don't know if it's realistic/possible but it might be a good idea to have elinks test pages .. you go to the test page and if you're set up right you should see this.. and a link to a screenshot. It's certainly a new approach to a more visual tutorial and might suit ELinks better than the poor introduction we have now. On the other hand I wonder if most users of text-mode browser is this visually oriented. But then again, Links2 has this calibration page to help you get the basics working and that is of course a great help. thanks, calibration is pretty much what I had in mind. And it should remain pretty simple. Just giving the new user the ability to verify that web pages are rendering correctly. As to a tutorial I don't really see the need for one. As long as a default configuration is provided the user can learn the basics of elinks by just using it. Same as any gui app. Call it tips and tricks or cheat sheet instead of tutorial. But yes, learning while using makes the learning experience feel less steep. One thing to put in these test pages would be the bottom table in test/css/styletags.html maybe with a 4ever appended ... ;) BTW, being new to ELinks, you should go over contrib/elinks.fortune, there's some good tips and tricks in it. practically everything that's in this file, I
Re: [elinks-users] color schemes
Miciah Dashiel Butler Masters [EMAIL PROTECTED] wrote Wed, Jun 07, 2006: If I may butt in... Certainly, I was wondering if I was the only developer reading/responding to the mailing list. ;) On Tue, Jun 06, 2006 at 08:33:48PM -0400, cga2000 wrote: On Tue, Jun 06, 2006 at 05:33:05AM EDT, Jonas Fonseca wrote: Someone posted a patch for something like this, using the X libraries. It never was polished to a degree where it was worth merging, tho'. Which patch was that? I can't find it in the archive and can't even remember when it was posted. I don't think I ever managed to get it working but remember that one of it flaws was that it broke communication between ELinks instances (interlinking). -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] color schemes
cga2000 [EMAIL PROTECTED] wrote Mon, Jun 05, 2006: On Mon, Jun 05, 2006 at 10:08:37AM EDT, Jonas Fonseca wrote: I'm not really convinced 256 colors was such a good idea to begin with. Naturally, it's orders of magnitude better than the 8/8 or even 8/16 on regular terms.. But why not go the whole hog and have a terminal that supports what the video card is capable of? 16-bit - 64k colors would probably have been a sensible choice and made life easier for everybody? Only one extra byte per cell.. Someone posted a patch for something like this, using the X libraries. It never was polished to a degree where it was worth merging, tho'. Ok, but if you feel like modding up your ELinks you should really try the Spidermonkey Javascript scripting backend created by Miciah. It's fairly easy to get working on a debian system Really? I was never able to get xterm, gnu/scren, and elinks.. to build from source - the debian way, I mean.. I was in a rush and it seemed I had to become a debian packaging expert before I could hope to get that to work.. So now I have a bunch of stuff that's all /.configure'd and compiled from source. Annoying. I can imagine. Only ever felt the need to compile school related stuff, elinks, git, (cogito), and xterm. The last one to get 256 colors, and I am still using the one I compiled on my previous debian system. This said, I'm very curious of the Javascript capabilities and I would really like to see the difference it makes. I do run into pages where I am stuck and I have to fire up mozilla and I suspect that not having Javascript enabled is part of my problem. Sorry, that I was not clear. I am talking about using JavaScript for browser scripting, not document scripting. That is, using JavaScript to define hooks that can handle stuff from the goto URL dialog or preformat the HTML source. Having a sane default configuration is very important. The many options is a weakness if you end up scaring new users away. If they feel they have to know of all the little details. That's pretty much what I meant. But as a new user I only noticed all the options when I took a look at the elinks.conf file. But then I was in so much of a rush that I did not really look at the o - Option Manager until recently.. As a new user you hopefully will get a long way by only using the terminal option dialog (under Setup in the main menu). Once your screen/terminal is configured most things should just work. Actually what I missed - again as a new user - was more samples of elinks in action.. I did find a few screenshots but I would have liked to see more. I have some (mostly 256 related) at http://jonas.nitro.dk/screenshots/ Now, the reason I say this is that for a new user and for something such as elinks that has the potential to display such a wide variety of documents.. I was never sure I was configured correctly and seeing what you or the other seasoned users of elinks are seeing. This nagging feeling that I may not be making the most of the product. For instance, until you told me this thing about setting my foreground and background to black I was seeing lots of pages revert to my xterm's black background. Now practically everything is rendered with a white/light background.. I don't know if this makes sense.. But my point is that being the only elinks user in my neighborhood .. as far as I know .. it was not likely one of the seasoned users I mentioned would have stopped by.. and said.. wait a minute.. this isn't right.. looked at my setup and fixed a couple of things. And conversely I could not walk up to someone's desk looked over his shoulder for a couple minutes and said.. wait a minute.. his elinks looks a lot better than mine.. iow, I was totally in the dark as to how an optimal setup of elinks should behave in real-life situations. May still be, for that matter.. Screenshots sells, I agree. Although most apps are easily downloaded, configured and installed, the first appearance by which you make the decision whether to even bother with all that may often be a screenshot. And properly more so for something as seemingly out-dated as a text-mode browser. Anyway, I have the same feeling about Mutt. I feel I am only using a very small subset of its capabilities and that some of my usage patterns might be a bit broken, but it works for me, I have become comfortable with it, and that is really all that matters. Especially, since I don't want to spent a lot of time configuring and reading docs. I don't know if it's realistic/possible but it might be a good idea to have elinks test pages .. you go to the test page and if you're set up right you should see this.. and a link to a screenshot. Confessions of the isolated noob.. not sure that's very useful. :-) It's certainly a new approach to a more visual tutorial and might suit ELinks better than the poor introduction we have now. On the other hand I wonder if most users
Re: [elinks-users] color schemes
cga2000 [EMAIL PROTECTED] wrote Sun, Jun 04, 2006: On Sun, Jun 04, 2006 at 12:42:14PM EDT, Jonas Fonseca wrote: cga2000 [EMAIL PROTECTED] wrote Sat, Jun 03, 2006: I'm somewhat sceptical about rgb distance calculators, though. There must be times when - with three dimensions.. there are two different choices.. or more.. and with human perception being what it is I am not convinced that even when there is just one mathematically correct choice it would be the natural choice that your average human would pick.. Well, zas and me discussed creating a more complex system for configuring the color model (see doc/color-model.txt) but it never got further than the above document and frankly I am not sure if it is worth it. I think the color picker does an OK job, but maybe my color blindness is just playing tricks with me. I can't spend as much time tinkering with elinks now as I would have liked so I'll probably live with it. Ok, but if you feel like modding up your ELinks you should really try the Spidermonkey Javascript scripting backend created by Miciah. It's fairly easy to get working on a debian system and it is currently one of the most developed scripting backends for ELinks. Examples are in contrib/smjs/. But why does the absence of the bgcolor attribute have different effects in elinks and graphical browsers such as mozilla? Because the default background color in mozilla is white, where as you said you have configured your default background color to be black or something. Yes, the many config options is one of ELinks' biggest asset (and weakness ;-). I really don't see it as a weakness at all. It's just that elinks - a bit like mutt - is really meant for people who know what they are doing. If like myself you know next to nothing about web stuff you should have the intelligence to accept it and live with some minor annoyances until you have the time to investigate further. Having a sane default configuration is very important. The many options is a weakness if you end up scaring new users away. If they feel they have to know of all the little details. As far as user satisfaction goes I would have given mozilla six out of ten.. At this point in time, I would give elinks 7.5.. and apart from changing a few keyboard actions I haven't really done anything to customize it. But it's nice to know that just about anything I may need to customize *is* customizable. Now you are just being nice. ;) I recall some of the options stem from developers not agreeing on a good default or rather, in a lot of cases it is easier to just add a new option than arguing whether or not the feature request makes sense. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] using telnet:// protocol
Jean-Yves Levesque [EMAIL PROTECTED] wrote Fri, Jun 02, 2006: Is it possible when we use the telnet protocol to launch in another tab or another xterm to have the window close on leaving telnet and not go back to a screen window ? In the option manager under: Protocols :: User protocols :: telnet, you should be able to edit what command ELinks runs when following a telnet link. So you should be able to atleast launch a new xterm. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] re-binding go forward and go back keys via the Keybinding Manager
cga2000 [EMAIL PROTECTED] wrote Wed, May 17, 2006: On Wed, May 17, 2006 at 10:08:14AM EDT, Jonas Fonseca wrote: Robert Michel [EMAIL PROTECTED] wrote Wed, May 17, 2006: Salve cga2000! - possibly a misunderstanding on my part regarding the functionality that this function provides: I assume they correspond to the back/forward buttons on other browsers Yes, they correspond to back/forward buttons in graphical browsers. Basically, the view state (what link you were on etc.) will be restored when moving back and forth in this manner. Thanks a ton. I have remapped them to h and l .. a lot more convenient for me than the arrow/cursor keys which are very difficult to reach on this laptop. In order to do that, I had to remap l - jump to link to u but I'm not sure what that does - sorry, I'm clueless about web stuff. I tried it in different contexts and it does nothing. What's the difference between jump to link and follow link? Jump to a link sounds clear enough but from where? When I first saw it I thought it just meant go to link target when a link is highlighted but that's apparently not the case. It takes an (undocumented) prefix number. So entering the sequence 5l sets the prefix to 5 (will be shown in the status bar) and then jumps to link number five. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Questions about rendering of some web pages and Numbered Links
Steve Holmes [EMAIL PROTECTED] wrote Sun, May 14, 2006: I would like to add to this thread another question concerning numbered links. I notice on some pages the link numbers don't always coincide with the arrow keys when navigating a page. I should probably explain further. Say a page is numbered in proper numeric order 1 through 30. But as you arrow down a page, the highlight will stop at numbered links out of sequence such as going from #4, next to #15, then on through the rest of the proper sequence and then wrap around to #5, #6,... thru #14, then back to #1 and do this all over again. The one site I know this for sure is my private banking website. I can't think of a public one I can give you for the example. I wonder if it might have to do with frame rendorring but don't recall if my banking site uses frames or not. Consider a long page which has three columns for example using tables. Due to how the HTML is structured all links in the first column will be encountered by the renderer before any in the two other columns. If the first column stretches over several pages the arrow keys will try to first traverse all links in the currently viewed page before starting to scroll. This may result in links being traversed out of order. I hope that answers you question. As another side effect to this problem, typing the link number will not take you to the desired link because of the navigation sequence being wrong so they are tied together some how. If link numbering seems to be broken, you can try to toggle the option: document.browse.links.use_tabindex I may sometimes have buggy affect on the allocation of link numbers. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Forwarding links?
Thomas Adam [EMAIL PROTECTED] wrote Mon, May 08, 2006: On Mon, May 08, 2006 at 10:14:04AM +0200, Jonas Fonseca wrote: Thomas Adam [EMAIL PROTECTED] wrote Sun, May 07, 2006: On Sun, May 07, 2006 at 01:55:57PM -0400, Seth Williamson wrote: After a lot of time messing around--I am pathetic at this--I discovered that I had to specify the path to the program. It installed in a place not in my $PATH statement. Took a while to find it. It was installed at /usr/X11R6/bin/xclip. Then your PATH is in grave error -- as /usr/X11R6/bin should always be in it. That's probably soemthing your distribution should fix. I remember reading somewhere that all X programs are migrating to /usr/bin in Debian (am running Ubuntu myself). That seems pointless, not to mention contradictory to the LSB (and FSH). Has there been some illogical and radical shift to want to make this happen? I'd find it odd that such a change would be distro-specific, given /usr/X11R6/bin's ubiquitous. The source is this: http://lists.debian.org/debian-devel-announce/2006/04/msg00010.html -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] enhanced -dump please ?
Sean [EMAIL PROTECTED] wrote Wed, Apr 05, 2006: Hi Hej, What about option: -dump-clean This option would make every effort to trash meta-garbage (including no-preferences no-numbering) and no links (to images or anything else) and suppress obvious meta-messages like 'your browser doesn't support script' and the like. Lynx already seems to be able to suppress the latter in dumped output. $ elinks --dump -no-numbering -no-references google.dk Should do most of it. You can set options so you don't have to specify them on the command line. I don't understand the rest and how can you know that there is not something meaningful in the noscript-tag or in img alt=text /? -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Control the BitTorrent transfer speed in eLinks v0.11.1?
Phillip Pi [EMAIL PROTECTED] wrote Thu, Mar 09, 2006: Hello! Hi Phillip, I like the BitTorrent (BT) feature in eLinks. Uh, so somebody is actually using it, that's good. :) However, I cannot find a way to control the file transfer speed. I have a slow Internet connection, and BT loves to use all my connection in eLinks. Is there a way to set limits? No unfortunately this is not supported and it sound non-trivial to add requiring a much more intelligent queuing of requests than is currently used. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Compile problem with 0.11.1
Christopher Moore [EMAIL PROTECTED] wrote Fri, Feb 03, 2006: On Fri, Feb 03, 2006 at 12:23:09AM +0100, Jonas Fonseca wrote: Christopher Moore [EMAIL PROTECTED] wrote Thu, Feb 02, 2006: Hello, Hi, I'm attempting to build the latest release. The ./configure ran fine but make gave the following error from autoheader: w1gm:/opt/elinks-0.11.1$ make cd ./. autoheader Can't locate object method path via package Autom4te::Request at /usr/bin/au tom4te line 81. autoheader: /usr/bin/autom4te failed with exit status: 1 make: *** [stamp-h.in] Error 1 I currently running 0.11.cvs built in May 2005. Could you try to remove the autom4te.cache directory in the root? Then to be safe rerun ./configure. That fixed the problem! Thanks Ok, the autom4te.cache directory is now removed when generating tarballs. Only the 0.12 snapshot is fixed due to the MD5 sums. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Howto make cursor visible in searches
cothrige [EMAIL PROTECTED] wrote Thu, Feb 02, 2006: When using elinks with 'use document-specified colors' set at 2 the cursor becomes invisible in most text fields, such as Google's. So editing something in one is impossible as you cannot even guess where in the field you are currently sitting. I have fiddled and toggled just about everything I can find in the options settings and have not found anything which will change the color of the cursor or at least render it visible, short of using a different setting for document-specified colors. Is there anyway to change this? No, ELinks currently doesn't support changing the cursor color to be more readable in a 'colorful' environment. Maybe you can workaround it by setting a more usable cursor color in a wrapper around ELinks. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Can't compile eLinks Debian (PowerMac; Kernel 2.4.22)
Phillip Pi [EMAIL PROTECTED] wrote Tue, Jan 31, 2006: [CC] src/main/timer.o In file included from ../.././src/main/timer.h:4, from timer.c:10: ../.././src/util/time.h:44: error: syntax error before 'n' make[2]: *** [timer.o] Error 1 make[2]: Leaving directory `/u00/home/ant/download/elinks-0.11.1/src/main' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/u00/home/ant/download/elinks-0.11.1/src' make: *** [all-recursive] Error 1 Try to insert that line: #include sys/types.h before #ifdef HAVE_SYS_TIME_H in file src/util/time.h line 3 I re-extracted the source, repatched, and modified the time.h file to add a line. I recompiled: $ ./configure [snip] checking for char... yes checking size of char... configure: error: cannot compute sizeof (char), 77 See `config.log' for more details. I didn't get very far. Heh. This obviously doesn't make sense. Does it do this every time? Anyway you don't have to unpack + patch + configure + make everytime. After configuring the first time, make'll do. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Can't compile eLinks Debian (PowerMac; Kernel 2.4.22)
are found. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Can't compile eLinks Debian (PowerMac; Kernel 2.4.22)
Phillip Pi [EMAIL PROTECTED] wrote Mon, Jan 30, 2006: On Tue, Jan 31, 2006 at 03:02:52AM +0100, Jonas Fonseca wrote: Phillip Pi [EMAIL PROTECTED] wrote Sun, Jan 29, 2006: Hello, I just downloaded and tried to compile eLinks v0.11.1 but make failed: Hello, thanks for reporting this. First a little general note that someone else will hopefully see. You _don't_ have to subscribe to post. I know this is a showstopper for some (not for you Phillip but for other). If you just send a message to the list it will go through our human filter and hopefully show up after a day or so depending on when messages from non-subscribers are checked. Ahh, I didn't know that. I always thought mailing lists required a subscription and valdiation. I've added a note about this on the community page. Good! I did not even recall seeing one. So, does the replies go back to my e-mail address? No, you have to request that you be CC'ed on replies. $ uname -a Linux dustball 2.4.22-pmac-benh-dm-evms_sorta-1 #4 Mon Oct 20 21:58:29 PDT 2003 ppc GNU/Linux Is this really Debian? I am using (the Debian-based) Ubuntu and do not have this problem. Yes, but on a PowerMac. That's the KEY thing. Not the latest or common platform as you can see. But it looks like you have off_t the same place I do. Could you dig out in what file the off_t type it is found on your system running something like this: find /usr/include/sys -name '*.h' | xargs grep off_t | grep typedef $ find /usr/include/sys -name '*.h' | xargs grep off_t grep typedef /usr/include/sys/types.h:typedef __loff_t loff_t; /usr/include/sys/types.h:typedef __off_t off_t; /usr/include/sys/types.h:typedef __off64_t off_t; /usr/include/sys/stat.h:typedef __off_t off_t; /usr/include/sys/stat.h:typedef __off64_t off_t; /usr/include/sys/mman.h:typedef __off_t off_t; /usr/include/sys/mman.h:typedef __off64_t off_t; I must say, I do not have any idea what is wrong, but if you have time to debug here are a few things to try out: - Try to run: ./configure --disable-largefile; make - Try to move the line #include elinks.h above the line #include ctype.h So the system headers cannot control what is included by elinks.h. - Along the same line as the above, try to add the lines: #include errno.h #include stdio.h #include stdlib.h between '#include config.h' and '#include ctype.h' in src/document/html/renderer.c. src/document/html/frames.c includes cache/cache.h as it's first ELinks header file and compiles ok. Could it be that one of the system header files it includes does some magic? maybe removing '/sys' and '| grep typedef' if no results are found. Did not try unless you want me to do so. :) That's not necessary. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Can't compile eLinks Debian (PowerMac; Kernel 2.4.22)
Phillip Pi [EMAIL PROTECTED] wrote Mon, Jan 30, 2006: On Tue, Jan 31, 2006 at 07:32:10AM +0100, Jonas Fonseca wrote: Phillip Pi [EMAIL PROTECTED] wrote Mon, Jan 30, 2006: Hello, I just downloaded and tried to compile eLinks v0.11.1 but make failed: I must say, I do not have any idea what is wrong, but if you have time to debug here are a few things to try out: - Try to run: ./configure --disable-largefile; make I extracted the source to start clean to compile... $ ./configure --disable-largefile; make [snip] checking for off_t... yes [snip] make[4]: Leaving directory `/u00/home/ant/download/elinks-0.11.1/src/document/html/parser' [CC] src/document/html/frames.o [CC] src/document/html/parser.o [CC] src/document/html/renderer.o In file included from ../../.././src/cache/cache.h:6, from renderer.c:13: ../../.././src/util/time.h:44: error: syntax error before 'n' In file included from renderer.c:13: [more of the same errors reported before] - Try to move the line #include elinks.h above the line #include ctype.h So the system headers cannot control what is included by elinks.h. - Along the same line as the above, try to add the lines: #include errno.h #include stdio.h #include stdlib.h between '#include config.h' and '#include ctype.h' in src/document/html/renderer.c. src/document/html/frames.c includes cache/cache.h as it's first ELinks header file and compiles ok. Could it be that one of the system header files it includes does some magic? Which file(s) are this/these in? And is this right after I extract the contents from the source? Sorry, I am sitting here buried in my own incomprehension. I want you to try and change the file src/document/html/renderer.c on a clean version. [ Clean as the file unpacked from tar.gz or tar.bz2 file. I assume that is what you mean by extracting the contents from the source. ] Correct. I didn't want to work on containmented files. :) Ok, please try the attached patch (which does what I wrote in the two last 'long shots'). First cd into the top-level elinks directory (in your case it looks like that is /u00/home/ant/download/elinks-0.11.1/). Then apply it by running the following command: patch -p1 /path/to/attached.patch -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Can't compile eLinks Debian (PowerMac; Kernel 2.4.22)
Phillip Pi [EMAIL PROTECTED] wrote Mon, Jan 30, 2006: Um, where's the attached file? :) Yes, I forgot to attached, but tried to sent a quick follow up ... anyway here it is again. -- Jonas Fonseca diff --git a/src/document/html/renderer.c b/src/document/html/renderer.c index 5422693..c8f4173 100644 --- a/src/document/html/renderer.c +++ b/src/document/html/renderer.c @@ -4,8 +4,13 @@ #include config.h #endif +#include elinks.h + #include ctype.h +#include errno.h #include stdarg.h +#include stdio.h +#include stdlib.h #include string.h #include elinks.h ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Can't compile eLinks Debian (PowerMac; Kernel 2.4.22)
And the famous last words: here is the patch! -- Jonas Fonseca diff --git a/src/document/html/renderer.c b/src/document/html/renderer.c index 5422693..c8f4173 100644 --- a/src/document/html/renderer.c +++ b/src/document/html/renderer.c @@ -4,8 +4,13 @@ #include config.h #endif +#include elinks.h + #include ctype.h +#include errno.h #include stdarg.h +#include stdio.h +#include stdlib.h #include string.h #include elinks.h ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] elinks and 64-bit SPARC builds
Jonas Fonseca [EMAIL PROTECTED] wrote Sat, Jan 14, 2006: Nelson H. F. Beebe [EMAIL PROTECTED] wrote Wed, Jan 11, 2006: If an elinks developer wants to examine the logs, I can make them available privately off-list. Sure I will have a look, although my past history of viewing your build logs is not so productive. I have only looked a little in the logs, it got boring to look at all the 'false positive' warnings about unsigned char vs. chars for stdlib calls. Anyway, at least two fixes seems to have made it in: be more careful when working on .deps/*.pp files which some systems don't create, and remove extra ';' from OBJECT_HEAD() macro. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
[elinks-users] [ANNOUNCE] ELinks-0.11.0
Hello and Happy New Year, The annual Christmas release got delayed and instead we ended up with a New Years release. Looking back at my notes for the roadmap of 0.11 only about half of it has made it into the tree. This includes the BitTorrent support that has been there since early summer and Ruby scripting. Missing parts are RSS support which actually isn't so far away, and inline images. Let's hope these things are taken care of before the next big release. I've decided to name the release `elated' because it is late but also because lately some great things has happened and I am very optimistic that ELinks is again moving in the right direction. Miciah has been paving the way for a new ECMAScript scripting interface which looks very promising already, and could in the future become an essential part of ELinks. The DOM implementation has also recieved some much deserved updates, among them are a test infrastructure to help find bugs faster and restructuring that hopefully will ease the upcoming work on writing a renderer that lives up to the Web standards of today. Finally, Witold has cooked up a patch that improves support for UTF-8, it looks very promising and will close one of the longer standing bugs. I have been a bit reluctant to release 0.11.0 because it has not gotten the 'spit and polish' you might expect of a release. Bug hunting season ended early this year, you might say. On the other hand, this code is already in use by several people and no really big problems has been found. The only real issue is with the document ECMAScript code that has been reported to crash regularly, but I regard it as still being experimental and more a taste of things to come. Anyway, the bottom line is that it might take a few updates before this new stable branch can truely live up to its name. The highlights of this particular release are listed below. See the NEWS file or the elinks-0.11rc0 announcement for a list of what's new in elinks-0.11 in general. Kalle Olavi Niemitalo: - Regenerate Makefile.config automatically if config.status changed. - Fix update-po and check-po when srcdir != builddir. - Use $@ to simplify a rule and try to nullify metacharacters. Laurent MONIN: - HTML table handling cleanups and optimizations. - French translation was updated. - Prevent successive calls to time(), since it doesn't have much impact. Miciah Dashiel Butler Masters: - Use lua_toboolean() for boolean options instead of lua_tonumber(), so `set_option(opt, not get_option(opt))' will always work to toggle a boolean option. - Use tput instead of hardcoded escape sequences in the colorized make system. - SpiderMonkey based ECMAScript scripting backend. - When checking the GCC version, use $CC instead of just gcc so that we get the right version if the user sets CC. - Fix problem in the plain text renderer, where the linked text was offset from the URI when there were backspaces earlier on the line. Petr Baudis: - Fix broken onClick on checkboxes etc. - Make the grafting script more usable. Russ Rowan: - Colorize Pasky's build system a bit. - Clean up 'make clean' and 'make install'. - bugmenot.com changed their format, so go back to the old method of handling it. Witold Filipczyk: - Fix problem with double decompression of local files Jonas Fonseca: - Add key parameter to the tracker announce URI, that allows the BitTorrent client to identify itself. Needed by some trackers. - Don't try configured MIME handlers for application/x-bittorrent when BitTorrent is compiled in. - In addition to highlighting HTML files also highlight RSS and XBEL files. - Add example to contrib/user.css about how to configure colors used for HTML highlighting. - Make URLs inside CDATA sections, comments and text accessible when using the HTML highlighter. - Fix cleanall to actually clean all. - In the various managers, place the cursor at the start of the listbox text and only highlight the actual text. - Add a Form fields entry to the link menu (if it is a form field), so that it is easier to move between field in the same form. The menu can be opened by configuring a keybinding for the link-form-menu action. - Grab GITs shell script-based test infrastructure and add tests for basic SGML parsing. May you time with ELinks be fruitful and bring you joy. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Italic color
Alex'a X Spirit [EMAIL PROTECTED] wrote Sat, Sep 10, 2005:
Hi, All!
Hello,
As I understand if we have `document.colors.use_document_colors = 0'
than any values from user.css are ignored. If this is true,
No, the option you mention and the user.css file is two totally
different things, however the option might affect how stuff in user.css
is used. If you set it to '0' like in your example then only the default
HTML style plus stuff in user.css will be used. Increasing the chances
that document specific colors won't 'get in the way'.
how can I
change the default color value for text marked in html by i tag?
You should set the CSS option for the default stylesheet to point at
your user.css. You should have this in ~/.elinks/elinks.conf
set document.css.stylesheet = user.css
Then put something like:
i { text: red; }
in the ~/.elinks/user.css file. Then restart ELinks.
For now it seems to be equal to cyan in 16-colors mode.
I don't know the exact codes, try to look at test/color.html. It would
actually be great to figure this out and have some note in contrib/ on
how to achieve the 16 different colors.
--
Jonas Fonseca
___
elinks-users mailing list
elinks-users@linuxfromscratch.org
http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Solaris Compile problem
Jacob Daniel [EMAIL PROTECTED] wrote Thu, Sep 08, 2005: Hello, Hi Jacob, I am not a C expert but I was trying to get elinks compiled on my Solaris box at work. I am getting a non-root directory compiled with some of the gnu utilities etc that I want to play with. I have gotten gettext-0.14.5 to compile. Howeverm it seems this package is making the compile of elinks break. Any ideas on what the problem could be? I have searched the archives but didn't see anything that would answer this question. I have an idea. The line: #include locale.h in src/intl/gettext/libgnuintl.h might include the system-wide gettext header. I don't have a fix for it. The non-optimal workaround is to pass --disable-nls to the configure script. But then the UI will only be available in English. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] garbled error messages
[ I keep CC'ing the mailing list. Hope that's ok ] Jon Shapcott [EMAIL PROTECTED] wrote Sat, May 07, 2005: On Fri, May 06, 2005 at 09:15:13PM +0200, Jonas Fonseca wrote: Jon Shapcott [EMAIL PROTECTED] wrote Fri, May 06, 2005: Thanks a lot for the help. I should return the favour, and maybe hack some on the unstable version. Both core.c and hooks.c get quite a lot shorter when you turn the cut'n'paste into functions, a drop some of the arcane passing of the global lua_State in and out of dialog events. Don't mind if you do. ;) It also means sorting out some of the stuff in the lua configuration files. So the whole job could take a while. I shall write some tests too. Then you should probably discuss your ideas with Miciah, since he has been taking care of the Lua code lately. Now to get those function references into the lua 5 api ... Huh? l_bind_key and a couple of the dialogs take references to functions, and use those references to push the appropriate function onto the top of the Lua stack (you know this, I'm sure). Lua 5 provides some compatability macros for the Lua 4 lua_ref(), lua_getref() and lua_unref() functions. These have become luaL_ref(), lua_rawgeti() and luaL_unref() respectively in Lua 5. It all looks straightforward, but I got distracted by broken dialogs before doing it. Those luaL_foo() functions are another reason why lauxlib.h is required. I've noticed this demand in the 0.11 CVS version of the Lua scripting module. core.h still uses the HAVE_LUAXLIB_H to provide the prototypes for lua_ref() and lua_unref(), which is best solved by using the new Lua reference interface. I'll download the CVS and start on those after I've tested it on the 0.10.5 version I'm using. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] garbled error messages
Miciah Dashiel Butler Masters [EMAIL PROTECTED] wrote Fri, May 06, 2005:
On Fri, May 06, 2005 at 01:50:24PM +0100, Jon Shapcott wrote:
[...]
Jon Shapcott [EMAIL PROTECTED] wrote Fri, May 06, 2005:
During my current hacking, I've had some trouble with the
alert_lua_error
function. Instead of displaying the desired message, it prints some
garbled
text instead. I've checked that I'm not feeding it broken messages by
printing them to stderr as well, and checking that output. Is this a
known
problem? If so, is there any known way of kicking it into proper
behaviour?
[...]
Sorry for the second response. I'm hacking elinks-0.10.5. I've tracked the
text for alert_lua_error through open_box and msg_box in src/bfu/msg_box.c,
and add_dlg_text in src/bfu/text.c. It doesn't get garbled in any of those
places, so I must be stamped on somewhere between there and being displayed.
As I was doing this, every now and then the leading part of the string would
be be mangled,, but the trailing part of the text would be shown normally.
Here is my guess: Something changes (maybe frees) the string after
passing it to alert_lua_error, which never does a strdup or similar.
This sounds very likely.
RCS file: /home/cvs/elinks/elinks/src/scripting/lua/core.c,v
retrieving revision 1.198
diff -u -u -r1.198 core.c
--- core.c 29 Apr 2005 07:40:52 - 1.198
+++ core.c 6 May 2005 17:01:03 -
@@ -717,9 +717,9 @@
alert_lua_error(unsigned char *msg)
{
if (errterm) {
- info_box(errterm, MSGBOX_NO_TEXT_INTL,
+ info_box(errterm, MSGBOX_NO_TEXT_INTL, MSGBOX_FREE_TEXT,
MSGBOX_NO_TEXT_INTL | MSGBOX_FREE_TEXT,
The two MSGBOX flags should be ORed together.
N_(Lua Error), ALIGN_LEFT,
- msg);
+ stracpy(msg));
return;
}
[...]
It looks like this sort of work is best done on the unstable version. Is the
unstable version updated daily on the download page?
Yes, when nothing is broken. [...]
Hmm, maybe the mail from failing crontabs should be forwarded! ;)
--
Jonas Fonseca
___
elinks-users mailing list
elinks-users@linuxfromscratch.org
http://linuxfromscratch.org/mailman/listinfo/elinks-users
[elinks-users] [ANNOUNCE] ELinks-0.10.5
Hello, This monthly update to the stable branch mostly brings you lots of bug fix and minor improvements. There is however also some changes which are a bit more experimental namely support for less aggressive caching. It is not perfect but it seems to do the right thing most of the time. Finally, the documentation is now available as one file in either plain text or HTML version. Following is a summary of the changes in ELinks 0.10.5. New features: - Most of the .txt files in the doc/ directory was lifted to the XML format defined in RFC 2629. It should make it easier to browse the documentation. Both .txt and .html version is available. Feature updates and improvements: - Try to add support for a less aggressive caching strategy. Disable document.cache.ignore_cache_control to try it. It will try to better honour info in the Expires, Pragma and Cache-Control in both the HTTP and the HTML headers. Inspired by Links2. - Introduce a workaround for document refreshing leading to never ending file download. It should do the right thing in most cases and the remaining ones the you will just have to reload to restart the refreshing. - Make the gopher code more robust for URIs without entity info. - Make it possible to have a specific features.conf file for each build tree and to change compile-time settings without modifying a file that is tracked by CVS. - Show link image info in the document dialog. - Improve error reporting for connections by showing which URI failed. Furthermore, make it clearer when an IP version specific URIs (http6://...) failed. - NNTP error messages are now translated. - Add --config-dump which dump a configuration file with default options to stdout. Helpfull for package maintainers when providing an example config file. - Don't sleep after config errors when --dump or --source was specified. Bugs fixed: - Fix form bug which caused form controls to be associated with the wrong form-element. - Only set a link's accesskey if the accesskey attribute's value is not an empty string. - Only show link title if it is actually there. - Fixes crash with refreshing downloads and mailcap asking disabled. - Fix the exit code when passing --config-* command line switches. - Skip non-link chars from attribute values. Fixes HTML highlighting of hrefs links with newlines etc in the value. - Fix the set_option() and get_option() functions available from Lua scripts to compile with Lua 4. - Fix configuration error on Solaris. - Fix dependency error for building util/scanner.o. Add to this various smaller fixes, cleanups and translation updates. The complete changelog is available in the package. Please, if a bug you reported in bugzilla (http://bugzilla.elinks.or.cz) has been fixed help to close it or verify whether the bug is infact fixed. As always you are more than welcome to join the insomniacs hanging out at the #elinks IRC channel on irc.freenode.net if you want to report issues or meet developers. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Newbie Needs Copy and Paste Help Please
Jim Tucker [EMAIL PROTECTED] wrote Sat, Apr 09, 2005: This may be an elementary question, but I have failed to find the answer in the elinks documentation. How can I copy and paste text within elinks? For example, if I am editing a bookmark URL, how do I select text and copy it so that I can later paste it into, say, a web page field? If I prefer not to use the mouse, is there a way to do this using only the keyboard? Thanks in advance for any help. http://elinks.or.cz/faq.html#cutnpaste :) -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] elinks crashes on website
Markus Haunschild [EMAIL PROTECTED] wrote Fri, Apr 08, 2005: Hi, elinks completely hangs, if I try to view the site www.wetter-oline.de. Do you mean http://www.wetter-online.de/? (missing 'n') What's going on there? Works for me in both ELinks version 0.10.4 and 0.11. What ELinks version are you using? -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] form submission problem
Rosenstrauch, David [EMAIL PROTECTED] wrote Mon, Apr 04, 2005: Hi. Anyone have any thoughts/suggestions on how to get around this problem I posted a few days back? It is a bit hard to figure out without knowing how to reproduce. What proxy is it? I think it would be best to maybe enter it in bugzilla.elinks.or.cz so it doesn't get lost. -- Jonas Fonseca ___ elinks-users mailing list elinks-users@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/elinks-users
Re: [elinks-users] Media links on mlb.com don't work in ELinks
Justin Ekis [EMAIL PROTECTED] wrote Sun, Mar 06, 2005:
Hi,
I have been very impressed with the JavaScript support in ELinks
recently. Being blind, I could not use a Graphical browser in Linux and
had to boot Windows to go to some pages using JavaScript. That happens
much less often now.
There's really only one site I badly want to use that doesn't fully
work in Elinks. That's www.mlb.com, the site for Major League Baseball.
They have some multimedia content such as being able to listen online to
the games being played and a few other things. These are javascript links
that just show an error when you hit enter. The live games you have to pay
fore but there are some links to video reports you can try out.
The links are similar to this one.
javascript:void(playMedia2({w:'/2005/open/teams05/det/video/05_st_preview_det_56.wmv',pid:'gen_video',cid:'mlb',v:'2'}));
Using current elinks cvs with error reporting on, this error
message is all that happens.
ReferenceError: playMedia2 is not defined
Is there anything I can do here to make this work? Or should I file a
bug about it?
Jikes! Almost a month already. Sorry for not responding sooner.
The www.mlb.com site uses a lot of javascript for their media player.
Much of it is not supported by ELinks.
Feel free to file it as an enhancement bug. It would be nice if you
could make the bug report a general bug for posting links to
sites/services that would be nice to have working.
--
Jonas Fonseca
___
elinks-users mailing list
elinks-users@linuxfromscratch.org
http://linuxfromscratch.org/mailman/listinfo/elinks-users
