Dear diary, on Sun, Feb 20, 2005 at 11:35:23PM CET, I got a letter,
where Andre Majorel <[EMAIL PROTECTED]> told me, that...
> On 2005-02-19 23:27 +0100, Petr Baudis wrote:
> > Hello,
> >
> > Dear diary, on Tue, Feb 15, 2005 at 08:47:01PM CET, I got a letter,
> > where Andre Majorel <[EMAIL PROTECTED]> told me, that...
> > > I'm having trouble getting mime.extension to work. I need to
> > > associate the ".HTM" extension (case-sensitive) to "text/html".
> > > What is the syntax ? Neither
> > >
> > > set mime.extension.HTM = "text/html"
> >
> > this one is right, and it works fine here. Could you send some details
> > about your ELinks version and environment? Are you setting the option
> > through the configuration file (do you restart ELinks properly? no
> > running instances left behind?), the exmode or the options manager?
>
> Hi Peter and Miciah. I'm running the Debian testing package
> (ELinks 0.9.2rc4 - Text WWW browser) on i386. The mime.extension
> directive is in ~/.elinks/elinks.conf.
>
> The latest Debian package, 0.9.3, behaves just like 0.9.2rc4.
>
> I've tried to compile 0.10.2 (./configure --without-ruby
> --without-lua --without-perl --without-guile --without-idn
> --without-gpm --without-x --disable-ipv6 --disable-cookies
> --disable-mouse && make) and run it from the build directory
> without installing it. It pops up a dialog titled "Go to URL".
> Typing at the keyboard or hitting ^C has no apparent effect except
> that it spontaneously exits at the 20th keystroke (I'm not making
> this up!). It's a moot point since, according to strace, it
> doesn't even look at elinks.conf anyway (just stats ~/.elinks).
>
> ...
> ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
> stat64("/home/me/.elinks", {st_mode=S_IFDIR|0700, st_size=4096, ...}) = 0
> socket(PF_UNIX, SOCK_STREAM, 0) = 5
> connect(5, {sa_family=AF_UNIX, path="/home/me/.elinks/socket0"}, 28) = 0
> close(3) = 0
> ...
Actually, I've hit this when doing some ELinks stuff on FC too. ELinks
0.9 and 0.10 is incompatible on this socket level (for the first time
from the Links times, AFAIK), but we fail miserably to handle it. We
should refuse to connect to an incompatible ELinks instance, and I'd
consider this a blocker for any further releases.
What do you think?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
98% of the time I am right. Why worry about the other 3%.
_______________________________________________
elinks-dev mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-dev
