14:59 <mwnaylor> What is a good how-to or tutorial for mastering modules in Racket?

15:34 <mwnaylor> What is a good how-to or tutorial for mastering modules in Racket?

15:43 <bremner> mwnaylor: are you looking for something beyond the racket guide? There is a fair amount there, fwiw.

15:44 <bremner> TBH I seem to have survived without really understanding collections

15:48 <mwnaylor> bremner: I guess I should plow through the entire guide. The cake and random-cake examples were simple; worked fine from the command line. But, when I loaded files into either drracket or geiser-racket, I can't see the definitions in the repl.

15:49 <mwnaylor> TBH, I've struggled with getting similar stuff to work with Clojure and cider.

15:50 <mwnaylor> bremner: Do you have a preferred repl/ide for racket?

15:50 <bremner> mwnaylor: I use racket-mode

15:54 <mwnaylor> bremner: is that the repl or the buffer editing major mode?

15:54 <bremner> mwnaylor: it includes both

15:55 <bremner> I guess the major mode in the repl is #'racket-repl

15:55 <mwnaylor> bremner: w/ racket-mode, how would I start the repl and connect to it?

15:56 <bremner> M-x racket-run (C-c C-c / F5) and you will be left in a repl

15:57 <mwnaylor> geiser is a layer that connects to a native repl: scheme, guile, racket, chicken, etc

15:57 <bremner> I know geiser, I used to maintain it in Debian

15:58 <bremner> I switched to racket-mode because geiser (at the time) had some problems with typed/racket

15:59 <mwnaylor> aside from typed/racket, does racket-mode have advantages over geiser?

15:59 <bremner> I think it has grown to have more racket specific features

16:00 <bremner> e.g. test coverage

16:01 <mwnaylor> with cider, I have gotten spoiler with compile commands, toggle between source and repl, documentation for functions, etc

16:01 <bremner> there's a a bunch of docs at https://racket-mode.com/

16:02 <mwnaylor> also orchestrating functions to step through debugging, much like emacs/elisp debugging.

16:02 <bremner> For example I have C-c C-t bound to "run tests"

16:02 <mwnaylor> I will check out that site, thanks for the info.

16:03 <bremner> for debugging I tend to use drracket. There is racket-debug-mode, but it seems to be still experimental

16:06 <mwnaylor> good hint. would suck to write code in emacs and rely on drracket, but will do it if needed. I think the editor part of drracket is terrible. I'm too used to paredit, rainbow parens, and all my emacs extension. Looks like there is also a limited set of racket yasnipptes available in emacs.

16:07 <bremner> I'm not a big user of completion when programming, so I don't know about that.

16:07 <mwnaylor> thankfully, (infor "racket-mode") gives us documentation. just found it, so don't know how good it is.

16:08 <mwnaylor> how about extensions like paredit?

16:11 <mwnaylor> looking at toc for info racket-mode. seems to cover a lot of relevent topics.

16:24 <mwnaylor> how do you get emacs to recognize *.rkt and initialize racket-mode? my setup loads those files in scheme-mode.

16:25 <bremner> it depends on auto-mode-alist. unfortunately I think geiser also sets that?

16:30 <mwnaylor> overiding w/ -*- mode: racket -*- is always an option. I knew there was an auto recognition method; good tip about auto-mode-alist.

16:33 <mwnaylor> geieser may set that. my alist has two entries for the key regex. the first is the one that triggers the scheme-mode.

17:16 <mwnaylor> Deleting the geiser-racket packag did the trick. Now when I execute racket-run, the right thing happens.

17:17 <mwnaylor> severe lack of information on geiser-racket. racket-mode looking to be the best option.