From: Tim Cross <theophilusx@gmail.com>
To: Adam Porter <adam@alphapapa.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-taskjuggler on MELPA useful despite org-plus-contrib
Date: Wed, 09 Aug 2017 07:54:02 +1000 [thread overview]
Message-ID: <87shh1sp39.fsf@gmail.com> (raw)
In-Reply-To: <873792nlhn.fsf@alphapapa.net>
While there are some minor issues with org-plus-contrib, I find them to
be minor and mostly due to limitations in package.el (for example,
dependency on org results in both org-plus-contrib and org packages
being installed). In fact, I find org-plus-contrib easier to manage than
just the straight org package as I experience fewer issues arising from
conflicts with the old 'bundled' version of org in emacs and the package
version. However, I also use use-package and I don't know to what extent
that impacts my load problems.
I do remember running into a frustrating limitation with org-taskjuggler
when I was using it a couple of years ago - cannot remember the specific
issue now, but do remember I would have to edit the exported taskjuggler
file after every export to adjust some parameters (it might have been
related to default project period, not sure).
Tim
Adam Porter writes:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>>> At least until the underlying problem with org-plus-contrib is
>>> resolved.
>>
>> What exactly is the underlying problem?
>
> FWIW I have been using org-plus-contrib for a while now, and I haven't
> had any problems with my customizations.
--
Tim Cross
next prev parent reply other threads:[~2017-08-08 21:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 22:57 ox-taskjuggler on MELPA useful despite org-plus-contrib Simon Guest
2017-08-07 23:13 ` Simon Guest
2017-08-08 7:50 ` Nicolas Goaziou
2017-08-08 15:10 ` Adam Porter
2017-08-08 21:54 ` Tim Cross [this message]
2017-08-08 23:19 ` Adam Porter
2017-08-09 17:24 ` Achim Gratz
2017-08-09 19:37 ` Thomas S. Dye
2017-08-09 21:15 ` Simon Guest
2017-08-09 21:49 ` Tim Cross
2017-08-08 21:19 ` Simon Guest
2017-08-08 22:03 ` Thomas S. Dye
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=87shh1sp39.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=adam@alphapapa.net \
--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).