[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #39846] Octave segfaults if keyboard() is in .
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #39846] Octave segfaults if keyboard() is in .octaverc |
Date: |
Wed, 21 Aug 2013 22:55:33 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 |
URL:
<http://savannah.gnu.org/bugs/?39846>
Summary: Octave segfaults if keyboard() is in .octaverc
Project: GNU Octave
Submitted by: rik5
Submitted on: Wed 21 Aug 2013 03:55:33 PM PDT
Category: Interpreter
Severity: 3 - Normal
Priority: 5 - Normal
Item Group: Crash
Status: None
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: GNU/Linux
_______________________________________________________
Details:
Octave executes the contents of .octaverc at start-up. I assumed that it
treated the contents of .octaverc like any other m-file. Apparently, however,
there are keywords which you cannot use in the initialization file which are,
however, valid in m-files.
This is a regression from 3.6.4 where keyboard works correctly.
I tested this with a recent tip (hg id 4c7ee36f591d) and "run-octave --no-gui"
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?39846>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #39846] Octave segfaults if keyboard() is in .octaverc,
Rik <=