On 20050226 18:34:00, Neon Absentius <[EMAIL PROTECTED]> wrote:
> On Thu, Feb 24, 2005 at 08:02:57PM +0000, Andrew Robinson wrote:
> > I have compiled and installed elinks 0.10.2 on a stock slackware 8.0 
> > installation running in standard 
> > console mode. All compile options were left at default.
> > 
> > While the program appears to load web pages and local text files, no 
> > content is displayed.
> > Toggling html/ plain from the view menu has no effect. I just get a blank 
> > (black) screen with a status bar at 
> > the bottom (reporting OK).
> > 
> > The filenames are recorded in History.
> > 
> > Attempting to save a page at this point results in an empty file on disk.
> > 
> > Has anyone any idea what the problem here might be please?
> > 
> > Precompiled lynx and links (currently uninstalled) packages work and render 
> > fine on the same machine.
> > 
> > Many thanks in advance for any help anyone can provide...
> 
> I have the same problem with elinks that come from the debian package.
> I just upgraded to elinks 0.10.2-2 from the unstable distribution and
> I have the same problems described by Andrew. Since he's having the 
> same problems in slack, I guess it's an elinks bug and not a Debian 
> one. 

Have you tried starting ELinks with the -no-connect option? This will
tell the new ELinks process not to connect to any existing processes
that might exist. ELinks will normally do this to share the cache,
global history, and so on between processes, but it can cause problems
when a newer version of ELinks connects to an older one.

Have you tried starting ELinks with the -no-home option? This will tell
ELinks that it has no home directory, which implies -no-connect (since
ELinks puts the pipe thru which processes communicate therein) and also
means that ELinks will not use your user configuration.

You might also combining -no-home with -config-file, which will ensure
that ELinks will not even read your system-wide configuration file
in /etc: -no-home -config-file some_dummy_name

If none of this solves the problem, please report what terminal
(emulator) you are using. Do dialogue boxes and menus work fine?

Thanks,

-- 
Miciah Masters <[EMAIL PROTECTED]> / <[EMAIL PROTECTED]>
_______________________________________________
elinks-users mailing list
[email protected]
http://linuxfromscratch.org/mailman/listinfo/elinks-users

Reply via email to