[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: jde + emacs-w3m problem
James Cox writes:
> I don't think this is the same problem as Jose's, but...
> A few months ago, I was able to get jdee and w3m to play nicely. (I was
> able to browse a local javadoc from within emacs). I was using jdee
> 2.3.3beta2, emacs-w3m-1.3.4, and w3m 0.4.1.
> I had to modify jde-help.el. I think w3m was choking on the file url - I
> believe that this was a problem with w3m, not jdee, so I never submitted
> I changed the line in jde-file-to-url from:
> (format "file://localhost/%s"
> (format "file:///%s"
> everything seemed to work fine after that...
Allowing JDEE users to browse javadoc, the JDK API, and the JDEE User's Guide
from within Emacs sounds like a great idea. Perhaps I could build support
into the JDEE for using w3m for this purpose and include a Windows binary
of w3m in the JDEE distribution (and any other binaries users care
From your experience, what is necessary to configure Emacs to allow
> hope this helps someone,
> > -----Original Message-----
> > From: Jose A. Ortega Ruiz [mailto:firstname.lastname@example.org]
> > Sent: Thursday, October 02, 2003 10:01 AM
> > To: email@example.com; firstname.lastname@example.org
> > Subject: Re: jde + emacs-w3m problem
> > hi,
> > Paul Kinnucan <email@example.com> writes:
> > >
> > > Anyway, it looks like Jose's problem is either with the version
> > > of Emacs he is using or his setup.
> > >
> > hmmm... i don't think so: i can reproduce the problem after invoking
> > emacs with the -q flag (i.e., avoiding that it reads my local
> > configuration). btw, i've got the problem with some sites (e.g.
> > slashdot.net), while not with others, but i've been unable to discover
> > what is the offending item :(
> > thanks,
> > jao
> > --
> > The mind commands the body and the body obeys. The mind
> > commands itself and
> > finds resistance. -St. Augustine (354-430)
> This E-mail message is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. Any unauthorized review,
> use, disclosure or distribution is prohibited. If you are not the intended
> recipient, please contact the sender by reply E-mail, and destroy all copies
> of the original message.