Peter Brett writes:
> l...@gnu.org (Ludovic Courtès) writes:
[...]
>> Then you are looking for Guile's nifty first-class modules. The module
>> API is unfortunately lightly documented (info "(guile) Module System
>> Reflection").
>
> Indeed. Should I file a feature request for "more useful
>
l...@gnu.org (Ludovic Courtès) writes:
> Hello!
>
> Peter Brett writes:
>
>> l...@gnu.org (Ludovic Courtès) writes:
>
> [...]
>
>>> What do you mean by "environment"? All the global variables associated
>>> with a given file in the editor?
>>
>> Sort of. The whole of Guile's top level bindings
Hello!
Peter Brett writes:
> l...@gnu.org (Ludovic Courtès) writes:
[...]
>> What do you mean by "environment"? All the global variables associated
>> with a given file in the editor?
>
> Sort of. The whole of Guile's top level bindings at that point. (The
> per-directory config is literall
l...@gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Peter Brett writes:
>
>> What I'd like to do is something like the following:
>>
>> * Load system config
>> * Load user config
>> * Save environment ==> [0]
>>
>> * User opens /path/to/a/file
>> * Load config from /path/to/a/editor.con
Hello,
Peter Brett writes:
> What I'd like to do is something like the following:
>
> * Load system config
> * Load user config
> * Save environment ==> [0]
>
> * User opens /path/to/a/file
> * Load config from /path/to/a/editor.conf
> * Edit, edit, hack, hack.
>
> * User opens /pa
Hi folks,
I've got an interesting problem I need some help with. I'm
implementing an editor which permits per-directory configuration
files, written in Guile Scheme. (There is also a system and user
configuration, as usual). Quite a lot of the editing actions are
implemented as Scheme procedures
