all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Robert Pluim <rpluim@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Headline generation as in diary?
Date: Fri, 04 Sep 2020 02:04:45 +0800	[thread overview]
Message-ID: <87wo1alosi.fsf@localhost> (raw)
In-Reply-To: <87imcukd60.fsf@web.de>

> I didn't know that eval specs support multi-line sexps, but seems that
> works, so I can indeed use this.  Thanks for the suggestion.

Hmm. According to manual, it should support multi-line string. Not sure
about sexps.

In the worst case when you absolutely want multi-line sexp to be really
multi-line and that is also not possible in file-local eval, you can
define your sexp in a named src block. Then, you can execute the named
block using file-local eval statement calling the following function:

(defun org-link-babel-follow (name &optional return-info)
  "Run src block NAME.
The NAME is parsed as in #+CALL: specification.
The src block should be in the same org file."
  (let* ((call (with-temp-buffer
		 (interactive)
		 (org-mode)
		 (insert "#+CALL: " (format "%s" (org-link-unescape name)) "\n")
		 (beginning-of-buffer)
		 (org-element-babel-call-parser (point-max) (list (point-min)))
		 ))
	 (info (org-babel-lob-get-info call)))
    (if return-info
	info
      (flet ((org-babel-insert-result (result &optional result-params info hash lang) nil))
	(org-babel-execute-src-block nil info)))))

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> I do not think there is support of multi-line planning everywhere.
>
> I see.
>
>> You can always use file-local definition at the beginning or end of your
>> org file. Below is an example of local definition at the end of an org
>> file.
>>
>> # Local Variables:
>> # eval: (defun your-function () (sexp))
>
> I didn't know that eval specs support multi-line sexps, but seems that
> works, so I can indeed use this.  Thanks for the suggestion.
>
> Michael.


  reply	other threads:[~2020-09-03 18:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01 14:34 Headline generation as in diary? Michael Heerdegen
2020-09-01 15:10 ` Eric S Fraga
2020-09-01 15:18   ` Michael Heerdegen
2020-09-01 15:28     ` Michael Heerdegen
2020-09-01 16:10     ` Robert Pluim
2020-09-01 16:17       ` Eric S Fraga
2020-09-01 16:51         ` Robert Horn
2020-09-01 21:56       ` Michael Heerdegen
2020-09-02  6:54         ` Robert Pluim
2020-09-02 13:45           ` Michael Heerdegen
2020-09-02 15:00             ` Robert Pluim
2020-09-02 22:51               ` Michael Heerdegen
2020-09-03  7:14                 ` Robert Pluim
2020-09-03 13:14                   ` Michael Heerdegen
2020-09-03 13:35                     ` Ihor Radchenko
2020-09-03 14:01                       ` Michael Heerdegen
2020-09-03 15:31                         ` Ihor Radchenko
2020-09-03 17:01                           ` Michael Heerdegen
2020-09-03 18:04                             ` Ihor Radchenko [this message]
2020-09-03 18:37                               ` Michael Heerdegen
2020-09-03 14:06                       ` Robert Pluim
2020-09-03 14:46                         ` Michael Heerdegen
2020-09-03 15:17                           ` Robert Pluim
2020-09-03 15:34                         ` Ihor Radchenko
2020-10-28 17:12 ` Michael Heerdegen

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=87wo1alosi.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=rpluim@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.