Bug: exporting ical files from read-only buffers [7.8.03 (release_7.8.03.112.g8861)]

Bug: exporting ical files from read-only buffers [7.8.03 (release_7.8.03.112.g8861)]

[Stephen Eglen]

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.

Stephen





----------------------------------------------------------------------
Emacs  : GNU Emacs 23.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.5)
 of 2011-08-14 on allspice, modified by Debian
Package: Org-mode version 7.8.03 (release_7.8.03.112.g8861)

Re: Bug: exporting ical files from read-only buffers [7.8.03 (release_7.8.03.112.g8861)]

[Eric S Fraga]

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)

Re: Bug: exporting ical files from read-only buffers [7.8.03 (release_7.8.03.112.g8861)]

[Stephen Eglen]

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

I also use RCS, which is how I got caught out today (trying to set up
Eric's neat guide for gettting org->ical-> google calendar; thanks for
that Eric.)  Before sending the bug, I tried exporting to pdf, which
worked fine; what other exporters do you use?

Stephen

Re: Bug: exporting ical files from read-only buffers [7.8.03 (release_7.8.03.112.g8861)]

[Eric S Fraga]

Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk> writes:

>> 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.
>
> I also use RCS, which is how I got caught out today (trying to set up
> Eric's neat guide for gettting org->ical-> google calendar; thanks for
> that Eric.)  Before sending the bug, I tried exporting to pdf, which
> worked fine; what other exporters do you use?
>
> Stephen

Mostly, I export to PDF but also less frequently to HTML, ODT and
ICAL...  I had imagined this to be a generic issue as I could not
imagine that there would be anything special about exporting to ICAL... 
I have just tried a read-only document I have and everything has worked
fine.  Strange.  Definitely faulty (wetware) memory; time for a RAM
upgrade ;-)

Apologies for the noise.

And you're very welcome, by the way!

-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.106.gc835)

[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]

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

I have just run into another case where text properties and/or overlays
clash with a read-only file: column view (M-x org-columns, C-c C-x
C-c).  In a read-only file, I get the error

   org-columns-compute-all: Buffer is read-only: #<buffer test.org>

If I make the file writable, org-columns works but, of course, does not
actually modify the file.

Thanks,
eric
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1
: using Org-mode version 7.8.03 (release_7.8.03.122.g5b407)