emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Org mode issue tracker
Date: Wed, 25 Sep 2013 09:51:20 +0200	[thread overview]
Message-ID: <86ioxp2vbb.fsf@somewhere.org> (raw)
In-Reply-To: A021C644-02F5-4BF9-8858-E7A44B971540@gmail.com

Hi Carsten,

Carsten Dominik wrote:
> we do not have an issue tracker for Org.  However, if you
> have some time to help, the file with open issues that need
> attention can be found here:
>
> https://dl.dropboxusercontent.com/u/530458/org-tracker.html
>
> Note that I do not enter every issue into this file.  Normally I wait
> and see if a report gets addressed on the mailing list, and only
> if that does not happen, than I make a note in this file.  I think
> this keeps it more manageable for me - an official online bug tracker
> would probably quickly fill with many small things we can better
> handle on the list.
>
> If you feel that this is not going well enough and if I am missing
> important reports in this way, let me know and we will find a better
> solution.
>
> Some of these bugs still need confirmation by a second party,
> and patches are always welcome.  If possible, reply in
> the original thread, while still mentioning the bug number
> in the above link.

The other solution that I'd see would be using Emacs' own bug tracker (the
`org' package is already known to them), if that's possible. Anyway, having the
bugs in an Org file seems natural too!

But shouldn't it, maybe, be in a Git project, so that other people can edit it?

And choosing to have the `Assignee' (or `ASSIGNEE') property be the official
Org way to delegate a task to someone would help?

Regarding the list itself, if I may, I would add 3 problems (identified by the
date and time it has been sent on the Org mailing list):

1. 20130315.1805: Background color reset for links and DONE headlines

   Allow to have more faces than just `org-headline-done' when `DONE'
   (`org-fontify-done-headline').

   I looked at it, following Bastien's hints, but never could make it work.

2. 20130909.1657: Clocktable error with multiple source files from parent dir

3. 20130912.1455: `org-agenda-sorting-strategy' does not work in `tags-todo'

   The following agenda view is supposed to display the tasks by ascending
   DEADLINE timestamp.

     (add-to-list 'org-agenda-custom-commands
                  '("B" "Today"
                    tags-todo "DEADLINE<=\"<today>\""
                    ((org-agenda-overriding-header "Today")
                     (org-agenda-sorting-strategy '(deadline-up)))) t)

   it sorts the list by category, instead!

OTOH, you can "delegate" the problem #24 to me.

- 20130911.1448: Colored tags generate an error when C-x C-w'ing the agenda

  I'll try to debug and fix it myself. I'll come back if I don't succeed.

Best regards,
  Seb

-- 
Sebastien Vauban

  parent reply	other threads:[~2013-09-25  7:51 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25  6:43 Org mode issue tracker Carsten Dominik
2013-09-25  7:28 ` Christian Moe
2013-09-25  7:30   ` Carsten Dominik
2013-09-25  7:51 ` Sebastien Vauban [this message]
2013-09-25  8:03   ` Carsten Dominik
2013-09-25  9:04     ` Sebastien Vauban
2013-09-25  9:37       ` Carsten Dominik
2013-09-25  8:04   ` Suvayu Ali
2013-09-25  9:06     ` Sebastien Vauban
2013-09-25  9:55       ` Michael Albinus
2013-09-25 12:59         ` Sebastien Vauban
2013-09-25 18:29         ` Loyall, David
2013-09-25 18:54           ` Suvayu Ali
2013-09-25 18:56           ` Michael Albinus
2013-09-26  0:21             ` Suvayu Ali
2013-09-26  7:29               ` Sebastien Vauban
2013-09-26  8:22                 ` Suvayu Ali
2013-09-26  8:42                   ` Michael Brand
2013-09-26  9:52                   ` Sebastien Vauban
2013-09-26  9:34                 ` Michael Albinus
2013-09-26 12:13                   ` Suvayu Ali
2013-09-26 12:21                     ` Suvayu Ali
2013-09-26 12:33                       ` Michael Albinus
2013-09-27 19:28                   ` org-debbugs.el Michael Albinus
2013-09-27 21:50                     ` org-debbugs.el Suvayu Ali
2013-10-02  7:46                     ` org-debbugs.el Michael Albinus
2013-10-02 10:05                       ` org-debbugs.el Suvayu Ali
2013-10-02 11:44                         ` org-debbugs.el Michael Albinus
2013-10-02 11:47                           ` org-debbugs.el Michael Albinus
2013-10-02 12:33                             ` org-debbugs.el Suvayu Ali
2013-10-02 12:33                           ` org-debbugs.el Suvayu Ali
2013-10-04 19:19                           ` org-debbugs.el Michael Albinus
2013-10-04 19:46                             ` org-debbugs.el Suvayu Ali
2013-10-11  8:03                       ` org-debbugs.el Michael Albinus
2013-10-11 10:44                         ` org-debbugs.el Suvayu Ali
2013-10-11 11:55                         ` org-debbugs.el Nicolas Richard
2013-10-11 12:06                           ` org-debbugs.el Thorsten Jolitz
2013-10-11 12:09                           ` org-debbugs.el Suvayu Ali
2013-10-11 12:11                           ` org-debbugs.el Michael Albinus
2013-10-25 11:28                         ` org-debbugs.el Michael Albinus
2013-11-05 16:15                     ` org-debbugs.el Bastien
2013-11-05 20:03                       ` org-debbugs.el Michael Albinus
2013-11-05 23:53                         ` org-debbugs.el Bastien
2013-09-26 14:01               ` Org mode issue tracker Brett Viren
2013-10-02 12:38                 ` Michael Albinus
2013-09-25  8:56 ` Carsten Dominik
2013-09-25 18:29   ` Sebastien Vauban
2013-09-25 22:27     ` Bastien

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=86ioxp2vbb.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).