emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Kosyrev Serge <_deepfire@feelingofgreen.ru>
To: Aaron Ecay <aaronecay@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-taskjuggler.el: allow direct 'depends' specification
Date: Tue, 10 Nov 2015 11:07:18 +0300	[thread overview]
Message-ID: <87d1vijn0p.fsf@feelingofgreen.ru> (raw)
In-Reply-To: <87egfysorn.fsf@gmail.com> (sfid-20151110_032802_646340_BC1FBBAC) (Aaron Ecay's message of "Tue, 10 Nov 2015 00:04:44 +0000")

Aaron Ecay <aaronecay@gmail.com> writes:
> Hi Kosyrev,
>> @@ -301,7 +301,7 @@ but before any resource and task declarations."
>>    :type '(string :tag "Preamble"))
>>  
>>  (defcustom org-taskjuggler-valid-task-attributes
>
> Is this an open-ended list that an average user could meaningfully add
> to?  If not, perhaps it should be a defconst.  (I don’t know anything
> about the taskjuggler format, so I’m sure whatever decision you make
> will be OK.)

Generally speaking, TaskJuggler own "attributes" and "properties" are
very numerous.  Suffice to point to the documentation:

  http://taskjuggler.org/tj3/manual/

Org is only able to provide a very limited amount of those, and the
approach it takes is by white-listing the properties that ought to
"pass through" from Org to TJP files.

So, naturally, whenever one faces a limitation in ox-taskjuggler,
the desire to extend the list arises.

I'm not sure how this relates to an average user, to be honest,
and whether I've at all helped with your question..

How do we proceed?

-- 
с уважениeм / respectfully,
Косырев Сергей

next prev parent reply	other threads:[~2015-11-10  8:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-08 10:12 [PATCH] ox-taskjuggler.el: allow direct 'depends' specification Kosyrev Serge
2015-11-10  0:04 ` Aaron Ecay
2015-11-10  8:07   ` Kosyrev Serge [this message]
2015-11-11  2:20     ` Aaron Ecay
2015-11-12 16:36   ` Rasmus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d1vijn0p.fsf@feelingofgreen.ru \
    --to=_deepfire@feelingofgreen.ru \
    --cc=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).