Aaron Ecay <aarone...@gmail.com> writes: >> Expansion templates are a great thing, but this is only sugar for Org, >> which is totally usable without them. Besides, some facilities are >> providing it for us. This falls into (2). By design, I'm convinced we >> should not include them. I also wish that anyone involved in this thread >> can take a step back to see the whole picture. > > This is a red herring. The changes do not eliminate expansion template > code from org. They merely substitute (incompatibly) one expansion > template mechanism for a new one. > > FWIW, I do think the idea is worth exploring of getting rid of the (old > and new) template expansion code and using emacsʼs built-in SRecode > template facility. Like most of the CEDET stuff, it looks horridly > overengineered at a first glance. But it is also included with emacs by > default (unlike e.g. yasnippet which otherwise looks more pleasant to > program to me), and it would be (even more) responsive to the concerns > from emacs-devel that were quoted in your full message. To be specific, > this would entail (eventually) getting rid of the > org-structure-template-alist variable entirely, as well as the menu now > bound to C-c C-,; the former would be replaced by (AFAIUI) template > files that would be included with org and/or created by users for their > custom templates; the latter would use SRecodeʼs built-in template > selection instead.
Cool, I at least did not know that one. Can you a reproducible way to try it out? Without having to make my own templates etc. Rasmus -- Not everything that goes around comes back around, you know
