From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ken Mankoff Subject: Re: Code, Sessions, and org-edit-special Date: Sat, 22 Nov 2014 19:17:49 -0500 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34503) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XsKsL-0003K8-03 for emacs-orgmode@gnu.org; Sat, 22 Nov 2014 19:18:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XsKsB-0006j9-Tl for emacs-orgmode@gnu.org; Sat, 22 Nov 2014 19:18:00 -0500 Received: from mail-qc0-x22d.google.com ([2607:f8b0:400d:c01::22d]:48176) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XsKsB-0006j5-PB for emacs-orgmode@gnu.org; Sat, 22 Nov 2014 19:17:51 -0500 Received: by mail-qc0-f173.google.com with SMTP id i17so5418337qcy.32 for ; Sat, 22 Nov 2014 16:17:51 -0800 (PST) Received: from gorgonzola (c-71-58-77-153.hsd1.pa.comcast.net. [71.58.77.153]) by mx.google.com with ESMTPSA id r4sm8350699qak.9.2014.11.22.16.17.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Nov 2014 16:17:50 -0800 (PST) In-reply-to: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi List, A simpler phrasing of my previous question. How do I find out if an Org function, `org-ctrl-c-ctrl-c`, was called somewhere up the stack. I'm trying to modify a function "python-shell-get-process-name", but I don't want it to be modified when somewhere, possibly far upstream, Org is happening. Perhaps this is the wrong approach? Rather than examining the stack, should I just be checking if Org is the active mode? But I think when a code segment is executed, a temp file is created and Org isn't the active mode? Thanks, -k. * On 2014-11-21 at 18:38, Ken Mankoff wrote: > Hi List, > > I'm trying to improve my code workflow. I use python and sessions. I'd > like to be able to run code in the session even if I'm editing/viewing > the code via `org-edit-special`. Furthermore, when I edit code outside > of Org, I'd like to have sessions, that is, optionally one Python > session per source file. This allows me to edit different code for > different projects in different folders on virtual desktops, etc. > > I've solved the non-Org part of this with the following one re-defined > and one new function: > > #+BEGIN_SRC emacs-lisp > (defun elpy-shell-get-or-create-process () > "Get or create an inferior Python process for current buffer and return it." > (let* ((bufname (format "*%s*" (kdm/python-shell-get-process-name t))) > (proc (get-buffer-process bufname))) > (if proc > proc > (run-python (python-shell-parse-command) t nil) ;; DEDICATED! > (get-buffer-process bufname)))) > > (defun kdm/python-shell-get-process-name (dedicated) > (if (boundp 'py-buf-proc-name) > (format "%s" py-buf-proc-name) > (setq-local py-buf-proc-name > (format "%s" > (completing-read "Python session name: " > nil nil nil (buffer-name) nil (buffer-name))) > ))) > #+END_SRC > > Now when I C-c C-c in a buffer without an associated Python session, I'm > prompted for a name (defaulting to the buffer-name). I provide a session > name, and then all future C-c C-c's for that buffer are executed there. > > This is good for Org. If I name a session "foo", I can edit code in > org-edit-special, assign Python session "foo", and execute code in a > session either from the org buffer or from the temp .py file. In theory. > > But since I've call kdm/pythons-shell-get-process-name, if I try to C-c > C-c in a #+BEGIN_SRC section, it no longer works. I'm prompted for a > session name (I should not be). Whatever I enter is ignored, and the > code is executed either in a temporary "*Python*" if no :session, or in > the :session name as it should be. > > How can I find out inside my `kdm/python-shell-get-process-name` if it > was called from Org, in which case I would implement the original > version. > > Thanks, > > -k.