Re: Pass argument to function

2023-03-11 Thread ipcore
You actually don't even need string-append here. The following should also work: (capture (docker inspect ,str)) Best wishes, -utz

Re: Pass argument to function

2023-03-10 Thread ipcore
(capture ,(string-append "docker inspect " str))) doesn't work because of the same reason that you expressed. You would get "quasiquote not found" from the shell. Yes, it does, and no, you don't get "quasiquote not found" from this.

Re: Pass argument to function

2023-03-10 Thread ipcore
Hi Brandon, 'capture' and its friends 'run' and 'run*' are macros that treat their arguments differently from what you would expect from a regular procedure. Looking at the documentation of '(run COMMAND ...)', you will find that COMMAND is also implicitly quasiquoted so subexpressions may

Re: Source code formatter?

2021-01-11 Thread ipcore
I don't know of any dedicated source code formatter for Scheme. Piping expressions through Chicken's pretty printer[1] can be (ab)used for this, though. (Credit goes to kooda for showing me this trick) [1] https://wiki.call-cc.org/man/5/Module%20(chicken%20pretty-print) On 1/11/21 5:36 AM,

Re: scm2wiki egg release

2020-11-14 Thread ipcore
Argh! Had only tested with salmonella, which, strangely enough, didn't trigger the issue. Anyway, should be fixed now. Sorry for the inconvenience. Cheers, -utz On 11/14/20 5:47 PM, Mario Domenech Goulart wrote: Hi Utz, On Sat, 14 Nov 2020 13:04:32 +0100 ipc...@arcor.de wrote: Think my

scm2wiki egg release

2020-11-14 Thread ipcore
Hi all, Think my little auto-documentation tool has matured enough for an official egg release. Wrote it mainly to generate API documentation for my Bintracker project (https://bintracker.org/documentation/index.html), but maybe some of you will find it useful, too.

Re: Bintracker: A modern chiptune editor

2020-06-08 Thread ipcore
I've released the source code for Bintracker, a powerful, hackable "chiptune audio workstation" written in Chicken Scheme. The project is work-in-progress, and is currently in an early alpha stage. Basic features work and the editor is usable, though not necessarily useful ;) I'm

Bintracker: A modern chiptune editor

2020-05-31 Thread ipcore
Hello everyone, I've released the source code for Bintracker, a powerful, hackable "chiptune audio workstation" written in Chicken Scheme. The project is work-in-progress, and is currently in an early alpha stage. Basic features work and the editor is usable, though not necessarily useful

Re: New egg: macaw

2020-04-21 Thread ipcore
Fantastic, just what I need for my current project. Thanks for your work! On 4/21/20 4:33 AM, John Croisant wrote: Hello everyone, I have published a new egg, macaw. It provides efficient color types, math operations, and color space conversion. It is primarily meant for computer graphics,

Re: is part of the wiki's hello world example broken?

2020-04-07 Thread ipcore
Your import.so should be named "hello.import.so". Doing `(import NAME)` will pull in NAME.import.so automatically. (You don't need to `,l hello.so`, btw) In your example, when you run `(import test)`, the interpreter does not find a local test.so, and so goes looking for it in

New version of scm2wiki

2020-04-06 Thread ipcore
Hello all, I've published a new version of scm2wiki, my CHICKEN auto-doc tool, at https://github.com/utz82/scm2wiki It's actually becoming quite a useful little tool. It now detects and transforms variable definitions, procedure definitions, various record definition styles, and coops

Re: Path problem when trying to compile under Windows

2019-10-30 Thread ipcore
Hi Cleverson, You could use the allegro egg as an alternative to sdl. It comes with with audio support and a full set of keyboard/mouse event handlers, and is available in Chicken 5. Cheers, -utz On 10/30/19 1:55 PM, Cleverson Casarin Uliana wrote: Hi Kristian, For now, I'm willing to try

Re: [Chicken-users] Auto CompletionProblems

2019-08-07 Thread ipcore
Hey, do you use helm by any chance? Then this might be related: https://gitlab.com/jaor/geiser/issues/271 Also if you haven't done so already, try running emacs with only the necessary packages enabled. On 8/3/19 4:47 PM, EfraimVagner via Chicken-users wrote: 1. You only ever get

Re: [Chicken-users] Auto CompletionProblems

2019-08-05 Thread ipcore
If you like, pastebin your init.el somewhere, then I'll check if I can spot any glaring errors. Other than that, I'm afraid I cannot help you. Maybe better ask the geiser folks. On 8/3/19 4:47 PM, EfraimVagner via Chicken-users wrote: 1. You only ever get auto-completion for the things you

Re: [Chicken-users] Auto CompletionProblems

2019-08-03 Thread ipcore
Hi, Geiser+company should work fine (though it can be very slow with a busy namespace), so I assume something isn't correct in your setup. A couple of things to check/note: 1) You only ever get auto-completion for the things you have loaded/imported in the geiser repl. 2) Is company mode

Re: [Chicken-users] [ANN] CHICKEN 5.1.0 release candidate available

2019-06-09 Thread ipcore
Yes, running chicken-belt with -b will run make spotless. Which I assume is required to build bootstrap CHICKEN, but in this case also appears to break it. On the bright side: Building from tarball as suggested works. So... Operating system: Gentoo 2.6 Hardware platform: x86_64 C Compiler:

Re: [Chicken-users] [ANN] CHICKEN 5.1.0 release candidate available

2019-06-09 Thread ipcore
Hi, I failed to build 5.1.0rc1. log: http://paste.call-cc.org/paste?id=049edb2b007bd9a1859362a6e99818a282aa5201 I know I forgot to set the LINKER flag, but setting it doesn't change anything. Likewise, using GCC doesn't work either, neither does building without chicken-belt. OS: Gentoo

Re: [Chicken-users] Back from the dead: pstk

2019-02-27 Thread ipcore
Ok, you've convinced me ;) Github repo is updated with history and old releases, so all cases should be covered now. I've also included the html documentation, as suggested by Vasilij. Best wishes, -Heinz On 2/26/19 3:59 PM, John Cowan wrote: >> From my viewpoint, it's not so much about

Re: [Chicken-users] Back from the dead: pstk

2019-02-26 Thread ipcore
Hello John, I considered doing this, but decided it would be a good idea to start with a clean slate. Wasn't 100% sure though, that's why I explicitly mentioned it. If the general opinion is that history from SVN should be preserved, then I'll do that of course. So what do you folks think?

Re: [Chicken-users] Back from the dead: pstk

2019-02-26 Thread ipcore
Hello Vasilij, Good point, I'll add the documentation to the repo. Regarding using the parens syntax for imports, that's good to know as well. I'm generally a fan of avoiding syntactic sugar that uses symbol characters, but I thought the dotted syntax was kind of neat. There are some

[Chicken-users] Back from the dead: pstk

2019-02-26 Thread ipcore
Hello, As promised, I've ported the pstk egg to Chicken 5, and would like to take over as maintainer. https://github.com/utz82/pstk https://raw.githubusercontent.com/utz82/pstk/master/pstk.release-info License has been reverted to BSD 2-clause, as the main source actually never was in the

Re: [Chicken-users] build failure and some questions about using chicken-belt

2019-02-24 Thread ipcore
That did the trick, I now have a working user installation of both 4.13.0 and 5.0.0. Thanks a lot for your help, Alexander. chicken-belt is up and running, too. Yay! On 2/24/19 4:45 PM, Alexander Shendi (Web.DE) wrote: Hi Heinz, AFAIK, this should work. Try extracting the tarball again and

Re: [Chicken-users] build failure and some questions about using chicken-belt

2019-02-24 Thread ipcore
Hi Alexander, Well spotted, I was indeed missing the #\S. However, after make ... confclean && make ... clean running make again still fails with the same error as before. Best wishes, -Heinz On 2/24/19 2:48 PM, Alexander Shendi (Web.DE) wrote: Dear Heinz, It maybe just a typo, but I

[Chicken-users] build failure and some questions about using chicken-belt

2019-02-24 Thread ipcore
Hello, I would like to transition from my current system-wide installation of Chicken 4.13.0 to a coop of different Chickens installed in ~/chickens, managed by chicken-belt. Namely, I want to have 4.13.0, 5.0.0, and a cross-chicken for MinGW (most likely based on 5.0.0) available. Steps