From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: emacs-orgmode@gnu.org
Subject: Re: error "Can’t expand minibuffer to full frame"
Date: Mon, 22 Feb 2021 11:58:12 -0500 [thread overview]
Message-ID: <3f2f9043a977f05ec2de4c6b845f2fb7@isnotmyreal.name> (raw)
In-Reply-To: <47-6033c300-d-3286d4c0@154476593>
On 2021-02-22 09:42, Florian Lindner wrote:
> Hello,
> I try to configure my org mode (Org mode version ( @
> /lhome/lindnfl/.emacs.d/elpa/org-9.4.4/)) to ask for a note and also
> for a specific property when moving a state to WAIT. For that I use
>
> (setq
> org-todo-keywords '((sequence "NEXT" "TODO" "WAIT(w@)" "|"
> "DONE(d!)" "NODO(n@)"))
> org-log-into-drawer t
> )
>
> (defun flo/org-state-change()
> (when (string= org-state "WAIT")
> (org-set-property "DELEGATED_TO" (read-string "Delegate To: "))))
>
> (setq org-after-todo-state-change-hook 'flo/org-state-change)
>
> However, I suspect the state-change-hook and the note when leaving
> WAIT state conflict:
>
> Error in post-command-hook (org-add-log-note): (error "Can’t expand
> minibuffer to full frame")
>
> resulting in that I am only asked to set the property, note the note.
>
> What can i do about it? I don't really care in which order I enter the
> two note / property.
>
> Thanks,
> Florian
I seem to recall having a similar conflict. In my case, I realized that
the calling script "kept going" instead of waiting for the note entry to
be completed. Therefore, try and make sure that org-log-into-drawer
gets called "last." I am pretty sure this will require digging into Org
internals to see in what order things go.
Sorry if that's vague, it's been a while since I dealt with this. And
it may or may not even actually be your problem.
Cheers,
TRS-80
prev parent reply other threads:[~2021-02-22 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 14:42 error "Can’t expand minibuffer to full frame" Florian Lindner
2021-02-22 16:58 ` TRS-80 [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=3f2f9043a977f05ec2de4c6b845f2fb7@isnotmyreal.name \
--to=lists.trs-80@isnotmyreal.name \
--cc=emacs-orgmode@gnu.org \
/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).