Re: Testing the welcome message (was: nmh is vital to me)

[David Levine]

Ken wrote:

> [Ibsen:]
> >Indeed that is what is happening. It seems like you prefer it work
> >this way rather than showing the welcome message just once; in that
> >case, there is nothing to do on the situation I present.
>
> I think you misunderstand me; I'm not saying I PREFER it work that way,
> I just am explaining why it DOES work that way.  It probably should be
> fixed to behave better, but since right now I lack the time to do it
> myself I don't make a big deal over it.

That was fixed post-1.8, in commit 82b04d3149.

Also, I just added this to the welcome message:

This message will not be repeated until nmh is next updated.  To
permanently suppress this message, add "Welcome: disable" to your
profile (/home/levine/.mh_profile).

The actual absolute value of the profile will be shown.

David

Re: Testing the welcome message (was: nmh is vital to me)

[Ken Hornstein]

>Indeed that is what is happening. It seems like you prefer it work
>this way rather than showing the welcome message just once; in that
>case, there is nothing to do on the situation I present.

I think you misunderstand me; I'm not saying I PREFER it work that way,
I just am explaining why it DOES work that way.  It probably should be
fixed to behave better, but since right now I lack the time to do it
myself I don't make a big deal over it.

--Ken

Re: Testing the welcome message (was: nmh is vital to me)

[Ibsen S Ripsbusker]

Dear Ken,

Indeed that is what is happening. It seems like you prefer it work
this way rather than showing the welcome message just once; in that
case, there is nothing to do on the situation I present.

Please accept the expression of my distinguished sentiments.
Ibsen

Re: Testing the welcome message (was: nmh is vital to me)

[Ken Hornstein]

>Dear colleagues,
>I have for a long time had a different issue with the welcome message.
>Perhaps it is worthwhile to report. To produce this issue, set up a new
>MH directory, and run a failing command as the first command.
>[...]
>$ scan +this-is-not-a-folder  # Show the welcome message
>$ scan +this-is-not-a-folder  # Show the welcome message
>$ folders # Show the welcome message
>$ scan +this-is-not-a-folder  # Don't show the welcome message

So what's happening here is the information that you've seen the welcome
message is stored in the context file.  But depending on what happens the
context file is not always updated; for example, if the command errors
out.  So the successful run of "folders" updates the context file and
subsequent commands don't show the welcome message.

--Ken