[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #49685] Set .m file encoding on a per-directory basis
Date: Fri, 18 Sep 2020 12:51:04 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36 Edg/85.0.564.51

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

I'm unsure if the dir_encoding should also apply to any private, @class or
(nested) +namespace folders in that directory.

One the one hand, it might make it easier for the user to write the necessary
PKG_ADD file if those were included automatically. Something like this would

dir_encoding (fileparts (mfilename ("fullpath")), "iso8859-1");

On the other hand, it's probably also conceivable that a user would like to
drop in a +namespace folder from another project that uses a different
encoding. For this to work, it would be best if the PKG_ADD file contained a
line for each (automatically loaded) subfolder.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]