[Octave-bug-tracker] [bug #62807] dir_encoding: report the actual encoding independent of whether it has been in the load path

[Markus Mützel]

Follow-up Comment #1, bug #62807 (project octave):

> Perhaps I'm still missing the point of this command: the current behaviour
smells like some internal tooling and yet its not `__dir_encoding__`...

Internal functions (padded in double underscores) might change their behavior
and interface at any point without any deprecation notice. When I added that
function, I figured it was important enough for downstream to give it a stable
and documented interface. Maybe, that was a mistake...

The documentation of `dir_encoding` is clear to me. But I wrote that
documentation. So there is definitely a bias.
Happy to see any suggestions.



    _______________________________________________________

Reply to this item at:

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

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