[Octave-bug-tracker] [bug #49685] Set .m file encoding on a per-directory basis

[Andrew Janke]

Follow-up Comment #14, bug #49685 (project octave):

Here's an idea: instead of doing a "recursive, overrideable" thing that would
require traversing the directory tree, you could require that an `.encoding`
file must be present at the exact directory level that's added as a `PATH`
entry (or you do one source_encoding() function call per PATH entry), and it
applies to the entire directory subtree below that path entry; no overrides
allowed. You want to combine source trees with different encodings, you need
to add them to the Octave `PATH` as separate entries. That way it costs you
just one file access per directory tree, no matter  how deep the +package or
`private/` hierarchy goes, and there's still a way to have sets of code with
different encodings.

(Maybe this is something that was already discussed.)

    _______________________________________________________

Reply to this item at:

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

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