emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ken Mankoff <mankoff@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org Mailing List <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] Add :eval only-manual to babel blocks
Date: Wed, 16 Oct 2019 13:36:28 +0200	[thread overview]
Message-ID: <878spk7whv.fsf@gmail.com> (raw)
In-Reply-To: <87r23d9dqn.fsf@nicolasgoaziou.fr>

Hi Nicolas,

On 2019-10-16 at 12:38 +02, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote...
> Note that what you want, i.e., to distinguish behaviour depending on
> the location of the call stack is cheesy, at best. Think about macros,
> user-defined functions, etc.

Yes, it felt a bit hackish. But I'm new to this level of Org coding.

> The Emacs' answer to this is usually to check if call to a function is
> interactive, or not.

Can you provide a more obvious hint? :) I've read the documentation on called-interactively-p but have not had success yet with that function. The bottom of that doc string suggests this is not an appropriate use for it.

I've read the manual part on "Distinguish Interactive Calls"[1] but working through those examples I can't get deeper called functions to know if the nth-parent was called interactively or not.

Would you solve this issue somewhere completely different? Like an advice around the org-ctrl-c-ctrl-c function or something?

Thanks,

  -k.

[1] https://www.gnu.org/software/emacs/manual/html_node/elisp/Distinguish-Interactive.html

  reply	other threads:[~2019-10-16 11:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14  7:10 [PATCH] Add :eval only-manual to babel blocks Ken Mankoff
2019-10-16  6:05 ` Ken Mankoff
2019-10-16 10:38   ` Nicolas Goaziou
2019-10-16 11:36     ` Ken Mankoff [this message]
2019-10-16 16:07       ` Nicolas Goaziou
2019-10-16 21:10     ` Ken Mankoff
2019-10-17 12:17       ` 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

  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=878spk7whv.fsf@gmail.com \
    --to=mankoff@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).