On Sun, Jun 14, 2015 at 02:58:25PM +0200, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > I was trying to edit the attr_latex line for the following table:
> >
> > #+attr_latex:
> > | year | 2012 | 2018 | 2022 | 2028 | 2035 |
> > | γ(°) |7 |4 | 1.3 | 0.9 | 0.6 |
>
> Fixed in
Suvayu Ali writes:
> I was trying to edit the attr_latex line for the following table:
>
> #+attr_latex:
> | year | 2012 | 2018 | 2022 | 2028 | 2035 |
> | γ(°) |7 |4 | 1.3 | 0.9 | 0.6 |
Fixed in 182ff104b77d1c4cd03a2749472d9da0c7733116. Thank you.
This change requires a modifi
On Thu, Jun 11, 2015 at 09:00:39AM +0200, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > I was trying to edit the attr_latex line for the following table:
> >
> > #+attr_latex:
> > | year | 2012 | 2018 | 2022 | 2028 | 2035 |
> > | γ(°) |7 |4 | 1.3 | 0.9 | 0.6 |
>
> I can rep
Suvayu Ali writes:
> I got a message like the following one quite a few times.
>
> Partially completed
> ==
> WARNING. Corrupted element (table-row) at 34386
>
> Real: (table-row (:type standard :begin 34386 :end
> 34430 :contents-begin 34387 :contents-end 34429 :post-blank
> 0 :po
Suvayu Ali writes:
> I got a message like the following one quite a few times.
>
> Partially completed
> ==
> WARNING. Corrupted element (table-row) at 34386
I wonder if this is the same bug that I've been seeing:
http://thread.gmane.org/gmane.emacs.orgmode/92883/focus=92884
Ras
Hi Nicolas,
On Sun, Jun 07, 2015 at 01:29:04AM +0200, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > I do not see anything happening. In the modeline I see OrgCacheD, so
> > the mode is definitely enabled. However to enable it, I had to do one
> > of these two:
> >
> > (setq ngz-debug-mod
On Sun, Jun 07, 2015 at 01:29:04AM +0200, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > I do not see anything happening. In the modeline I see OrgCacheD, so
> > the mode is definitely enabled. However to enable it, I had to do one
> > of these two:
> >
> > (setq ngz-debug-mode nil)
> >
Suvayu Ali writes:
> I do not see anything happening. In the modeline I see OrgCacheD, so
> the mode is definitely enabled. However to enable it, I had to do one
> of these two:
>
> (setq ngz-debug-mode nil)
> (setq ngz-debug-mode t)
My bad, it should be
(define-minor-mode element-debug-m
Hi Nicolas,
On Tue, Jun 02, 2015 at 11:27:55PM +0200, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > I have enabled the mode on my document. Let's see how this goes.
>
> OK. You have to keep an eye on the *Messages* buffer so that warning
> don't go unnoticed.
I do not see anything happeni
On Tue, Jun 02, 2015 at 11:27:55PM +0200, Nicolas Goaziou wrote:
> Suvayu Ali writes:
>
> > Btw, since you warn against large documents, would it help if
> > I narrowed a large document before enabling the mode?
>
> It wouldn't: cache ignores narrowing anyway.
Okay thanks :)
--
Suvayu
Open s
Suvayu Ali writes:
> I have enabled the mode on my document. Let's see how this goes.
OK. You have to keep an eye on the *Messages* buffer so that warning
don't go unnoticed.
> Btw, since you warn against large documents, would it help if
> I narrowed a large document before enabling the mode?
Hi Nicolas,
On Tue, Jun 02, 2015 at 10:26:54PM +0200, Nicolas Goaziou wrote:
> Hello,
>
> Suvayu Ali writes:
>
> > I have been noticing a strange heisenbug. From time to time, Org starts
> > eating CPU for certain specific tasks: org-end-of-line, fill-paragraph,
> > folding or unfolding trees,
Hello,
Suvayu Ali writes:
> I have been noticing a strange heisenbug. From time to time, Org starts
> eating CPU for certain specific tasks: org-end-of-line, fill-paragraph,
> folding or unfolding trees, or adding/changing properties with
> org-set-property. However these happen only after I h
13 matches
Mail list logo
