spell check in outli headings

[rdiaz02]

I am using outli: https://github.com/jdtsmith/outli , mainly in prog-mode. To have jinx spell check the headings I have added org-level-1, org-level-2, ..., org-level-8 to jinx-include-faces in the faces of prog-mode.

(setq jinx-include-faces '((prog-mode font-lock-comment-face font-lock-doc-face font-lock-string-face
						;; the next are to have jinx work with outli
						org-level-1 org-level-2 org-level-3 org-level-4
						org-level-5 org-level-6 org-level-7 org-level-8)
                                             (conf-mode font-lock-comment-face font-lock-string-face)
				             (yaml-mode . conf-mode)
				            (yaml-ts-mode . conf-mode)))

This seems to work fine (as the face for the headings is org-level-1 , org-level-2, ...).

Is this the recommended way of doing it? Or am I missing something? Adding here @jdsmith , in case he regards this as something worth mentioning in outli's README.

[minad]

Doesn't outli use outline-1, outline-2 faces and so on instead of the org-level faces?

[rdiaz02]

Not sure, since I haven't tried Outli yet. Maybe @jdtsmith can help?

Sorry if I was ambiguous: it does work perfectly (i.e., jinx checks headings) by adding outline-1 ... to jinx-include-faces. And this is the way to do it, and this is not an ugly kludge? That was my question.

And the second question is (provided the answer to the first is "yes"), should this be mentioned in outli's README?

[jdtsmith]

Thanks, but as usual, you are running and outdated version. ;)

You'd think by now I'd update all of your and Omar's packages before asking. Fixed, complete with a new mnemonic — andnotation.

[minad]

You'd think by now I'd update all of your and Omar's packages before asking. Fixed, complete with a new mnemonic — andnotation.

Yes, please do that. I don't want to sound too annoyed, but it gets a little bit repetitive.

[jdtsmith]

I typically don't update too frequently, because that can require me to hunt down and fix incompatibilities that have been introduced, which I don't often have the time for. But I can make a list of exceptions for high quality packages ;).

[minad]

I typically don't update too frequently, because that can require me to hunt down and fix incompatibilities that have been introduced, which I don't often have the time for. But I can make a list of exceptions for high quality packages ;).

I understand that, but I also value my time. Just don't install any low quality packages. It is quite easy. Packages which break repeatedly are better kicked out. Furthermore the more packages you install, the more potential security holes will open up. Packages from ELPA at least should be relatively safe since changes are inspected from time to time. However even there we don't have proper commit signature checks in place yet.