From: Eric S Fraga <esflists@gmail.com>
To: Lawrence Bottorff <borgauf@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Bizarre gnuplot file creation error
Date: Thu, 09 Nov 2017 18:07:11 +0000 [thread overview]
Message-ID: <87zi7ve374.fsf@delle7240.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <CAFAhFSXQmbn9K2g9mEgUbx4pZG+wvn7ny14azev4A_3tH1nRzw@mail.gmail.com> (Lawrence Bottorff's message of "Tue, 7 Nov 2017 09:42:36 -0500")
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
On Tuesday, 7 Nov 2017 at 09:42, Lawrence Bottorff wrote:
> Still haven't tracked down the exact steps to reproduce this problem, but
> it happened again recently -- and starting a new emacs from the command
> line solved it, i.e., my usual daemon-run emacs seems to be "crudding up"
> somehow.
The issue is that gnuplot mode uses a gnuplot session (in the *gnuplot*
buffer). If you start gnuplot by executing a src block somewhere in
your file system and then move to another org file elsewhere in the file
system, the same *gnuplot* buffer will be used, placing the file in the
wrong place as far as the second file is concerned. The working
directory of the gnuplot buffer is not updated.
The immediate solution is to kill the *gnuplot* buffer... messy but works.
The proper solution would be to update ob-gnuplot to change the working
directory at every invocation of gnuplot to be the directory where the
org file is found. (gnuplot has a "cd" command for this purpose)
--
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.2-117-g5b2b8f
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2017-11-09 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 17:05 Bizarre gnuplot file creation error Lawrence Bottorff
2017-11-07 14:42 ` Lawrence Bottorff
2017-11-09 18:07 ` Eric S Fraga [this message]
2017-11-16 21:40 ` Nicolas Goaziou
2017-11-17 7:45 ` Eric S Fraga
2017-11-22 14:03 ` Eric S Fraga
2017-11-28 23:21 ` Nicolas Goaziou
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=87zi7ve374.fsf@delle7240.chemeng.ucl.ac.uk \
--to=esflists@gmail.com \
--cc=borgauf@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).