On Wed, Sep 04 2013, David Bremner wrote:
> Tomi Ollila writes:
>
>> can be used to quickly experiment with new development.
>
> What about explicitely putting this under devel? I'm a bit nervous about
> promoting this feature since mismatch between CLI and emacs code is
> already a source of pr
Added Makefile recipes to create notmuch emacs client in just one
.el[c] file.
This is an experimental feature and not built by default.
This is useful for example when one wants to build the latest
emacs client and then distribute the elisp file to many machines.
This is also useful for (initia
Tomi Ollila writes:
> can be used to quickly experiment with new development.
What about explicitely putting this under devel? I'm a bit nervous about
promoting this feature since mismatch between CLI and emacs code is
already a source of problems for users.
d
On Wed, Sep 04 2013, David Bremner wrote:
> Tomi Ollila writes:
>
>> can be used to quickly experiment with new development.
>
> What about explicitely putting this under devel? I'm a bit nervous about
> promoting this feature since mismatch between CLI and emacs code is
> already a source of pr
Tomi Ollila writes:
> can be used to quickly experiment with new development.
What about explicitely putting this under devel? I'm a bit nervous about
promoting this feature since mismatch between CLI and emacs code is
already a source of problems for users.
d
__
Added Makefile recipes to create notmuch emacs client in just one
.el[c] file.
This is an experimental feature and not built by default.
This is useful for example when one wants to build the latest
emacs client and then distribute the elisp file to many machines.
This is also useful for (initia
