eev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [edrx/eev] Question: why not a single command for the "eepitch block


From: Suhail
Subject: Re: [edrx/eev] Question: why not a single command for the "eepitch block" idiom? (Issue #10)
Date: Fri, 23 Feb 2024 20:45:50 +0000

Moving thread to mailing list per request.  Also cross-posting to
Github.  Apologies for the duplicate message.

"Eduardo Ochs" <notifications@github.com> writes:

> You're right that "generally, one would either execute all three or
> none of them", but I found that there were many cases in which I just
> wanted to redisplay the target buffer at the window at the right
> without restarting it, and in these cases I would just execute the
> (eepitch-shell)...

Yes, I can see value in not altering the behaviour of eepitch-shell.  I
wasn't proposing that the definition of eepitch-$name be altered.  My
proposal was for a new function (or family of functions), say,
eepitch-init-$name where (eepitch-init-$name) would be equivalent to
something like (progn (eepitch-$name) (eepitch-kill) (eepitch-$name)) .

-- 
Suhail




reply via email to

[Prev in Thread] Current Thread [Next in Thread]