From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: [PATCH 7/8] ox-taskjuggler.el: allow 'priority' to be a directly-specified integer Date: Tue, 10 Nov 2015 00:12:37 +0000 Message-ID: <87bnb2soei.fsf@gmail.com> References: <87611alrmu.fsf@feelingofgreen.ru> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44500) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvwYF-00071W-6D for emacs-orgmode@gnu.org; Mon, 09 Nov 2015 19:12:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZvwYB-0000wA-Vh for emacs-orgmode@gnu.org; Mon, 09 Nov 2015 19:12:43 -0500 Received: from mail-wm0-x22e.google.com ([2a00:1450:400c:c09::22e]:33822) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZvwYB-0000vu-Ow for emacs-orgmode@gnu.org; Mon, 09 Nov 2015 19:12:39 -0500 Received: by wmnn186 with SMTP id n186so132590062wmn.1 for ; Mon, 09 Nov 2015 16:12:39 -0800 (PST) In-Reply-To: <87611alrmu.fsf@feelingofgreen.ru> 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@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Kosyrev Serge <_deepfire@feelingofgreen.ru>, emacs-orgmode@gnu.org Hi Kosyrev, 2015ko azaroak 8an, Kosyrev Serge-ek idatzi zuen: > > * ox-taskjuggler.el (org-taskjuggler--build-task): fix priority specification > by allowing it to be directly passed down, in case it parses as an integer. > --- > contrib/lisp/ox-taskjuggler.el | 12 +++++++++--- > 1 file changed, 9 insertions(+), 3 deletions(-) > > diff --git a/contrib/lisp/ox-taskjuggler.el b/contrib/lisp/ox-taskjuggler.el > index 44ffeb6..d49db62 100644 > --- a/contrib/lisp/ox-taskjuggler.el > +++ b/contrib/lisp/ox-taskjuggler.el > @@ -875,10 +875,16 @@ a unique id will be associated to it." > (org-taskjuggler-get-end task)) > (org-element-property :PERIOD task))))) > (priority > - (let ((pri (org-element-property :priority task))) > + (let ((pri (org-element-property :PRIORITY task))) > (and pri > - (max 1 (/ (* 1000 (- org-lowest-priority pri)) > - (- org-lowest-priority org-highest-priority))))))) > + ;; The exported task priority can be either specified > + ;; via the Org priority mechahism (which is currently broken), Can you say more about what breakage you mean? Is it something that can be easily fixed? Thanks, -- Aaron Ecay