OK, the verdict is this:
in the next version, M-RET will split again, unless you configure
the new option `org-M-RET-may-split-lines'.
That variable will govern the behavior of M-RET when creating headlines,
when creating items, and also in tables.
- Carsten
On Feb 19, 2008, at 7:02 PM, Scott O
Carsten Dominik <[EMAIL PROTECTED]> writes:
> thanks. Please try the following patch:
That seems to fix it - thanks!
Bernt
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.o
Hi Bernt,
thanks. Please try the following patch:
- Carsten
--- org.el.orig 2008-02-20 22:45:38.0 +0100
+++ org.el 2008-02-20 22:45:59.0 +0100
@@ -4670,7 +4670,7 @@
(defun org-remove-keyword-keys (list)
(mapcar (lambda (x)
- (if (string-match "(..?)$" x)
+
Carsten Dominik <[EMAIL PROTECTED]> writes:
> Changes to logging progress
> ---
>
> There is now more control over which state changes are being
> logged in what way. Please read carefully the corresponding
> sections in the manual. Basically:
>
> - The v
On Feb 20, 2008, at 12:44 PM, Bastien wrote:
Detlef Steuer <[EMAIL PROTECTED]> writes:
On Wed, 20 Feb 2008 11:04:38 +
Phil Jackson <[EMAIL PROTECTED]> wrote:
Carsten Dominik <[EMAIL PROTECTED]> writes:
+1 vote on that one. I haven't tried out 5.22 yet, but the
M-RET/M- behavior that S
Detlef Steuer <[EMAIL PROTECTED]> writes:
> On Wed, 20 Feb 2008 11:04:38 +
> Phil Jackson <[EMAIL PROTECTED]> wrote:
>
>> Carsten Dominik <[EMAIL PROTECTED]> writes:
>>
>> >>> +1 vote on that one. I haven't tried out 5.22 yet, but the
>> >>> M-RET/M- behavior that Scott describes, also fits m
Detlef,
Detlef Steuer <[EMAIL PROTECTED]> writes:
>> Any chance of making it configurable (default to the old behavior)? I
>> like the new behaviour better, am I the only one?
>
> You're not alone!
Phew, my abandonment issues remain buried for a while longer :)
Cheers,
Phil
--
Phil Jackson
h
On Wed, 20 Feb 2008 11:04:38 +
Phil Jackson <[EMAIL PROTECTED]> wrote:
> Carsten Dominik <[EMAIL PROTECTED]> writes:
>
> >>> +1 vote on that one. I haven't tried out 5.22 yet, but the
> >>> M-RET/M- behavior that Scott describes, also fits my
> >>> way of working perfectly.
> >>
> >>
> >> Arg
Carsten Dominik <[EMAIL PROTECTED]> writes:
>>> +1 vote on that one. I haven't tried out 5.22 yet, but the
>>> M-RET/M- behavior that Scott describes, also fits my
>>> way of working perfectly.
>>
>>
>> Arghh ... me too ... so count me in on this vote for wanting to having
>> it back ... please ..
The fast fix for all you guys is:
Get the git repo by cloning it,
then in the repo do
$ git-checkout release_5.21
$ make
I'll fix this for the next release, but I am traveling for the next
few days
- Carsten
On Feb 19, 2008, at 8:17 PM, Raimund Kohl-Füchsle wrote:
-BEGIN PGP SIG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nick Dokos schrieb:
> +1 vote on that one. I haven't tried out 5.22 yet, but the
> M-RET/M- behavior that Scott describes, also fits my
> way of working perfectly.
Arghh ... me too ... so count me in on this vote for wanting to having
it back ... pl
Scott Otterson <[EMAIL PROTECTED]> wrote:
> Carsten Dominik wrote:
> > - M-RET no longer brakes a line in the middle, it will make a
> > new line after the current or (if cursor is at the beginning
> > of the line) before the current line.
> >
> Is there a way to restore the old
Carsten Dominik wrote:
- M-RET no longer brakes a line in the middle, it will make a
new line after the current or (if cursor is at the beginning
of the line) before the current line.
I there a way to restore the old M-RET behavior?
I use it all the time when brainstorming:
13 matches
Mail list logo
