« first day (2671 days earlier)      last day (26 days later) » 

12:02 AM
REFRESH!
[Minesweeper] 95 Games Played. 72 Bombs Used. 12972 Moves Performed. 5 New Users
 
@M.Doerner we already have the "hacktoberfest" topic on the repo...
AFAICT from the website that should be sufficient to opt RD in.
We really need to get on top of reviewing and merging though...
having that many open PRs suggests we don't actually merge contributions
 
 
4 hours later…
3:48 AM
 
 
9 hours later…
12:41 PM
0
Q: PRINTF LAMBDA function in Excel with ParamArray arguments - no VBA

GreedoThe TEXTJOIN function has a really nice interface: =TEXTJOIN(delimiter, ignore_empty, text1, [text2], …, [text252]) ... where text2 onwards are optional args, and each text argument can be a string (hardcoded or function return) or an array of strings (from a range or an array formula). This le...

 
 
2 hours later…
2:44 PM
0
Q: Outlook VBA to Replace Tokens from an email template

immobile2I'm creating a few macros that open specific Outlook templates an allow you to replace specific tokens before sending the email. It seems to work, but I'm admittedly doing full loops when I probably don't need to. So I'm just wondering if anyone sees a better way to approach this. As you can see ...

 
 
5 hours later…
7:35 PM
@Vogel612 Ah, I did not notice we already had the topic.
I currently feel in the mood to do something for RD again and do not have really pressing matters. So, I might actually review some stuff soon.
5
 
 
Got an exam on October 7th, so until then I won't be able to review PRs or code stuff ...
 
10:17 PM
> SLL mode failures are not really a bug. They are a bit complex to explain, but basically fixing this particular set of SLL failures ***will*** invariably introduce a new set.

As such it's preferrable to have an SLL failure set that occurs as little as possible and `Debug.Print` is one place where we decided to just "take" the SLL failures. As such this behaviour is [status-by-design]
> SLL mode failures are not really a bug. They are a bit complex to explain, but basically fixing this particular set of SLL failures ***will*** invariably introduce a new set.

As such it's preferrable to have an SLL failure set that occurs as little as possible and `Debug.Print` is one place where we decided to just "take" the SLL failures. As such this behaviour is [status-bydesign]
 
@Duga I actually think the expression in the output list is the problem here.
 
yea, probably, but I don't think that makes much of a difference for the bug in the end. Parsing does seem to work as intended, soo...
 
 
1 hour later…
11:47 PM
[rubberduck-vba/Rubberduck] 1422 stars vs. [decalage2/oletools] 1742 stars
 

« first day (2671 days earlier)      last day (26 days later) »