headers
Peter S Galbraith | 1 Nov 2003 03:42
Favicon

Re: mparam

Raimund Kohl-Fuechsle <ray <at> nabuli.de> wrote:

> Hello,
> 
> as new as I am to this list am I new to mh-e (since now I am working
> with pine).  I have a machine running Debian woody, emacs 21.2.1. and,
> as far as Debian is right on it's website, have mh-e 6.1-1.

First off, feel free to install the mh-e package from unstable (sid).
It works on woody and it's the last stable MH-E release.

> I thought to give mh-e a try and started by reading the info,
> following it's suggestions:
> 
> `M-x load-library <RET> mh-e <RET>'
> `Loading mh-e...done'
> 
> `M-x mh-version <RET>'
> Unable to determine paths from mhparam command
> 
> Oops, what is this?  I didn't compile mh-e myself.  Instead I just
> used apt-get.  What do I have to do to make mh-e work?

You don't have to load it.  Simply try:

M-x mh-rmail

This assumes you don't mind using MH type mail directories instead of a
mail file.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Peter S Galbraith | 1 Nov 2003 04:04
Favicon

Re: mparam

Bill Wohler <wohler <at> newt.com> wrote:

> Raimund Kohl-Fuechsle <ray <at> nabuli.de> wrote:
> 
> > `M-x mh-version <RET>'
> > Unable to determine paths from mhparam command
> > 
> > Oops, what is this?  I didn't compile mh-e myself.  Instead I just
> > used apt-get.  What do I have to do to make mh-e work?
> 
> This is confusing. If you used apt-get to install the stable version of
> MH-E (6.1), then it should have installed nmh also and everything should
> have just worked.

That's what I'm thinking too.

> Hmmm, maybe we didn't have the autoloads right in that version for
> mh-version. Do you get the same error when you run "M-x mh-rmail"?

I'm not sure about mh-version.  I have not added any enter point
autoloads to the Debian package, relying on Emacs default autoloads for
MH-E instead.  It's possible that as we move stuff around to new files
these defaults won't work.  I'll need to include autoloads in the Debian
package to make sure we're okay.  Sorry about that; my fault.

> Maybe your Emacs environment isn't good enough although even MH-E 6.1
> should be finding mhparam just the same. What do you get if you run "M-x
> getenv RET PATH RET" within Emacs?
> 
> Maybe, somehow, nmh isn't installed. What do you get if you run "type
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bill Wohler | 1 Nov 2003 08:55
Picon
Picon
Gravatar

Re: mparam

Peter S Galbraith <p.galbraith <at> globetrotter.net> wrote:

> I'm not sure about mh-version.  I have not added any enter point
> autoloads to the Debian package, relying on Emacs default autoloads for
> MH-E instead.  It's possible that as we move stuff around to new files
> these defaults won't work.  I'll need to include autoloads in the Debian
> package to make sure we're okay.  Sorry about that; my fault.

Note to self: ensure autoloads for mh-version, in addition to the
others, is in Emacs source.

--

-- 
Bill Wohler <wohler <at> newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
Permalink | Reply | 0 comments |
headers
Raimund Kohl-Fuechsle | 1 Nov 2003 13:14
Picon

Re: mparam

On Fri, 31 Oct 2003, Peter S Galbraith wrote:

> > `M-x load-library <RET> mh-e <RET>'
> > `Loading mh-e...done'
> >
> > `M-x mh-version <RET>'
> > Unable to determine paths from mhparam command
> >
> > Oops, what is this?  I didn't compile mh-e myself.  Instead I just
> > used apt-get.  What do I have to do to make mh-e work?
>
> You don't have to load it.  Simply try:
>
> M-x mh-rmail

Same error message as above:

Unable to determine paths from mhparam command

Does your suggestion imply to first have mh-e installed from sid?

ray
Permalink | Reply | 1 comment |
headers
Raimund Kohl-Fuechsle | 1 Nov 2003 13:30
Picon

Re: mparam

On Fri, 31 Oct 2003, Peter S Galbraith wrote:

> Raimund Kohl-Fuechsle <ray <at> nabuli.de> wrote:
>
> > Hello,
> >
> > as new as I am to this list am I new to mh-e (since now I am working
> > with pine).  I have a machine running Debian woody, emacs 21.2.1. and,
> > as far as Debian is right on it's website, have mh-e 6.1-1.
>
> First off, feel free to install the mh-e package from unstable (sid).
> It works on woody and it's the last stable MH-E release.

That way I would have to use pinning ... since I am not running on a
network but a single user machine I wonder if it wouldn't be more
appropriate to install my own version in /home/ray?  Just a question.
It's what the info suggests.

ray
Permalink | Reply | 0 comments |
headers
Raimund Kohl-Fuechsle | 1 Nov 2003 13:43
Picon

Re: mparam

On Fri, 31 Oct 2003, Bill Wohler wrote:

> Raimund Kohl-Fuechsle <ray <at> nabuli.de> wrote:
>
> > `M-x mh-version <RET>'
> > Unable to determine paths from mhparam command
> >
> > Oops, what is this?  I didn't compile mh-e myself.  Instead I just
> > used apt-get.  What do I have to do to make mh-e work?
>
> Sagt "ich glaube" drei mal ;-).
>
> This is confusing. If you used apt-get to install the stable version of
> MH-E (6.1), then it should have installed nmh also and everything should
> have just worked.

I checked that:

ray <at> oldsmartoffice apt-get install nmh
ray <at> oldsmartoffice Sorry, nmh is already the newest version.

So it's installed.

ray

> Hmmm, maybe we didn't have the autoloads right in that version for
> mh-version. Do you get the same error when you run "M-x mh-rmail"?

Yep
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter S Galbraith | 1 Nov 2003 15:26
Favicon

Re: mparam

Raimund Kohl-Fuechsle <ray <at> nabuli.de> wrote:

> On Fri, 31 Oct 2003, Peter S Galbraith wrote:
> 
> > > `M-x load-library <RET> mh-e <RET>'
> > > `Loading mh-e...done'
> > >
> > > `M-x mh-version <RET>'
> > > Unable to determine paths from mhparam command
> > >
> > > Oops, what is this?  I didn't compile mh-e myself.  Instead I just
> > > used apt-get.  What do I have to do to make mh-e work?
> >
> > You don't have to load it.  Simply try:
> >
> > M-x mh-rmail
> 
> Same error message as above:
> 
> Unable to determine paths from mhparam command

Strange.  I've tried setting p a new user here and starting MH-E and it
setup MH for me and it worked.  Do you have an ~/.mh_profile file?

> Does your suggestion imply to first have mh-e installed from sid?

It should work on either.  But you might as well be using the package
from sid since it's more recent and has more stuff.  I'm pretty sure
that when we figure out what is going wrong it will fix either stable or
sid's version.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Raimund Kohl-Fuechsle | 1 Nov 2003 17:15
Picon

Re: mparam

On Sat, 1 Nov 2003, Peter S Galbraith wrote:

> Try with the full path to mhparam like so:
> 
> $ /usr/bin/mh/mhparam libdir
> /usr/lib/mh

Yepp!  That worked!

$ /usr/bin/mh/mhparam libdir
You already have the standard nmh directory '/home/ray/Mail".
Do you want to use it for nmh? y
[Using existing directory]
/usr/lib/mh

I then sent me a test mail with mh-e and it worked fine.

> There's no need for pinning.  Just download the package and install it
> with `dpkg -i':
> 
> $ wget http://ftp.debian.org/debian/pool/main/m/mh-e/mh-e_7.4.2-1_all.deb
> $ su
> # dpkg -i mh-e_7.4.2-1_all.deb
> 
> Please do that and we'll start from there.

Ok, I did that.  Works fine too.

Thank you very much!
(Continue reading)

Permalink | Reply | 502 comments |
headers
Peter S Galbraith | 1 Nov 2003 19:55
Favicon

Re: mparam

Raimund Kohl-Fuechsle <ray <at> nabuli.de> wrote:

> On Sat, 1 Nov 2003, Peter S Galbraith wrote:
> 
> 
> > Try with the full path to mhparam like so:
> > 
> > $ /usr/bin/mh/mhparam libdir
> > /usr/lib/mh
> 
> Yepp!  That worked!
> 
> $ /usr/bin/mh/mhparam libdir
> You already have the standard nmh directory '/home/ray/Mail".
> Do you want to use it for nmh? y
> [Using existing directory]
> /usr/lib/mh
> 
> I then sent me a test mail with mh-e and it worked fine.

Okay, so the problem was likely that nmh was expecting interactive
input.  Maybe the manual section on installation (and mh-e.el
commentary) should recommend using _one_ such command manually to make
sure nmh is correctly setup?

> > There's no need for pinning.  Just download the package and install it
> > with `dpkg -i':
> > 
> > $ wget http://ftp.debian.org/debian/pool/main/m/mh-e/mh-e_7.4.2-1_all.deb
> > $ su
(Continue reading)

Permalink | Reply | 502 comments |
headers
Bill Wohler | 1 Nov 2003 20:53
Picon
Picon
Gravatar

Re: mparam

Peter S Galbraith <p.galbraith <at> globetrotter.net> wrote:

> Bill, MH-E doesn't rely on the PATH to find stuff.

I know, but I was fishing for all possible leads that occurred to me,
however unlikely, in the one note.

> Raimund Kohl-Fuechsle <ray <at> nabuli.de> wrote:
> 
> > On Sat, 1 Nov 2003, Peter S Galbraith wrote:
> > 
> > 
> > > Try with the full path to mhparam like so:
> > > 
> > > $ /usr/bin/mh/mhparam libdir
> > > /usr/lib/mh
> > 
> > Yepp!  That worked!
> > 
> > $ /usr/bin/mh/mhparam libdir
> > You already have the standard nmh directory '/home/ray/Mail".
> > Do you want to use it for nmh? y
> > [Using existing directory]
> > /usr/lib/mh
> > 
> > I then sent me a test mail with mh-e and it worked fine.

Very cool.

> Okay, so the problem was likely that nmh was expecting interactive
(Continue reading)

Permalink | Reply | 5 comments |

Gmane