From mboxrd@z Thu Jan  1 00:00:00 1970
From: Samuel Wales <samologist@gmail.com>
Subject: Re: can't press ret without error
Date: Sun, 17 Jul 2016 12:24:38 -0700
Message-ID: <CAJcAo8uSod4rDgykPmkey-44ZYht+GPGpuCv0bjHUuYWaBcAEw@mail.gmail.com>
References: <CAJcAo8t7hyVxVqU4dHAKU0dGwjbFBL2d+UiM3qyWTBVTUQmDzw@mail.gmail.com>
	<87shv8h9fg.fsf@saiph.selenimh>
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]:59687)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <samologist@gmail.com>) id 1bOrgB-0004Im-1B
	for emacs-orgmode@gnu.org; Sun, 17 Jul 2016 15:24:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <samologist@gmail.com>) id 1bOrg9-0006fw-3C
	for emacs-orgmode@gnu.org; Sun, 17 Jul 2016 15:24:41 -0400
Received: from mail-vk0-x230.google.com ([2607:f8b0:400c:c05::230]:33173)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <samologist@gmail.com>) id 1bOrg8-0006fo-V9
	for emacs-orgmode@gnu.org; Sun, 17 Jul 2016 15:24:41 -0400
Received: by mail-vk0-x230.google.com with SMTP id x130so215304499vkc.0
	for <emacs-orgmode@gnu.org>; Sun, 17 Jul 2016 12:24:39 -0700 (PDT)
In-Reply-To: <87shv8h9fg.fsf@saiph.selenimh>
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"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Samuel Wales <samologist@gmail.com>, emacs-orgmode@gnu.org

thanks for your reply.  next time i will check for long lines.

On 7/17/16, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> It seems you are using very long lines.
>
> In particular one of them is ambiguous and the parser has to match too
> much (hence the stack overflow) to decide what is that line.