branch: elpa/magit
commit 07f092ad6445dea216e43c4f95dc7b6c4db9c7ae
Author: Iñaki Arenaza <iaren...@escomposlinux.org>
Commit: Jonas Bernoulli <jo...@bernoul.li>
Make magit-stash-index respect user configured function
When magit-stash-read-message-function was introduced (in commit
72fbb3a579b), magit-stash-read-args was updated to use it, but
magit-stash-index was not.
Which means that if the user customizes
magit-stash-read-message-function, the customized value will not be
used in magit-stash-index.
---
lisp/magit-stash.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/magit-stash.el b/lisp/magit-stash.el
index 1a8779e9742..836b874a6cb 100644
--- a/lisp/magit-stash.el
+++ b/lisp/magit-stash.el
@@ -143,7 +143,7 @@ Unstaged and untracked changes are not stashed. The stashed
changes are applied in reverse to both the index and the
worktree. This command can fail when the worktree is not clean.
Applying the resulting stash has the inverse effect."
- (interactive (list (magit-stash-read-message)))
+ (interactive (list (funcall magit-stash-read-message-function)))
(magit-stash-save message t nil nil t 'worktree))
;;;###autoload
