[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #45872] default site octaverc file still execu
From: |
John W. Eaton |
Subject: |
[Octave-bug-tracker] [bug #45872] default site octaverc file still executed even if OCTAVE_SITE_INITFILE is defined |
Date: |
Thu, 03 Sep 2015 23:25:57 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Iceweasel/38.1.0 |
URL:
<http://savannah.gnu.org/bugs/?45872>
Summary: default site octaverc file still executed even if
OCTAVE_SITE_INITFILE is defined
Project: GNU Octave
Submitted by: jwe
Submitted on: Thu 03 Sep 2015 11:25:56 PM GMT
Category: Interpreter
Severity: 2 - Minor
Priority: 5 - Normal
Item Group: Other
Status: None
Assigned to: None
Originator Name: jwe
Originator Email:
Open/Closed: Open
Discussion Lock: Any
Release: dev
Operating System: Any
_______________________________________________________
Details:
If OCTAVE_SITE_INITFILE is defined in the environment, Octave uses that as the
site startup file but will also execute the default site init file. I see
this problem when using the run-octave script in my build tree when I also
have the same development version installed.
I first noticed this when working on bug #45869 because finish.m was being
executed twice. I traced that to having __finish__ added twice to the list of
atexit functions, once from the octaverc file in the build tree and once from
the directory where I had previously installed a copy of Octave from the same
sources.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?45872>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #45872] default site octaverc file still executed even if OCTAVE_SITE_INITFILE is defined,
John W. Eaton <=