From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: stardiviner <numbchild@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: [RFC] Let Org Mode's completion support all Babel header arguments
Date: Wed, 13 May 2020 19:04:02 +0200 [thread overview]
Message-ID: <87pnb7bwcd.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87lflwuq9o.fsf@gmail.com> (stardiviner's message of "Wed, 13 May 2020 17:40:19 +0800")
Hello,
stardiviner <numbchild@gmail.com> writes:
> Add a test for Babel src block languages and header arguments.
Thank you.
> I'm wandering how to complete header argument values? Do you have any
> hints?
You can use, again, `org-babel-common-header-args-w-values' for some
parameters. However, most of them specify `:any', which means the value
can be anything, and, therefore, cannot be completed.
You may want to have a look at `org-lint-wrong-header-value' for an
example on how to treat
> +(ert-deftest test-org-pcomplete/src-block ()
> + "Test Babel src block header arguments completion."
"source block" instead of "src block".
> + (should
> + (string-prefix-p
> + "#+begin_src emacs-lisp"
> + (org-test-with-temp-text "#+begin_src emac<point>"
> + (pcomplete)
> + (buffer-string))
> + t))
You can remove the t
> + (should
> + (string-prefix-p
> + "#+begin_src emacs-lisp :session"
> + (org-test-with-temp-text "#+begin_src emacs-lisp :sess<point>"
> + (pcomplete)
> + (buffer-string))
> + t)))
Ditto.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2020-05-13 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 7:33 [RFC] Let Org Mode's completion support all Babel header arguments stardiviner
2020-05-10 12:35 ` Nicolas Goaziou
2020-05-12 13:48 ` stardiviner
2020-05-12 14:39 ` Nicolas Goaziou
2020-05-13 9:40 ` stardiviner
2020-05-13 17:04 ` Nicolas Goaziou [this message]
2020-05-14 4:05 ` stardiviner
2020-05-14 12:59 ` Nicolas Goaziou
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnb7bwcd.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=numbchild@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.