Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

pinging SELMA

 [1/16] from: jeff:rebol at: 18-Sep-2000 7:47


Just FYI: If you think one of the lists is down you can always send SELMA a message with only the word "help" on the subject line. If she's running she'll let you know with a copy of the commands she knows: -------------------------------------------------- Here is some helpful information: Commands to REBOL SELMA are given on the subject line of your message. These commands are currently supported: help - get this information suggest - make a suggestion about the list selma-source - get the current source code to SELMA get msg N - send yourself message #N subscribe - add yourself to the list unsubscribe - remove yourself from the list No other commands are provided at this time. -SELMA ------------------------------------------------------- BTW: Anyone made any improvements to SELMA that they would like to share? -jeff

 [2/16] from: tbrownell:yaho:o at: 18-Sep-2000 9:04


Here's a thought.. some sort of thread control/filtering? Enjoy monitoring the conversation, but deleting upwards of 100 e-mails on busy days. T Brownell --- [jeff--rebol--net] wrote: BTW: Anyone made any improvements to SELMA that they would like to share? -jeff

 [3/16] from: civicminded4:y:ahoo at: 18-Sep-2000 10:15


--0-2027907669-969297354=:14359 Content-Type: text/plain; charset=us-ascii Yes, please, thread the comments! [tbrownell--yahoo--com] wrote: Here's a thought.. some sort of thread control/filtering? Enjoy monitoring the conversation, but deleting upwards of 100 e-mails on busy days. T Brownell --- [jeff--rebol--net] wrote: BTW: Anyone made any improvements to SELMA that they would like to share? -jeff __________________________________________________ Do You Yahoo!? Yahoo! Mail - Free email you can access from anywhere! http://mail.yahoo.com/ --0-2027907669-969297354=:14359 Content-Type: text/html; charset=us-ascii <P> <BR>Yes, please, thread the comments! <P>&nbsp; <B><I>[tbrownell--yahoo--com]</I></B> wrote: <BR> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Here's a thought.. some sort of thread<BR>control/filtering? Enjoy monitoring the conversation,<BR>but deleting upwards of 100 e-mails on busy days.<BR><BR>T Brownell<BR><BR><BR>--- [jeff--rebol--net] wrote:<BR><BR><BR>BTW: Anyone made any improvements to SELMA that<BR>they would<BR>like to share?<BR><BR>-jeff<BR><BR><BR><BR>__________________________________________________<BR>Do You Yahoo!?<BR>Yahoo! Mail - Free email you can access from anywhere!<BR>http://mail.yahoo.com/<BR></BLOCKQUOTE> --0-2027907669-969297354=:14359--

 [4/16] from: jeff:rebol at: 18-Sep-2000 14:01


Howdy, T: Nice idea, senior! :) Anyone actually hacked some improvements to the SELMA code? (You can obtain a copy of the selma source by sending the subject "selma-source" to SELMA. Now there's a mouthful!) -jeff

 [5/16] from: al:bri:xtra at: 19-Sep-2000 16:33


Jeff wrote:
> Anyone actually hacked some improvements to the SELMA code?
I did a while back, but I've since mislaid the code. Andrew Martin ICQ: 26227169 http://members.ncbi.com/AndrewMartin/ http://members.xoom.com/AndrewMartin/

 [6/16] from: bobr:dprc at: 19-Sep-2000 1:18


for threading, we could have Selma insert/replace a line in the body like PriorMsg: http://rebol.org/userlist/archive/373/164.html which points to the most recent (highest numbered) entry in the same thread. probably DONT want it to be in the X-headers though, many email browsers will make clickable an http:// sequence so long as it is in the body of the message. If Selma does this before broadcasting then both archive readers and email subscribers will get the benefit. At 04:33 PM 9/19/00 +1200, [Al--Bri--xtra--co--nz] wrote:
>Jeff wrote: > > Anyone actually hacked some improvements to the SELMA code?
<<quoted lines omitted: 4>>
>http://members.xoom.com/AndrewMartin/ >-><-
;# mailto: [bobr--dprc--net]

 [7/16] from: rryost:home at: 18-Sep-2000 23:49


In Outlook Express, I can achieve threading by simply clicking at the top of the Subject column to cause the InBox list to be sorted by Subject; this groups all messages with the same subject together, so it's easy to read through them in sequence. Afterwards, I click on the "Received" (date/time) column so the newest messages are at the bottom of the list. Russell [rryost--home--com]

 [8/16] from: bobr:dprc at: 19-Sep-2000 3:44


>At 11:49 PM 9/18/00 -0700, [rryost--home--com] wrote: >In Outlook Express, I can achieve threading by simply clicking at the top of
yes, so can eudora sort by subject (which I am currently using). The netscape browser also goes a long way to thread messages too. I am suggesting something which goes beyond just sorting by subject. You and I have the advantage that we never or rarely purge our email. If we did, we would find it difficult to go back on a thread by simply sorting by subject right after a [big] purge. A whole lot of people (those with hotmail accounts come to mind) aren't permitted the luxury of an infinite inbox. Daily pruning gets to be a chore. However, if we made it less of a requirement to have to keep a large history then we will invite more participation by people with smaller inboxes. [or those who have smaller inboxes because Rebol is not their only interest and they must share space] Suppose you were new to this list entirely, or perhaps, due to some other aberrant proggie, you lost or corrupted all your inboxes. Then what? How would a newbie be able (easily) to know where in the archives a thread started? do they even know of [the existence of ] the archives? Most subscribers lurk. lurking is polite and safe. lets make it so you don't have to come forward and ask "where is the start of the thread for the XYZ discussion?" an http reference like the one(s) at the bottom of this message gently announces that there is an archive and also how to get to it. lets make it so recovering a thread is quick so folks don't have to keep an infinite mailbox history. PriorMsg: http://rebol.org/userlist/archive/373/550.html ThreadHead: http://rebol.org/userlist/archive/370/103.html

 [9/16] from: brett:codeconscious at: 20-Sep-2000 0:34


Re threading, I think your suggestion is really good because it is both useful and simple. However I guess there will be a non-trivial amount of work to get the threading result/functionality from archival program into Selma. Nevertheless, the user archive would be a lot more useful. Brett.

 [10/16] from: jeff:rebol at: 19-Sep-2000 15:49


You really just need this function: get-head-next-by-XSELMA returns a block containing two URLS and/or none values. You really would want the list archiver to make available a simple REBOL data file of thread info for SELMA to grok on. -jeff

 [11/16] from: brian:hawley:bigfoot at: 19-Sep-2000 21:20


Jeff wrote:
> BTW: Anyone made any improvements to SELMA that they would > like to share? > > -jeff
Now that you mention it, here's a suggestion that I majáÜ–n February 1 to fix SELMA. There is a long-standing bug in the parse native in all versions of REBOL that affects the code in SELMA that parses subject lines. I've reported this bug to Feedback a few times. The parse bug still stands in all current (and experimental) versions that I have tested. Here's the last message that I sent on the subject: ------------------------------------------------------------ I found a bug in parse that affects the Repost function in the Selma source. I'll tell you more about the bug after I can do a little more analysis. There was also a potentially crash-causing call to to-integer for some subject lines, and "[REBOL]" used instead of list-tag. This will fix the Repost function: Repost: func [message /local here there re-cnt] [ re-cnt: 0 parse message/subject [ some [ to "re:" here: 3 skip [ "(" copy num digits ")" ( if num [re-cnt: re-cnt + to-integer trim num] ) | none (re-cnt: 1 + re-cnt) ] any " " there: (remove/part here there) :here ] ] parse message/subject [ here: any list-tag any " " there: (remove/part here there) :here ] insert tail trim message/subject " Re:" if re-cnt > 1 [ insert tail message/subject reduce ["(" re-cnt ")"] ] post message ] While you're at it, the parse rule in Process-Mail, [thru "re:" list-tag] can be changed to [thru "re:"] . This should work for the [ALLY] list as well. ------------------------------------------------------------ ...And here's some code that demonstrates the parse bug, that I also sent to Feedback: -----------------------------------------------------------[ REBOL [ Title: "Parse bug demonstration" Author: "Brian Hawley" Email: [brian--hawley--bigfoot--com] Date: 3-Feb-2000 ] ; First, with optional one "a" y-cnt: 0 parse a: "y a a y z" [ some [ to "y" here: "y" 0 1 "a" ; Note only one "a" optional here any " " there: (y-cnt: 1 + :y-cnt remove/part :here :there) :here ] ; This block should run twice, and does ] print [mold a y-cnt {(should be "a z" 2)}] ; Second, with optional more than one "a" y-cnt: 0 parse a: "y a a y z" [ some [ to "y" here: "y" 0 2 "a" ; Note more than one "a" optional here any " " there: (y-cnt: 1 + :y-cnt remove/part :here :there) :here ] ; This block should run twice, but doesn't ] print [mold a y-cnt {(should be "z" 2)}] comment { This error shows up when you use any form to express wanting multiple "a", including [0 n "a"], [some "a"] and [any "a"]. I haven't found any dependency on which letters you are searching for or how many, at least in this example. You know, if I had the source to parse I could figure this out for you, hint, hint :). } ]----------------------------------------------------------- I hope that this helps. Brian Hawley

 [12/16] from: jeff:rebol at: 20-Sep-2000 11:05


Howdy, Brian:
> There is a long-standing bug in the > parse native in all versions of REBOL that affects the code
<<quoted lines omitted: 10>>
> ] > print [mold a y-cnt {(should be "z" 2)}]
Hmmm, I don't believe this is a bug. The 0 2 "a" matches two instances of "a". Check out: http://www.rebol.com/users/parspace.html "The parse function ignores all intervening whitespace between patterns that it scans." Try these: parse "a a a a a b" [0 1 "a" m: (print m)] parse "a a a a a b" [0 2 "a" m: (print m)] parse "a a a a a b" [0 3 "a" m: (print m)] . . . [0 2 "a"] is like saying [0 1 "a" 0 1 "a"] -jeff

 [13/16] from: brian:hawley:bigfoot at: 20-Sep-2000 22:20


Jeff wrote:
> Howdy, Brian: > > There is a long-standing bug in the
<<quoted lines omitted: 13>>
> Hmmm, I don't believe this is a bug. The 0 2 "a" matches > two instances of "a". Check out:
Well, it took me a long time, but I figured out a bug in my test code that made it look like parse had a bug. It's not whitespace, but I still feel foolish now :( I formally apologize for the Feedback messages I sent. Reviewing the SELMA source I can't reproduce the bug I found before so it must have been fixed. Good! Another thing I haven't figured out is how Gabriele is able to consistently end up with a Re: after the list tag on all of his posts. It's not the messed-up thread sorting that results from this that gets me, it's that everything I can find in the SELMA source tells me it's impossible to do that! It's this behavior that got me searching the SELMA source in the first place. I hate it when I can't track down a bug :( Brian Hawley

 [14/16] from: jeff:rebol at: 21-Sep-2000 7:26


Howdy, Brian:
> > Hmmm, I don't believe this is a bug. The 0 2 "a" matches > > two instances of "a". Check out: > > Well, it took me a long time, but I figured out a bug in my > test code that made it look like parse had a bug. It's not > whitespace, but I still feel foolish now :(
Don't! Your efforts are not wasted. Someone may well have learned more about PARSE as a result of it. Reminds me of a story a pilot once told me about "flying the seatbelt". That's when the seatbelt gets caught in the door and when you're up in the air it starts rattling like mad and you start freaking out looking around for the problem and you end up "flying the seatbelt", instead of the plane, so you end up plowing into a mountain! :) Even pilots fly seatbelts occasionally. (How's that for a cheery anecdote?)
> I formally apologize for the Feedback messages I sent.
No apologies. That's what feedback's there for, but I think we could/should have spotted that earlier and saved you some frustration. :-) Hmm.. I suppose I should see if any bug reports were filled out on this one. (Yep) Well -- all's well that ends well.
> Reviewing the SELMA source I can't reproduce the bug I > found before so it must have been fixed. Good! > > Another thing I haven't figured out is how Gabriele is able > to consistently end up with a Re: after the list tag on all > of his posts.
Hey, Gabriele has magic SELMA confusing powers! -jeff

 [15/16] from: g:santilli:tiscalinet:it at: 21-Sep-2000 19:58


Hello [jeff--rebol--net]! On 21-Set-00, you wrote: j> Hey, Gabriele has magic SELMA confusing powers! Argh! Now you've spotted me! My magic powers were supposed to remain a secret... 8^P Regards, Gabriele. -- Gabriele Santilli <[giesse--writeme--com]> - Amigan - REBOL programmer Amiga Group Italia sez. L'Aquila -- http://www.amyresource.it/AGI/

 [16/16] from: g:santilli:tiscalinet:it at: 21-Sep-2000 19:43


Hello [brian--hawley--bigfoot--com]! On 21-Set-00, you wrote: b> Another thing I haven't figured out is how Gabriele is b> able to consistently end up with a Re: after the list b> tag on all of his posts. It's not the messed-up thread I'm afraid that's a "feature" of my mailer (YAM). It automatically strips the list tag, so SELMA receives: Subject: Re: pinging SELMA Re:(3) instead of the more common: Subject: Re: [REBOL] pinging SELMA Re:(3) Does this make sense now? Regards, Gabriele. -- Gabriele Santilli <[giesse--writeme--com]> - Amigan - REBOL programmer Amiga Group Italia sez. L'Aquila -- http://www.amyresource.it/AGI/

Notes
  • Quoted lines have been omitted from some messages.
    View the message alone to see the lines that have been omitted