Carsten Dominik writes:
> On Feb 1, 2011, at 12:22 PM, Dan Davison wrote:
>
>> Carsten Dominik writes:
>>
>>> Hi Dan,
>>>
>>> maybe just header in the default value to keep the echo area open for
>>> error messages?
>>
>> Absolutely. But if you prefer, we could just do away with the echo-
>> ar
On Feb 1, 2011, at 12:22 PM, Dan Davison wrote:
Carsten Dominik writes:
Hi Dan,
maybe just header in the default value to keep the echo area open for
error messages?
Absolutely. But if you prefer, we could just do away with the echo-
area
message entirely. That would have the advantage
Carsten Dominik writes:
> Hi Dan,
>
> maybe just header in the default value to keep the echo area open for
> error messages?
Absolutely. But if you prefer, we could just do away with the echo-area
message entirely. That would have the advantage of leaving the user
interface unchanged.
With the
Hi Dan,
maybe just header in the default value to keep the echo area open for
error messages?
Cheers
- Carsten
On Feb 1, 2011, at 12:01 PM, Dan Davison wrote:
On Mon, Jan 31, 2011 at 5:04 AM, Andrea Crotti
wrote:
I found a strange behaviour which might be a bug, but maybe of my
configur
>> On Mon, Jan 31, 2011 at 5:04 AM, Andrea Crotti
>> wrote:
>>> I found a strange behaviour which might be a bug, but maybe of my
>>> configuration.
[...]
>>> - go over an elisp code block
>>> - C-c ' to edit in the overlay
>>> - C-c ' to go back when done
>>>
>>> And it works perfectly, BUT if fo
Jeff Horn writes:
> I can reproduce this. emacs 23.1 and org 7.4
>
> On Mon, Jan 31, 2011 at 5:04 AM, Andrea Crotti
> wrote:
>> I found a strange behaviour which might be a bug, but maybe of my
>> configuration.
>>
>> This is org mode version:
>> Org-mode version 7.4 (release_7.4.199.g8be1.dirty
Jeff Horn writes:
> I can reproduce this. emacs 23.1 and org 7.4
>
Good that I'm not alone :)
Another thing is that also changing mode in the overlay messes things
up, but that's not an orgmode fault I think, it's just how they work...
___
Emacs-orgm
