From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sebastien Vauban" Subject: Re: Org mode issue tracker Date: Wed, 25 Sep 2013 11:04:02 +0200 Message-ID: <86wqm51ddp.fsf@somewhere.org> References: <86ioxp2vbb.fsf@somewhere.org> <28629A87-C3D1-4D37-9725-9339CDC98469@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: 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-mXXj517/zsQ@public.gmane.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org To: emacs-orgmode-mXXj517/zsQ@public.gmane.org Carsten Dominik wrote: > On 25.9.2013, at 09:51, Sebastien Vauban wrote: >> 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: >>>=20 >>> https://dl.dropboxusercontent.com/u/530458/org-tracker.html >>>=20 >>> 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. >>>=20 >>> 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. >>>=20 >>> 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. >>=20 >> The other solution that I'd see would be using Emacs' own bug tracker (t= he >> `org' package is already known to them), if that's possible. Anyway, hav= ing the >> bugs in an Org file seems natural too! >>=20 >> But shouldn't it, maybe, be in a Git project, so that other people can e= dit it? >>=20 >> And choosing to have the `Assignee' (or `ASSIGNEE') property be the offi= cial >> Org way to delegate a task to someone would help? >>=20 >> 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): > > To make my life easier, cold you please provide gmane links? DONE=C2=A0;-) See below. >> 1. 20130315.1805: Background color reset for links and DONE headlines >>=20 >> Allow to have more faces than just `org-headline-done' when `DONE' >> (`org-fontify-done-headline'). >>=20 >> I looked at it, following Bastien's hints, but never could make it wor= k. http://permalink.gmane.org/gmane.emacs.orgmode/68552 >> 2. 20130909.1657: Clocktable error with multiple source files from paren= t dir http://comments.gmane.org/gmane.emacs.orgmode/76207 >> 3. 20130912.1455: `org-agenda-sorting-strategy' does not work in `tags-t= odo' >>=20 >> The following agenda view is supposed to display the tasks by ascending >> DEADLINE timestamp. >>=20 >> (add-to-list 'org-agenda-custom-commands >> '("B" "Today" >> tags-todo "DEADLINE<=3D\"\"" >> ((org-agenda-overriding-header "Today") >> (org-agenda-sorting-strategy '(deadline-up)))) t) >>=20 >> it sorts the list by category, instead! http://permalink.gmane.org/gmane.emacs.orgmode/76347 >> OTOH, you can "delegate" the problem #24 to me. >>=20 >> - 20130911.1448: Colored tags generate an error when C-x C-w'ing the age= nda >>=20 >> I'll try to debug and fix it myself. I'll come back if I don't succeed. > > OK, will do that, thank you. Best regards, Seb --=20 Sebastien Vauban