• Scanning for new messages

    From MysticOne@THERLMOD to All on Tue Jan 1 18:51:00 2008
    Hi all, hopefully a fairly quick question. I already ran this by Deuce in #synchronet, but he wasn't quite sure and suggested I ask DM. Rather than send a message directly to DM, I figured I might as well use the echo! Woooo!

    Anyway, I've written my own shell in JavaScript. For the option that users can select to scan for new messages, I have it executing:

    bbs.scan_subs(SCAN_NEW, false);

    This works great at scanning new messages, but, it fails to constrain the scan to only the areas that are enabled in the new message scan config. I looked at the the other copies of the JavaScript shells (lbshell.js and whatever the classic one is), and they're doing the same thing that I'm doing. While perusing the CVS repo, though, I noticed that lbshell.js had a change at one time that didn't use bbs.scan_subs(), but actually went through a list of the areas where the user had enabled new message scanning, and then scanned those areas individually for new messages. I'd like to avoid that if possible, but, thought I'd toss it to the echo and see what you all think.

    Thanks!

    -- MysticOne

    ---
    ■ Synchronet ■ :: The Realm of Dreams :: telnet://bbs.mysticone.com
  • From Digital Man to MysticOne on Wed Jan 2 10:55:48 2008
    Re: Scanning for new messages
    By: MysticOne to All on Tue Jan 01 2008 06:51 pm

    Hi all, hopefully a fairly quick question. I already ran this by Deuce in #synchronet, but he wasn't quite sure and suggested I ask DM. Rather than s a message directly to DM, I figured I might as well use the echo! Woooo!

    Anyway, I've written my own shell in JavaScript. For the option that users select to scan for new messages, I have it executing:

    bbs.scan_subs(SCAN_NEW, false);

    This works great at scanning new messages, but, it fails to constrain the sc to only the areas that are enabled in the new message scan config. I looked

    Are you absolutely positive? That's the correct JS method to use and it calls the same underlying code that is used in all the Baja shells and the other .js shells uses that method with no problem.

    digital man (xbox-live: digitlman)

    Snapple "Real Fact" #67:
    There are 18 different animal shapes in the Animal cracker zoo.
    Norco, CA WX: ---.-°F, --% humidity, NaN mph --- wind, --.-- inches rain/24hrs
  • From MysticOne@THERLMOD to Digital Man on Wed Jan 2 18:49:00 2008
    Re: Scanning for new messages
    By: Digital Man to MysticOne on Wed Jan 02 2008 10:55 am

    Are you absolutely positive? That's the correct JS method to use and it calls the same underlying code that is used in all the Baja shells and the other .js shells uses that method with no problem.

    Yes, if I run that it will scan all echoes, even the ones I have marked not to scan. The same thing happens for scanning for new messages when I log in, am prompted, and select "Yes". Keep in mind this is also on my SysOp account, just in case that makes a difference for some reason.

    -- MysticOne

    ---
    ■ Synchronet ■ :: The Realm of Dreams :: telnet://bbs.mysticone.com
  • From Digital Man to MysticOne on Thu Jan 3 20:38:39 2008
    Re: Scanning for new messages
    By: MysticOne to Digital Man on Wed Jan 02 2008 06:49 pm

    Re: Scanning for new messages
    By: Digital Man to MysticOne on Wed Jan 02 2008 10:55 am

    Are you absolutely positive? That's the correct JS method to use and it calls the same underlying code that is used in all the Baja shells and th other .js shells uses that method with no problem.

    Yes, if I run that it will scan all echoes, even the ones I have marked not scan. The same thing happens for scanning for new messages when I log in, a prompted, and select "Yes". Keep in mind this is also on my SysOp account, just in case that makes a difference for some reason.

    No, it makes no difference. I suspect you're confusing one type of scan configuration with another. If you logon using a stock command shell and perform a new-scan, do you have the same problem? Make sure you're configuring the *new* message scan (e.g. &N from the Synchronet classic command shell) and not the *your* message scan (&S) - these are 2 different stored message scan configurations for 2 different purposes.

    digital man (xbox-live: digitlman)

    Snapple "Real Fact" #175:
    In 1634, tulip bulbs were a form of currency in Holland.
    Norco, CA WX: ---.-°F, --% humidity, NaN mph --- wind, --.-- inches rain/24hrs
  • From MysticOne@THERLMOD to Digital Man on Fri Jan 4 09:12:00 2008
    Re: Scanning for new messages
    By: Digital Man to MysticOne on Thu Jan 03 2008 08:38 pm

    No, it makes no difference. I suspect you're confusing one type of scan configuration with another. If you logon using a stock command shell and perform a new-scan, do you have the same problem? Make sure you're configuring the *new* message scan (e.g. &N from the Synchronet classic command shell) and not the *your* message scan (&S) - these are 2 different stored message scan configurations for 2 different purposes.

    For the configuration option, I'm using:

    bbs.cfg_msg_scan(SCAN_CFG_NEW);

    For the scanning option, I'm using:

    bbs.scan_subs(SCAN_NEW, false);

    That's apparently what's being used in classic_shell.js as well. But, I haven't switched over to that shell yet to try it out and see if I get the same behavior.

    -- MysticOne

    ---
    ■ Synchronet ■ :: The Realm of Dreams :: telnet://bbs.mysticone.com
  • From Digital Man to MysticOne on Thu Jan 10 12:19:30 2008
    Re: Scanning for new messages
    By: MysticOne to Digital Man on Fri Jan 04 2008 09:12 am

    Re: Scanning for new messages
    By: Digital Man to MysticOne on Thu Jan 03 2008 08:38 pm

    No, it makes no difference. I suspect you're confusing one type of scan configuration with another. If you logon using a stock command shell and perform a new-scan, do you have the same problem? Make sure you're configuring the *new* message scan (e.g. &N from the Synchronet classic command shell) and not the *your* message scan (&S) - these are 2 differe stored message scan configurations for 2 different purposes.

    For the configuration option, I'm using:

    bbs.cfg_msg_scan(SCAN_CFG_NEW);

    For the scanning option, I'm using:

    bbs.scan_subs(SCAN_NEW, false);

    That's apparently what's being used in classic_shell.js as well. But, I haven't switched over to that shell yet to try it out and see if I get the s behavior.

    Those are the same methods used in lbshell.js, which doesn't not exhibit the problem you're describing.

    digital man (xbox-live: digitlman)

    Snapple "Real Fact" #1:
    A Goldfish's attention span is three seconds.
    Norco, CA WX: ---.-°F, --% humidity, NaN mph --- wind, --.-- inches rain/24hrs
  • From MysticOne@THERLMOD to Digital Man on Fri Jan 11 12:47:00 2008
    Re: Scanning for new messages
    By: Digital Man to MysticOne on Thu Jan 10 2008 12:19 pm

    Those are the same methods used in lbshell.js, which doesn't not exhibit
    the problem you're describing.

    Exactly! Since it doesn't not exhibit the problem, when will a fix be available? :)

    -- MysticOne

    ---
    ■ Synchronet ■ :: The Realm of Dreams :: telnet://bbs.mysticone.com
  • From Finnigann@BNB to Digital Man on Fri Jan 11 15:17:00 2008

    //- With quill in hand, Finnigann
    sends off a short note to MysticOne,
    about Scanning for new messages -\\

    Re: Scanning for new messages
    By: Digital Man to MysticOne on Thu Jan 10 2008 12:19 pm

    Those are the same methods used in lbshell.js, which doesn't not exhibit
    the problem you're describing.

    Exactly! Since it doesn't not exhibit the problem, when will a fix be available? :)

    <hand_waving_frantically>

    Oh Oh OH !!! Let me take this one...

    </hand_waving_frantically>


    If it's not exihibiting a problem... I'd say instantly. *I* could even
    fix something that is not exhibiting any problems.



    When you make the finding yourself - even if
    you're the last person on Earth to see the
    light - you'll never forget it. -- Carl Sagan


    ... Battery assembly...some required.
    --- MultiMail/Win32 v0.47
    ■ Synchronet ■ Bits-N-Bytes - bnb.dtdns.net / bnb.synchro.net
  • From MysticOne@THERLMOD to Finnigann on Sat Jan 12 02:15:00 2008
    Re: Scanning for new messages
    By: Finnigann to Digital Man on Fri Jan 11 2008 03:17 pm

    Exactly! Since it doesn't not exhibit the problem, when will a fix be available? :)

    <hand_waving_frantically>

    Oh Oh OH !!! Let me take this one...

    </hand_waving_frantically>

    If it's not exihibiting a problem... I'd say instantly. *I* could even
    fix something that is not exhibiting any problems.

    You missed the part where DM said that it does NOT NOT exhibit the problem. That's a double-negative, meaning it DOES exhibit the problem. :)

    -- MysticOne

    ---
    ■ Synchronet ■ :: The Realm of Dreams :: telnet://bbs.mysticone.com
  • From Digital Man to MysticOne on Sat Jan 12 10:41:12 2008
    Re: Scanning for new messages
    By: MysticOne to Finnigann on Sat Jan 12 2008 02:15 am

    Re: Scanning for new messages
    By: Finnigann to Digital Man on Fri Jan 11 2008 03:17 pm

    Exactly! Since it doesn't not exhibit the problem, when will a fix available? :)

    <hand_waving_frantically>

    Oh Oh OH !!! Let me take this one...

    </hand_waving_frantically>

    If it's not exihibiting a problem... I'd say instantly. *I* could even fix something that is not exhibiting any problems.

    You missed the part where DM said that it does NOT NOT exhibit the problem. That's a double-negative, meaning it DOES exhibit the problem. :)

    Yeah, of course I meant "does not exhibit the problem". Are you still having this problem with your command shell?

    digital man (xbox-live: digitlman)

    Snapple "Real Fact" #26:
    The Hawaiian alphabet only has 12 letters.
    Norco, CA WX: ---.-°F, --% humidity, NaN mph --- wind, --.-- inches rain/24hrs
  • From Finnigann@BNB to MysticOne on Sat Jan 12 14:27:00 2008

    //- With quill in hand, Finnigann
    sends off a short note to MysticOne,
    about Scanning for new messages -\\

    Re: Scanning for new messages
    By: Finnigann to Digital Man on Fri Jan 11 2008 03:17 pm

    Exactly! Since it doesn't not exhibit the problem, when will a fix be available? :)

    <hand_waving_frantically>

    Oh Oh OH !!! Let me take this one...

    </hand_waving_frantically>

    If it's not exihibiting a problem... I'd say instantly. *I* could even
    fix something that is not exhibiting any problems.

    You missed the part where DM said that it does NOT NOT exhibit the problem. That's a double-negative, meaning it DOES exhibit the problem.
    :)

    You could have quoted that part...



    When you make the finding yourself - even if
    you're the last person on Earth to see the
    light - you'll never forget it. -- Carl Sagan


    ... Laddie, don't you think you should...rephrase that?
    --- MultiMail/Win32 v0.47
    ■ Synchronet ■ Bits-N-Bytes - bnb.dtdns.net / bnb.synchro.net
  • From MysticOne@THERLMOD to Digital Man on Sat Jan 12 14:20:00 2008
    Re: Scanning for new messages
    By: Digital Man to MysticOne on Sat Jan 12 2008 10:41 am

    You missed the part where DM said that it does NOT NOT exhibit the problem. That's a double-negative, meaning it DOES exhibit the problem. :)

    Yeah, of course I meant "does not exhibit the problem". Are you still
    having this problem with your command shell?

    I know what you meant. I just thought it was funny. :) I've not messed with the lbshell.js again yet since I've been a bit busy, but will do it a bit later today and compare the results. I'll let you know after that and see if I can figure anything else out.

    -- MysticOne

    ---
    ■ Synchronet ■ :: The Realm of Dreams :: telnet://bbs.mysticone.com
  • From MysticOne@THERLMOD to Finnigann on Sat Jan 12 20:02:00 2008
    Re: Scanning for new messages
    By: Finnigann to MysticOne on Sat Jan 12 2008 02:27 pm

    You missed the part where DM said that it does NOT NOT exhibit the problem. That's a double-negative, meaning it DOES exhibit the
    problem. :)

    You could have quoted that part...

    It was in the original post, and my post even said "since it doesn't not exhibit the problem..." :)

    -- MysticOne

    ---
    ■ Synchronet ■ :: The Realm of Dreams :: telnet://bbs.mysticone.com