[Octave-bug-tracker] [bug #62780] oruntests looks in file without respecting .oct-config

[Markus Mützel]

Follow-up Comment #9, bug #62780 (project octave):

The behavior that you show in comment #6 and comment #7 is expected if that
directory was never in Octave's load path and no encoding has manually been
specified with `dir_encoding`. See also the tests here:
https://hg.savannah.gnu.org/hgweb/octave/file/7d4cf04665e6/test/file-encoding/file-encoding.tst

If the documentation of `dir_encoding` is unclear in that respect, updates to
it are welcome. It currently contains the following sentence:
> The directory encoding is automatically read from the file .oct-config when
a new path is added to the load path (for example with addpath).

Negate that sentence, and it says: "The encoding is not read from those files
unless their path is added to the load path." (The current directory is always
in the load path.)

IIUC, `make check` or `__run_test_suite__` change to each directory for which
they are running tests. The possible change that you describe in comment #8
would bring `oruntests` more in line with those commands. However, it might
also break some use cases that rely on the current directory not changing
during the tests...
If we decide to make that change, it would definitely be worth to at least add
a comment about it in the NEWS file (and maybe also clarify that in the
[currently very sparse] documentation of `oruntests`).


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?62780>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/