Date: Tue, 16 May 2017 12:34:15 +0200
So before anything else, I would like to assess if we can have a majority agreement that prog-mode is NOT an
implementation detail, but rather an API both users and developers are encouraged to use for
programming-related activities and customizations.
If we can agree on that, I think there are options for moving forward.
Beware: you are shifting the focus of this discussion from nxml-mode
and its ilk, which was the original issue, to an almost completely
unrelated one. There be a lot of unrelated bikeshedding (which
actually already began).
Thanks Eli.
That's a good point. A point well taken.
Trying to get things back to where we started, with a minimal of bikeshedding, I think there's 3 obvious choices for what direction we can go:
- Keep everything as is. Keep nxml-mode derived from text-mode (and annoy whoever finds that unexpected)
- Derive nxml-mode from prog-mode instead (and annoy whoever finds that unexpected)
- Create a new intermediate mode for deriving (structured-text-mode, or similar) and use this for all structured and textual data-format files (and thus, nxml-mode). Let people make new hooks as they see fit.
Personally I feel like the third option may be the most "proper" one, but if people for some reason should be opposed to that, I still think the second option makes more sense than the first one.
So... Is there any obvious counter-arguments to the third option? Any reasons we should definitely not do that?