From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bastien <bzg@gnu.org>
Subject: Re: Regex Speedup for org-refresh-category-properties.
Date: Tue, 29 Jul 2014 16:56:48 +0200
Message-ID: <878uncb4cv.fsf@bzg.ath.cx>
References: <m261igx25h.fsf@purvis.id.au>	<871tt4jk7k.fsf@alphaville.bos.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43685)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bounce+0e656e.a52ba-emacs-orgmode=gnu.org@bzg.fr>)
	id 1XC8pt-00043b-HQ
	for emacs-orgmode@gnu.org; Tue, 29 Jul 2014 10:57:12 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <bounce+0e656e.a52ba-emacs-orgmode=gnu.org@bzg.fr>)
	id 1XC8pm-0005lh-RC
	for emacs-orgmode@gnu.org; Tue, 29 Jul 2014 10:57:05 -0400
Received: from mail-s76.mailgun.info ([184.173.153.204]:51783)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <bounce+0e656e.a52ba-emacs-orgmode=gnu.org@bzg.fr>)
	id 1XC8pm-0004jX-Ne
	for emacs-orgmode@gnu.org; Tue, 29 Jul 2014 10:56:58 -0400
In-Reply-To: <871tt4jk7k.fsf@alphaville.bos.redhat.com> (Nick Dokos's
	message	of "Tue, 29 Jul 2014 10:47:11 -0400")
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: Nick Dokos <ndokos@gmail.com>
Cc: emacs-orgmode@gnu.org

Hi Nick,

Nick Dokos <ndokos@gmail.com> writes:

>                    What does the asterisk do?

I think this is simply a code typo, fixed in master.

-- 
 Bastien