Re: [racket-users] Re: preferences file

William, that's a neat idea, I'll try your package. Thanks! --Geoff -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com.

Re: [racket-users] raco planet open tries to install?

If it ever helps, the ancient Quack package for Emacs has a convenient and safe mode for quickly inspecting ".plt" files (page through them, isearch): http://www.neilvandyke.org/temporary/20171102-quack-plt-screenshot.png http://www.neilvandyke.org/quack/ (So ancient, I just notic

Re: [racket-users] raco planet open tries to install?

I think that, at some point, we changed things so that planet declines to run arbitrary code in the .plt file. I'm not sure how this works, tho, it could just check that the code is the known code and then runs it. (Or I could misremember and we merely planned to do that.) Robby On Thu, Nov 2,

Re: [racket-users] raco planet open tries to install?

Ooh… yikes. Looking at the code, it looks like PLT files include their own unpackers? Is this correct? In this case, I understand that this could be a problem. This also seems like a bad idea; I wouldn’t have expected unpacking to run potentially untrusted code. Anyhow, that’s all in the past,

[racket-users] raco planet open tries to install?

I’m surprised by this interaction with raco planet: % raco planet open ../margrave3-dev-0203.plt . cannot install; version (400) of collection ("mzscheme") is required, but version is installed context...: /Users/clements/racket/racket/collects/setup/unpack.rkt:408:31: loop

Re: [racket-users] Re: preferences file

Recent discussion thread: https://groups.google.com/forum/#!topic/racket-users/6hn9J-r0Nek Since we're discussing dotfiles and I missed the previous thread, I'm going to shamelessly promote my basedir package[1], which provides functions for conveniently reading/writing config files according

[racket-users] Bluetooth LE - Typed Racket

While deep lurking I noticed a mention concerning some older Racket code of mine. Specifically porting sha-256 from typed to untyped racket. Well that led to a wiki page that listed a number of suggested starter tasks for new Racket inductees wanting to get involved. A number of those were in

Re: [racket-users] Re: preferences file

Awesome, Neil, great suggestions! -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit

Re: [racket-users] Re: preferences file

For a "home directory dotfile" kind of preferences file that's arbitrary Racket code, I'd do `dynamic-require` instead of `require`. If you want to use `require` instead, maybe the application is a framework, and the user-specific `.rkt` file is the program that is run and is what `require`s

Re: [racket-users] preferences file

Thanks John! Good ideas, and no, nothing is too obvious for me! --Geoff On Thursday, November 2, 2017 at 12:56:14 PM UTC-4, johnbclements wrote: > > > One solution is to use a .gitignore. I have a convention that files ending > with ‘private.rkt’ don’t go in the repo. > > Alternatively, you

[racket-users] Re: preferences file

The following seems to work for me: (require (file "~/.dbaccess.rkt")) Is that normal / ok ? Just wondering what other people do. Geoff On Thursday, November 2, 2017 at 12:35:25 PM UTC-4, Geoffrey Knauth wrote: > > Let's suppose I want to have a preferences file, e.g., "~/.dbaccess.rkt".

Re: [racket-users] preferences file

> On Nov 2, 2017, at 9:35 AM, Geoffrey Knauth wrote: > > Let's suppose I want to have a preferences file, e.g., "~/.dbaccess.rkt". I > used to have a module I would import via > "../some-relative-path/dbaccess.rkt", but I thought I would try > "~/.dbaccess.rkt" as a module

[racket-users] preferences file

Let's suppose I want to have a preferences file, e.g., "~/.dbaccess.rkt". I used to have a module I would import via "../some-relative-path/dbaccess.rkt", but I thought I would try "~/.dbaccess.rkt" as a module path. It turned out a module path cannot begin with "/", which happens with the