[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #35392] /etc/octaverc
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #35392] /etc/octaverc |
Date: |
Thu, 04 Jun 2015 00:26:43 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.0.1 |
Update of bug #35392 (project octave):
Category: Interpreter => Configuration and Build
System
Priority: 5 - Normal => 3 - Low
Release: 3.6.0 => dev
_______________________________________________________
Follow-up Comment #7:
This bug is still actionable. There are a few open bugs all having to do with
the location of startup files.
Octave currently kind of follows the gdb model, in that configs are loaded
from a system-wide config file, a user config file, and a startup file in the
current directory.
This bug is about moving the system-wide startup file to something like
$(sysconfdir)/octave/octaverc by default, or maybe allowing it to be
configured, as gdb does in its configure script. Right now it defaults to
$(datadir)/octave/$(version)/m/startup/octaverc with no easy way to change
that. The user can set the OCTAVE_VERSION_INITFILE enviroment variable, and
that is documented, but can't be set to something else globally.
But then there is also a site configuration file that is different from the
version configuration file. Should both be moved to $(sysconfdir), one or the
other, or neither? Or should a startup file in $(sysconfdir) be in addition to
the current startup files? Lots of options.
Updating release to dev.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?35392>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #35392] /etc/octaverc,
Mike Miller <=