[racket-users] inspecting a table error 'error 'query: multiple statements given'

2017-04-14 Thread Stephen De Gabrielle
Hi, Having a little trouble with the db library. In the following test the first '(query db "PRAGMA' works, but the second fails with the error 'query: multiple statements given given: "PRAGMA table_info($1)"' Any ideas about what I'm doing wrong? Not including the single quotes in the

Re: [racket-users] Scribbling documentation for a module beginning with _

2017-04-14 Thread Matthias Felleisen
Serves you well for writing Python names with Racket tools :-) > On Apr 14, 2017, at 4:50 PM, 'John Clements' via Racket Users > wrote: > > >> On Apr 14, 2017, at 6:05 AM, Matthew Flatt wrote: >> >> I don't didn't find any other

Re: [racket-users] Scribbling documentation for a module beginning with _

2017-04-14 Thread 'John Clements' via Racket Users
> On Apr 14, 2017, at 6:05 AM, Matthew Flatt wrote: > > I don't didn't find any other workaround. > > I think it makes no sense to treat an `_` prefix specially in > `defmodule`, `racketmodlink`, etc. (and it wasn't really a good idea > for `racket`), so I've pushed a

[racket-users] #:grammar and #:contracts of scribble

2017-04-14 Thread Jos Koot
Hi, In a defform of scribble, the grammar (#:grammar) is nicely alligned such as to put every = and every | in the same column of the text. However the contracts (#:contracts) are not alligned such as to put the colons in the same column. MHO is that placing the colons in the same column in a way

Re: [racket-users] Scribbling documentation for a module beginning with _

2017-04-14 Thread Matthew Flatt
I don't didn't find any other workaround. I think it makes no sense to treat an `_` prefix specially in `defmodule`, `racketmodlink`, etc. (and it wasn't really a good idea for `racket`), so I've pushed a change to Scribble to disable `_` treatment in those forms. At Thu, 13 Apr 2017 21:11:57

Re: [racket-users] Announcing Leibniz, a new language in the Racket universe

2017-04-14 Thread Konrad Hinsen
Shriram Krishnamurthi writes: > I would suggest adding a @(table-of-contents) to the top of every page: it > helps the reader know what is coming ahead. For instance, it's good for me That looks useful indeed. I'll put it on my to-do list for revising the presentation,