DDMsgReader: As a loadable module, now make use of user# parameter for reading personal email (for the sysop when deleting a user account)
1 unresolved thread
Compare changes
+ 56
− 21
@@ -91,11 +91,17 @@
@@ -195,8 +201,8 @@ var ansiterm = require("ansiterm_lib.js", 'expand_ctrl_a');
@@ -1089,10 +1095,18 @@ function DigDistMsgReader(pSubBoardCode, pScriptArgs)
@@ -1962,7 +1976,6 @@ function DigDistMsgReader_ClearSearchData()
@@ -2200,7 +2213,8 @@ function DigDistMsgReader_PopulateHdrsIfSearch_DispErrorIfNoMsgs(pCloseMsgbaseAn
@@ -9886,6 +9900,8 @@ function DigDistMsgReader_ReplyToMsg(pMsgHdr, pMsgText, pPrivate, pMsgIdx)
@@ -16613,13 +16629,15 @@ function canDoHighASCIIAndANSI()
@@ -16662,8 +16680,7 @@ function searchMsgbase(pSubCode, pSearchType, pSearchString, pListingPersonalEma
@@ -16671,7 +16688,7 @@ function searchMsgbase(pSubCode, pSearchType, pSearchString, pListingPersonalEma
@@ -16851,10 +16868,12 @@ function searchMsgbase(pSubCode, pSearchType, pSearchString, pListingPersonalEma
@@ -16862,13 +16881,17 @@ function msgIsToUserByNum(pMsgHdr)
@@ -16878,10 +16901,12 @@ function msgIsToUserByNum(pMsgHdr)
@@ -16889,6 +16914,8 @@ function msgIsFromUser(pMsgHdr)
@@ -16899,7 +16926,7 @@ function msgIsFromUser(pMsgHdr)
@@ -16907,7 +16934,15 @@ function msgIsFromUser(pMsgHdr)
@@ -17185,13 +17220,13 @@ function parseLoadableModuleArgs(argv)
Just curious: what does +(string) accomplish, differently than say parseInt()?
It's just a different style of ensuring it's a number, I suppose. I saw this style in an example years ago and have been doing it this way for a while. I don't know if there's any real advantage either way.
It doesn't ensure it's a number however:
Just as an FYI.
Yep. For this block of code, I did a regex test to make sure argv[1] is all digits, so that I'd be able to expect it could be cast to a number successfully.