From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: exporting ical files from read-only buffers [7.8.03 (release_7.8.03.112.g8861)]
Date: Thu, 12 Jan 2012 13:19:53 +0000 [thread overview]
Message-ID: <8739blqcqu.fsf@ucl.ac.uk> (raw)
In-Reply-To: <E1RlKO4-00006S-9w@mea> (Stephen Eglen's message of "Thu, 12 Jan 2012 13:08:12 +0000")
Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk> writes:
> I've found a small bug with exporting ical files from read-only org
> buffers. Create a simple buffer, e.g.:
>
> * test1
> <2012-01-12 Thu>
>
> and then hit C-x C-q to make the buffer read-only. Then do C-c C-e i
> to export an ical file. You get an error that the buffer is read-only.
>
> I think this is due to the call to org-refresh-category-properties,
> which can't update text proprties.
>
> My workaround is to do:
> (setq inhibit-read-only nil)
>
> so that text properties can be added to read-only buffers. This could
> be done locally within the ical export functions if others thought
> sensible, for which I can send a patch if desired.
Could this be done more generally? I think I've run into this for other
export targets as well, although it may be my memory that is faulty
here. I use RCS for version control for standalone files and often have
files read-only from which I want to export.
Thanks,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.106.gc835)
next prev parent reply other threads:[~2012-01-12 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 13:08 Bug: exporting ical files from read-only buffers [7.8.03 (release_7.8.03.112.g8861)] Stephen Eglen
2012-01-12 13:19 ` Eric S Fraga [this message]
2012-01-12 13:23 ` Stephen Eglen
2012-01-12 13:37 ` Eric S Fraga
2012-01-13 13:36 ` [bug] org-columns for read only buffer (was Re: Bug: exporting ical files from read-only buffers [7.8.03 (release_7.8.03.112.g8861)]) 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=8739blqcqu.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=S.J.Eglen@damtp.cam.ac.uk \
--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).