hmm, that’s not ideal but certainly better than assembly code packaged up as a .txt
what is a .ss file?
is that for a generic Scheme impl?
Old abbreviation for “Scheme source”.
ah. Guile uses .sc
or is it .sm :thinking_face:
I think .scm is the most common?
is there a way to get hold of a PDF version of The Racket Guide?
#lang scribble/doc is some doc format I’ve never heard of before, so I’d struggle to compile that
I want to make a super simple PR that fixes drracket/check-syntax to give make-traversal a directory not a full pathname (i.e. /path/to not /path/to/file.rkt). That is a two-line change. At the same time, Emacs is highlighting a dozen more lines with gratuitous whitespace. I can toggle that off, or, I can M-x cleanup-whitespace. Should I: 1. Do one commit with only the substantive two lines changed, leaving the extra whitespace? 2. Do one commit changing it all? 3. Do two commits, one for the substantive change, the other for the whitespace?
I guess I’ll do 3, on the theory that whoever merges it can choose to use just one commit, squash them, or whatever.
@greg I think @robby prefers not to change only whitespace because it makes blame easier to track
(that is, 1)
Dang and I was so excited to have my commit message be: I have deleted
the whitespace
that was in
the source code
and which
you were probably
saving ....
giggles
I’m interested in trying to make a language that uses honu’s reader and parser, but nothing else. Does anyone know of useful examples or docs that might help speed up the process?
Didn’t read everything, but at least separate out the whitespace edits into their own commit if you want to do them. Only necessary on the code that I read the history a lot and if you guess wrong on what code that is, I’ll deal! :slightly_smiling_face:
Oh, looks like I may have committed too soon, @greg!