From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Brand <michael.ch.brand@gmail.com>
Subject: Re: org-table-copy-down incrementor
Date: Wed, 21 May 2014 17:32:10 +0200
Message-ID: <CALn3zoiy_fkyHLoTPHxunBF5Y2jpMNX4q3D0RSNBSSoOQXchCA@mail.gmail.com>
References: <26CB62FB-01B3-49F6-A3E2-61FC25825493@oracle.com>
	<87ioq8ym8g.fsf@bzg.ath.cx>
	<CALn3zoi5LWVNV__76XcTG7dO7oK3CM9758pPfNaY+zzmEmSg6A@mail.gmail.com>
	<87k39gilps.fsf@bzg.ath.cx>
	<CALn3zojfEj-5CXiWGDX24F6qWu0Desh_M_PGVgyHmCWotJnhKg@mail.gmail.com>
	<87k39gs07o.fsf@bzg.ath.cx>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37651)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <michael.ch.brand@gmail.com>) id 1Wn8V5-0000IO-Rs
	for emacs-orgmode@gnu.org; Wed, 21 May 2014 11:32:16 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <michael.ch.brand@gmail.com>) id 1Wn8V1-0006XK-Pj
	for emacs-orgmode@gnu.org; Wed, 21 May 2014 11:32:15 -0400
In-Reply-To: <87k39gs07o.fsf@bzg.ath.cx>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Bastien <bzg@gnu.org>
Cc: Org Mode <emacs-orgmode@gnu.org>, Stacey Marshall <stacey.marshall@oracle.com>

Hi Bastien

On Tue, May 20, 2014 at 9:45 PM, Bastien <bzg@gnu.org> wrote:
> Yes.  There is also `thing-at-point' which does not recognize 1.1 as a
> number... I circumvented this by using `calc-eval'.  The above should
> now work correctly.

Yes it does. Using Calc is a nice solution, thank you.

I did not notice before but the first commit
7ac468ff5547891503b6b8f5fa03793d79b3bff6
changed SHIFT-RET on the empty field
    | 2 |
    | 5 |
    |   |
to add a new row instead of only replacing the current field.

Michael