@samth The current placement of LICENSE files in the root of multi-package repos means that someone who just installs one of the packages (rather than cloning the whole repo) won’t get a copy of the license file and may not get any text about the license for that package on their system at all. Does that seem like a problem?

I usually post at least one new link to Racket Stories every day. Today I have run out of inspiration. Hope somebody else will post a link. https://racket-stories.com

Sigh. https://www.reddit.com/r/programming/comments/dsdssv/racket_is_an_acceptable_python/

(The sigh is for the comments on the story)

Python, sadly, is an unacceptable Racket.

I’ve gone back and forth about this. I think there should be a LICENSE file at the top-level of the repo; for example GitHub expects it to be there. On the other hand, you point to a real issue. On the third hand, duplicating seems unfortunate, but maybe the best option. And that’s where I’m at.

Maybe other people (like @mflatt or @jbclements) have thoughts on this, or maybe I should ask SFC.

Any Vim users? https://www.reddit.com/r/Racket/comments/dsim0v/emulating_drracket_functionality_in_shell_with/

I have no better idea than duplicating

I haven’t used it as a workflow with vim, but I think running xrepl (with ,en etc.) in a tmux pane gets you mostly there.

@soegaard2 that comment about DrRacket scrolling through :sob:

Yeah…

I picked that one out too…

Does anyone know if there is a way to render emoji characters in a pict ?

https://docs.racket-lang.org/emoji/index.html

Oh. That’s for a terminal.

But … it works in the examples too, so maybe …?

I do like that. Remembering/looking up codepoints (or wiring them into scripts) is annoying.

They’re just characters, so put them in a string and call text (or t, para, etc if you’re using slideshow). That just worked on the simple test I tried on Linux, but in general you might have to be careful to pick a font that has (or can find via font substitutions) a glyph for the characters you want.

The example I tried: (slide (t "Hello 🐈!")), with the text copy-pasted from the doc page soegaard2 linked to.

Ok, yeah I figured it may be a font issue.

It works in ITerm2 but not in DrRacket repl using the same font.

OS?

OSX

I have a problem where raco test -x -p ... silently returns with a zero exit code without running tests. The problem reproduces using exec from a pre-commit hook running under sh. I confirmed that the hook does run since other checks occur, but raco test -x -p ... will only run tests when I execute it manually in my terminal. Any ideas as to why this is happening?

Relevant (last line): https://github.com/zyrolasting/racket-vulkan/blob/master/pre-commit

(Removing exec does not fix the problem)

@deactivateduser60718 random suggestions:

1. Add set -euo pipefail to the top of the script (a.k.a. the “unofficial bash strict mode” http://redsymbol.net/articles/unofficial-bash-strict-mode/)
2. Use raco test --drdr -p ...
3. Get rid of all exec usages
4. Get rid of the script-wide redirection of all output to stderr, and instead localize stderr redirection to just the commands whose output you want redirected

Super helpful. Thanks much!

Trying now.

But my general approach to shell scripting is to treat it as a pile of magic where the only way to truly be safe is to not do it at all, and failing that to follow a bunch of possibly-unnecessary safety rituals I don’t fully understand

Funny you should say that: The changes had the effect of making git commit no-op entirely. My staged changes do not make it to the repository.

??? weird

The only thing I did extra was switch to /bin/bash

I usually use CI systems and pull requests to do the sort of thing you’re trying to do there. Would that approach work for you?

Absolutely. That’s on my list. The hook just helps keep me accountable during a refactor.

I got the script working after removing the set -euo pipefail. Couldn’t say why it had the effect it did.

as is usually the case with bash, all I can offer is a shrug emoji ¯_(ツ)_/¯

by the way for the CI setup, I made a Github Action for racket packages that builds and tests your package: https://github.com/jackfirth/racket-package-ci-action

You can see an example of how to use it in the template repository I use for my projects: https://github.com/jackfirth/racket-package-template

Fantastic, thank you!