From: Aaron Ecay <aaronecay@gmail.com>
To: Kosyrev Serge <_deepfire@feelingofgreen.ru>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-taskjuggler.el: allow direct 'depends' specification
Date: Wed, 11 Nov 2015 02:20:02 +0000 [thread overview]
Message-ID: <87ziylqnu5.fsf@gmail.com> (raw)
In-Reply-To: <87d1vijn0p.fsf@feelingofgreen.ru>
Hi Kosyrev,
2015ko azaroak 10an, Kosyrev Serge-ek idatzi zuen:
>
> 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?
The difference between a defvar and a defcustom is whether the variable
shows up in M-x customize. Customize often serves as the first port of
call for users discovering the features of a library. So the question
is, will presenting users with such a list in the customize interface
empower them to have better taskjuggler export? Or will it be too
intimidating? It’s a subjective decision, I was just wondering whether
you had considered it.
Either way, it would be good to put the documentation link you gave into
the docstring, as a pointer to the allowed values of the variable.
Does that make sense?
--
Aaron Ecay
next prev parent reply other threads:[~2015-11-11 2:20 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
2015-11-11 2:20 ` Aaron Ecay [this message]
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=87ziylqnu5.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=_deepfire@feelingofgreen.ru \
--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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).