From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Samuel Wales" Subject: Re: Searching for tags or todo keywords Date: Mon, 15 Sep 2008 22:15:06 -0700 Message-ID: <20524da70809152215y55dccdd3sd62d299b893ce287@mail.gmail.com> References: <1219411261.28705.1269971211@webmail.messagingengine.com> <8B62D5CA-840C-4464-A7DE-310209EB8FEA@uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KfSu6-0007xy-C1 for emacs-orgmode@gnu.org; Tue, 16 Sep 2008 01:15:10 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KfSu5-0007xb-1n for emacs-orgmode@gnu.org; Tue, 16 Sep 2008 01:15:09 -0400 Received: from [199.232.76.173] (port=53043 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KfSu4-0007xQ-Kv for emacs-orgmode@gnu.org; Tue, 16 Sep 2008 01:15:08 -0400 Received: from ey-out-1920.google.com ([74.125.78.147]:26826) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KfSu4-0003B6-O8 for emacs-orgmode@gnu.org; Tue, 16 Sep 2008 01:15:08 -0400 Received: by ey-out-1920.google.com with SMTP id 4so1083084eyg.24 for ; Mon, 15 Sep 2008 22:15:06 -0700 (PDT) In-Reply-To: <8B62D5CA-840C-4464-A7DE-310209EB8FEA@uva.nl> Content-Disposition: inline List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org On Sat, Sep 13, 2008 at 12:10, Carsten Dominik wrote: > I would like to have parenthesis, but since the parsing is done by string > processing, any parenthesis in one of the search strings would be difficult > to handle. Have you considered using Lisp syntax, perhaps as an alternate? Benefits include: trivial to parse (no parsing at all -- let Lisp parse and maybe even eval for you!), easier for the user to remember (for some of us :)), orthogonal, easy to extend (even with user-defined functions), easier to quote and escape, consistent, standard, free of precedence lists, proven technology, pretty-printable, print-readable, etc. The old syntax can easily be converted to sexp, thus separating syntax from semantics and ensuring that the behavior is the same -- without making anybody have to switch. Just a possibility.