[O] Firefox 4 in Ubuntu 11.04 and org-protocol
Hi! Has anybody been succesful in using the tutorial http://orgmode.org/worg/org-contrib/org-protocol.html in the setting described in the subject (Firefox 4, Ubuntu 11.04)? Those instructions worked perfectly for me in previous versions of Ubuntu and Firefox, but now I always get the dreaded message Firefox doesn't know how to open this address, because the protocol (org-protocol) isn't associated with any program. I have run the two commands starting with 'gconftool-2', I have checked with gconf-editor that the settings intended have been set, I have tried the method in http://kb.mozillazine.org/Register_protocol and also that in http://support.mozilla.com/en-US/kb/The%20protocol%20is%20not%20associated%20with%20any%20program?s=protocol&as=s. No luck so far...
Re: [O] Bug: No property change from ‘org-clock-sum’
Carsten Dominik writes: > However, I seen now that there is a bug here, cause by a rewrite (for > speed) of property access some time ago. After that rewrite, the > special CLOCKSUM property used by org-invoice.el was no longer > accessible. Thanks! I am glad to finally have attracted enough attention to this bug :-) Bernt Hansen writes: > Carsten Dominik writes: > > This problem has just been fixed, so with the current git master, > > org-invoice.el should work again. > > Ah! Thanks Carsten. It does indeed return values after this fix. Great. I look forward to a new release making its way into Debian. Thanks again for the diagnosis and bug fix, guys. -- \ “Pinky, are you pondering what I'm pondering?” “I think so, | `\Brain, but if we give peas a chance, won't the lima beans feel | _o__)left out?” —_Pinky and The Brain_ | Ben Finney
Re: [O] [PATCH] worg/org-contrib list items are missing
Hello, Ethan Ligon writes: > Here's a patch that fixes the regex in org-list.el: I have applied the patch to master branch. Thank you. Regards, -- Nicolas Goaziou
Re: [O] case sensitivity in sorting
Hello, Samuel Wales writes: > C-c ^ seems to sort case-sensitively regardless of argument. > > 1) a > 2) B This should be fixed now. Thank you for reporting this. Regards, -- Nicolas Goaziou
Re: [O] [Orgmode] Grouping clock report by tag?
John Hendy writes: > On Thu, May 5, 2011 at 6:08 PM, Bernt Hansen wrote: >> Niels Giesen posted some patches for summarizing clock reports by >> arbitrary properties. Maybe this will be useful? >> >> http://thread.gmane.org/gmane.emacs.orgmode/40160 >> >> I'm not aware of any functionality that does what you describe above. >> > > His is actually pretty darn close. It looks like Carsten just > re-requested a patch in some standard format a few days ago, so > perhaps I can hold my breath for it to get applied. Otherwise, do I > just copy/paste his code into manual files and then do something like > 'patch -p0 file.patch'? > > And will it get overrun by my next pull? > > Sorry... never applied a patch to org-mode files. Creating the patches is fairly easy. 1) Take the email with the patches in it and cut out the #+begin_src and #+end_src lines and everything in front of the first patch so the file is just the 3 patches consecutively. 2) Save the file (I put mine in /tmp/patch) 3) Create a local topic branch for these patches $ git checkout -b clock-report-by-property origin/master 4) Apply the patches to create the 3 commits on this branch $ git am /tmp/patch Then try it out. I've done the above steps and pushed the result to git://git.norang.ca/org-mode.git ng/clock-reports-by-property after fixing up the email address since git doesn't like the syntax provided in the mail. I have not fixed the changelog entries for these patches but they should be fine for just giving it a trial run. You can grab the patches from my git repository with $ git fetch git://git.norang.ca/org-mode.git ng/clock-reports-by-property This will create a temporary ref called FETCH_HEAD which you can check out. $ git checkout FETCH_HEAD and later just go back to your master with $ git checkout master HTH, Bernt
[O] case sensitivity in sorting
C-c ^ seems to sort case-sensitively regardless of argument. 1) a 2) B Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com/2010/12/welcome-to-kafka-pandemic-two-forces_9182.html I support the Whittemore-Peterson Institute (WPI) === I want to see the original (pre-hold) Lo et al. 2010 NIH/FDA/Harvard MRV paper.
Re: [O] PERL, org-mode and literal document input.
a...@ufl.edu (Allen S. Rout) writes: > "Eric Schulte" writes: > >> alternately you could just include your yaml as an example block >> >> #+results: yaml-config >> : erpalpha:... > > This is what I've eventually done. It feels dirty; I'm asserting the > "results" block of a nonexistent src, and saying "edit this". But > perhaps I should just deal with it. > > Am I silly to want to be able to label it 'srcname' instead of > 'results'? My elisp-fu is not good enough to let me define > > :var-but-read-the-src-block > These are just labels, and more than that they are just the labels that first occurred to Dan and I. Semantically they are used to name data, and I can understand your "dirty" feeling of having results without a related code block, but rest assured, Babel does not assume that there should exist such a code block and this sort of usage is both supported and intended. To emphasize this point, I've just pushed up a change so that you can now label such inline data with #+data: my-named-data : 3 and more importantly you can add your own labels by customizing the new `org-babel-data-names' variable. Cheers -- Eric n Note: if you update the `org-babel-data-names' variable you might want to later run the following code... (setq org-babel-result-regexp (concat "^[ \t]*#\\+" (regexp-opt org-babel-data-names) "\\(\\[\\([[:alnum:]]+\\)\\]\\)?\\:[ \t]*")) > > - Allen S. Rout > > > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [Orgmode] Grouping clock report by tag?
On Thu, May 5, 2011 at 6:08 PM, Bernt Hansen wrote: > John Hendy writes: > >> Following up on this again... It's been almost 2mos. Is there any way >> to add a tag grouping to clock reports rather than needing to create >> clock reports for every tag? >> >> Many thanks, >> John >> >> My initial example: >> >> A rough idea might be like this: >> >> --- >> >> #+BEGIN: clocktable :maxlevel 2 :scope agenda >> Clock summary at [2011-03-06 Sun 17:59] >> | Tag | Headline | Time | | File | >> |--+--+-+--+| >> | | ALL *Total time* | *10:00* | | | >> |--+--+-+--+| >> | Tag1 | *Tag time* | *5:00* | | | >> | | [2011-02-04 Fri] | 3:30 | | 2011-02Feb.org | >> | | Some task | | 3:30 | | >> | | [2011-01-21 Fri] | 0:30 | | 2011-01Jan.org | >> | | Some task | | 0:30 | | >> | | [2010-12-09 Thu] | 1:00 | | 2010-12Dec.org | >> | | Some task | | 1:00 | | >> |--+--+-+--+| >> | Tag2 | *Tag time* | *5:00* | | | >> | | [2011-02-04 Fri] | 3:30 | | 2011-02Feb.org | >> | | Some task | | 3:30 | | >> | | [2011-01-21 Fri] | 0:30 | | 2011-01Jan.org | >> | | Some task | | 0:30 | | >> | | [2010-12-09 Thu] | 1:00 | | 2010-12Dec.org | >> | | Some task | | 1:00 | | >> |--+--+-+--+| >> - > > Hi John, > > Niels Giesen posted some patches for summarizing clock reports by > arbitrary properties. Maybe this will be useful? > > http://thread.gmane.org/gmane.emacs.orgmode/40160 > > I'm not aware of any functionality that does what you describe above. > His is actually pretty darn close. It looks like Carsten just re-requested a patch in some standard format a few days ago, so perhaps I can hold my breath for it to get applied. Otherwise, do I just copy/paste his code into manual files and then do something like 'patch -p0 file.patch'? And will it get overrun by my next pull? Sorry... never applied a patch to org-mode files. John > Regards, > Bernt >
Re: [O] PERL, org-mode and literal document input.
"Eric Schulte" writes: > alternately you could just include your yaml as an example block > > #+results: yaml-config > : erpalpha:... This is what I've eventually done. It feels dirty; I'm asserting the "results" block of a nonexistent src, and saying "edit this". But perhaps I should just deal with it. Am I silly to want to be able to label it 'srcname' instead of 'results'? My elisp-fu is not good enough to let me define :var-but-read-the-src-block - Allen S. Rout
Re: [O] turn headline(s) into plain list?
Juan Pechiar writes: > Hi, > > 'C-c -' may help to some extent: > > Cycle the entire list level through the different itemize/enumerate > bullets (‘-’, ‘+’, ‘*’, ‘1.’, ‘1)’) or a subset of them, depending on > org-plain-list-ordered- item-terminator, the type of list, and its > position17. With a numeric prefix argument N, select the Nth bullet > from this list. If there is an active region when calling this, > selected text will be changed into an item. With a prefix argument, > all lines will be converted to list items. If the first line already > was a list item, any item marker will be removed from the list. > Finally, even without an active region, a normal line will be > converted into a list item. > > It will convert headings into nested list items, but not the other > way. C-c * converts the other way. -Bernt > > Regards, > .j. > > On Fri, May 06, 2011 at 02:39:27PM -0400, Gary Oberbrunner wrote: >> Is there any way to turn a headline (and its subtree) into a plain >> list (and nested list items)? Or better yet, turn all level N and >> below headlines into plain lists at the corresponding level? >>
Re: [O] orgtbl multicolumn support
Michael Bach writes:
What kind of evil, sleep-deprived line of thoughts took me when I wrote
this? Must have been too late for anything remotely meaningful. This
one clearly did not deserve any answer... Sorry for the noise
> Michael Bach writes:
>
> # edit
>
>> Dear org-mode Users and Developers,
>
>> I just wanted to know whether there are plans to support multicolumns in
>> default orgtbl-to-latex. Something along these lines:
>>
>> #+ORGTBL: SEND multicol orgtbl-to-latex :splice t :skip 0 :hline "\\midrule"
>> | | a | b | c |
>> |---+---+-+---|
>> | 1 | | mc(2)(c)(3) | |
>> | | 2 | mc(2)(c)(4) | |
>>
>> Would produce
>>
>> % % BEGIN RECEIVE ORGTBL multicol
>> & a & b & c\NN
>> \midrule
>> 1 & & \multicolumn{2}{c}{3} & \NN
>> & 2 & \multicolumn{2}{c}{4} & \LL
>> % END RECEIVE ORGTBL multicol
>
> # This should correctly read:
>
> % % BEGIN RECEIVE ORGTBL multicol
> & a & b & c \\
> \midrule
> 1 & & \multicolumn{2}{c}{3} \\
> & 2 & \multicolumn{2}{c}{4} \\
> % END RECEIVE ORGTBL multicol
>
>> The reason being that I would like to use \multicolumn often in the
>> middle of an orgtbl. My workarounds with manually inserting the LaTeX
>> macro are clumsy.
>>
>> I understood that users should write their own conversion functions. If
>> I was going to try my fresh elisp fu, I wanted to ask here whether there
>> exists a generic orgtbl syntax to implement the above intercell
>> modification. I read the doc for version 7.5 but maybe there are also
>> new methods in the dev version which I freshly use.
>>
>> Kind Regards,
>> Michael Bach
Re: [O] turn headline(s) into plain list?
Hi, 'C-c -' may help to some extent: Cycle the entire list level through the different itemize/enumerate bullets (‘-’, ‘+’, ‘*’, ‘1.’, ‘1)’) or a subset of them, depending on org-plain-list-ordered- item-terminator, the type of list, and its position17. With a numeric prefix argument N, select the Nth bullet from this list. If there is an active region when calling this, selected text will be changed into an item. With a prefix argument, all lines will be converted to list items. If the first line already was a list item, any item marker will be removed from the list. Finally, even without an active region, a normal line will be converted into a list item. It will convert headings into nested list items, but not the other way. Regards, .j. On Fri, May 06, 2011 at 02:39:27PM -0400, Gary Oberbrunner wrote: > Is there any way to turn a headline (and its subtree) into a plain > list (and nested list items)? Or better yet, turn all level N and > below headlines into plain lists at the corresponding level? >
Re: [O] turn headline(s) into plain list?
Gary Oberbrunner writes: > Is there any way to turn a headline (and its subtree) into a plain > list (and nested list items)? Or better yet, turn all level N and > below headlines into plain lists at the corresponding level? Hi Gary, Just select the subtree of headings you want to convert and hit C-c - In the example below I select lines 2-17 (Subheading 1 to the line before All done) --8<---cut here---start->8--- * Lists ** This is a heading *** Subheading 1 *** Subheading 2 [2011-05-06 Fri 14:50] *** Subheading3 [2011-05-06 Fri 14:51] Three.1 [2011-05-06 Fri 14:51] Three.2 [2011-05-06 Fri 14:51] *** Four [2011-05-06 Fri 14:51] Five [2011-05-06 Fri 14:51] * Six [2011-05-06 Fri 14:51] * All done [2011-05-06 Fri 14:51] --8<---cut here---end--->8--- and then C-c - gives me this: --8<---cut here---start->8--- * Lists ** This is a heading - Subheading 1 - Subheading 2 [2011-05-06 Fri 14:50] - Subheading3 [2011-05-06 Fri 14:51] - Three.1 [2011-05-06 Fri 14:51] - Three.2 [2011-05-06 Fri 14:51] - Four [2011-05-06 Fri 14:51] - Five [2011-05-06 Fri 14:51] - Six [2011-05-06 Fri 14:51] * All done [2011-05-06 Fri 14:51] --8<---cut here---end--->8--- Regards, Bernt
[O] turn headline(s) into plain list?
Is there any way to turn a headline (and its subtree) into a plain list (and nested list items)? Or better yet, turn all level N and below headlines into plain lists at the corresponding level? -- -- Gary
Re: [O] Agenda todo filter order
Hi Carsten,
Thanks for the patch! This almost does what I want :)
This patch works for TODO agendas but not tags match agendas which is
what I am trying to use.
C-c a y returns the result I want
C-c a x should be identical and is not.
,[ C-c a y ]
| Non Project TODO Tasks
| test: TODO Single Task
| test: TODO Task Three
| test: TODO Task Four
`
,[ C-c a x ]
| Non Project Tasks
| test: TODO Single Task
| test: TODO Subtask Four
| test: TODO Subtask Five
| test: TODO Subtask Six
| test: TODO Subtask Seven
| test: TODO Subtask Eight
| test: TODO Subtask Nine
| test: TODO Task Three
| test: TODO Task Four
`
Below is the minimal emacs setup which I'm using to test:
Regards,
Bernt
~/bin/minimal-emacs
--8<---cut here---start->8---
#!/bin/sh
TESTEL=
TESTFILE=/tmp/test.el
if test -e $TESTFILE
then
TESTEL="-l /tmp/test.el"
fi
emacs -q -l ~/minimal.emacs $TESTEL $1
--8<---cut here---end--->8---
~/minimal.emacs
--8<---cut here---start->8---
(add-to-list 'load-path (expand-file-name "~/git/org-mode/lisp"))
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
(require 'org-install)
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
(global-set-key "\C-cb" 'org-iswitchb)
--8<---cut here---end--->8---
/tmp/test.el
--8<---cut here---start->8---
(setq org-agenda-files (list "/tmp/test.org"))
(setq org-agenda-todo-ignore-scheduled t)
(setq org-agenda-todo-ignore-deadlines t)
(setq org-agenda-tags-todo-honor-ignore-options t)
(setq org-agenda-custom-commands (quote (("x" "Non-Project Tasks" tags-todo "/!"
((org-agenda-overriding-header "Non
Project Tasks")
(org-agenda-skip-function
'bh/skip-project-trees)))
("y" "Non-Project TODO Tasks" todo ""
((org-agenda-overriding-header "Non
Project TODO Tasks")
(org-agenda-skip-function
'bh/skip-project-trees))
(defun bh/is-subproject-p ()
"Any task which is a subtask of another project"
(let ((is-subproject)
(is-a-task (member (nth 2 (org-heading-components))
org-todo-keywords-1)))
(save-excursion
(while (and (not is-subproject) (org-up-heading-safe))
(when (member (nth 2 (org-heading-components)) org-todo-keywords-1)
(setq is-subproject t
(and is-a-task is-subproject)))
(defun bh/is-project-p ()
"Any task with a todo keyword subtask and is not a subtask of another project
This does not support projects with subprojects"
(let ((has-subtask)
(subtree-end (save-excursion (org-end-of-subtree t)))
(is-subproject (bh/is-subproject-p))
(is-a-task (member (nth 2 (org-heading-components))
org-todo-keywords-1)))
(save-excursion
(forward-line 1)
(while (and (not has-subtask)
(< (point) subtree-end)
(re-search-forward "^\*+ " subtree-end t))
(when (member (org-get-todo-state) org-todo-keywords-1)
(setq has-subtask t
(and is-a-task has-subtask (not is-subproject
(defun bh/skip-project-trees ()
"Skip trees that are projects"
(let ((subtree-end (save-excursion (org-end-of-subtree t
(cond
((bh/is-project-p)
subtree-end)
(t
nil
--8<---cut here---end--->8---
/tmp/test.org
--8<---cut here---start->8---
* TODO Single Task
* TODO Project One
** TODO Subtask One
** TODO Subtask Two
** TODO Subtask Three
* TODO Project Two
DEADLINE: <2011-05-13 Fri>
** TODO Subtask Four
** TODO Subtask Five
** TODO Subtask Six
* TODO Project Three
SCHEDULED: <2011-05-08 Sun>
** TODO Subtask Seven
** TODO Subtask Eight
** TODO Subtask Nine
* Tasks
** TODO Task One
DEADLINE: <2011-05-20 Fri>
** TODO Task Two
SCHEDULED: <2011-05-13 Fri>
** TODO Task Three
** TODO Task Four
--8<---cut here---end--->8---
Carsten Dominik writes:
> Hi Bernt,
>
> I don't see a compelling reason why these two skipping checks could not
> be exchanged:
> ---
> diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
> index 609edd4..a386a18 100644
> --- a/lisp/org-agenda.el
> +++ b/lisp/org-agenda.el
> @@ -4573,6 +4573,7 @@ the documentation of `org-diary'."
> (goto-char (point-min))
> (while (re-search-forward regexp nil t)
>(catch :skip
> + (org-agenda-skip)
> (save-match-data
> (beginning-of-line)
> (setq beg (point) end (save-excursion (out
Re: [O] Collapse LaTeX source before start of main document?
On Fri, 06 May 2011 16:41:19 +0100 Eric S Fraga wrote: > It works, however, if there is at least one headline *before* the one > to be omitted, one that will not be omitted; if the omitted one is the > first headline, the whole block is gone. Strange. I can confirm this, when I had tried this it I was ignoring only headlines at the end. Ignoring the first headline behaves as you and Chris describe. -- Suvayu Open source is the future. It sets us free.
Re: [O] Collapse LaTeX source before start of main document?
Suvayu Ali writes: > On Thu, 05 May 2011 17:45:13 + > chris.m.mal...@gmail.com wrote: > >> Hi Suvayu, >> >> I think Matt's lisp code /should/ work for doing exactly what we are >> talking about, but for some reason I can't get it to work with LaTeX >> export. >> > > I just tried Matt's code, worked very smoothly for me. :) This is strange. I have tried it just now and it fails for me for a very simple case. It works for html and not for latex. The same bol and eol values are found in either case (which is as it should be, of course). It works, however, if there is at least one headline *before* the one to be omitted, one that will not be omitted; if the omitted one is the first headline, the whole block is gone. Strange. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.258.ga173)
Re: [O] Bug: No property change from ‘org-clock-sum’
Peter Jones writes: > Bernt Hansen writes: >> The org-invoice.el contributed file created by Peter Jones uses a >> CLOCKSUM property but I'm not sure if this is intended to be updated >> manually or automatically from the clocking lines in org. I've CC-ed >> Peter in case he can shed any light on this. > > IIRC, when I wrote org-invoice.el the function (org-clock-sum) updated > the CLOCKSUM entry in the property drawer. I don't remember anything > about text properties being updated, and that doesn't seem very useful > to me. Hi Peter, Carsten just pushed a fix so org-invoice.el can again access the CLOCKSUM special property. I've mocked up a sample task tree with clock times and dates and tried to generate an invoice using a rate of $60 - which makes each clock minute $1. The total time in the tree is 55 minutes so this invoice should be $55 but the total is $115. Please let me know if I'm doing this completely wrong. org-invoice.el has a number of problems on a sample tree I ran this against. The clocked time in this file is as follows: #+BEGIN: columnview :hlines 1 :id: local | Task | Estimated Effort | CLOCKSUM | |+--+--| | ** DONE Project Foo| | 0:55 | | *** DONE Task 1 for foo| | 0:05 | | *** DONE Task 2 for foo| | 0:20 | | DONE Task 2.1 for foo | | 0:05 | | *** DONE Task 3 for foo| | 0:20 | | DONE Task 3.1 for foo | | 0:05 | | *** DONE Task 4 for foo| | 0:05 | #+END: There are 5 minutes clocked in the Project Foo task and all other clocked times are in the subtasks. There are 55 minutes total clocked on this project. The clock detail per task is | Task | Clocked Minutes | |+-| | ** DONE Project Foo|0:05 | | *** DONE Task 1 for foo|0:05 | | *** DONE Task 2 for foo|0:15 | | DONE Task 2.1 for foo |0:05 | | *** DONE Task 3 for foo|0:15 | | DONE Task 3.1 for foo |0:05 | | *** DONE Task 4 for foo|0:05 | and the resulting invoice looks like this: | Task / Date | Time | Price | |---+--+| | Tuesday, April 19, 2011 | 0:55 | 55.00 | | DONE Project Foo | 0:55 | 55.00 | |---+--+| | Monday, April 18, 2011| 0:05 | 5.00 | | DONE Task 1 for foo | 0:05 | 5.00 | |---+--+| | Tuesday, April 19, 2011 | 0:25 | 25.00 | | DONE Task 2 for foo | 0:20 | 20.00 | | DONE Task 2.1 for foo | 0:05 | 5.00 | |---+--+| | Wednesday, April 20, 2011 | 0:25 | 25.00 | | DONE Task 3 for foo | 0:20 | 20.00 | | DONE Task 3.1 for foo | 0:05 | 5.00 | |---+--+| | Tuesday, April 19, 2011 | 0:05 | 5.00 | | DONE Task 3 for foo | 0:05 | 5.00 | |---+--+| | Total:| 1:55 | 115.00 | There is double accounting of clock times in the invoice. 1) Trees with subtasks are double accounted for time. This inflates the invoice and is incorrect. 2) The total time at the bottom of the invoice also includes double accounted for clock times. The 3rd entry |-+--+---| | Tuesday, April 19, 2011 | 0:25 | 25.00 | | DONE Task 2 for foo | 0:20 | 20.00 | | DONE Task 2.1 for foo | 0:05 | 5.00 | |-+--+---| is really only 20 minutes long with 15 minutes clocked in the Task 2 parent task and 5 minutes clocked in the Task 2.1 subtask. The total for the day should be 0:20 not 0:25 which also affects the invoice total at the bottom. Ditto for the 4th entry. The Project Foo entry includes all 55 minutes for the project and is added to all of the subtask entries which inflates the total for the invoice. Regards, Bernt --8<---cut here---start->8--- * Invoices ** DONE Project Foo CLOSED: [2011-04-19 Tue 13:57] :LOGBOOK: - State "DONE" from "STARTED"[2011-04-19 Tue 13:57] CLOCK: [2011-04-18 Mon 16:13]--[2011-04-18 Mon 16:18] => 0:05 :END: :PROPERTIES: :RATE: 60 :END: [2011-04-18 Mon 15:36] #+BEGIN: columnview :hlines 1 :id: local | Task | Estimated Effort | CLOCKSUM | |+--+--| | ** DONE Project Foo| | 0:55 | | *** DONE Task 1 for foo| | 0:05 | | *** DONE Task 2 for foo| | 0:20 | | DONE Task 2.1 for foo | | 0:05 | | *** DONE Task 3 for foo| | 0:20 | | DONE Task 3.1 for foo
Re: [O] Bug: No property change from ‘org-clock-sum’
Carsten Dominik writes: > No. CLOCKSUM is a special property, and it can be used to > access the clocking sum of an entry after (org-clock-sum) has > been called. This is what org-invoice does. It calls > org-clock-sum to do the computation, and then used the property > API to get to the value. > > However, I seen now that there is a bug here, cause by a > rewrite (for speed) of property access some time ago. > After that rewrite, the special CLOCKSUM property used > by org-invoice.el was no longer accessible. > > This problem has just been fixed, so with the current git master, > org-invoice.el should work again. Ah! Thanks Carsten. It does indeed return values after this fix. However there are numerous problems with the resulting invoice for a sample tree I have with clocked data. I'll send these details to the list shortly. Regards, Bernt
Re: [O] Slowness in Org - how to disable mouse popups/followings
Am 06.05.2011 16:29, schrieb Tom: > Rainer Stengele diplan.de> writes: > >> I am always struggling with performance problemns when using >> Emacs orgmode under Windows. Under Linux I do not see slow >> respsonses for my several and long org files. >> >> Under Windows I run GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600) >> from trunk 2011-02-16 on LENNART-69DE564 (patched) >> >> Hovering with the emouse over the Emacs windows I see some >> popups showing up very slowly. Emacs also highlights the links in >> my org files when moving the mouse over it. This all semmes to >> slow down Emacs a lot - under Windows ... > > > Sounds like an Emacs 24 problem, because with Emacs 23 I don't experience > this on Windows. You may want to let the emacs developers know about this. > > Hi, I am afraid not - the slowness I also had with emacs 23. It looks like Emacs for Windows in general has performance problems. Look at older threads where we fought other display performance problems under windows. So maybe someone has an idea how to disable the mouse functions. -- Rainer
Re: [O] Bug: No property change from ‘org-clock-sum’
On 7.4.2011, at 23:51, Ben Finney wrote: > Howdy all, > > When I use ‘org-clock-sum’ in Org-mode version 7.4, nothing appears to > happen: the items in the subtree are not updated and no ‘CLOCKSUM’ > property appears. CLOCKSUM is a special property which is only a way to access clocking information, but the property is never set literally. org-invoice was broken due to changes in the property code in org.el, fixed now. HTH - Carsten > > Org-mode version 7.4 > GNU Emacs 23.2.1 (powerpc-unknown-linux-gnu, GTK+ Version 2.20.1) of > 2010-12-12 on porpora, modified by Debian > > > I'm trying to generate an invoice report using ‘org-invoice.el’. > > The items on which I want to report have clock entries, generated > correctly with ‘org-clock-in’ and ‘org-clock-out’. An example: > > = > * foo > ** bar > *** [2011-03-24 Thu] >CLOCK: [2011-03-24 Thu 14:15]--[2011-03-24 Thu 18:03] => 3:48 >CLOCK: [2011-03-24 Thu 09:10]--[2011-03-24 Thu 12:27] => 3:17 > *** [2011-03-23 Wed] >CLOCK: [2011-03-23 Wed 14:10]--[2011-03-23 Wed 18:16] => 4:06 >CLOCK: [2011-03-23 Wed 09:30]--[2011-03-23 Wed 13:10] => 3:40 > *** [2011-03-22 Tue] >CLOCK: [2011-03-22 Tue 14:00]--[2011-03-22 Tue 17:30] => 3:30 >CLOCK: [2011-03-22 Tue 08:58]--[2011-03-22 Tue 13:31] => 4:33 > = > > According to the doc string for ‘org-invoice-report’, the ‘CLOCKSUM’ > property on each item in the subtree will be used for the report. > > So apparently I need to ‘org-clock-sum’ on the tree before updating the > report, in order to automatically generate the ‘CLOCKSUM’ property. But > that function doesn't change anything. > > Why wouldn't the ‘org-clock-sum’ function do what its doc string says? > How should I be updating the ‘CLOCKSUM’ property? > > -- > \“The industrial system is profoundly dependent on commercial | > `\ television and could not exist in its present form without it.” | > _o__)—John Kenneth Galbraith, _The New Industrial State_, 1967 | > Ben Finney > >
Re: [O] Bug: No property change from ‘org-clock-sum’
On 6.5.2011, at 15:56, Bernt Hansen wrote: > Ben Finney writes: > >> Bernt Hansen writes: >> >>> I don't think the org-clock-sum function does what you think/want it >>> to do. The docstring says it sets text properties on the headline - so >>> I don't think it is intended to update a CLOCKSUM property in the >>> headings. >> >> I don't underastand the distinction. Isn't the CLOCKSUM property a text >> property? What do I need to know here? > > Sorry I didn't explain that very well. Hopefully this will shed a > little more light on this. > > Text properties is an emacs feature where you can add extra (invisible, > and temporary) data to text in an emacs buffer. > > An Org-mode properties are part of the org file and normally lives in > the :PROPERTY: drawer. > > The column view overlay is displayed using emacs text properties - and > this doesn't alter the data in the org file. Thus the org-invoice.el > code that queries the _org_ property CLOCKSUM never gets a value. > >> >>> These text properties are temporary (ie. not saved in the org file) and >>> I think these are used by the column view overlays for display-only. >>> >>> The org-invoice.el contributed file created by Peter Jones uses a >>> CLOCKSUM property but I'm not sure if this is intended to be updated >>> manually or automatically from the clocking lines in org. I've CC-ed >>> Peter in case he can shed any light on this. >> >> Thanks. It does seem that they're much the same purpose, so I hope they >> can be unified. > > I think the fix is probably to make org-invoice.el look for the CLOCKSUM > text property instead of a CLOCKSUM org-mode property value. > org-invoice.el should probably also automatically call org-clock-sum so > this doesn't need to be a manual step. No. CLOCKSUM is a special property, and it can be used to access the clocking sum of an entry after (org-clock-sum) has been called. This is what org-invoice does. It calls org-clock-sum to do the computation, and then used the property API to get to the value. However, I seen now that there is a bug here, cause by a rewrite (for speed) of property access some time ago. After that rewrite, the special CLOCKSUM property used by org-invoice.el was no longer accessible. This problem has just been fixed, so with the current git master, org-invoice.el should work again. - Carsten
Re: [O] Bug: No property change from ‘org-clock-sum’
Bernt Hansen writes: > The org-invoice.el contributed file created by Peter Jones uses a > CLOCKSUM property but I'm not sure if this is intended to be updated > manually or automatically from the clocking lines in org. I've CC-ed > Peter in case he can shed any light on this. IIRC, when I wrote org-invoice.el the function (org-clock-sum) updated the CLOCKSUM entry in the property drawer. I don't remember anything about text properties being updated, and that doesn't seem very useful to me. -- Peter Jones - pmade inc. 303-219-0226 http://pmade.com
Re: [O] Slowness in Org - how to disable mouse popups/followings
Rainer Stengele diplan.de> writes: > I am always struggling with performance problemns when using > Emacs orgmode under Windows. Under Linux I do not see slow > respsonses for my several and long org files. > > Under Windows I run GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600) > from trunk 2011-02-16 on LENNART-69DE564 (patched) > > Hovering with the emouse over the Emacs windows I see some > popups showing up very slowly. Emacs also highlights the links in > my org files when moving the mouse over it. This all semmes to > slow down Emacs a lot - under Windows ... Sounds like an Emacs 24 problem, because with Emacs 23 I don't experience this on Windows. You may want to let the emacs developers know about this.
Re: [O] outline formatting in html
Thanks, this is nice. It is fairly easy to add indentation using the padding-left css property. The interaction between org OPTIONS, html export, and css styles has the virtue of allowing a lot of flexibility. On the other hand, it sure can be confusing. It is not entirely clear what the "right" approach is for someone like myself who only knows enough css to be dangerous. The file simple-outline.css might make a good addition to worg. On Fri, May 6, 2011 at 5:32 AM, Christian Moe wrote: > Hi, > > That would be a good feature to have. While waiting for someone to patch it > in, a workaround for HTML output would be to turn off section numbering and > then fake it with CSS. I enclose a four-level example I happen to have lying > around. You can extend if needed (note that the title becomes h1, so the > top-level heading is h2). > > Yours, > Christian > > > > On 5/6/11 5:59 AM, Skip Collins wrote: >> >> I thought this would be easy. But I cannot find a way to get html >> formatted the way I want. I would like to view org content in >> "traditional" outline format, with indentation, Roman numerals for >> the top level heading, etc: >> >> I. This is a top level heading >> II. Here is another level-1 heading >> A. Here is a level 2 heading >> 1. This is a level-3 heading >> 2. Another level-3 >> a. Level-4 >> b. Another level-4 >> (1) Level-5 >> (a) Level-6 >> B. Another level 2 >> >> When I customize org-export-section-number-format, I do not get >> exactly what I want in html output. All heading numbers include >> higher level numbers, e.g. II.A.2.b. I am looking for a less cluttered >> output in which a heading only includes the single counter for its level.
Re: [O] Bug: No property change from ‘org-clock-sum’
Ben Finney writes: > Bernt Hansen writes: > >> I don't think the org-clock-sum function does what you think/want it >> to do. The docstring says it sets text properties on the headline - so >> I don't think it is intended to update a CLOCKSUM property in the >> headings. > > I don't underastand the distinction. Isn't the CLOCKSUM property a text > property? What do I need to know here? Sorry I didn't explain that very well. Hopefully this will shed a little more light on this. Text properties is an emacs feature where you can add extra (invisible, and temporary) data to text in an emacs buffer. An Org-mode properties are part of the org file and normally lives in the :PROPERTY: drawer. The column view overlay is displayed using emacs text properties - and this doesn't alter the data in the org file. Thus the org-invoice.el code that queries the _org_ property CLOCKSUM never gets a value. > >> These text properties are temporary (ie. not saved in the org file) and >> I think these are used by the column view overlays for display-only. >> >> The org-invoice.el contributed file created by Peter Jones uses a >> CLOCKSUM property but I'm not sure if this is intended to be updated >> manually or automatically from the clocking lines in org. I've CC-ed >> Peter in case he can shed any light on this. > > Thanks. It does seem that they're much the same purpose, so I hope they > can be unified. I think the fix is probably to make org-invoice.el look for the CLOCKSUM text property instead of a CLOCKSUM org-mode property value. org-invoice.el should probably also automatically call org-clock-sum so this doesn't need to be a manual step. Regards, Bernt
Re: [O] Any way to identify a DEADLINE or SCHEDULED item via org-agenda-prefix-format?
Anupam Sengupta writes: > Hello, > > In my custom agenda block, I wanted to distinguish between SCHEDULED and > DEADLINE items using a small character flag. The docstring for > `org-agenda-prefix-format' mentions %s as the one to use for the > scheduled/deadline string (as is used in the default agenda) - however, > this string does not seem to be working for me (orgmode 7.5). > > As an example of a custom agenda block: > > (tags-todo > "+TODO=\"TODO\"+SCHEDULED>=\"\"+SCHEDULED<\"\"|+TODO=\"TODO\"+DEADLINE>=\"\"+DEADLINE<\"\"|+TODO=\"TODO\"+TIMESTAMP>=\"\"+TIMESTAMP<\"\"" > ((org-agenda-overriding-header "\nToday's Action > Items\n") >(org-agenda-prefix-format " [ ] %12:c%?-12t % s"))) > > Note the % s in the `org-agenda-prefix-format' setting. All other > settings are showing up fine, but the schedule information is missing in > the display. AFAIK, scheduling information is not included when constructing tags or todo views. > As an aside, %s is not exactly what I need, as I was looking for a way > to display a single character flag (S or D for scheduled or deadline), > but this is also fine. You can control the display of scheduled and deadline information with org-agenda-scheduled-leaders and org-agenda-deadline-leaders, but I believe this only applies to the agenda view. Best, Matt
Re: [O] Collapse LaTeX source before start of main document?
Chris Malone writes: > @Matt: I can get your example to work fine for html export, but not > LaTeX export where the entire contents of the headline are removed as > well. =org-version=: 7.5 (release_7.5.105.g8d0c) if that makes any > difference. Hmm... I have no idea why the LaTeX backend is removing the content of that headline as well, as it survives in all other backends. Best, Matt
Re: [O] [Accepted] Making the output of %% functions linkable in agenda views
Bert Burgemeister writes:
> Just curious, is there anything I should have known that prevented the
> patch submitted in http://article.gmane.org/gmane.emacs.orgmode/39313,
Is it still in the bugtracker, or was it rejected? (I attempted to check
myself, but the patchwork site seems to be down right now.)
There has been a cascade of patches on the list recently (I plead guilty
to adding my fair share), and there aren't many people who are
authorized to push to the repo.
With your patch, what would happen if there were two or more links in
the headline?
* Two links
%%(format "%s" (concat "[[elisp:(info)]" "[Link to info]]"))
http://www.orgmode.org
This entry would show up in the agenda as:
org: [[elisp:(info)][Link to info]]
But AFAICT, hitting C-c C-o in the agenda-buffer (even on the elisp
link) would jump immediately to http://www.orgmode.org, bypassing the
opportunity to select the the %%(...) generated link.
Best,
Matt
>> From: Bert Burgemeister
>> Subject: [O] [PATCH] Bugfix: org-agenda-open-link
>> Newsgroups: gmane.emacs.orgmode
>> To: emacs-orgmode@gnu.org
>> Date: Sun, 13 Mar 2011 16:18:44 +0100
>>
>>
>> * Org-agenda.el (org-agenda-open-link): C-c C-o didn't open links
>> inserted via the `%%( )' mechanism, affecting usability of
>> `%%(org-bbdb-anniversaries).
>>
>> TINYCHANGE
>> ---
>>
>>
>> The bug was apparently introduced in commit
>> ba1e90893d128d8004e4cb6763af692c5a6cd677.
>>
>> --
>> Bert
>>
>>
>>
>> lisp/org-agenda.el | 14 +++---
>> 1 files changed, 7 insertions(+), 7 deletions(-)
>>
>> diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
>> index 4b4dd68..123668c 100644
>> --- a/lisp/org-agenda.el
>> +++ b/lisp/org-agenda.el
>> @@ -6742,13 +6742,13 @@ at the text of the entry itself."
>>(+ (point-at-bol)
>> (or (org-get-at-bol 'prefix-length) 0)
>> (cond
>> - (buffer
>> - (with-current-buffer buffer
>> -(save-excursion
>> - (save-restriction
>> -(widen)
>> -(goto-char marker)
>> -(org-offer-links-in-entry arg prefix)
>> + ((and buffer
>> + (with-current-buffer buffer
>> + (save-excursion
>> + (save-restriction
>> + (widen)
>> + (goto-char marker)
>> + (org-offer-links-in-entry arg prefix))
>> ((or (org-in-regexp (concat "\\(" org-bracket-link-regexp "\\)"))
>>(save-excursion
>> (beginning-of-line 1)
>> --
>> 1.7.2.3
>
> from being noticed?
Re: [O] inline task?
On Fri, May 6, 2011 at 1:49 AM, Piter_ wrote: > Hi all. > As I understand inlene-task is part of org-mode. > But I cant find it between functions. But the file is present in lisp > folder. > Do I have to enable it somehow? (require 'org-inlinetask) -- Suvayu Open source is the future. It sets us free.
[O] [PATCH 3/3] Adjust wl-contact functions to overall conventions.
---
contrib/lisp/org-contacts.el | 20 +++-
1 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el
index 60eb542..ff4374d 100644
--- a/contrib/lisp/org-contacts.el
+++ b/contrib/lisp/org-contacts.el
@@ -403,7 +403,7 @@ This adds `org-contacts-gnus-check-mail-address' and
(add-hook 'gnus-article-prepare-hook 'org-contacts-gnus-check-mail-address)
(add-hook 'gnus-article-prepare-hook 'org-contacts-gnus-store-last-mail))
-(defun wl-get-from-header-content ()
+(defun org-contacts-wl-get-from-header-content ()
"Retrieve the content of the `From' header of an email.
Works from wl-summary-mode and mime-view-mode - that is while viewing email.
Depends on Wanderlust been loaded."
@@ -429,16 +429,18 @@ See `org-contacts-wl-get-from-header-content' for
limitations."
(wl-address-header-extract-address from)
(defun org-contacts-template-wl-name (&optional return-value)
- (let ((from (wl-get-from-header-content)))
-(or (and from (wl-address-header-extract-realname from))
- return-value
- "%^{Name}")))
+ "Try to return the contact name for a template from wl.
+If not found return RETURN-VALUE or something that would ask the user."
+ (or (car (org-contacts-wl-get-name-email))
+ return-value
+ "%^{Name}"))
(defun org-contacts-template-wl-email (&optional return-value)
- (let ((from (wl-get-from-header-content)))
-(or (and from (wl-address-header-extract-address from))
- return-value
- (concat "%^{" org-contacts-email-property "}p"
+ "Try to return the contact email for a template from wl.
+If not found return RETURN-VALUE or something that would ask the user."
+ (or (cadr (org-contacts-wl-get-name-email))
+ return-value
+ (concat "%^{" org-contacts-email-property "}p")))
(defun org-contacts-view-send-email (&optional ask)
"Send email to the contact at point.
--
1.7.4.4
[O] [PATCH 2/3] Add name-email function for to unificate template interface.
--- contrib/lisp/org-contacts.el |8 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index f0cf131..60eb542 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -420,6 +420,14 @@ Depends on Wanderlust been loaded." (std11-fetch-field "From") (widen)) +(defun org-contacts-wl-get-name-email () + "Get name and email address from wanderlust email. +See `org-contacts-wl-get-from-header-content' for limitations." + (let ((from (wl-get-from-header-content))) +(when from + (cons (wl-address-header-extract-realname from) + (wl-address-header-extract-address from) + (defun org-contacts-template-wl-name (&optional return-value) (let ((from (wl-get-from-header-content))) (or (and from (wl-address-header-extract-realname from)) -- 1.7.4.4
[O] Adjust org-contacts-wl functions to used standards
Hi, Following the merge of org-contacts-wl with org-contacts I thought it would be nice to unify the interfaces. The patches follow separately. Open Problems: * Make both accessible through `org-contacts-template-name', I see two (a half) possibilities 1. Use a variable to specify a "name-email" function 2. pass a variable to `org-contacts-template-name' to choose per call 3. half: Use 2. but define functions (per backend) that call with the appropriate variable Michael pgpOgZ2H6z41w.pgp Description: PGP signature
[O] [PATCH 1/3] Add docstring for `wl-get-from-header-content'.
--- contrib/lisp/org-contacts.el |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index 3f4d97c..f0cf131 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -404,6 +404,9 @@ This adds `org-contacts-gnus-check-mail-address' and (add-hook 'gnus-article-prepare-hook 'org-contacts-gnus-store-last-mail)) (defun wl-get-from-header-content () + "Retrieve the content of the `From' header of an email. +Works from wl-summary-mode and mime-view-mode - that is while viewing email. +Depends on Wanderlust been loaded." (save-excursion (set-buffer (org-capture-get :original-buffer)) (cond -- 1.7.4.4
[O] Slowness in Org - how to disable mouse popups/followings
Hi, I am always struggling with performance problemns when using Emacs orgmode under Windows. Under Linux I do not see slow respsonses for my several and long org files. Under Windows I run GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600) from trunk 2011-02-16 on LENNART-69DE564 (patched) Hovering with the emouse over the Emacs windows I see some popups showing up very slowly. Emacs also highlights the links in my org files when moving the mouse over it. This all semmes to slow down Emacs a lot - under Windows ... I do not need the special mouse functionality in Orgmode. Is there a way to deactivate the highlighting of links etc.? I searched a bit in the custom variables but did not find the right places. -- Rainer
Re: [O] outline formatting in html
Hi,
That would be a good feature to have. While waiting for someone to
patch it in, a workaround for HTML output would be to turn off section
numbering and then fake it with CSS. I enclose a four-level example I
happen to have lying around. You can extend if needed (note that the
title becomes h1, so the top-level heading is h2).
Yours,
Christian
On 5/6/11 5:59 AM, Skip Collins wrote:
I thought this would be easy. But I cannot find a way to get html
formatted the way I want. I would like to view org content in
"traditional" outline format, with indentation, Roman numerals for
the top level heading, etc:
I. This is a top level heading
II. Here is another level-1 heading
A. Here is a level 2 heading
1. This is a level-3 heading
2. Another level-3
a. Level-4
b. Another level-4
(1) Level-5
(a) Level-6
B. Another level 2
When I customize org-export-section-number-format, I do not get
exactly what I want in html output. All heading numbers include
higher level numbers, e.g. II.A.2.b. I am looking for a less cluttered
output in which a heading only includes the single counter for its level.
body {
counter-reset: head1 head2 head3 head4;
}
.outline-2 h2:before {
counter-increment: head1;
content: counter(head1, upper-roman) ". ";
}
h2 {
counter-reset: head2 head3 head4;
}
h3:before {
counter-increment: head2;
content: counter(head2, upper-latin) ". ";
}
h3 {
counter-reset: head3 head4;
}
h4:before {
counter-increment: head3;
content: counter(head3, decimal) ". ";
}
h4 {
counter-reset: head4;
}
h5:before {
counter-increment: head4;
content: counter(head4, lower-latin) ". ";
}#+TITLE: css-simple-outline.org
#+OPTIONS: H:4 num:nil toc:nil
#+STYLE:
* Top heading, Level 1 (I)
** Level 2 subhead (A)
*** Level 3 subhead (1)
Level 4 subhead (a)
Level 4 subhead (b)
*** Level 3 subhead (2)
Level 4 subhead (a)
* Level 5 subhead (no formatting)
[O] inline task?
Hi all. As I understand inlene-task is part of org-mode. But I cant find it between functions. But the file is present in lisp folder. Do I have to enable it somehow? Thanks. Petro.
Re: [O] [semi-OT] issue trackers?
Matt Price writes: > I'm collaborating on a project where I'm starting to feel the need for > a shared issue tracker. Anyone have any suggestions? We use Redmine[1] here which is very nice and flexible. What I do is that I read the tasks from Redmine into org-mode using org-feed.el[2]. I have not had the time to implement a way to push my changes back to redmine. This should be doable as Redmine has a RESTful interface. John Wiegeley has shown a way to push back data to Bugzilla[3]. Hope that helps Christian Footnotes: [1] http://www.redmine.org/ [2] http://orgmode.org/worg/org-contrib/org-feed.html [3] http://www.mail-archive.com/emacs-orgmode@gnu.org/msg25391.html -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [Accepted] Making the output of %% functions linkable in agenda views
Carsten Dominik writes: > Patch 781 (http://patchwork.newartisans.com/patch/781/) is now "Accepted". > > Maintainer comment: none > > This relates to the following submission: > > http://mid.gmane.org/%3C87aaf3tv5l.fsf%40fastmail.fm%3E > > Here is the original message containing the patch: > >> Content-Type: text/plain; charset="utf-8" >> MIME-Version: 1.0 >> Content-Transfer-Encoding: 7bit >> Subject: [O] Making the output of %% functions linkable in agenda views >> Date: Wed, 04 May 2011 00:56:54 - >> From: Matt Lundin >> X-Patchwork-Id: 781 >> Message-Id: <87aaf3tv5l@fastmail.fm> >> To: charles.seb...@lcms.org (Sebold, Charles) >> Cc: emacs-orgmode >> >> charles.seb...@lcms.org writes: >> >> > On 7 Apr 2011, Charles Sebold wrote: >> > >> >> Here's a test. Take the line below and put it in an agenda file, then >> >> view the agenda. >> >> >> >> %%(format "%s" (concat "[[elisp:(info)]" "[Link to info]]")) >> >> >> >> The results as I see them give me a link that I can mouse-click on, >> >> but I can't move point to it and hit C-c C-o. >> >> >> >> What do I need to do to make this a normal org link in every way? Or >> >> is this a bug? >> >> >> >> Here's what seems to be going on. >> >> Clicking with the mouse works because it calls org-open-at-mouse, which >> (by calling org-open-at-point) simply looks at the text surrounding the >> click point to find a link. >> >> The function org-agenda-open-link, on the other hand, grabs part of the >> headline as a string (the prefix), then jumps to the location in the >> original buffer and calls org-offer-links-in-entry to look for links in >> both the entry and the prefix of agenda text. Obviously, it won't find >> your link in the original entry since it looks like this: >> >> %%(format "%s" (concat "[[elisp:(info)]" "[Link to info]]")) >> >> I think it shouldn't be a problem to pass the whole agenda line to >> org-offer-links-in-entry. This will not result in duplicate links, since >> org-offer-links-in-entry "uniquifies" the links. >> >> I've attached a patch. >> >> The bigger question, however, is why the expression above is even >> showing up in the agenda, since it contains no scheduling information. >> :) >> >> Best, >> Matt >> >> >> >From 58c7621c0c84b9c1930098a098e4559aa516eec0 Mon Sep 17 00:00:00 2001 >> From: Matt Lundin >> Date: Tue, 3 May 2011 15:54:35 -0400 >> Subject: [PATCH] Pass entire text of agenda line to org-offer-links-in-entry. >> >> * lisp/org-agenda.el (org-agenda-open-link): Pass entire text of >> agenda line to org-offer-links-in-entry. >> >> This fixes bug noticed by Charles Sebold, in which links that are >> dynamically formatted for the agenda view are ignored. >> http://permalink.gmane.org/gmane.emacs.orgmode/40673 >> --- >> lisp/org-agenda.el |4 +--- >> 1 files changed, 1 insertions(+), 3 deletions(-) >> >> diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el >> index 65f7cea..609edd4 100644 >> --- a/lisp/org-agenda.el >> +++ b/lisp/org-agenda.el >> @@ -6879,9 +6879,7 @@ at the text of the entry itself." >> (org-get-at-bol 'org-marker))) >> (buffer (and marker (marker-buffer marker))) >> (prefix (buffer-substring >> - (point-at-bol) >> - (or (text-property-any (point-at-bol) (point-at-eol) >> 'org-heading t) >> - (point-at-bol) >> + (point-at-bol) (point-at-eol >> (cond >> (buffer >>(with-current-buffer buffer >> -- >> 1.7.5 >> >> > > Just curious, is there anything I should have known that prevented the patch submitted in http://article.gmane.org/gmane.emacs.orgmode/39313, > From: Bert Burgemeister > Subject: [O] [PATCH] Bugfix: org-agenda-open-link > Newsgroups: gmane.emacs.orgmode > To: emacs-orgmode@gnu.org > Date: Sun, 13 Mar 2011 16:18:44 +0100 > > > * Org-agenda.el (org-agenda-open-link): C-c C-o didn't open links > inserted via the `%%( )' mechanism, affecting usability of > `%%(org-bbdb-anniversaries). > > TINYCHANGE > --- > > > The bug was apparently introduced in commit > ba1e90893d128d8004e4cb6763af692c5a6cd677. > > -- > Bert > > > > lisp/org-agenda.el | 14 +++--- > 1 files changed, 7 insertions(+), 7 deletions(-) > > diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el > index 4b4dd68..123668c 100644 > --- a/lisp/org-agenda.el > +++ b/lisp/org-agenda.el > @@ -6742,13 +6742,13 @@ at the text of the entry itself." > (+ (point-at-bol) >(or (org-get-at-bol 'prefix-length) 0) > (cond > - (buffer > - (with-current-buffer buffer > - (save-excursion > - (save-restriction > - (widen) > - (goto-char marker) > - (org-offer-links-in-entry arg prefix) > + ((and buffer > +(with-current-buffer buffer > + (save-excursion > +(save-restriction > + (widen) > + (goto-char marker) > + (org-offer-link
