
@tim986 has joined the channel

:wave:lo all… long time no see

I’ve just got a pixelbook (woo), and I’m trying to run drracket in linux. It won’t start. Reporting $ drracket
xkbcommon: ERROR: Key "<CAPS>" added to modifier map for multiple modifiers; Using Mod3, ignoring Lock
(drracket:1722): Gdk-WARNING **: /build/gtk+3.0-NmdvYo/gtk+3.0-3.22.11/./gdk/x11/gdkwindow-x11.c:5573 drawable is not a native X11 window
Window->C: argument is not non-null `Window' pointer
argument: #f

Is this a known thing?

I googled and found https://github.com/racket/drracket/issues/87 and https://github.com/racket/racket/issues/1547

you know, I’m so out of the loop… I didn’t even notice that v6.7 is neolithic.

(and I should have mentioned the racket version)

@tim986 Probably not. I don’t think too many have ChromeBooks.

I have a ChromeBook Pixel 1 and 2, where I used Crouton to run Linux apps. The new Crostini thing sounds way simpler. Them using Wayland instead of X11 seems a little too bleeding edge, means some apps will have problems, but idk. I can’t try b/c Google not supporting that on their own older hardware. Probably I’ll wipe ChromeOS and install Ubuntu or whatever directly.

I’ve built a version from source. It works fine for me now!

You can M-x racket-check-syntax-mode
and racket-check-syntax-mode-rename
. But:

That only works within one source file at a time.

It is a little bit “buried” in the UX.

Also when I try it now on my local build of racket-mode I see that check-syntax-mode is confused about the position of usages, so, rename won’t work. This has worked “forever” so I’ll figure out what broke when, and fix it.

Oh. I think it’s simply because the buffer had changed and wasn’t saved (I just used some /tmp/foo.rkt
buffer I’d had open for something else). The backend check-syntax uses the file. Maybe the bug to fix is a missing save-if-changed
….

Yeah. TL;DR: I’ll push a commit to have racket-check-syntax-mode
call save-if-changed
automatically. Meanwhile, just be sure to save the buffer before running M-x racket-check-syntax-mode
.

Apropos, are you satisfied with your ChromeBooks?

I am trying to open a specific locally-installed documentation page programmatically (from a DrRacket toolbar button). On my machine (send-main-page #:sub "bib-db-grammar/index.html")
works great, but for my collaborators it tries to send them to <http://docs.racket-lang.org\|docs.racket-lang.org>
, where this document doesn’t exist. Is there something obvious I’m doing wrong? Is send-main-page
the right place to start? https://docs.racket-lang.org/help/index.html#(def._((lib._help%2Fsearch..rkt)._send-main-page)) (This is for a #lang
for my collaborators to just give them some editor support for a temporary data file format we’re working with internally.)

Do you have “bib-db-grammer” installed in installation scope or use scope? How about your collaborators?

I have it in installation scope, but I think my collaborators have it in user scope: I use (default-pkg-scope)
, and I doubt they’d have changed theirs.

I think that’s pronbably the reason, since user-scope documentation goes in the package directory instead of a centralized directory. If you can make find-help/lib
work, that’s probably a better way to go. Or the more primitive functions like xref-tag->path+anchor
, although it always takes me a while to figure out again how to assemble those parts.

Thanks, I will look into that!


For awhile I’ve noticed CI builds of racket-mode fail for HEADCS trying to start the REPL. Today I finally got time to catch up, install HEADCS locally, and investigate. (I’ve been super busy last N months on a consulting project.) I reproduced the failure. Took a deep breath. Ready for a long, complicated debugging session. Is there some change with module->namespace
, or something super intricate?

Turns out "Welcome to Racket v7.2"
is now instead "Welcome to Racket 7.3.0.3"
— no leading "v"
. So a test regexp needs to change from "Welcome to Racket [0-9.]+\n> "
to "Welcome to Racket v?[0-9.]+\n> "
.

Truly, I am operating at the pinnacle of software engineering mastery and sophistication here. :smirk:

Insert “what people think I do what I actually do” meme here.

No such thing as an innocent change.

At least I noticed it within a couple minutes. ¯_(ツ)_/¯

The longer a debugging mystery continues, the simpler the cause turns out to be. So this should have kept me busy for a few days. I’m sort of disappointed.

The “v” should still be there for plain Racket. Is this something other than the startup banner from racket
?

@mflatt It looks like banner
isn’t consistent. greg@x1c:~$ ~/racket/7.3.0.3-cs/bin/racket --version
Welcome to Racket v7.3.0.3 [cs].
greg@x1c:~$ ~/racket/7.3.0.3-cs/bin/racket
Welcome to Racket v7.3.0.3 [cs].
> (banner)
"Welcome to Racket 7.3.0.3\n"
>

Whereas with 7.2: greg@x1c:~$ ~/racket/7.2/bin/racket --version
Welcome to Racket v7.2.
greg@x1c:~$ ~/racket/7.2/bin/racket
Welcome to Racket v7.2.
> (banner)
"Welcome to Racket v7.2.\n"
>

Will fix. Thanks!

Hello, I’m new here, so is it appropriate to ask about the pollen language here? Or is this just for the main racket language?

It’s fine to ask. I think pollen is awesome but am not using it so I probably won’t be able to answer. But someone else probably can, eventually.

Thanks!

I’m looking to transition a file from Markdown authoring mode to Pollen markup to support multiple target formats (regular HTML and a different Wiki friendly HTML). Is there a decode-x type function I can add to my pollen.rkt that would allow me to continue rendering the markdown as before? I’ll gradually then change out markdown for pollen markup as I update the pages.

At the basic level, this should do what you want:
;; pollen.rkt
#lang racket
(provide markdown)
(require markdown/parse)
(define (markdown . xs)
(cons '@ (parse-markdown (string-join xs))))
;; <http://my-file.poly.pm\|my-file.poly.pm>
#lang pollen
◊(define hello "Hello")
◊markdown{
◊hello _world_!
How are you?
Here's a *new* paragraph.
}

And FWIW, Pollen users usually ask questions at https://groups.google.com/forum/#!forum/pollenpub

Exactly what I was looking for. I’ll take a stab at it later. Thanks for sharing the Google group, I’ll give it a look. Though, I’m in China so it’s not easy (but not impossible) for me to access.