Okay, let's stick to nil as the default value for
`org-catch-invisible-edits' -- it is now documented in
the manual, which is good enough IMO.
Thanks,
--
Bastien
At Tue, 12 Mar 2013 13:45:27 +0100,
Bastien wrote:
>
> Hi Darlan,
>
> Darlan Cavalcante Moreira writes:
>
> > That is another nice feature of org-mode I didn't know about.
>
> I just documented it in the manual, thanks!
>
> > I set the variable to 'error now..
> >
> > Any reason why nil is t
Hi Darlan,
Darlan Cavalcante Moreira writes:
> That is another nice feature of org-mode I didn't know about.
I just documented it in the manual, thanks!
> I set the variable to 'error now..
>
> Any reason why nil is the default?
IMO setting it to non-nil would be too intrusive for
most users.
That is another nice feature of org-mode I didn't know about.
I set the variable to 'error now..
Any reason why nil is the default?
At Sun, 10 Mar 2013 10:57:15 +0100,
Suvayu Ali wrote:
>
> Hi Bastien,
>
> On Sun, Mar 10, 2013 at 10:34:26AM +0100, Bastien wrote:
> > Suvayu Ali writes:
> >
>
Hi Bastien,
On Sun, Mar 10, 2013 at 10:34:26AM +0100, Bastien wrote:
> Suvayu Ali writes:
>
> > I remember someone (maybe Bastien) putting in a safeguard quite sometime
> > back that would unfold a headline with a warning when you tried to edit
> > near the ellipses. This was to protect against
Hi Suvayu,
Suvayu Ali writes:
> I remember someone (maybe Bastien) putting in a safeguard quite sometime
> back that would unfold a headline with a warning when you tried to edit
> near the ellipses. This was to protect against accidental edits. I see
> this not there anymore, can we have it b
Hi Bastien and others,
I remember someone (maybe Bastien) putting in a safeguard quite sometime
back that would unfold a headline with a warning when you tried to edit
near the ellipses. This was to protect against accidental edits. I see
this not there anymore, can we have it back?
I tried loo
