From: Christian Egli <christian.egli@sbszh.ch>
To: emacs-orgmode@gnu.org
Subject: Re: Sorting by todo-keyword
Date: Thu, 14 Aug 2008 16:38:00 +0200 [thread overview]
Message-ID: <j2od3vachj.fsf@sbszh.ch> (raw)
In-Reply-To: e7cdbe30808122002n43405e01q755394c9d78e918c@mail.gmail.com
Manish <mailtomanish.sharma@gmail.com> writes:
> I tried applying the patch to 5.18a but it failed again. How can I
> help get more debug information?
>
> ,----
> | lappy:~/elisp/org-mode.git $ git checkout -b release_5.18a release_5.18a
> | Checking out files: 100% (112/112), done.
> | Switched to a new branch "release_5.18a"
> | lappy:~/elisp/org-mode.git $ git branch
> | master
> | * release_5.18a
> | zms
> | lappy:~/elisp/org-mode.git $ git-apply.exe 5066-001.bin
> | error: patch failed: org.el:2679
> | error: org.el: patch does not apply
> `----
Yes, I know, I tried myself. The problem is most likely that Carsten
rearranged the source code substantially. My patch was for org.el but
the changes should now probably be applied to lisp/org-agenda.el.
I don't know git well enough to judge if there is an automated way to
bring this patch back to life. The only way I see ATM is to manually
port it to the current version of org.
Basically the patch is (was) fairly simple:
* add a function org-cmp-todo-state along the lines of org-cmp-* which
compares todo states.
* add this function to org-entries-lessp
* adapt the various functions that are invoked by
org-finalize-agenda-entries (org-agenda-get-todos,
org-agenda-get-scheduled, etc) to include the todo state in the
properties of the text for the agenda line. You can probably get
some inspiration from my old patch.
HTH
Christian
prev parent reply other threads:[~2008-08-14 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 18:42 Sorting by todo-keyword Jan Seeger
2008-08-12 8:06 ` Christian Egli
2008-08-12 8:42 ` Manish
2008-08-12 8:52 ` Christian Egli
2008-08-12 9:15 ` Manish
2008-08-13 3:02 ` Manish
2008-08-14 14:38 ` Christian Egli [this message]
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=j2od3vachj.fsf@sbszh.ch \
--to=christian.egli@sbszh.ch \
--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).