[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] odd 1.6 behavior
From: |
Paul Fox |
Subject: |
Re: [Nmh-workers] odd 1.6 behavior |
Date: |
Tue, 15 Jul 2014 08:53:43 -0400 |
i think merging mhshow and show would be a worthy 1.7 goal (if it's not
already on the list). for myself, i never use anything but mhshow, via
a wrapper that turns 'show', 'n', 'p', and a few others shortcuts into
their "mhshow" equivalents (e.g., "mhshow next"). but i assume there's
stuff done by mh's show that i've forgotten about, since i never use it.
paul
jon wrote:
> I think that this is pretty broken from a user perspective. Not the current
> change, but having both show and mhshow. I would just use mhshow for
> everything
> except that it doesn't do next and prev. And I can't use show for everything
> because it doesn't understand -part. Well, it sort of since "show -part 1"
> makes message number 1 the current message but that's not the result that I
> expected either. And "show -part 2" gives and error message and sets cur to
> 2.
> Seems like a bug.
>
> So while I have no time to pay attention to this or do any work at the
> moment,
> it seems like this is a step along the path to what I suggested years ago. I
> would be happier if mhshow got consumed by show. And happier still if the
> resultant program could have next and prev arguments to -part so that I could
> have aliases like nextp which would be "show -part next". Would eliminate
> the
> pain of having to read and type in part numbers.
>
=----------------------
paul fox, address@hidden (arlington, ma, where it's 70.2 degrees)