On Jun 7, 2021, at 9:05 AM, Michael Richardson wrote:
>
> Well, it's outgoing email, so it's all mine, so it's all in my time zone.
>
> On Jan. 1, I do:
> refile -src +outgoing all +outgoing/y2020
>
> well, I often forget Jan. so, "all" might be adjusted having run "scan"
>
> It would be
Michael Richardson wrote in
<31957.1623081930@localhost>:
|Ralph Corderoy wrote:
|>> outgoing/y2001 has 1287 messages (1-1287).
|>> outgoing/y2002 has 9335 messages (1-9335).
|>> outgoing/y2003 has 3909 messages (1-3909).
|
|> Out of interest, how did you pick what's in each year?
>> Or whatever, and that will be the current folder. You can also push
>> them on the folder stack. If you want them to show up when you do
>> "folders", that's harder.
>
>I don't know what the folder stack is.
Check out folder(1), specifically the -push, -pop, and -list arguments.
Ken Hornstein wrote:
>> I rather wish that NMH would take a "Path" to be...
>> well.. $PATH-like thing, such that I could move folders to an archive
>> machine, with NMH being aware that they are elsewhere.
> You're allowed to give an absolute path as a folder name. E.g., you
Ralph Corderoy wrote:
> Hi Michael
>> outgoing/y2001 has 1287 messages (1-1287).
>> outgoing/y2002 has 9335 messages (1-9335).
>> outgoing/y2003 has 3909 messages (1-3909).
> Out of interest, how did you pick what's in each year? Textually, with
> ‘2002’
>> The address parser code is used for a lot of things. The specific bug
>> report was about a draft message that contained Cyrillic characters.
>> We know what that character set was in THAT case, because it's a draft
>> message and we can derive the locale from the environment or the nmh
>>
>I rather wish that NMH would take a "Path" to be...
>well.. $PATH-like thing, such that I could move folders to an archive
>machine, with NMH being aware that they are elsewhere.
You're allowed to give an absolute path as a folder name. E.g., you could
do something like:
% scan
> I rather wish that NMH would take a "Path" to be... well.. $PATH-like
> thing, such that I could move folders to an archive machine, with NMH
> being aware that they are elsewhere. Ideally, it could be told that
> they are even RO, burnt on DVD or something like that.
Not quite what you want,
Ralph Corderoy writes:
> U+0081 as 0x81 is ‘is a character representable as an unsigned char’ for
> it's a character, U+0081, and unsigned char holds [0, 0x100) so it
> suffers no loss of representation as an unsigned char.
Sure, but then what you are feeding the function is *not* UTF8.
UTF8
Hi Ken,
> I am wondering if the simplest solution is to put in isascii() in
> front of those tests in that function. We only really care about
> those tests returning "true" for ASCII characters. Thoughts?
Just some tests, really, on Linux of different locales. One multibyte,
the other two
Hi Michael
> outgoing/y2001 has 1287 messages (1-1287).
> outgoing/y2002 has 9335 messages (1-9335).
> outgoing/y2003 has 3909 messages (1-3909).
Out of interest, how did you pick what's in each year? Textually, with
‘2002’ appearing in the Date field. Or as a year and if so was that
Just FYI, I have...
obiwan-[~](2.6.6) mcr 10003 %folders +outgoing
FOLDER # MESSAGES RANGE ; CUR (OTHERS)
outgoing+ has 2084 messages (1-2094); cur=2084; (others).
outgoing/pgphas 73 messages (1- 73); (others).
outgoing/y2001 has 1287 messages
Michael,
> Wow. Please share :-)
presumably, you didn't really mean it (thus the :-).
but, here they are anyway, in the format i keep them (a makefile puts
them in ~/Mail/mhl.headers).
cheers, Greg
; 1 these are all the fields i want to ignore when displaying a message.
; 2 automatically
Greg Minshall wrote:
> fwiw, i'm up to 732 ignored components. but, i'm happy adding them as
Wow. Please share :-)
> needed -- always the optimist that some day, some vital, otherwise
> un-acknowledged, header will show up in an e-mail i am viewing.
I feel the same way.
Hi Tom,
> Anyway, interpreting the input as a Unicode code point, for values
> above U+7F (or, if you stretch it unreasonably, U+FF) is very clearly
> outside the spec.
I'm not sure it is. An unwise design choice by 4.4BSD, yes.
U+0081 as 0x81 is ‘is a character representable as an unsigned
On Sun, 06 Jun 2021 10:22:38 -0700 Jon Steinhart sez:
> Ken Hornstein writes:
> > >Out of curiosity, then what is the value of "extras?" Was there
> > >a time it provided value, before header content exploded?
> >
> > Well, I don't mean to crap on anyone, Robert Elz in particular, but
> > you
16 matches
Mail list logo
