From: Eric Schulte <eric.schulte@gmx.com>
To: nicholas.dokos@hp.com
Cc: Loris Bennett <loris.bennett@fu-berlin.de>, emacs-orgmode@gnu.org
Subject: Re: Invalid function: with-parsed-tramp-file-name with Perl
Date: Thu, 20 Sep 2012 12:29:50 -0600 [thread overview]
Message-ID: <87k3vo35up.fsf@gmx.com> (raw)
In-Reply-To: <14004.1348162579@alphaville> (Nick Dokos's message of "Thu, 20 Sep 2012 13:36:19 -0400")
Nick Dokos <nicholas.dokos@hp.com> writes:
> Nick Dokos <nicholas.dokos@hp.com> wrote:
>
>> I haven't chased it all the way down because the reverts are
>> making my head spin, but it may be that somehow the above commit
>> got lost somewhere - or it got fixed and then the big revert lost
>> the fix. Maybe Eric or Bastien remembers what happened.
>>
>
> This doesn't make sense (I blame the head-spinning reverts :-) ), so let
> me try again: Eric's commit broke it between 7.8.03 and 7.8.04. It got
> fixed somehow, either because of a revert or because some fix was
> actually applied, I don't know which. It was working until 7.8.10 and
> then Bastien's commit reverted to (broken) 7.8.04, so from 7.8.11- on
> the breakage exists.
>
> So if there was a fix, we need to find it and reapply. If not, someone
> (presumably Eric) will need to take a look and possibly develop a fix.
>
I've spent some time looking at this.
A couple of things are happening. Back in the time of 7.8.03 and
7.8.04, the org-babel-execute:sh call happened in such a context that
all external function calls would take place on the remote machine if
the :dir header specified a tramp path to a remote machine. This is
true both before and after my 5cb80c7e5b9bca commit.
However this has changed between then and now, meaning that reverting
the 5cb80c7e5b9bca commit now will not solve this problem. In the
current branch there is no change of context s.t. external calls made by
the org-babel-execute:* functions happen by default on the remote
machine. I think this is the real problem. Perhaps it would be
possible to git bisect with another language like perl?
Sorry I'm not more help here, the remote-execution magic was mainly
implemented by Dan Davison.
Best,
>
> Nick
>
>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2012-09-20 18:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 11:54 Invalid function: with-parsed-tramp-file-name with Perl Loris Bennett
2012-06-21 13:53 ` Nick Dokos
2012-06-21 14:51 ` Loris Bennett
2012-06-21 15:13 ` Nick Dokos
2012-06-25 7:05 ` Loris Bennett
2012-09-18 14:04 ` Loris Bennett
2012-09-19 7:45 ` Bastien
2012-09-19 9:28 ` Loris Bennett
2012-09-19 9:59 ` Bastien
2012-09-19 10:29 ` Loris Bennett
2012-09-19 13:49 ` Nick Dokos
2012-09-19 18:52 ` Achim Gratz
2012-09-19 19:51 ` Nick Dokos
2012-09-20 14:12 ` Loris Bennett
2012-09-20 15:11 ` Nick Dokos
2012-09-20 15:30 ` Nick Dokos
2012-09-20 17:21 ` Nick Dokos
2012-09-20 17:36 ` Nick Dokos
2012-09-20 18:29 ` Eric Schulte [this message]
2012-09-20 19:18 ` Achim Gratz
2012-09-20 20:51 ` Nick Dokos
2012-09-20 21:00 ` Achim Gratz
2012-09-20 22:26 ` Nick Dokos
2012-09-21 17:49 ` Achim Gratz
-- strict thread matches above, loose matches on Subject: below --
2012-09-22 5:05 Nick Dokos
2012-09-22 6:41 ` Achim Gratz
2012-09-22 6:57 ` Bastien
2012-09-22 7:03 ` Achim Gratz
2012-09-22 8:19 ` Bastien
2012-09-22 11:57 ` Achim Gratz
2012-09-22 16:14 ` Bastien
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=87k3vo35up.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=emacs-orgmode@gnu.org \
--cc=loris.bennett@fu-berlin.de \
--cc=nicholas.dokos@hp.com \
/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).