[Conkeror] Bug: minibuffer history and completion

marting at gmx.ch marting at gmx.ch
Mon Sep 15 10:41:14 PDT 2008


Jeremy Maitin-Shepard <jeremy at jeremyms.com> writes:


> I agree the behavior in these cases could improve.  Would you care to
> send a patch? (I don't think it would be very difficult to fix.)

The following modification seems to improve the behaviour:

diff --git a/modules/minibuffer-read.js b/modules/minibuffer-read.js
index 5c9efb1..079558f 100644
--- a/modules/minibuffer-read.js
+++ b/modules/minibuffer-read.js
@@ -454,6 +454,7 @@ function minibuffer_history_next (window, count)
     s.history_index = index;
     m._input_text = s.history[index];
     m._set_selection();
+    s.handle_input();
 }
 interactive("minibuffer-history-next", null, function (I) {minibuffer_history_next(I.window, I.p);});
 interactive("minibuffer-history-previous", null, function (I) {minibuffer_history_next(I.window, -I.p);});

However, it may break something else or not be the right way to
approach the problem. I really don't know (and that's the reason why I
reported the bug in the first place; I'm not very proficient in these
matters).

--
Martin


More information about the Conkeror mailing list