>> I have some vague memory of this being added in a pull request shortly
>> after I started maintaining stump...
>
>The commit might be 0df1e87.
>
>The commit message reads:
>
> Defcommand exports the command to the UI. Obviously it should export
> the command t the API.
And the reason for that
Jay Belanger writes:
>> I just published the 0.9.9 release:
>> https://github.com/stumpwm/stumpwm/releases
>>
>> Here's News:
>
> Fantastic; thanks!
>
> (Also, stumpwm.asd lists the version as 0.9.8)
>
> I just installed this; works like a charm.
Annoyingly, I was working on some last minute chan
> I have some vague memory of this being added in a pull request shortly
> after I started maintaining stump...
The commit might be 0df1e87.
The commit message reads:
Defcommand exports the command to the UI. Obviously it should export
the command t the API.
> I just published the 0.9.9 release:
> https://github.com/stumpwm/stumpwm/releases
>
> Here's News:
Fantastic; thanks!
(Also, stumpwm.asd lists the version as 0.9.8)
I just installed this; works like a charm.
___
Stumpwm-devel mailing list
Stumpwm-
>> By using `defcommand' in a module (separate package), I couldn't
>> redefine the package because the symbols defining the commands were
>> exported but they were not listed in my new package redefinition.
>
> If you call (stumpwm:defcommand foo ...) from an external package, you
> export foo fro
> I think its there because a defcommand exposes commands to the user, and
> so it makes sense that their exported from the package. This is more a
> policy than a requirement. (if the user can call the command, then other
> parts of StumpWM itself should be able to call the command too.)
>
> I'm
"Diogo F. S. Ramos" writes:
>> I think its there because a defcommand exposes commands to the user, and
>> so it makes sense that their exported from the package. This is more a
>> policy than a requirement. (if the user can call the command, then other
>> parts of StumpWM itself should be able
David Bjergaard writes:
> Hi All,
>
> I just published the 0.9.9 release:
> https://github.com/stumpwm/stumpwm/releases
Very cool! Many thanks to David and all who contributed!
___
Stumpwm-devel mailing list
Stumpwm-devel@nongnu.org
https://lists.non
Hi Diogo,
I think its there because a defcommand exposes commands to the user, and
so it makes sense that their exported from the package. This is more a
policy than a requirement. (if the user can call the command, then other
parts of StumpWM itself should be able to call the command too.)
I'm
The `defcommand' macro has a (export ',name) form to export the symbol
`name', which gives the defining command its name.
Why does it do it?
___
Stumpwm-devel mailing list
Stumpwm-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
Hi All,
I just published the 0.9.9 release:
https://github.com/stumpwm/stumpwm/releases
Here's News:
- New module system based on asdf modules
- contrib-dir is no more, now the module-dir sets the default place
to look for modules, otherwise the user must add modules to the
load-p
11 matches
Mail list logo
