Re: [TASK] Rewriting org-pcomplete into capf backend (was: Completions Registry)

2024-12-27 Thread Karthik Chikmagalur
> 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 assumpti

[TASK] Rewriting org-pcomplete into capf backend (was: Completions Registry)

2024-12-27 Thread Ihor Radchenko
Karthik Chikmagalur writes: > As discussed in the last Org meetup, I would like to write a CAPF that > provides completions and annotations when typing in keywords provided by > (loaded) Org libraries. The annotations providing inline documentation > require this information to be available in t

Re: Completions Registry

2024-12-26 Thread Karthik Chikmagalur
operty/babel-header-args documentation via Elisp? i.e. a Completions Registry. As discussed in the last Org meetup, I would like to write a CAPF that provides completions and annotations when typing in keywords provided by (loaded) Org libraries. The annotations providing inline documentation requi

Re: Completions Registry

2024-12-25 Thread Ihor Radchenko
Psionic K writes: > More directly, how can I inject extra values into `org-special-properties' > or elsewhere so that they appear when completing `org-set-property'? > Applications that use non-standard properties don't have a way AFIAK to > inform these completions. org-default-properties --

Re: Completions Registry

2024-12-25 Thread Psionic K
Sorry, my initial thoughts are too far ranging. More directly, how can I inject extra values into `org-special-properties' or elsewhere so that they appear when completing `org-set-property'? Applications that use non-standard properties don't have a way AFIAK to inform these completions.

Re: Completions Registry

2024-12-25 Thread Ihor Radchenko
Psionic K writes: > Not just a problem for dslide but for org in general, any time a > package adds keys to configure blocks or properties, these do not > complete except through dabbrev etc. > ... I am sorry, but it is not clear for me from your email what concrete improvement you want to see.

Completions Registry

2024-12-11 Thread Psionic K
Not just a problem for dslide but for org in general, any time a package adds keys to configure blocks or properties, these do not complete except through dabbrev etc. The keys are likely not already in documents. The only way I can reason to make them visible is to provide functions to register