Since there doesn’t appear to be an organized thing the night before this year, do any Racketeers going to RacketCon want to get dinner this evening?

@d_run: The most general solution would be to wrap the relevant code with (assert x real?). But depending on the specific code, you may be able to naturally get Real as a return type by tightening the arguments to whatever operations you’re using.

@lexi.lambda: Sure! Should be getting in in time for dinner. Currently waiting at O’Hare. :)

@lexi.lambda I think what @stamourv means to say is that he’s hoping the gods smile on him and that he leaves o’hare before tuesday :slightly_smiling_face:

Well, at least the food’s better here than near the office. :P

@stamourv that’s not saying very much

True.

Eh. I gotta admit that it’s pretty convenient to have direct flights everywhere.

@stamourv @samth I’m just as bad; I’m currently waiting in LAX :)

probably more comfortably than this exit row

at least it’s closer to Seattle than to St. Louis

Sorry, can’t hear you all over the sound of my two hour long flight from SFO :)

I’m having an off day… why does (date-display-format 'iso-8601) (date->string (seconds->date (current-seconds))) not print the time portion? Looking at the code, it seems like it should

I verified that (seconds->date (current-seconds)) still has the time portion of the data… but nothing

Pass #t as the optional second argument

Am I crazy, or does the --clock option to slideshow not work anymore?

derp. told you I was having an off day :slightly_smiling_face:

I’m trying to follow some of the posts on lisp.sh and they refer to a lot of calls that aren’t part of racket and it is getting tedious… but I want to stick to plain racket for now

thanks @mflatt

@lexi.lambda I’ve got plans tonight. sorry. Lunch maybe?

@apg I don’t know; --clock seems to work for me

@mflatt I’ve used it successfully in the past, and I thought it showed up on the preview window, but not happening now.

It shows up on the main window for me, and not on the preview window

oh. where in the main window?

(I didn’t remember the --clock flag at all, but apparently I added it 4 years ago. And I never use the preview window.)

In small text at the bottom left

oooh yes. I see it now. it’s an actual “clock”

maybe I’m simply crazy. I could have sworn I’ve used a sort of timer on the preview window.

it was red.

but, likely I’m misremembering.

(maybe I used google present, and then thought I should add a timer to the preview window. That’s probably the most likely scenario…)

anyway. thanks for sanity checking me @mflatt!

doco says that the default log level is 'error but I’m getting back '(#f #f) from (log-all-levels (current-logger))

oh… this may be a racket-mode-ism… plain repl in terminal says 'error

not that I can figure out why… seems like it should work

so… I never ate lunch today, so if anyone else is in Seattle and interested, I would be very interested in getting some food :)

@stamourv @samth @notjack ^ ?

@zenspider doc: https://github.com/greghendershott/racket-mode/blob/master/Reference.md#racket-logger-config

src: https://github.com/greghendershott/racket-mode/blob/master/racket-custom.el#L215-L245

@greg yeah. even after reducing * from fatal to error I’m still not seeing anything. Not sure why

Oh in a *Racket REPL* buffer? I get: > (log-all-levels (current-logger)) '(fatal #f debug deals warning http debug aws warning cm-accomplice info GC warning module-prefetch info optimizer error racket/contract info sequence-specialization)

(I might be misunderstanding the context what you’re trying to do, or expecting)

in my terminal:

> (log-all-levels (current-logger))
'(error #f)

in racket-mode-repl: bserver.rkt> (log-all-levels (current-logger)) '(#f #f) with: (* . error) in the config saved for current session (and I killed the repl after)

then when I call (log-error "blah") I get “blah” output in the terminal and not in racket-mode-repl

Oh OK. Hmm. I’ll take a look, but might not be able to until tmr

… maybe I can SHOW you tomorrow? Are you going to be here?

Alas no.

boo!

kk. well… hit me up here if you need any more infos. I’ve given up and yanked the error handler from the servlet for now

Will do.

thanks!

btw speaking of loggers earlier this week I got stuff set up for a Racket log-receiver to also put things into AWS CloudWatch Logs for a project I’m working on.

@zenspider I can repro the problem you describe when I (setq racket-logger-config ((* . error))) and restart the REPL: Then (log-all-levels (current-logger)) returns '(#f #f) as you report. Until I figure this out: As a work-around can you try going to the *Racket Logger* buffer — e.g. in a racket-mode buffer hit C-c C-l to open it — then press l and choose * and type error? IOW set racket-logger-config using the “UI”. (That works for me).

lexi.lambda: Just got to the hotel, and definetly interested in dinner in the short term.

@samth, @notjack: ^

@stamourv shall I meet you in the lobby?

5 minutes?

sounds great

(Oh, and FYI, I don’t have slack on my phone.)

you should get slack on your phone ;)

It’s intentional. :)

Vincent and I are at Thanh Vi on University Way if anyone is interested in joining us

@lexi.lambda we ( @dan @shu—hung and I) will attempt to join! (Just getting off the train)

@lexi.lambda @florence I only just got off the plane so unless your meal lasts three hours I don’t think I’ll make it :p

@notjack we just got back from dinner; I think the Chicago folks may be turning in, but I’d be down to meet up and chat for a while :)

@lexi.lambda I could say hi but I gotta head to bed early tonight

oh?

ya, didn’t get enough sleep and otherwise I’ll sleep through the morning and miss my own talk :p

hah, that’s a good reason. see ya tomorrow then.

kk!