On 11/29/2021 6:45 PM, Nathaniel Griswold wrote:
It’s getting through my filters, neither rspamd or my local client can catch on
to it.
Is there a good simple filter?
Nate
Something has changed very recently because until this last week I
rarely saw it (even marked AS spam) ... maybe a
My spamassassin catches most of it, but also sometimes catches real list emails
because it has stopped trusting racket-users. Some combination of bayes and
txrep plugins are doing the heavy lifting, I think.
--
William J. Bowman
On Mon, Nov 29, 2021 at 05:45:37PM -0600, Nathaniel Griswold
It’s getting through my filters, neither rspamd or my local client can catch on
to it.
Is there a good simple filter?
Nate
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send
If you simply want the source location to be the macro call site, one
approach is finding where the source location currently is (in this case,
it’s the lambda inside make-keyword-procedure). Then, you simply need to
thread syntax/loc through macros to put the source location there.
Here’s an
Oops, just saw the discourse forum. Moved to:
https://racket.discourse.group/t/let-over-lambda-and-source-location-information/306
Christine Lemmer-Webber writes:
> Take the following code:
>
> #+BEGIN_SRC racket
> (require racket/match)
>
> (define-syntax-rule (methods* [(method-name
Take the following code:
#+BEGIN_SRC racket
(require racket/match)
(define-syntax-rule (methods* [(method-name method-args ...) body ...] ...
fallback)
(let ((method-name
(lambda (method-args ...)
body ...)) ...)
(define all-methods (list
6 matches
Mail list logo
