Re: Proposal: 'executable' org-capture-templates

[Max Nikulin <manikulin@gmail.com>]

On 03/07/2022 22:12, Arthur Miller wrote:
> Max Nikulin writes:
>>
>> My impression is that Emacs process per task scenario is not supported.
> 
> I am not sure if we think of same thing, but "process per task" means simply how
> people use Emacs. Some people open each file in a new Emacs process, some people
> like to keep different tasks in different instances of Emacs, for example Gnus
> in one Emacs, and editing work in another etc. It is not that Emacs has some
> feature that would make one prohibit to start Gnus in other session, or to load
> same set of files in different Emacs processes, but I don't think it is
> necessary either.

I am aware of a workaround with a separate process for gnus since it is 
implemented as a synchronous single thread application, so network 
latency becomes a disaster. Emacs process per file is inconvenient when 
emacs server is desired (e.g. for org-protocol). True init directory is 
required for easy customization. There are may be subtle differences 
whether a file loaded as a part of initialization of as -l argument and, 
of course, bugs.

After all, it would be much more convenient to tune init.el file if it 
were possible to specify just config directory. It is disappointing that 
emacs offers rather strange options instead: --user and XDG_CONFIG_HOME. 
Even mount namespace might be more convenient than the latter one to 
override just .emacs.d without touching of over desktop settings.

So menu with multitasking support sounds promising to avoid multiple 
processes, but requires some care at the call sites.