Hello, Alex Branham <alex.bran...@gmail.com> writes:
> The issue I see with putting it into org-art.el is that users won't be > able to just call M-x prettify-symbols-mode in an org buffer. They'll > have to do something like > > (require 'org-art) > (add-hook 'org-mode-hook #'org-art-prettify) I don't think users should call M-x prettify-symbols-mode. Instead, they could call `org-art-prettify-buffer', an autoloaded function, which would properly initialize `prettify-symbols-mode' and so on. What mechanism is behind prettification is not important. BTW, we could have a defcustom listings all eye candy `org-art-prettify-buffer' -- or simply `org-prettify-buffer' if the library is called "org-prettify" -- could do (e.g., headlines, bullets...). > prettify-symbols-alist isn't, so I don't think this should be either. Of course. But Org users may want to control what symbol is used. Anyway, I don't have a strong opinion about it. >>> +(defun org-pretty-compose-p (start end match) >>> + "Return t if the symbol should be prettified. >> >> "Non-nil if symbol between START and END should be prettified. >> MATCH is ..." > > Sure thing Actually, I was mistaken: this is a function, not a variable. So, it should be more like: Return non-nil when symbol between START and END is to be prettified. >> Can it be tested somehow? > > I'll look into it Thank you. Regards, -- Nicolas Goaziou 0x80A93738
