I made it many years ago and forgot what they hey it's for.

subject: {^[[]}

On Thu, 24 Mar 2022 22:47:59 -0500, andy@invalid.com wrote:

> I made it many years ago and forgot what they hey it's for.
>
> subject: {^[[]}

It matches subject lines with a [ as the first character

For example, these:

[Solved] How to filter crossposts to a bad group
[OT] Spinach on sale at the supermarket
[Update] Agent post direct write
[NFilter] Not working with Acme Usenet
[Ping Dodd Gee] Recommended hardware

but not these:

Re: [Solved] How to filter crossposts to a bad group
Re: [OT] Spinach on sale at the supermarket
Re: [Update] Agent post direct write
Re: [NFilter] Not working with Acme Usenet
Re: [Ping Dodd Gee] Recommended hardware

--
Kind regards
Ralph

Δος μοι πα στω και ταν γαν κινάσω
-- Ἀρχιμήδης (Archimedes)

On Fri, 25 Mar 2022 18:36:11 +1300, Ralph Fox <-rf-nz-@-.invalid>
wrote:

>On Thu, 24 Mar 2022 22:47:59 -0500, andy@invalid.com wrote:
>
>> I made it many years ago and forgot what they hey it's for.
>>
>> subject: {^[[]}
>
>
>It matches subject lines with a [ as the first character
>
>For example, these:
>
> [Solved] How to filter crossposts to a bad group
> [OT] Spinach on sale at the supermarket
> [Update] Agent post direct write
> [NFilter] Not working with Acme Usenet
> [Ping Dodd Gee] Recommended hardware
>
>but not these:
>
> Re: [Solved] How to filter crossposts to a bad group
> Re: [OT] Spinach on sale at the supermarket
> Re: [Update] Agent post direct write
> Re: [NFilter] Not working with Acme Usenet
> Re: [Ping Dodd Gee] Recommended hardware

Thanks!

I must have been having some problem with somebody many years back
whom I couldn't filter that easily and used this one. Totally forgot
about it.

Thanks again!

On Fri, 25 Mar 2022 18:36:11 +1300, Ralph Fox <-rf-nz-@-.invalid>
wrote:

>
>??? ??? ?? ??? ??? ??? ??? ??????
> -- ????????? (Archimedes)

This is not Greek to me nor to my Agent though I suppose it is
intended to be.
I've tried "Tools/Options/Languages" and setting the options to UTF,
Western and all of the other suggestions on Forté's webpages.

I know it is my fault but what am I missing?

Thanks,

J.

On Fri, 25 Mar 2022 00:36:28 -0600, andy@invalid.com wrote:

>On Fri, 25 Mar 2022 18:36:11 +1300, Ralph Fox <-rf-nz-@-.invalid>
>wrote:
>
>>On Thu, 24 Mar 2022 22:47:59 -0500, andy@invalid.com wrote:
>>
>>> I made it many years ago and forgot what they hey it's for.
>>>
>>> subject: {^[[]}
>>
>>
>>It matches subject lines with a [ as the first character
>>
>>For example, these:
>>
>> [Solved] How to filter crossposts to a bad group
>> [OT] Spinach on sale at the supermarket
>> [Update] Agent post direct write
>> [NFilter] Not working with Acme Usenet
>> [Ping Dodd Gee] Recommended hardware
>>
>>but not these:
>>
>> Re: [Solved] How to filter crossposts to a bad group
>> Re: [OT] Spinach on sale at the supermarket
>> Re: [Update] Agent post direct write
>> Re: [NFilter] Not working with Acme Usenet
>> Re: [Ping Dodd Gee] Recommended hardware
>
>Thanks!
>
>I must have been having some problem with somebody many years back
>whom I couldn't filter that easily and used this one. Totally forgot
>about it.
>
>Thanks again!

Me, I just kill-file the author but yours is very clever.

Thank you,
J.

Note: can we please clone hundreds of copies of Ralph to preserve for
posterity? He's a marvelous resource.

On Sat, 26 Mar 2022 12:17:57 +0000, John wrote:

> On Fri, 25 Mar 2022 18:36:11 +1300, Ralph Fox <-rf-nz-@-.invalid>
> wrote:
>
>>
>> Δος μοι πα στω και ταν γαν κινάσω
>> -- Ἀρχιμήδης (Archimedes)
>
>
> This is not Greek to me nor to my Agent though I suppose it is
> intended to be.
>
> I've tried "Tools/Options/Languages" and setting the options to UTF,
> Western and all of the other suggestions on Forté's webpages.
>
> what am I missing?
>
> Thanks,

1. You would need to configure _both_ "Tools >> Options >> Languages"
and "Tools >> Options >> Display >> Fonts".

2. You should create a new 'Language' at "Tools >> Options >> Languages".
Reconfiguring your existing language may mess up existing messages.
Reconfiguring your existing language will definitely trash
"extended ASCII" (8-bit) characters in your sent messages.

After that you should configure the fonts for this new language,
at "Tools >> Options >> Display >> Fonts". You _must_ select the
new language in the 'Fonts for the language' drop-down before
you configure the fonts for this new language.

3. The key options to configure are
* the 'Code Page' setting for the language, and
* the 'Script' setting for the two 'Body...' fonts for the
_same_ language.
These two must match, e.g. both should be 'Greek', both should
be 'Western', or both should be (say) 'Unicode UTF-8'.

3. See the help file at Help >> Index >> International fonts.
But also note that:
* (Step 1) For Greek, you will not need new fonts.
The basic fonts which have come with Windows for over 20 years,
support Greek and other European languages.
* (Step 2) Since Agent 4.0, the Forte-supplied .cod files are
already installed in the Agent working directory (the same
directory as agent.exe).

5. To show the characters correctly, select the message and use
"Edit >> Language" to select the new language.

6. If you configure the new language 'Greek' with code page and
font script as 'Greek', one or two of the characters will still
show as question marks.

The text uses the polytonic Greek system, which is the standard
today for writing Ancient Greek. The Windows font script setting
'Greek' supports the monotonic Greek system, which is the standard
today for writing modern Greek but is missing some of the accented
characters in polytonic Greek.
<https://en.wikipedia.org/wiki/Greek_diacritics>

7. To see all of the polytonic Greek characters, you could configure
the new language with code page and font script as 'Unicode UTF-8'.
This requires the Agent Unicode Extension (AgtEx) in message
<news:dmor1h9gtisfvq4tt663lbp2jou2f23gpk@4ax.com>.

--
Kind regards
Ralph

Ὁ βίος βραχύς, ἡ δὲ τέχνη μακρή
Vita brevis, ars longa
The lyf so short, the craft so long to lerne

On Sat, 26 Mar 2022 12:17:57 +0000, John <Man@the.keyboard> wrote:

>On Fri, 25 Mar 2022 18:36:11 +1300, Ralph Fox <-rf-nz-@-.invalid>
>wrote:
>
>>
>>??? ??? ?? ??? ??? ??? ??? ??????
>> -- ????????? (Archimedes)
>
>
> This is not Greek to me nor to my Agent though I suppose it is
>intended to be.
>
> I've tried "Tools/Options/Languages" and setting the options to UTF,
>Western and all of the other suggestions on Forté's webpages.
>
> I know it is my fault but what am I missing?
>
> Thanks,
>
> J.
>

Just an aside...

To filter out this junk...
From:??????????Jen??????????Dershmender????????????????????<root@127.0.0.1>

I use this: {[0]+}

Just saying...

(I don't understand it...but it works.)

On Sat, 26 Mar 2022 12:20:43 +0000, John <Man@the.keyboard> wrote:

>On Fri, 25 Mar 2022 00:36:28 -0600, andy@invalid.com wrote:
>
>>On Fri, 25 Mar 2022 18:36:11 +1300, Ralph Fox <-rf-nz-@-.invalid>
>>wrote:
>>
>>>On Thu, 24 Mar 2022 22:47:59 -0500, andy@invalid.com wrote:
>>>
>>>> I made it many years ago and forgot what they hey it's for.
>>>>
>>>> subject: {^[[]}
>>>
>>>
>>>It matches subject lines with a [ as the first character
>>>
>>>For example, these:
>>>
>>> [Solved] How to filter crossposts to a bad group
>>> [OT] Spinach on sale at the supermarket
>>> [Update] Agent post direct write
>>> [NFilter] Not working with Acme Usenet
>>> [Ping Dodd Gee] Recommended hardware
>>>
>>>but not these:
>>>
>>> Re: [Solved] How to filter crossposts to a bad group
>>> Re: [OT] Spinach on sale at the supermarket
>>> Re: [Update] Agent post direct write
>>> Re: [NFilter] Not working with Acme Usenet
>>> Re: [Ping Dodd Gee] Recommended hardware
>>
>>Thanks!
>>
>>I must have been having some problem with somebody many years back
>>whom I couldn't filter that easily and used this one. Totally forgot
>>about it.
>>
>>Thanks again!
>
> Me, I just kill-file the author but yours is very clever.
>
> Thank you,
> J.
>
>
>Note: can we please clone hundreds of copies of Ralph to preserve for
>posterity? He's a marvelous resource.

You keep talking like that and he's going to go on strike for a raise.
What do us dummies do than?

On Sat, 26 Mar 2022 16:29:33 -0600, andy@invalid.com wrote:

> Just an aside...
>
> To filter out this junk...
> From:??????????Jen??????????Dershmender????????????????????<root@127.0.0.1>
>
> I use this: {[0]+}
>
> Just saying...
>
> (I don't understand it...but it works.)

This
{[0]+}
will filter out any message which has a '0' (zero) character
anywhere in the Subject and/or From headers.

For example, it will also filter out these recent threads:

64-bit Windows 10
Agent 7.2 or 8.0 for Gmail after May 30, Usable?
Mess in alt.comp.os.windows-10
Agent 8.0 and UTF-8
default picture viewer doesn't get remembered in Agent 8.00

It could be simplified to this, and have exactly the same result:
{0}

--
Kind regards
Ralph
🦊

On Sun, 27 Mar 2022 11:08:31 +1300, Ralph Fox <-rf-nz-@-.invalid>
wrote:

>On Sat, 26 Mar 2022 16:29:33 -0600, andy@invalid.com wrote:
>
>> Just an aside...
>>
>> To filter out this junk...
>> From:??????????Jen??????????Dershmender????????????????????<root@127.0.0.1>
>>
>> I use this: {[0]+}
>>
>> Just saying...
>>
>> (I don't understand it...but it works.)
>
>
>This
> {[0]+}
>will filter out any message which has a '0' (zero) character
>anywhere in the Subject and/or From headers.
>
>For example, it will also filter out these recent threads:
>
> 64-bit Windows 10
> Agent 7.2 or 8.0 for Gmail after May 30, Usable?
> Mess in alt.comp.os.windows-10
> Agent 8.0 and UTF-8
> default picture viewer doesn't get remembered in Agent 8.00
>
>
>It could be simplified to this, and have exactly the same result:
> {0}

Jeesh!

>will filter out any message which has a '0' (zero) character
>anywhere in the Subject and/or From headers.
>

That could be a problem.

I gonna have to take a break now. You're giving me a headache with
all this deep thinking stuff. I think I'm stuck with a 16 bit brain
and you keep giving us this 32 - 64 bit headache posts. :o(

On Sun, 27 Mar 2022 09:35:07 +1300, Ralph Fox <-rf-nz-@-.invalid>
wrote:

>On Sat, 26 Mar 2022 12:17:57 +0000, John wrote:
>
>> On Fri, 25 Mar 2022 18:36:11 +1300, Ralph Fox <-rf-nz-@-.invalid>
>> wrote:
>>
>>>
>>> ??? ??? ?? ??? ??? ??? ??? ??????
>>> -- ????????? (Archimedes)
>>
>>
>> This is not Greek to me nor to my Agent though I suppose it is
>> intended to be.
>>
>> I've tried "Tools/Options/Languages" and setting the options to UTF,
>> Western and all of the other suggestions on Forté's webpages.
>>
>> what am I missing?
>>
>> Thanks,

Oh!

Well!

Thank you lots and lots, sir, you have done an extraordinary amount
of work to solve what I thought of as a small, passing little issue.

Your kindness is ever so much appreciated.

J.

>
>
> 1. You would need to configure _both_ "Tools >> Options >> Languages"
> and "Tools >> Options >> Display >> Fonts".
>
> 2. You should create a new 'Language' at "Tools >> Options >> Languages".
> Reconfiguring your existing language may mess up existing messages.
> Reconfiguring your existing language will definitely trash
> "extended ASCII" (8-bit) characters in your sent messages.
>
> After that you should configure the fonts for this new language,
> at "Tools >> Options >> Display >> Fonts". You _must_ select the
> new language in the 'Fonts for the language' drop-down before
> you configure the fonts for this new language.
>
> 3. The key options to configure are
> * the 'Code Page' setting for the language, and
> * the 'Script' setting for the two 'Body...' fonts for the
> _same_ language.
> These two must match, e.g. both should be 'Greek', both should
> be 'Western', or both should be (say) 'Unicode UTF-8'.
>
> 3. See the help file at Help >> Index >> International fonts.
> But also note that:
> * (Step 1) For Greek, you will not need new fonts.
> The basic fonts which have come with Windows for over 20 years,
> support Greek and other European languages.
> * (Step 2) Since Agent 4.0, the Forte-supplied .cod files are
> already installed in the Agent working directory (the same
> directory as agent.exe).
>
> 5. To show the characters correctly, select the message and use
> "Edit >> Language" to select the new language.
>
> 6. If you configure the new language 'Greek' with code page and
> font script as 'Greek', one or two of the characters will still
> show as question marks.
>
> The text uses the polytonic Greek system, which is the standard
> today for writing Ancient Greek. The Windows font script setting
> 'Greek' supports the monotonic Greek system, which is the standard
> today for writing modern Greek but is missing some of the accented
> characters in polytonic Greek.
> <https://en.wikipedia.org/wiki/Greek_diacritics>
>
> 7. To see all of the polytonic Greek characters, you could configure
> the new language with code page and font script as 'Unicode UTF-8'.
> This requires the Agent Unicode Extension (AgtEx) in message
> <news:dmor1h9gtisfvq4tt663lbp2jou2f23gpk@4ax.com>.

On Sat, 26 Mar 2022 16:29:33 -0600, andy@invalid.com wrote:

>On Sat, 26 Mar 2022 12:17:57 +0000, John <Man@the.keyboard> wrote:
>
>>On Fri, 25 Mar 2022 18:36:11 +1300, Ralph Fox <-rf-nz-@-.invalid>
>>wrote:
>>
>>>
>>>??? ??? ?? ??? ??? ??? ??? ??????
>>> -- ????????? (Archimedes)
>>
>>
>> This is not Greek to me nor to my Agent though I suppose it is
>>intended to be.
>>
>> I've tried "Tools/Options/Languages" and setting the options to UTF,
>>Western and all of the other suggestions on Forté's webpages.
>>
>> I know it is my fault but what am I missing?
>>
>> Thanks,
>>
>> J.
>>
>
>Just an aside...
>
>To filter out this junk...
>From:??????????Jen??????????Dershmender????????????????????<root@127.0.0.1>
>
>I use this: {[0]+}
>
>Just saying...
>
>(I don't understand it...but it works.)

OhhhhKayyy, but what else does it filter out?

I'm just curious. Thanks.

J.

On Sun, 27 Mar 2022 11:08:31 +1300, Ralph Fox <-rf-nz-@-.invalid>
wrote:

>On Sat, 26 Mar 2022 16:29:33 -0600, andy@invalid.com wrote:
>
>> Just an aside...
>>
>> To filter out this junk...
>> From:??????????Jen??????????Dershmender????????????????????<root@127.0.0.1>
>>
>> I use this: {[0]+}
>>
>> Just saying...
>>
>> (I don't understand it...but it works.)
>
>
>This
> {[0]+}
>will filter out any message which has a '0' (zero) character
>anywhere in the Subject and/or From headers.
>
>For example, it will also filter out these recent threads:
>
> 64-bit Windows 10
> Agent 7.2 or 8.0 for Gmail after May 30, Usable?
> Mess in alt.comp.os.windows-10
> Agent 8.0 and UTF-8
> default picture viewer doesn't get remembered in Agent 8.00
>
>
>It could be simplified to this, and have exactly the same result:
> {0}

Oh, sorry, I should have read this one before replying to the
previous.

I really must learn to do this more. :(

J.