[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #43729] Octave doesn't store command history a
From: |
Mark |
Subject: |
[Octave-bug-tracker] [bug #43729] Octave doesn't store command history after crash |
Date: |
Sun, 30 Nov 2014 10:26:56 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0 Iceweasel/31.2.0 |
URL:
<http://savannah.gnu.org/bugs/?43729>
Summary: Octave doesn't store command history after crash
Project: GNU Octave
Submitted by: mb1234
Submitted on: Sun 30 Nov 2014 10:26:54 AM GMT
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: None
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: 3.8.2
Operating System: GNU/Linux
_______________________________________________________
Details:
When playing with data, I frequently resort to crashing out of Octave with
CTRL-C. When doing this, the command history is not saved. I was wondering if
it possible to include and option to update the command history file after
every command? I browsed the documentation but this isn't an option.
https://www.gnu.org/software/octave/doc/interpreter/Commands-For-History.html
The effect of CTRL-C is still a little "random" on Octave. Sometimes you end
up at the octave prompt and sometimes at the linux prompt.
E.g. CTRL-C out of either of these: q=randn(5000); q=fftn(q);
Not too big of a deal but losing the command history is a shame.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?43729>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #43729] Octave doesn't store command history after crash,
Mark <=