You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when I edit a php (only) file with web-mode major mode, the value of outline-regexp still matches html comments, therefore outshine obviously doesn't work (with php commented headings).
outshine work great with web-mode outside php blocks, but outline-regexp isn't updated as the comment syntax change. It's a problem with php only files where I need to use php comments for headings.
I have no idea if it is a limitation of outshine, a bug, or if I'm supposed to set things myself (in the latter case I have no idea how to make outshine works automatically in both cases, inside and outside php blocks). Any comment appreciated.
emacs 27.0.50
outshine: 20190131.535
The text was updated successfully, but these errors were encountered:
I don't know how web-mode works, but I guess its outline-regexp only matches HTML comments. I don't think this is a bug, but just a limitation of how outline-minor-mode and/or outshine work. There isn't a facility to support multiple independent outline-regexp values.
You could try changing the regexp to one that would match both HTML and PHP comments. If that works, you might consider submitting it as a patch to web-mode.
Hi,
when I edit a php (only) file with web-mode major mode, the value of outline-regexp still matches html comments, therefore outshine obviously doesn't work (with php commented headings).
outshine work great with web-mode outside php blocks, but outline-regexp isn't updated as the comment syntax change. It's a problem with php only files where I need to use php comments for headings.
I have no idea if it is a limitation of outshine, a bug, or if I'm supposed to set things myself (in the latter case I have no idea how to make outshine works automatically in both cases, inside and outside php blocks). Any comment appreciated.
emacs 27.0.50
outshine: 20190131.535
The text was updated successfully, but these errors were encountered: