hello! I was hoping to go through the SICP text book and wanted to use racket for it as I hear there is good SICP tooling for it. But i’m on an old chromebook and basically have a command line only linux environment installed and use vim. is it still feasible to do this? can i still use the racket SICP (dialect?) if I’m only using vim and the command line?

@chasote yes you can! SICP does not care which editor or shell you use. You’re free to use whatever tool you want to write and run your code.

@chasote (not sure why I can’t tab complete you?)

@chasote you can do everything in the terminal EXCEPT the portion of chapter 2 that does functional graphics composition… that’s fine tho. You can still work through them and think about the problems even if you can’t visualize them

oh. deactivated. meh

@mflatt Have you ever had slideshow lock up (like its trying to cache in new slides), but never return? (Also it ignores Ctr+C events to kill it get ignored)?

I ask because I’m having that problem, and trying to diagnose a cause. At first I thought it was video, but it seems to happen on non-video slides as well.

(But only sporadically)

I don’t see that. I would attach to the process with gdb to get an idea of why it’s not responding to Ctl-C

Mmm…good idea. I’ll try that the next time it happens.

(Its very hard to catch when like 99% of the time it doesn’t freeze. :confused: )

@mflatt Okay, it happened again, and this is the output lldb gave: https://gist.github.com/LeifAndersen/64cc0971d737217502c0bbef093c32e6

Does that mean anything to you?

try bt

Ah, good call. It looks like its ffmpeg (or at least how I am using it):

  * frame #0: 0x00007fff90f1c5fe libsystem_c.dylib`__vfprintf + 507
    frame #1: 0x00007fff90f466c9 libsystem_c.dylib`__v2printf + 669
    frame #2: 0x00007fff90f2a915 libsystem_c.dylib`_vsnprintf + 596
    frame #3: 0x00007fff90f2a9ca libsystem_c.dylib`vsnprintf + 80
    frame #4: 0x000000010f75c319 libavutil.55.dylib`av_bprintf + 265

It looks like its the logger that’s causing the problem. Sigh. Thanks. :slightly_smiling_face: