Kevin, thank you. I am in last minute packing mode, family holiday, travel tomorrow, back around the 4th. There should be Internet connection, probably sporadic, (visiting another generation and expect to be kept busy). Will look at your post and expect to pick up on again in the new year if not before. Happy Holidays, and Best Wishes for the coming year. Thanks, Ralph
On Fri, Dec 18, 2015 at 10:58 PM, Kevin Ryde <user42_ke...@yahoo.com.au> wrote: > Ralph Amissah <ralph.amis...@gmail.com> writes: >> >> I did use a subdirectory as it looks cleaner and is available should >> there ever be more files to place there > > The startup will need that, eg. per attached below. > >> (and I copied the autoload file there as well). > > Slight doubt about extending load-path in sisu-autoloads.el, otherwise > no worries. > >> ultimately as upstream, > > Actually on the upstream front I meant to say I think outline-regexp > should be buffer-local. It could go in the main mode function too > as a setup for inter-operation. Bit of a diff attached below, > > 2015-12-19 Kevin Ryde <user42_ke...@yahoo.com.au> > > * sisu-mode.el: outline-regexp buffer local, more autoload cookies, > auto-mode-alist use \' for end-of-string. > > >> Remaining holdouts: (i) from the most recent posting, not having sorted >> syntax highlighting for tic block types ``` > > Non-greedy might help (untested), > > ```.*?\n```\n > > which matches as little as possible to satisfy. Except . doesn't match > newline so umm \\(.\\|\n\\)*? A matcher function is also possible if it > gets too much. > > You might have seen in info node "(elisp)Multiline Font Lock" some extra > trouble is needed to make a multi-line match work fully. Hard work this > font lock eh :-) > >> (ii) anticipated changes for code block tags: >> will need to identify the code language held by the block (but that is >> down the line, as sisu does not take this into account yet (having come >> from a more law and literature text background rather than a code text >> one)). > > Some "multiple major modes" things can supposedly apply different modes > to buffer sub-parts. I think I've seen it work but never needed it. >
