From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@gnu.org>
Subject: Re: [bug] new exporter fails on read only files
Date: Thu, 26 Apr 2012 14:59:55 +0200
Message-ID: <8762cmk5ro.fsf@gnu.org>
References: <87k412k6uy.fsf@ucl.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:52935)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1SNOHg-00006D-7I
	for emacs-orgmode@gnu.org; Thu, 26 Apr 2012 08:59:01 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1SNOHb-0000is-82
	for emacs-orgmode@gnu.org; Thu, 26 Apr 2012 08:58:55 -0400
Received: from mail-wg0-f49.google.com ([74.125.82.49]:40925)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bastienguerry@googlemail.com>) id 1SNOHa-0000iU-VH
	for emacs-orgmode@gnu.org; Thu, 26 Apr 2012 08:58:51 -0400
Received: by wgbds1 with SMTP id ds1so343679wgb.30
	for <emacs-orgmode@gnu.org>; Thu, 26 Apr 2012 05:58:48 -0700 (PDT)
In-Reply-To: <87k412k6uy.fsf@ucl.ac.uk> (Eric Fraga's message of "Thu, 26 Apr
	2012 22:06:21 +0930")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: emacs-orgmode@gnu.org

Hi Eric,

Eric Fraga <e.fraga@ucl.ac.uk> writes:

> 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

Mhh.. I can't reproduce this error with latest Org.

> and I get the error:
>
> ,----
> | org-refresh-category-properties: Buffer is read-only: #<buffer proposal.org>
> `----

Maybe you have a hook which call this function?

In any case, as the other place where `org-refresh-category-properties'
is called is `org-prepare-agenda-buffers' and those buffers might be
read-only (for some obscure reason), I pushed a fix that make sure 
`org-refresh-category-properties' can modify the buffer correctly.

Please let me know if this fixes your problem.

-- 
 Bastien