RE: when deleting in minibuffer, don't change kill-ring

["Drew Adams" <drew.adams@oracle.com>]

> I guess the OP means `backward-kill-word' (<M-backspace>) and friends.
> I'm also interested in something like that.  I want to use the word,
> line, and region editing commands in the minibuffer, but I 
> don't want to have the killed text in the global kill-ring.

I think you need deleting (non-killing) commands to remap the killing commands
to:

(defun delete-word (arg)
  (interactive "p")
  (delete-region (point) (progn (forward-word arg) (point))))

(defun backward-delete-word (arg)
  (interactive "p")
  (delete-word (- arg)))

Then, as I said, bind these in _each_ of the minibuffer keymaps.  This is for
one of the maps:

(define-key minibuffer-local-must-match-map
    [remap kill-word] 'delete-word)

(define-key minibuffer-local-must-match-map
    [remap backward-kill-word] 'backward-delete-word)

> What I'd really like to have is a separate kill-ring for the
> minibuffers.  I've tried
> (dolist (b (buffer-list))
>   (when (minibufferp b)
>     (set-buffer b)
>     (make-local-variable 'kill-ring)))
> or entering a recursive edit
>   M-: M-: (make-local-variable 'kill-ring) RET C-g,
> but that doesn't have an effect. 

Try doing it on `minibuffer-setup-hook' instead.

(add-hook 'minibuffer-setup-hook'
          (lambda ()
            (make-local-variable 'kill-ring)))

> Isn't it possible to have buffer local values for
> variables defined at the C level?

Yes, AFAIK.