Re: [STUMP] [PATCH] New defvar *interactive* used to know if a defcommand is called interactively

[Shawn Betts]

On Sat, May 24, 2008 at 10:37 AM, Lionel Flandrin
<address@hidden> wrote:
> * replaced all references to *executing-stumpwm-command* with *interactive*

I think *interactive* has a different meaning. There are currently 4
ways to call a stumpwm command:
* remotely from stumpish
* from lisp code
* from a key binding
* from the colon command

I think *interactive* would be a useful variable that could be turned
on for the last two possibilities exceeeept since you could call a
command interactively that calls a command function, you would want
*interactive-p* to be on in the first function but then turned off in
the second one, like emacs:

(defun bar ()
  (message "interactive in bar? %s" (interactive-p)))

(defun foo ()
  (interactive)
  (message "interactive in foo? %s" (interactive-p))
  (bar))

How you would do that in common lisp I have no idea.

-Shawn