From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: logdone enhancement Date: Wed, 27 Feb 2013 11:04:25 +0100 Message-ID: <86wqtu8446.fsf@somewhere.org> References: <512DA5E5.7040703@lbl.gov> <87vc9eupes.fsf@bzg.ath.cx> <864ngy9ky3.fsf@somewhere.org> <87ehg2t8fj.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Bastien, Bastien wrote: > Hi S=C3=A9bastien, > > "Sebastien Vauban" > writes: > >> Now that this "syntax order" is enforced, will we get commit 6b04bef bac= k in >> Org 8? That'd be great... > > Why not. Can you heavily test commit 6b04bef and see if > anything goes wrong? I can try, though it already had been heavily tested back in that time. But first, For me, the question comes down to: do we agree that John (in th= is case) won't be allowed anymore to write such an entry? --8<---------------cut here---------------start------------->8--- *** NOTE Assets:Receivable:CEG #+begin_src sh :results value :exports results ledger reg --inject=3DExpected '^income:ceg' ledger reg --sort date -b 2007 receivable:CEG #+end_src :PROPERTIES: :ID: 8BEF6C42-8B23-495B-9421-3810B58907A1 :VISIBILITY: folded :CREATED: [2010-06-18 Fri 07:37] :END: --8<---------------cut here---------------end--------------->8--- Best regards, Seb --=20 Sebastien Vauban