-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Org exporter packages to follow a different namespace convention #89
Comments
Thanks for filing this. I'm not super keen to consider a PR for this, because whatever the example in |
I'd like to do the right thing too. So I have raised this question on the Org mailing list. |
From Nicolas's reply:
I don't understand that reason. Does anyone run Org on DOS? Org filenames already exceed 8.3, so what systems would break with |
I agree. Though, I like the convention of And about why to use the
|
DOS is absolutely not a compelling reason, but if the Org guys want to stick to that, then fine. The wider community doesn't need to. I read the |
The For instance, in ;; Copy specific buffer local variables and variables set
;; through BIND keywords.
,@(let ((bound-variables (org-export--list-bound-variables))
vars)
(dolist (entry (buffer-local-variables (buffer-base-buffer)) vars)
(when (consp entry)
(let ((var (car entry))
(val (cdr entry)))
(and (not (memq var org-export-ignored-local-variables))
(or (memq var
'(default-directory
buffer-file-name
buffer-file-coding-system))
(assq var bound-variables)
(string-match "^\\(org-\\|orgtbl-\\)"
(symbol-name var)))
;; Skip unreadable values, as they cannot be
;; sent to external process.
(or (not val) (ignore-errors (read (format "%S" val))))
(push `(set (make-local-variable (quote ,var))
(quote ,val))
vars)))))) That's only one place I know where having a variable with |
I was suggesting this exception for Org exporter ( |
I also have this problem with smartparens where I use I use (defgroup smartparens ()
"Smartparens minor mode."
:group 'editing
:prefix "sp-") Maybe if this is defined we could pick up the |
The prefix defined like that should still match the overall conventions, though, so I'm not keen to do anything special with it. I don't really want to add a user-defined back door that could be used to work around unconventional prefixes. Several popular packages have historical prefixes that we shouldn't now encourage: Having reflected on this specific issue, though, I would be happy to have a PR that allowed |
Valid mappings are stored in `package-lint--allowed-prefix-mappings`. Its default value is: '(("ox-" . ("org-")) ("ob-" . ("org-"))) This means that in packages starting with "ox-" and "ob-", functions and symbols starting with "org-" are allowed. After the mapping, the symbols still must match the whole package match. For example, in package "ox-foobar", symbols starting with "org-foobar" will be allowed. Fixes purcell#89.
Valid mappings are stored in `package-lint--allowed-prefix-mappings`. Its default value is: '(("ox-" . ("org-")) ("ob-" . ("org-"))) This means that in packages starting with "ox-" and "ob-", functions and symbols starting with "org-" are allowed. After the mapping, the symbols still must match the whole package match. For example, in package "ox-foobar", symbols starting with "org-foobar" will be allowed. Fixes #89.
Following the examples of in-built Org exporters, for an Org exporter
ox-FOO
, the namespace prefix used by the variables and functions in the package isorg-FOO
.An example from
ox-html
:[Link]
Without this namespace prefix rule exception, I get these errors on doing
package-link-current-buffer
on my recentox-hugo
submission:The text was updated successfully, but these errors were encountered: