Hi Samuel,
this remains a contriversial issue. However, since I made the change,
I have not received any concrete reports of problems - so I guess it
is working pretty well the way it is now.
Case closed - until the next bug report :-)
- Carsten
On Jan 22, 2010, at 5:50 PM, Samuel
Hi Carsten,
On 2010-02-01, Carsten Dominik carsten.domi...@gmail.com wrote:
Hi Samuel,
this remains a contriversial issue. However, since I made the change,
I have not received any concrete reports of problems - so I guess it
is working pretty well the way it is now.
Case closed - until
On Feb 1, 2010, at 6:26 PM, Samuel Wales wrote:
Hi Carsten,
On 2010-02-01, Carsten Dominik carsten.domi...@gmail.com wrote:
Hi Samuel,
this remains a contriversial issue. However, since I made the
change,
I have not received any concrete reports of problems - so I guess it
is working
Applied (but not yet pushed because of hardware upgrade at
repo.or.cz), thanks.
I had implemented it the other way round because that would avoid
making new empty lines by accident, but I do agree that swallowing a
headline is by fare the more severe problem.
Thanks.
- Carsten
On Jan
I'm not so sure about this patch.
Are you sure this will work with sorting headlines? Swallowed
headlines occur if end of narrowed region is at eol. What about other
operations, including user-written commands? Can we be sure that they
will not to swallowed headlines?
IMO the behavior
Consider the following situation:
* A
Some text.
* B
- Place the cursor on A, press C-x n w (org-narrow-to-subtree).
- Go to the very end of the buffer and insert xyz.
- C-x n w (widen).
You end up with:
* A
Some Text
xyz* B
The attached one-line patch fixes this by passing `nil' for the
