> Yup. > We may simply define a new special variable like, > > (defvar org-babel-header-arg-docs:sqlite > '((db "...." > (header "....") > ...)) > "Description of sqlite-specific header arguments.") > > and global > > (defvar org-babel-header-args-docs ...)
I'll work with this assumption. > As I said during the meetup, this design is (hopefully) temporary. > Sooner or later, I hope to switch things to ox.el-like backend > definition like `org-export-define-backend'. But that may or may not > happen, so we should not wait for it. Okay. > It would also be nice to add documentation for export options, just > like for header arguments. That documentation could also be used in the > completion. (for #+EXPORT_KEYWORD and #+OPTIONS: foo:val) Yes, available export options are a frequent source of frustration. Other candidates are - Special properties assigned meaning by packages -- Org Noter is a good example. - ATTR_* keywords and allowed values. - Citation and bibliography options -- partially covered by export options. Karthik
