emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Fraga <e.fraga@ucl.ac.uk>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] new exporter fails on read only files
Date: Fri, 27 Apr 2012 22:52:15 +0930	[thread overview]
Message-ID: <87y5phia2g.fsf@ucl.ac.uk> (raw)
In-Reply-To: <8762cmk5ro.fsf@gnu.org> (Bastien's message of "Thu, 26 Apr 2012 14:59:55 +0200")

Bastien <bzg@gnu.org> writes:

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

Arghhh.  Strange.

>
>> 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?

I do not believe so.  Grepping for "category" in my .el files (including
custom variable setting) finds nothing org related.

Obviously, I can try emacs -Q etc and will do so later this weekend
hopefully.

In the meantime:

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

Actually, I have updated (one minute ago) and the problem has now
changed!  I now get this error:

,----
| and: Wrong type argument: stringp, (latex-fragment (:value "\\ref{sec:evaporative}" :begin 11957 :end 11978 :post-blank 0))
`----

and I have no idea what is happening here.  For this error, I do get a
debug trace but it is rather long and my org file has material I cannot
post. The old exporter still works perfectly fine.

I will try emacs -Q later and will also see if I can come up with a
minimal example that fails in the same way as my longer confidential
document.

Thanks,
eric

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.1.50.1
: using Org-mode version 7.8.09 (release_7.8.09-392-ge02226 @ /home/ucecesf/git/org-mode/lisp/org-install.el)

  reply	other threads:[~2012-04-27 13:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26 12:36 [bug] new exporter fails on read only files Eric Fraga
2012-04-26 12:59 ` Bastien
2012-04-27 13:22   ` Eric Fraga [this message]
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:
  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=87y5phia2g.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=bzg@gnu.org \
    --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).