>Paul F wrote:
>
>> agreed. doesn't seem like a release blocker to me.
>
>+1
Alright, so ... give it a week and if nothing crops up, we'll go for 1.7.1
final?
--Ken
--
Nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers
Paul F wrote:
> agreed. doesn't seem like a release blocker to me.
+1
David
--
Nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers
>> Ken, would it be a bad idea to call context_save() in
>> nmh_version_changed() if the Version context is replaced?
>
>That's probably the same as asking if no code fiddles with context in
>temporary ways knowing *it's* not going to save it later?
Generally when the context is going to be fiddle
ken wrote:
> >> > I don't remember that glitch in the past, but it is so minor that I
> >> > might
> >> > well have not noticed or ignored it.
> >> > [...]
> >>
> >> Oh, I guess that's because `scan -v' does not modify `context', e.g.:
> >
> >Right. Neither does -help.
> >
> >Ken, would
>> > I don't remember that glitch in the past, but it is so minor that I might
>> > well have not noticed or ignored it.
>> > [...]
>>
>> Oh, I guess that's because `scan -v' does not modify `context', e.g.:
>
>Right. Neither does -help.
>
>Ken, would it be a bad idea to call context_save() in nmh
David Levine writes:
>Norm wrote:
>
>> show no longer accepts -nopref
>
>mhshow accepts -[no]pref. show never did. Maybe it should?
>
>These arg parsing error messages are a bit odd:
>
>$ show -pref
>show: missing argument to -pref
>
>$ show -pref text/plain
>mhl: -pref unknown
mhshow -nopr 170
Ralph wrote:
> That's probably the same as asking if no code fiddles with context in
> temporary ways knowing *it's* not going to save it later?
In this case, no code fiddles with context within the same program
before nmh_version_changed() is called, because it's only called at the
beginning. C
Hi David,
> > Oh, I guess that's because `scan -v' does not modify `context',
> > e.g.:
>
> Right. Neither does -help.
>
> Ken, would it be a bad idea to call context_save() in
> nmh_version_changed() if the Version context is replaced?
That's probably the same as asking if no code fiddles with
Norm wrote:
> show no longer accepts -nopref
mhshow accepts -[no]pref. show never did. Maybe it should?
These arg parsing error messages are a bit odd:
$ show -pref
show: missing argument to -pref
$ show -pref text/plain
mhl: -pref unknown
David
--
Nmh-workers
https://list
Leonardo wrote:
> n...@dad.org writes:
> >
> > I don't remember that glitch in the past, but it is so minor that I might
> > well have not noticed or ignored it.
> > [...]
>
> Oh, I guess that's because `scan -v' does not modify `context', e.g.:
Right. Neither does -help.
Ken, would it be a bad
-- nmh-1.7.1-RC3 built 2018-02-22 18:01:22 + on boh
| % scan cur
|
| Welcome to nmh version 1.7.1-RC3
| [...]
| >N 3495 n...@dad.org Thu Feb 22 08:51 Re: [Nmh-workers] Third release
candidate for 1.7.1 is now available
| % scan -v
| scan -- nmh-1.7.1-RC3 built 2018-02-22 18:01:2
show no longer accepts -nopref
Norman Shapiro
--
Nmh-workers
https://lists.nongnu.org/mailman/listinfo/nmh-workers
>I compiled and am running 1.7.1.
>make test revealed no problems.
>
>Extremely minor glitch:
>
>I got the initial greeting twice, with the first and
>second commands I ran. The first was:
>
> scan -v
>
>The second was via a perl script and was something like:
>
> MAILDROP=something inc -n
Ken Hornstein writes:
I would greatly appreciate it if people would take this
>chance to test it out and report any feedback to the nmh-workers mailing
>list (nmh-workers@nongnu.org).
I compiled and am running 1.7.1.
make test revealed no problems.
Extremely minor glitch:
I got the initial gre
14 matches
Mail list logo
