Eric Abrahamsen writes: > Rasmus <ras...@gmx.us> writes: > >> Hi Eric, >> >> Eric Abrahamsen <e...@ericabrahamsen.net> writes: >> >>>> Also, Eric, it seems that org-structure-template-alist only supports a >>>> single letter for short-hands (the car of an entry in >>>> org-structure-template-alist is a char). I used to have blocks like "<ab" >>>> expanding to an "abstract" special-block, which I guess isn’t possible >>>> anymore? >>> >>> I hadn't thought of that. Really, all I ever wanted was to wrap things >>> in blocks... >>> >>> I don't see any reason why org-structure-template-alist couldn't go back >>> to using string keys. Then we could use read-string, and wouldn't have >>> to have special <TAB> behavior -- a string that didn't exist in the >>> alist could just be used literally to make a block. >> >> I’d prefer that. For some special blocks, a few characters might makes it >> more intuitive, e.g. "def" → "definition", "hyp" → "hypothesis" etc. > > Here's the simplest solution. > > There still remains the fact that `org-structure-template-alist' has > changed format, and `org-try-structure-completion' no longer exists. > That may still annoy some people who were using the internals of the > process, but...
Would something like this work? (defun org-try-structure-completion () (tempo-complete-tag)) All the best, Tom -- Thomas S. Dye http://www.tsdye.com
