emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Michael Eliachevitch <m.eliachevitch@posteo.de>
To: emacs-orgmode@gnu.org
Subject: Re: discovering export (and other) keywords?
Date: Thu, 21 Jul 2022 11:51:14 +0000	[thread overview]
Message-ID: <87mtd2hdrg.fsf@posteo.de> (raw)
In-Reply-To: <tb98uu$lad$1@ciao.gmane.io>

[-- Attachment #1: Type: text/plain, Size: 1324 bytes --]


On 2022-07-20 at 23:02 +07, Max Nikulin <manikulin@gmail.com> wrote:
> On 18/07/2022 19:10, kevinbanjo wrote:
>> Also, for various elements (e.g. begin_src emacs-lisp, begin_export html,
>> etc...) how do I discover what the acceptable keywords are, preferably without
>> only having to go thru the manual pages?
> For source blocks you may try `org-babel-view-src-block-info' (C-c C-v I, C-c
> C-v TAB).

For source blocks I found the  company-org-block [1] package helpful to get auto-completion candidates for code-block keywords.

Recently I moved away from using company and just use completion-at-point-functions with corfu [2] for selecting the completion candidate. Luckily, the "cape" package of the same developer has an experimental company-adapter [3] to convert company backends to completion-at-point functions and this seemeed to work well for me with company-org-block.

I just wonder if it wouldn't be better to have a package providing completion-at-point-functions for that from the start and if this couldn't be provided by org.

Cheers, Michael

[1]: https://github.com/xenodium/company-org-block
[2]: https://github.com/minad/corfu
[3]: https://github.com/minad/cape#company-adapter

Michael Eliachevitch
Public PGP Key: https://keyoxide.org/hkp/546908c782383ad0e7d894ec1b8f95c8125dce31

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]

      reply	other threads:[~2022-07-21 12:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 12:10 discovering export (and other) keywords? kevinbanjo
2022-07-19  6:57 ` Alain.Cochard
2022-07-20  7:29   ` Ihor Radchenko
2022-07-20 16:02 ` Max Nikulin
2022-07-21 11:51   ` Michael Eliachevitch [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mtd2hdrg.fsf@posteo.de \
    --to=m.eliachevitch@posteo.de \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).