On Tue, Dec 12, 2017 at 04:52:42PM +0100, Clemens Schrimpe wrote:
> > Note that .birdc_history is created during exit from birdc, not during
> > start of birdc. Do you get .birdc_history if you use new birdc, do some
> > commands and exit from it without crashing it?
>
> Yes, works fine. And it also appears to be read when I restart birdc, because
> now I can crash it with ^P or ↑ without having typed a command before.
> (strace confirmed: .birdc_history is read successfully)
You can try attached patch (disables reading of history).
You can also try to build BIRD 1.6.3 in the same way like 2.0.0 and see
if it by chance does not express the same problem.
--
Elen sila lumenn' omentielvo
Ondrej 'Santiago' Zajicek (email: santi...@crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
diff --git a/client/birdc.c b/client/birdc.c
index f1aea2fe..a682c9fe 100644
--- a/client/birdc.c
+++ b/client/birdc.c
@@ -157,8 +157,8 @@ history_init(void)
void
input_init(void)
{
- if (interactive)
- history_init();
+// if (interactive)
+// history_init();
rl_readline_name = "birdc";
rl_add_defun("bird-complete", input_complete, '\t');
rl_add_defun("bird-help", input_help, '?');
@@ -236,7 +236,7 @@ cleanup(void)
return;
input_hide();
- if (interactive)
- write_history(history_file);
+// if (interactive)
+// write_history(history_file);
rl_callback_handler_remove();
}
