emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Loris Bennett <loris.bennett@fu-berlin.de>
Cc: Achim Gratz <Stromeko@nexgo.de>, emacs-orgmode@gnu.org
Subject: Re: Erroneous "No such file or directory" with babel and remote dir
Date: Wed, 14 Nov 2012 00:04:11 -0500	[thread overview]
Message-ID: <7557.1352869451@alphaville> (raw)
In-Reply-To: Message from "Loris Bennett" <loris.bennett@fu-berlin.de> of "Tue\, 13 Nov 2012 16\:16\:31 +0100." <87fw4dlei8.fsf@slate.zedat.fu-berlin.de>

Loris Bennett <loris.bennett@fu-berlin.de> wrote:

> Achim Gratz <Stromeko@nexgo.de> writes:
> 
> > Loris Bennett writes:
> >> OK, I must have goofed.  What I did after starting the bisection was
> >>
> >> - run 'make autoload'
> >> - open test file in emacs with minimal .emacs
> >> - test
> >> - end emacs
> >> - mark bisection good or bad
> >>
> >> I then repeated this for the next commit.
> >
> > This would be the correct thing to do, yes.
> >
> >> Is something missing here, or did I just incorrectly mark a commit?
> >
> > I really don't know, I'm just guessing… :-)
> >
> > It may be more informative if you traced the invocation of the remote
> > execution in both a failing and a working version in the debugger and
> > look for any differences as the arguments are cobbled together.  Once
> > you find where an how these diverge it would be much easier to find the
> > code that is responsible for it (if it wasn't glaringly obvious from the
> > trace already).
> >
> >
> > Regards,
> > Achim.
> 
> So just as a reminder:
> 
> Back in the days of release_7.01h, the following used to work:
> 
> ,------------------------------------------
> | #+begin_src sh :dir /loris@othercomputer:
> | hostname
> | #+end_src
> `------------------------------------------
> 
> Currently it produces the error:
> 
> ,---------------------------------------------------
> | apply: Wrong type argument: number-or-marker-p, ""
> `---------------------------------------------------
> 
> I have had another go at bisecting this problem and came up with this:
> 
> ,-------------------------------------------------------------------------------------------------------------
> | 9c878a8290c071fbe5e97bc33c300ef2f07d6153 is the first bad commit
> | commit 9c878a8290c071fbe5e97bc33c300ef2f07d6153
> | Author: Dan Davison <davison@stats.ox.ac.uk>
> | Date:   Mon Aug 30 09:34:05 2010 -0700
> | 
> |     babel: Fix temporary file processing in the remote execution case.
> |     
> |         * ob.el (org-babel-temp-file): Don't use babel temporary
> |         directory in remote case; use make-temp-file with remote file
> |         name so that temp file is guaranteed not to exist previously
> |         on remote machine.
> |         (org-babel-tramp-localname): New function to return local name
> |         portion of possibly remote file specification
> |     
> |         * ob-R.el (org-babel-R-evaluate-external-process): Respond to
> |         changes in `org-babel-temp-file'; pass local file name to
> |         remote R process.
> |         (org-babel-R-evaluate-session) Respond to
> |         changes in `org-babel-temp-file'; pass local file name to
> |         remote R process.
> | 
> | :040000 040000 b31e072cf6b2951e95b7956d907303e7a04a8cfd 5f794ada52cceb0614fe7962a399f7e549759003 M      lisp
> `-------------------------------------------------------------------------------------------------------------
> 
> Does that help anyone any further?
> 

I don't think so: afaict, both 7.01h (which did not contain this patch)
and 7.02 (which did) do the right thing (at least with your simple
script above). Something else broke it.

[I've been wrong about these things before so before Achim asks, I
did

  git tag --contains 9c878a8290c071fbe5e97bc33c300ef2f07d6153

and used its output as a basis of the above statement. I think (hope?)
it's correct.]

> Loris
> 
> PS: I am amazed there aren't any more peasants like myself with torches
> and pitchforks beating on the gates of Castle Org about this - remote
> execution is/was such great feature!
> 

Agreed, but Dan Davison (the principal contributor of the remoting code)
is gone from Castle Org (as you put it), Eric S. is busy, and nobody
else has stepped up to the plate. I've made fitful attempts to debug it,
but have had no success: I've never looked at the code in detail and I
don't have much time either.

So how about becoming a resident of Castle Org rather than beating on
the gates? There's glory galore if you fix it - and you get to scratch
your itch too :-)

Nick

  reply	other threads:[~2012-11-14  5:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 14:36 Loris Bennett
2012-09-10 14:42 ` Loris Bennett
2012-09-19  7:37 ` Bastien
2012-09-25 14:11   ` Loris Bennett
2012-09-25 15:30     ` Memnon Anon
2012-09-25 19:54     ` Achim Gratz
2012-09-26  6:56       ` Loris Bennett
2012-09-26  7:14         ` Bastien
2012-09-26 12:10   ` Loris Bennett
2012-09-26 18:09     ` Achim Gratz
2012-09-26 18:38       ` Nick Dokos
2012-09-26 18:57       ` Loris Bennett
2012-09-26 20:06         ` Achim Gratz
2012-09-27  6:38           ` Loris Bennett
2012-09-27 17:22             ` Achim Gratz
2012-11-13 15:16               ` Loris Bennett
2012-11-14  5:04                 ` Nick Dokos [this message]
2012-11-14  6:23                   ` Nick Dokos
2012-11-14  7:48                     ` Loris Bennett
2012-11-14 19:47                     ` Nick Dokos
2012-11-15  6:55                     ` Nick Dokos
2012-11-15 18:31                       ` Achim Gratz
2012-11-14  7:28                   ` Loris Bennett
2012-11-13 15:39               ` Loris Bennett

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=7557.1352869451@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=loris.bennett@fu-berlin.de \
    /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).