bug / regression: C-x C-s is broken in org-edit-special

Previously, C-x C-s in an org-edit-special buffer (invoked via C-')
would save the underlying org buffer (provided (setq
org-src-window-setup (quote current-window)) was set; it was buggy
with other settings, see
http://thread.gmane.org/gmane.emacs.orgmode/50979 for discussion).
Currently, C-x C-s prompts to save the temporary source edit buffer in
a new file, which is almost certainly not what the user intends.  I
hope someone can look into this, C-x C-s shouldn't be broken in any
context.

This broke some time between commit
fc93b6f34071703d5a154a51540f3f4e3f15b8a2 (Jan. 18) and this week,
_possibly_ as a result of the change ensuring that buffer-file-name is
nil in temporary org-src buffers.  Buffer-file-name not being nil in a
temp buffer is incorrect behavior, but in this context having C-x C-s
not working is a much worse behavior, so perhaps that change ought to
be reverted if it's the culprit.

--Leo

Pushing *.org.gpg file to MobileOrg without prompting for the password

Links to Gnus articles don't export correctly

Hello,

When I export (to HTML) a link to a gnus article, for example:

[[gnus:inbox#A1B422BC2355834C81A44135AF25E4392CF4254F <at> domain.com][email]]

...it turns into this:

<gnus:inbox#A1B422BC2355834C81A44135AF25E4392CF4254F <at> domain.com>

How can I make it export like a normal link?  It's okay if the link is
broken.  I just don't want it exporting a long string.

I'm using Org-mode version 7.8.02 and GNU Emacs 23.3.1.

Thanks,
Jason

SO question on dynamic arguments

Multiple/sticky agenda buffers branch updated

In case anyone is trying out git <at> github.com:7max/org-mode.git sticky
agendas functionality, I pushed some bug fixes.

M-x org-toggle-sticky-agenda now works correctly when its turned on
when agenda buffer already exists.

When refreshing agenda buffers, prefix format was being pickup up from
the last time non-sticky agenda was generated, instead of the agenda
that is being refreshed.

[PATCH] Fix J in agenda when clock out hook clocks in again

* org-clock.el (org-clock-out): Do not delete the current clocking task
when org-clock-out-hook clocks in another task

My clock out hook keeps the clock running by automatically clocking in
a new task (the parent task, or the default task).  This sets a new
clocking task which was then clobbered at the end of org-clock-out
so that J in the agenda would return

    "No running clock, use `C-c C-x C-j' to jump to the most recent one"

We now detect that another task is clocked in and skip clearing the
org-clock-current-task variable used by the agenda to determine if
the clock is currently running.
---
 lisp/org-clock.el |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/lisp/org-clock.el b/lisp/org-clock.el
index a1df776..7dff094 100644
--- a/lisp/org-clock.el
+++ b/lisp/org-clock.el
@@ -1387,7 +1387,8 @@ If there is no running clock, throw an error, unless FAIL-QUIETLY is set."
 	  (message (concat "Clock stopped at %s after HH:MM = " org-time-clocksum-format "%s") te h m
 		   (if remove " => LINE REMOVED" ""))
           (run-hooks 'org-clock-out-hook)
-	  (org-clock-delete-current))))))
+	  (unless (org-clocking-p)
+	    (org-clock-delete-current)))))))

 (add-hook 'org-clock-out-hook 'org-clock-remove-empty-clock-drawer)

--

-- 
1.7.9.48.g85da4d

Collaborative edition?

Hi, Org friends.

Let me send this message in "chat mode", nothing important in here! 

Before Org mode, I was using a mix of Tomboy and Workflowy.  Tomboy is a
note taking application, which I used under GNOME, and Workflowy.com is
an outlining Web service.  I used and liked both intensely, each is full
of various virtues.

There is one thing in Workflowy that I miss a bit in Org mode, and this
is the capability of collaborative edition.  I once much used it with
some of my co-workers.  I presume such things have been discussed to
death already on this mailing list?  Did some consensus emerged?

My question is a rhetorical one, as I'm pretty sure my co-workers are
never going to switch to Emacs, and anyway, collaboration is managed
differently for the time being.  Yet, I'm curious, so my question.  And
who knows, ideas sometimes germinate while being exchanged! 

François

issue with babel R evaluate session vs external process

still a beginner, and maybe therefore, in my setup (release is: 7.8.03,
emacs 23.2.1) the following occurs

-------------org.snip-----------------------
* here it works: org-ctrl-c-ctrl-c and export

#+begin_src R :results output :exports results
  foo=matrix(1:2)
  foo
#+end_src

#+RESULTS:
:      [,1]
: [1,]    1
: [2,]    2

* here it does not:

#+begin_src R :results output :exports results :session *R*
  foo=matrix(3:8)
  foo
#+end_src

the buffer *R* shows this:

> 'org_babel_R_eoe'
[1] "org_babel_R_eoe"
----------------org.snap------------------

some debugging revealed this:

ELISP> (org-babel-R-evaluate-session "*R*" "foo=matrix(1:2)\nfoo" 'output '("output" "replace")
nil nil)
*** Eval error ***  
ELISP> (org-babel-R-evaluate-external-process  "foo=matrix(1:2)\nfoo" 'output '("output"
"replace") nil nil)
"     [,1]\n[1,]    1\n[2,]    2\n"

but strange-enough when I try to edebug org-babel-R-evaluate-session, I
 get an error:

Symbol's value as variable is void: edebug-after

can someone explain this? 

thanks!
tomy

--

-- 
sent from nil

Setting multiple variables for code blocks in one property drawer

Hi,

after following the discussion about the new BABEL syntax I was under
the impression that the following should work to set two variables in
one PROPERTIES drawer:

:PROPERTIES:
:var: foo=1
:var+: bar=2
:END:

However, the definition of bar is ignored. It turns out that there can
only be one :var: or :var+: entry in a drawer and the latter can only be
used to append to inherited entries, but not to those defined in the
same drawer. Is this the intended behavior? How would I define multiple
variables in a drawer (except for putting them all on one line)?

Thanks,
Viktor

Journalling certain BBDB contacts in org

Does anyone have something which potentially auto creates a journal
entry with an org link back to sent items in gnus for certain email
addresses which, present in bbdb, are somehow tagged in bbdb as
needing journalling? Failing that some method to query sent items
directly and auto insert journal entries in the agenda from the sent
date and recipient address.

worg access source

in worg it would be great if (as in emacs muse) there was a link to the
underlying .org file which was used to generate the page. my naiive
attempt to catch a glimpse of the source of

http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.html

was to browse-url

http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.org

but this page just says "nginx"

(if beginner-has-not-read-the-documentation-carefully-question-p "sorry"
"thanks")

tomy

--
sent from nil