Installing emacs-w3m (via el-get) on OS X?

Peter

unread,

Sep 17, 2012, 1:14:17 PM9/17/12

to

I'm trying to install w3m on my OS X system so I can read HTML
messages
with Wanderlust. I've managed to install el-get and, with that,
Wanderlust. However, when I try to install emacs-w3m, I get errors
that
autoconf is not found:

el-get is waiting for "/bin/bash" to complete
emacs-w3m failed to install: (error el-get: /bin/bash el-get could not
build emacs-w3m [/bin/bash -c autoconf]) [2 times]
el-get-installation-failed: el-get: /bin/bash el-get could not build
emacs-w3m [/bin/bash -c autoconf]

Anyone know how to get past this?

Thanks,
-pd

Peter Dyballa

unread,

Sep 17, 2012, 1:29:46 PM9/17/12

to Peter, help-gn...@gnu.org

Am 17.09.2012 um 19:14 schrieb Peter:

> Anyone know how to get past this?

Do you have autoconf in your PATH?

--
Greetings

Pete

Don't just do something, sit there.

Peter

unread,

Sep 17, 2012, 1:49:11 PM9/17/12

to

On Sep 17, 1:29 pm, Peter Dyballa <Peter_Dyba...@Web.DE> wrote:
> Am 17.09.2012 um 19:14 schrieb Peter:
>
> > Anyone know how to get past this?
>
> Do you have autoconf in your PATH?
>

Hi, Peter,

Yes, it's in /usr/local/bin, which is in PATH and also in the exec-
path variable.

Thanks,
-pd

Lewis Perin

unread,

Sep 17, 2012, 3:33:15 PM9/17/12

to

For reasons that will soon become obvious, I can’t answer your question
exactly as asked. But maybe I can help anyway.

I don’t use Wanderlust, but VM, which I do use, has certain similarities
to Wanderlust. I was pondering how to use emacs-w3m with VM not too
long ago, and it seemed kind of daunting. At that point, I noticed that
it was possible to use w3m directly with VM, basically redirecting w3m’s
stdout to VM’s stdin. I tried it, and I’m quite pleased with the
results. Maybe Wanderlust lets you do this, too?

/Lew
---
Lew Perin / pe...@acm.org
http://babelcarp.org

Ellen Taylor

unread,

Sep 17, 2012, 3:43:14 PM9/17/12

to

Is there a reason you can't just install it manually? Just grab the CVS
version (packaged version is severely OOD) and install it normally.

Peter

unread,

Sep 18, 2012, 10:05:49 AM9/18/12

to

I did manage to get this resolved. Although 'which autoconf' worked in a normal shell window, it did not work in emacs shell. I had set both the PATH environment variable and the exec-path variable in emacs, but somehow, emacs shell was using something else. Anyone know where that path comes from?

Anyway, I wound up creating a symlink to autoconf from /usr/sbin, which was on the emacs shell path, and that worked.

I could have installed it manually, I suppose, but el-get really makes it easy (usually) to install and manage different packages.

Thanks,
-pd

Peter Dyballa

unread,

Sep 18, 2012, 2:02:53 PM9/18/12

to Peter, help-gn...@gnu.org

Am 18.09.2012 um 16:05 schrieb Peter:

> I had set both the PATH environment variable and the exec-path variable in emacs, but somehow, emacs shell was using something else. Anyone know where that path comes from?

Two sources. First it inherits it from the environment which launches GNU Emacs – in Mac OS X this is not really something useful (because you should play with the apps and not work hard on the command line). Second it's the RC files that set up the shell environment. Depending on the kind of shell used they have different names (~/.login, ~/.(t)cshrc, ~/.profile, ~/.bashrc, …) and depending on the character of the shell (log-in or not) different sorts of files are used for its initialisation. Finally you have control with ~/.emacs_<shell's name>.

--
Greetings

Pete

If it does exist, it's out of date.
– Arnold's Second Law of Documentation

Peter Davis

unread,

Sep 19, 2012, 10:33:22 AM9/19/12

to Peter Dyballa, Peter, help-gn...@gnu.org

At Tue, 18 Sep 2012 20:02:53 +0200,

Peter Dyballa wrote:
>
>
> Am 18.09.2012 um 16:05 schrieb Peter:
>
> > I had set both the PATH environment variable and the exec-path variable in emacs, but somehow, emacs shell was using something else. Anyone know where that path comes from?
>
> Two sources. First it inherits it from the environment which launches
> GNU Emacs – in Mac OS X this is not really something useful (because
> you should play with the apps and not work hard on the command line).
> Second it's the RC files that set up the shell environment. Depending
> on the kind of shell used they have different names (~/.login,
> ~/.(t)cshrc, ~/.profile, ~/.bashrc, …) and depending on the character
> of the shell (log-in or not) different sorts of files are used for its
> initialisation. Finally you have control with ~/.emacs_<shell's name>.
>

Thanks very much, Peter. I will experiment with this. By the way, I use
command line emacs fairly often as I am frequently SSH'ed to my Mac at
home from my laptop.

I had not heard of the .emacs_<shell's name> initialization file
before. That would certainly be worth exploiting to managed
platform-specific handling, etc.

Thank you.

-pd