Asumu Takikawa [16-10-23 18:12]:
> Hi Meino,
>
> On 2016-10-23 11:09:48 +0200, meino.cra...@gmx.de wrote:
> > It there any way to tell raco what kind
> > of doc processing is wanted and what don't?
>
> In addition to Daniel's answer, there is a temporary workaround you
Hi everyone,
I've been trying to get to know Racket's threads and particularly
filesystem-change-evt, and I've come to a point of confusion. I thought that a
filesystem-change-evt's synchronization result was supposed to be the event
itself, which it is most of the time, but in combination
Does anyone have any tips on how to turn on transparent request logging from
this question above?
2) How do I insert the transparent request logger in my dispatch-rules so that
request info will be shown on stdout?
Thanks!
Luke
--
You received this message because you are subscribed to the
Well, that was ridiculously easy.
Thanks!
Luke
--
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 an email
to racket-users+unsubscr...@googlegroups.com.
For more options,
I have been writing my CSS engine.
[sorry this reply might be a little off-topic here]
Long period before, someone in this mailing list asked if their are user
editable configuration file formats that can be used in real world
applications. `info.rkt` might be a choice but it is not designed for
> On Nov 13, 2016, at 06:42, David Storrs wrote:
>
> Thanks, all. Points well taken and I'll go back to writing lambda (x). I
> appreciate the pointer to those packages, though.
Minor point; you know that you can type λ directly in DrRacket using
cmd-backslash,
I have written one in my project
this task varies both from OS and filesystem.
https://github.com/digital-world/sakuyamon/blob/master/digitama/posix.c
It works on Solaris/Linux/MacOSX, and collects more sysinfo metrics than
just disk usage.
`ffi_prefab_ksysinfo` is the main struct, and
On Sun, Nov 13, 2016 at 6:48 AM, Ian Barland wrote:
> [...]
>
> Also, in this particular case, my chafing at the extra-characters was
> ameliorated by a tip from Eli Barzilay: drop the space after the "λ",
> e.g. `(λ(n) (+ n 1))`. It's still quite readable, and whittles
Thanks, all. Points well taken and I'll go back to writing lambda (x). I
appreciate the pointer to those packages, though.
On Sat, Nov 12, 2016 at 6:21 PM, Hendrik Boom
wrote:
> On Sat, Nov 12, 2016 at 01:22:42PM -0800, David Storrs wrote:
> > The 'thunk' procedure is
On Sat, Nov 12, 2016 at 01:22:42PM -0800, David Storrs wrote:
> The 'thunk' procedure is really useful and is sprinkled liberally through
> my code because it saves keystrokes / is clearer than (lambda () ...). I
> often find myself writing (lambda (x) ...) for something and wishing that
> there
> Personally however, I recommend against such a macro ...
> This is the kind of feature where everyone's got their own favorite
syntax for it.
>
+1 on this wisdom, for this particular construct. I used my own
personalized macro for several years, but finally decided it wasn't worth
the cost of
I'm assuming you intend to *use* the argument, in which case this is a trickier
macro to write than `thunk` because you have to make sure the macro respects
scope properly. If you wanted a function that accepts one argument and ignores
it, you can use `const`. Otherwise, you can implement a
12 matches
Mail list logo