Proposed lexer for parsing krb5.conf files
tytso at MIT.EDU
Tue Nov 22 17:41:32 EST 2005
On Tue, Nov 22, 2005 at 04:04:24PM -0600, Nicolas Williams wrote:
> But time passes and issues accumulate. The lack of a configuration tool
> means that the configuration tool for krb5.conf is $EDITOR, and that
> causes I18N problems that will soon bite. The primary allure of any
> other format, for me, is that it's a chance to start with a clean slate
> -- even taking backwards compatibility into account (a significant
> constraint, that).
But switching to XML doesn't solve the lack of a configuration tool;
writing a configuration tool solves that lack, and you can do that
without regard to what the back-end format looks like.
If you think that using a generic XML editor (which typically has the
usability of Window's regedit) counts as a configuration tool, I'll
take emacs in UTF-8 mode any day, thanks.
More information about the krbdev