I suggest moving /usr/bin/mh/ to /usr/lib/mh/bin/, and installing a script in
/usr/bin/mh that simply notifies the user to read the mh man page for
instructions.
Or, if we don't want to move /usr/bin/mh, one could always put the script in
/bin, but that might be just as ugly.
--
Dwayne C. Litzen
On Sat, 13 Jan 2001, Moshe Zadka wrote:
>On Fri, 12 Jan 2001 10:46:19 +, "Oliver Elphick" wrote:
>> Moshe Zadka wrote:
>> >OTOH, it bothers me that there are subdirectories under /usr/bin.
>> >E.g.:
>> >Try typing "mh" at the prompt for weird behaviour.
>>
>> [EMAIL PROTECTED] mh
>> b
> "Moshe" == Moshe Zadka <[EMAIL PROTECTED]> writes:
Moshe> U.that doesn't strike you as a weird error message?
Moshe> Especially since the shell thinks "mh" *is* a valid
Moshe> completion? I expect things that are valid completions to
Moshe> work.
I agree with this.
On Fri, 12 Jan 2001 10:46:19 +, "Oliver Elphick" wrote:
> Moshe Zadka wrote:
> >OTOH, it bothers me that there are subdirectories under /usr/bin.
> >E.g.:
> >Try typing "mh" at the prompt for weird behaviour.
>
> [EMAIL PROTECTED] mh
> bash: /usr/bin/mh: is a directory
> [EMAIL PROTECT
Ok. No need to get combative. If the admin saw the package, got
interested, and installed it, the message *to the admin* seems potentially
useful, since PATH is fundamental and mh requires an unusual change to
work at all. Since debian ships things like mh-e, which usefully wrap and
simplify nm
On Thu, Jan 11, 2001 at 01:29:04AM -0900, Britton wrote:
> I don't think it would be excessively interactive for nmh
> to somehow give a prompt notifying the user that the package requires
> something that debian packages normally never need in order to work
And how is it supposed to notify the us
On Jan 12, Peter S Galbraith <[EMAIL PROTECTED]> wrote:
>> What's weird about that?
>
>In tcsh:
>
>$ mh
>/usr/bin/mh: Permission denied.
So tcsh is broken. Big news.
--
ciao,
Marco
Peter S Galbraith <[EMAIL PROTECTED]> wrote:
>"Oliver Elphick" wrote:
>> [EMAIL PROTECTED] mh
>> bash: /usr/bin/mh: is a directory
>> [EMAIL PROTECTED]
>>
>> What's weird about that?
>
>In tcsh:
>
>$ mh
>/usr/bin/mh: Permission denied.
Non-intuitive at best ... sounds like somebody who uses tcsh
"Oliver Elphick" wrote:
> Moshe Zadka wrote:
> >OTOH, it bothers me that there are subdirectories under /usr/bin.
> >E.g.:
> >Try typing "mh" at the prompt for weird behaviour.
Me too.
> [EMAIL PROTECTED] mh
> bash: /usr/bin/mh: is a directory
> [EMAIL PROTECTED]
>
>
> What's weird a
Moshe Zadka wrote:
>OTOH, it bothers me that there are subdirectories under /usr/bin.
>E.g.:
>Try typing "mh" at the prompt for weird behaviour.
[EMAIL PROTECTED] mh
bash: /usr/bin/mh: is a directory
[EMAIL PROTECTED]
What's weird about that?
--
Oliver Elphick
On Wed, 10 Jan 2001 17:41:43 -0800, Joey Hess <[EMAIL PROTECTED]> wrote:
> I think others in this thread have provided suffucient arguments that
> it's reasonable to expect mh users to do what they are used to doing to
> get mh to work.
OTOH, it bothers me that there are subdirectories under /usr
e only just gotten nmh+mh-e working
correctly after seeing this thread. Must have glossed over the relevant
section of the man page that required something so strange as a PATH
modification :) I don't think it would be excessively interactive for nmh
to somehow give a prompt notifying the u
Jon Eisenstein wrote:
> If, according to policy, no package is allowed to modify
> environment variables, how should any package make the needed
> change? Furthermore, doesn't this violate the policy (in the same
> section) that no program can require an environment variable to be changed
> in orde
In message <[EMAIL PROTECTED]>, Jon Eisenstein wr
ites:
>I recently filed a bug report (80092) against the nmh package regarding
>the location of its program files. It installs files into /usr/bin/mh,
>which isn't in the path, making running the program difficult until the
>reason is found.
The nm
> > Jon Eisenstein <[EMAIL PROTECTED]> writes:
> > > I recently filed a bug report (80092) against the nmh package
> > > regarding the location of its program files. It installs files
> > > into /usr/bin/mh, which isn't in the path, making running the
> > > program difficult until the reason is fo
> Jon Eisenstein <[EMAIL PROTECTED]> writes:
> > I recently filed a bug report (80092) against the nmh package regarding
> > the location of its program files. It installs files into /usr/bin/mh,
> > which isn't in the path, making running the program difficult until the
> > reason is found.
MH is
Jon Eisenstein <[EMAIL PROTECTED]> writes:
> I recently filed a bug report (80092) against the nmh package regarding
> the location of its program files. It installs files into /usr/bin/mh,
> which isn't in the path, making running the program difficult until the
> reason is found.
>
> A suggestio
I recently filed a bug report (80092) against the nmh package regarding
the location of its program files. It installs files into /usr/bin/mh,
which isn't in the path, making running the program difficult until the
reason is found.
A suggestion was made by the maintainer to file a report against
b
18 matches
Mail list logo
