Hello,<div><br></div><div>I have observed that even though the exporter backend package names begin with ox-, all the variables and functions inside still start with org-.</div><div><br></div><div>Is there a strong reason to do so? Or was that to prevent the older org-html, etc packages from breaking when they got renamed to ox-html, etc?</div><div><br></div><div>So the question is if the new export backends should also follow the same convention. </div><div><br></div><div>This question came up because if the ox- packages follow the convention used in core, they fail the lint check done by an external package called package-lint[1]. The lint checkers expects all variables and functions in a package FOO to have FOO- prefix. Here[2] the discussion on that package&#39;s GitHub issue thread. </div><div><br></div><div>PS: I believe it is the same case with ob- packages. </div><div><br></div><div>[1]: <a href="https://github.com/purcell/package-lint">https://github.com/purcell/package-lint</a></div><div>[2]: <a href="https://github.com/purcell/package-lint/issues/89">https://github.com/purcell/package-lint/issues/89</a></div><div><br></div><div>Thanks. </div><div dir="ltr">-- <br></div><div class="gmail_signature" data-smartmail="gmail_signature"><p dir="ltr">Kaushal Modi</p>
</div>