Alan Schmitt <alan.schm...@polytechnique.org> writes:
> On 2014-09-01 19:18, Thorsten Jolitz <tjol...@gmail.com> writes:
>
>> Does outshine work with that buffer (without navi-mode)?
>
> I guess not … How can I test it?
>
>> Are the headlines fontified like Org headlines?
>
> No.
>
>> Can you cycle visibility?
>
> Using TAB does nothing.
>
>> Can you call 'M-x outorg-edit-as-org' on a subtree?
>
> No, I get a backtrace:
>
> Debugger entered--Lisp error: (error "before first heading")
> signal(error ("before first heading"))
> error("before first heading")
> outline-back-to-heading(INVISIBLE-OK)
> outorg-copy-and-convert()
> outorg-edit-as-org(nil)
> call-interactively(outorg-edit-as-org record nil)
>
>> What does C-h v outline-regexp return?
>
> outline-regexp is a variable defined in `outline.el'.
> Its value is ";;[;]\\{1,8\\} "
> Original value was "[*\f]+"
> Local in buffer untitled; global value is "[*\f]+"
Wrong regexp for the example file, these are old-school headers, the
example file has outshine (=org-style headers). So the
outshine-hook-function wasn't really called on that buffer (again) to
find out it has outshine headers.
>> I suspect the problem is in your outshine installation. Does it work
>> otherwise for you?
>
> I don't use it otherwise, so I don't know. I tried 'M-x
> outorg-edit-as-org' on this message and it works.
>
>> What happens if you call M-x outline-minor-mode again in that example
>> buffer?
>
> It works! I have to call it twice (once to disable it, and once to
> enable it again), but then TAB and navi work as expected (no
> fontification, though).
Good!
This whole thing is related to loading libraries and calling hooks, and
its quite hard to tell whats going on there inside emacs sometimes.
When I have all the hooks set in my init file, so that opening an elisp
file calls outline-minor-mode-hook, and loading outline-minor-mode calls
outshine-hook-function, then things just work.
But putting an active fundamental-mode tmp-buffer with elisp code in
emacs-lisp-mode sometimes doesn't activate outshine right away, and I
have to call M-x emacs-lisp-mode again.
Calling M-x nuke-and-eval on an outshine buffer is not a good idea
either, probably because of the buffer-local-vars set.
And currently I'm working with latex/auctex again and added a few
(actually really nice) convenience functions to tj-outshine and tj-navi
branches to make outshine work with latex-mode too, and it works well,
only that latex-mode seems to re-fontify the buffer frequently so the
outshine fontification is lost and I have to call M-x latex-mode again
to make it reappear, whats a bit annoying ...
> So for some reason emacs-lisp-mode sets up outline-mode, but the later
> does not seem to load outshine automatically.
I think thats really an internal emacs thing, because
,----
| C-h v outline-minor-mode-hook
`----
will probably show you this:
,----
| outline-minor-mode-hook's value is (outshine-hook-function)
`----
--
cheers,
Thorsten
