Michael Albinus writes:
> Eric Schulte writes:
>
>> I'd rather not hard-code the value of "/tmp/". Perhaps you could rework
>> the patch so that it introduces a new customizable variable (including a
>> documentation string) so that users can set the value for their system.
>>
>> Also, please p
Eric Schulte writes:
> I'd rather not hard-code the value of "/tmp/". Perhaps you could rework
> the patch so that it introduces a new customizable variable (including a
> documentation string) so that users can set the value for their system.
>
> Also, please package the patch with git format-p
Alexander Vorobiev writes:
> #+BEGIN_SRC sql :engine postgresql :dir /grid: :results output :
> colnames yes
> select 2+2 as four, 1+1 as one;
> #+END_SRC
>
> #+RESULTS:
> | 4\t2 |
>
> It works! As you see there are still some problems with ob-sql (no
> column names and \t is not parsed correctly
#+BEGIN_SRC sql :engine postgresql :dir /grid: :results output :colnames yes
select 2+2 as four, 1+1 as one;
#+END_SRC
#+RESULTS:
| 4\t2 |
It works! As you see there are still some problems with ob-sql (no column
names and \t is not parsed correctly) but the remote execution seems to be
fixed.
Alexander Vorobiev writes:
> Michael,
Hi Alex,
> * this doesn't work
> #+BEGIN_SRC sql :engine postgresql :dir /grid: :results output
> select 1+2 as three;
> #+END_SRC
>
> /plinkx:grid:/tmp/sql-in-7928arv...done
> psql -A -F " " -f "c:/tmp/sql-in-7928arv" -o "c:/tmp/sql-out-7928Z_E"
> -f c:/t
Michael,
I found that the patch doesn't work for sql code blocks. Here is an example
* this works
#+BEGIN_SRC sh :results output :dir /grid:
ls
#+END_SRC
* this doesn't work
#+BEGIN_SRC sql :engine postgresql :dir /grid: :results output
select 1+2 as three;
#+END_SRC
and here is what appear
Eric Schulte writes:
> I'd rather not hard-code the value of "/tmp/". Perhaps you could rework
> the patch so that it introduces a new customizable variable (including a
> documentation string) so that users can set the value for their system.
Will do, tomorrow. I would even prefer a more gener
Michael Albinus writes:
> Alexander Vorobiev writes:
>
>> Hi Michael,
>
> Hi Alex,
>
>> The patch seems to be working, the only thing I noticed is having
>> http://www.emacswiki.org/emacs/setup-cygwin.el loaded together with
>> the patched ob-core.el makes tramp prepend "/cygwin" to /tmp/. When
Alexander Vorobiev writes:
> Hi Michael,
Hi Alex,
> The patch seems to be working, the only thing I noticed is having
> http://www.emacswiki.org/emacs/setup-cygwin.el loaded together with
> the patched ob-core.el makes tramp prepend "/cygwin" to /tmp/. When I
> disabled (require 'setup-cygwin)
Hi Michael,
The patch seems to be working, the only thing I noticed is having
http://www.emacswiki.org/emacs/setup-cygwin.el loaded together with the
patched ob-core.el makes tramp prepend "/cygwin" to /tmp/. When I disabled
(require 'setup-cygwin) the patch works as expected. Outside of org/babel
Alexander Vorobiev writes:
> Hi Michael,
Hi Alex,
> Here it is.
Thanks. I believe, the following patch shall cure it:
--8<---cut here---start->8---
--- a/lisp/ob-core.el
+++ b/lisp/ob-core.el
@@ -2735,8 +2735,12 @@
value of `temporary-file-directory' tempo
Alexander Vorobiev writes:
> Here is what I have:
>
> ELISP> emacs-version
> "24.3.1"
> ELISP> tramp-version
> "2.2.7"
> ELISP> org-version
> "8.2"
Well, that sounds recent. Could you, please, perform (setq tramp-verbose 6)
prior your test? There will be a Tramp debug buffer, which I would like
Here is what I have:
ELISP> emacs-version
"24.3.1"
ELISP> tramp-version
"2.2.7"
ELISP> org-version
"8.2"
Thanks,
Alex
On Tue, Sep 24, 2013 at 7:57 AM, Michael Albinus wrote:
> Alexander Vorobiev writes:
>
> > The ":results output" doesn't help in my setup (I'm on Windows, the
> > remote syste
Alexander Vorobiev writes:
> The ":results output" doesn't help in my setup (I'm on Windows, the
> remote system is linux, access is via putty/plink)
I do not run Windows, so I cannot reproduce exactly. However, ...
> #+BEGIN_SRC sh :results output :dir /grid:
> ls
> #+END_SRC
>
> executing Sh
The ":results output" doesn't help in my setup (I'm on Windows, the remote
system is linux, access is via putty/plink)
#+BEGIN_SRC sh :results output :dir /grid:
ls
#+END_SRC
executing Sh code block...
Tramp: Encoding region using function `base64-encode-region'...done
Tramp: Decoding region in
thanks! so the ":results output" does the trick.
On Thu, Aug 29, 2013 at 10:25 AM, Loris Bennett
wrote:
> Johannes Rainer writes:
>
> > dear all,
> >
> > I have some computation intense R-code that I want to run remotely on my
> server,
> > and, according to the org manual that should be poss
Johannes Rainer writes:
> dear all,
>
> I have some computation intense R-code that I want to run remotely on my
> server,
> and, according to the org manual that should be possible with the ":dir"
> parameter. so I went on and tried the following (user/server masked):
>
> #+BEGIN_SRC R :dir /xx
dear all,
I have some computation intense R-code that I want to run remotely on my
server, and, according to the org manual that should be possible with the
":dir" parameter. so I went on and tried the following (user/server masked):
#+BEGIN_SRC R :dir /xx@xxx:
system("hostname")
#+END_SRC
whe
18 matches
Mail list logo
