Hi David,
> > sort(1) has this functionality. It's -c for check. -check? Don't
> > see why we should deviate.
>
> sortm already has a -check, for a slightly different purpose. It was
> recently added, though, so maybe its meaning could be changed?
Ah, OK.
sortm always issues a warning f
On Mar 1, 2014, at 4:59 PM, Ralph Corderoy wrote:
>> Might be a little word-smithy, but I'd say "durable code" or "hidden
>> invocations" instead of "permanent code"
>
> "long-lasting"?
Portable.
signature.asc
Description: Message signed with OpenPGP using GPGMail
___
Hi,
Jerrad wrote:
> Might be a little word-smithy, but I'd say "durable code" or "hidden
> invocations" instead of "permanent code"
"long-lasting"?
Cheers, Ralph.
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/lis
Hi David,
> > The `storing message 42 to stdout' on stderr is annoying but I've
> > never looked into if it can easily be shut-up.
>
> I just committed a fix for mhstore to obey -noverbose.
Thanks!
> > It clearly should be off by default unless running on VMS.
>
> To not break anything that de
Ken Hornstein writes:
>>I chose '-recon" because "recon" is an English word, "-recon" is a make
>>switch and because no other sortm switch presently begins with "-r".
>>"-dryrun" would be much better, but it and "-datefield" have the same
>>first two letters.
>
>-recon is a make switch? Which ver
GNU make has --recon as a synonym for --just-print/--dry-run/-n
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
>I chose '-recon" because "recon" is an English word, "-recon" is a make
>switch and because no other sortm switch presently begins with "-r".
>"-dryrun" would be much better, but it and "-datefield" have the same
>first two letters.
-recon is a make switch? Which version of make is that?
Oh, wa
Ralph wrote:
> sort(1) has this functionality. It's -c for check. -check? Don't see
> why we should deviate.
sortm already has a -check, for a slightly different purpose.
It was recently added, though, so maybe its meaning could be
changed?
David
_
Ralph wrote:
> The `storing message 42 to stdout' on stderr is annoying but I've
> never looked into if it can easily be shut-up.
I just committed a fix for mhstore to obey -noverbose.
> It clearly should be off by default unless running on VMS.
To not break anything that depends on it, I left
Might be a little word-smithy, but I'd say "durable code"
or "hidden invocations" instead of "permanent code", but
otherwise sounds good! (also something to include in
hypothetical "extending nmh" docs ;-) ... maybe I'll give
that a crack sometime soon, although I don't grok roff.
Norm wrote:
> By the way, is there some admonition anywhere advising mh
> script writers to always use the full name of switches,
> lest later versions of nmh create an ambiguity? Maybe it's
> in Peek somewhere?
How about this addition to the nmh(7) man page? It
currently doesn't have an introdu
Hi Ken,
> Although I'm not sure I'm in love with the switch name; anyone
> else have a suggestion?
sort(1) has this functionality. It's -c for check. -check? Don't see
why we should deviate.
Cheers, Ralph.
___
Nmh-workers mailing list
Nmh-workers@n
Ken Hornstein writes:
>>I suggest two new switches to sortm: -recon and -norecon.
>>
>>The -recon switch (like the -n, --just-print, --dry-run, or --recon switch to
>>make) would cause sortm to not change the order of any messages. It would be
>>useful in connection with the -check and -verbose sw
> Again, that's an issue with '|'
That reminds me, I removed this from mhn.defaults recently:
mhshow-show-application/PostScript: %plpr -Pps
(or lp -dps if lpr wasn't found). While PostScript attachments
are probably close to extinct, I didn't see a need for any
potential security risk/embarr
>In not keeping with usual MH practice, don't provide
>-nodryrun? It just seems too confusing, and if you get it
>wrong there's no -undo.
Thre's a certain amount of logic to that, but because there's no undo
someone one might want to set a default of -dryrun to prevent errors,
and then explicitly
Paul F. wrote:
> ken wrote:
> > That seems pretty straightforward to implement (just don't call rename()
> > and the hook at the appropriate place). I can work on that in a little
> > while. Although I'm not sure I'm in love with the switch name; anyone
> > else have a suggestion?
>
> it's
ken wrote:
> >I suggest two new switches to sortm: -recon and -norecon.
> >
> >The -recon switch (like the -n, --just-print, --dry-run, or --recon switch
> >to
> >make) would cause sortm to not change the order of any messages. It would be
> >useful in connection with the -check and -verbose
>I suggest two new switches to sortm: -recon and -norecon.
>
>The -recon switch (like the -n, --just-print, --dry-run, or --recon switch to
>make) would cause sortm to not change the order of any messages. It would be
>useful in connection with the -check and -verbose switches.
That seems pretty s
Ken wrote:
> >If arbitrary means "what the user put into their profile",
> >yes, but we can't prevent that. Is there a way to get
> >mhstore to execute arbitrary code provided by the message?
>
> It does occur to me that there might be security concerns with using
> %a with '|', depending on she
>If arbitrary means "what the user put into their profile",
>yes, but we can't prevent that. Is there a way to get
>mhstore to execute arbitrary code provided by the message?
It does occur to me that there might be security concerns with using %a
with '|', depending on shell quoting, etc etc (%a
I suggest two new switches to sortm: -recon and -norecon.
The -recon switch (like the -n, --just-print, --dry-run, or --recon switch to
make) would cause sortm to not change the order of any messages. It would be
useful in connection with the -check and -verbose switches.
The default would be -no
David Levine writes:
>Norm wrote:
>
>> David Levine writes:
>> > Is clobbering the only [mstore] security concern with -auto?
>>
>> Wouldn't the '|' feature, combined with an mhstore-store- in
>> .mh_profile, alllow the execution of arbitrary code?
>
>If arbitrary means "what the user put into th
Ralph wrote:
> I'd say it's more a flawed design decision than a bug and should be
> described as the behaviour of -list in DESCRIPTION so every user is
> aware of it without having to read BUGS.
Done.
David
___
Nmh-workers mailing list
Nmh-workers@n
Norm wrote:
> David Levine writes:
> > Is clobbering the only [mstore] security concern with -auto?
>
> Wouldn't the '|' feature, combined with an mhstore-store- in
> .mh_profile, alllow the execution of arbitrary code?
If arbitrary means "what the user put into their profile",
yes, but we can'
Hi,
pick(1) describes the printing of 0 for -list when nothing matches in
the BUGS section.
http://git.savannah.gnu.org/cgit/nmh.git/tree/man/pick.man#n373
I'd say it's more a flawed design decision than a bug and should be
described as the behaviour of -list in DESCRIPTION so every user is
aware
David Levine writes:
> Is clobbering the only [mstore] security concern with -auto?
Wouldn't the '|' feature, combined with an mhstore-store- in
.mh_profile, alllow the execution of arbitrary code?
Norman Shapiro
___
Nmh-workers mailing list
Nmh-w
26 matches
Mail list logo
