emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: [bug] new exporter fails on read only files
Date: Thu, 26 Apr 2012 22:06:21 +0930	[thread overview]
Message-ID: <87k412k6uy.fsf@ucl.ac.uk> (raw)

Hello all,

From one of the recent threads (on producing latex files for ACM
publications), I was finally motivated to try the new export engine.  I
have run into a small problem: org-export-dispatch fails if the file is
read only.  I often have read only files as I use RCS as my version
control system for one-off standalone files (as opposed to git or
mercurial for larger projects).

Specifically, I have added

   (require 'org-export)
   (require 'org-e-latex)

to my org customisation.  Then, while visiting a read only file, I try

   M-x org-export-dispatch RET p

and I get the error:

| org-refresh-category-properties: Buffer is read-only: #<buffer proposal.org>

This doesn't happen if I use the old exporter (C-c C-e p).  Also, the
error does not appear if I try the new export engine on a writable
file.  Toggling debug-on-error doesn't actually put me in the debugger
when the error occurs, by the way.

I *think* am running an up to date org (from an hour or so ago) but the
org-version information (auto-generated for my signature) seems
confused...  but maybe that's a problem for another day?


: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs
: using Org-mode version 7.8.06 (release_7.8.09.392.ge0222)

             reply	other threads:[~2012-04-26 12:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 12:36 Eric Fraga [this message]
2012-04-26 12:59 ` [bug] new exporter fails on read only files Bastien
2012-04-27 13:22   ` Eric Fraga
2012-04-27 14:50     ` Bastien
2012-04-27 20:39     ` Nicolas Goaziou
2012-05-03  9:37       ` Eric Fraga
2012-05-03 12:34         ` Nicolas Goaziou
2012-05-06 13:55           ` Eric Fraga
2012-05-06 18:13             ` Nicolas Goaziou
2012-05-06 23:48               ` Eric S Fraga

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:

  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=87k412k6uy.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \


* 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


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).