From: Arne Babenhauserheide <arne_bab@web.de>
To: Marco Wahl <marcowahlsoft@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: :completion-function no longer takes a lambda [9.3.6 (9.3.6-elpa @ /home/arne/.guix-profile/share/emacs/site-lisp/)]
Date: Mon, 30 Mar 2020 14:40:05 +0200 [thread overview]
Message-ID: <871rpac8yi.fsf@web.de> (raw)
In-Reply-To: <84a73y8bau.fsf@gmail.com>
Hi Marco,
Marco Wahl <marcowahlsoft@gmail.com> writes:
> Arne Babenhauserheide <arne_bab@web.de> writes:
>> (setq org-publish-project-alist
>> '(("guile-basics"
>> :base-directory "~/eigenes/py2guile"
>> :publishing-directory (concat private-publish-ftp-proj "guile-basics/")
>> :base-extension "org"
>> :publishing-function org-html-publish-to-html
>> :completion-function (lambda () (private-publish-rename-to-index
>> (concat private-publish-ftp-proj "guile-basics/")
>> "guile-basics.html"))
>> :section-numbers nil
>> :with-toc t
>> :html-preamble t
>> :exclude ".*"
>> :include ["guile-basics.org"])))
>>
>>
>> This used to work, but now it breaks with
>>
>> org-publish-projects: Invalid function: lambda
>
> An additional pair of parens should help as workaround. Concretely try
>
> :completion-function ((lambda () (private-publish-rename-to-index
> (concat private-publish-ftp-proj "guile-basics/")
> "guile-basics.html")))
>
> This works since it's possible to use a list of functions also.
>
> I'll commit a fix against master in a second to be able to use a lambda
> instead of a list containing one lambda.
That’s awesome — thank you! ♡
Also thank you for the workaround!
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein
ohne es zu merken
prev parent reply other threads:[~2020-03-30 12:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 7:00 Bug: :completion-function no longer takes a lambda [9.3.6 (9.3.6-elpa @ /home/arne/.guix-profile/share/emacs/site-lisp/)] Arne Babenhauserheide
2020-03-30 9:03 ` Marco Wahl
2020-03-30 12:40 ` Arne Babenhauserheide [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=871rpac8yi.fsf@web.de \
--to=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=marcowahlsoft@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).