On 2015-06-17 11:18 AM, Nathan Froyd wrote:
On Wed, Jun 17, 2015 at 11:03 AM, Ehsan Akhgari <ehsan.akhg...@gmail.com <mailto:ehsan.akhg...@gmail.com>> wrote:On 2015-06-17 10:49 AM, Nathan Froyd wrote: Speaking as an emacs user, I'd be OK with removing modelines, adding editorconfig files, and adding .dir-locals.el files (modelines, but on a directory-wide basis, including subdirectories). Just removing modelines and adding editorconfig files requires several steps on my part to get back to the functionality I already enjoy, which doesn't seem helpful. I use vim, and the modelines are definitely useful to me. I didn't mean to imply that they aren't useful to me! They certainly are (and it's annoying to encounter files where indentation settings don't get setup correctly). I don't understand why you are suggesting to remove the modelines instead of fixing them, and potentially adding an editorconfig for people who use those, but I guess I can live with it if that happens. Hey, Mike is the one who suggested removing them, I'm just trying to make sure that a potential removal happens the way I would like it to. ;)
Yep, both of my comments were addressed to Mike. Sorry for the confusion. :-)
I don't mind removing the modelines so long as I don't have to configure other things to get back to my present editing state. If there aren't equivalent mechanisms for setting modelines on a per-directory basis in vim, I'd be OK with leaving the vim modelines in. Also, if we *do* have per-directory settings, let's please have them at the top of the tree and not permit per-module settings... (js/ excepted from this, of course).
Why would we need per-directory settings? IIRC we agreed that there is one Mozilla coding style that all Mozilla code should strive to adhere to.
_______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
