Re: [O] Journal versus clock tables: Opposing requirements?
Tommy Kelly writes: > Bernt wrote: >> For item 1) can you use the display of inactive timestamps to get part >> of the information you want in the agenda and then visit the items with >> either follow mode (F) or manually visit each item with SPC to get more >> detail? > > Thanks. That's pretty much exactly my workaround now. So I enter data > all over the place in my file, so as to preserve position with respect > to headings (so my clock table is correct). Therefore the only way to > get the journal-style output seems to be as you suggest. > > The problem is, at the end of the week, when I want to output a report > of what I did, it's a fairly manual task. It's true that even with a > chronological report I wouldn't necessarily leave the chronological > output as-is, with no editing or grouping. But it will be *much* > easier to get what I want if I can start with a simple linear-time > report of everything, than if I have to work my way through the weekly > agenda in follow mode. If you can manually create your report (even if it is tedious) then it should be possible to automate most of it. This is Emacs after all - you can program it to do whatever you need it to do. It should be possible to write code that walks your agenda, visits the tasks, and copies and pastes the details to a temporary org buffer/file just for your chronological report. I have no idea what that code would look like though... it depends on how often you require this weekly report if writing that code would be worth it or not. Regards, Bernt
[O] Improving bug reporting documentation
Hi Bastien and others, Lately I have been seeing a lot of bug reports sent using the org-submit-bug-report. The reporter usually reports the bug from a session they have been using with their full blown customisations. And often they are requested to reproduce the bug with emacs -Q. So I thought it would be easier if the manual mentioned this little detail. A patch is attached. Hope this helps. PS: I marked the patch as TINY CHANGE. -- Suvayu Open source is the future. It sets us free. >From cf8935331d2f57ef5c954fad2f5e3f179d902081 Mon Sep 17 00:00:00 2001 From: Suvayu Ali Date: Mon, 7 Nov 2011 23:54:05 +0100 Subject: [PATCH] Improve Feedback section in docs * org.texi (Feedback): Add instruction o how to start emacs with minimal customisations TINY CHANGE --- doc/org.texi | 30 ++ 1 files changed, 30 insertions(+), 0 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index 4a547d0..1bc9a98 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -987,6 +987,36 @@ @section Feedback that you only need to add your description. If you re not sending the Email from within Emacs, please copy and paste the content into your Email program. +Sometimes you might face a problem due to an error in your Emacs or Org-mode +setup. Before reporting a bug, it is very helpful to start Emacs with minimal +customisations and reproduce the problem. Doing so often helps you determine +if the problem is with your customisation or with Org-mode itself. You can +start a typical minimal session with a command like the example below. + +@example +$ emacs -Q -l /path/to/minimal-org.el +@end example + +However if you are using Org-mode as distributed with Emacs, a minimal setup +is not necessary. In that case it is sufficient to start Emacs as @code{emacs +-Q}. The @code{minimal-org.el} setup file can have contents as shown below. + +@example +;;; Minimal setup to load latest `org-mode' + +;; activate debugging +(setq debug-on-error t + debug-on-signal nil + debug-on-quit nil) + +;; add latest org-mode to load path +(add-to-list 'load-path (expand-file-name "/path/to/org-mode/lisp")) +(add-to-list 'load-path (expand-file-name "/path/to/org-mode/contrib/lisp")) + +;; activate org +(require 'org-install) +@end example + If an error occurs, a backtrace can be very useful (see below on how to create one). Often a small example file helps, along with clear information about: -- 1.7.7
Re: [O] Emacs-orgmode Digest, Vol 68, Issue 23
-Urspr. Mitteilung- Betreff: Emacs-orgmode Digest, Vol 68, Issue 23 Von: emacs-orgmode-requ...@gnu.org Datum: 21.10.2011 18:01 Send Emacs-orgmode mailing list submissions to emacs-orgmode@gnu.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.gnu.org/mailman/listinfo/emacs-orgmode or, via email, send a message with subject or body 'help' to emacs-orgmode-requ...@gnu.org You can reach the person managing the list at emacs-orgmode-ow...@gnu.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Emacs-orgmode digest..." Today's Topics: 1. Re: outline-demote incorrectly demotes leaf nodes (Carsten Dominik) 2. Re: Cannot display images inline any more => solved (Rainer Stengele) 3. Re: Cannot display images inline any more => solved (Rainer Stengele) -- Message: 1 Date: Fri, 21 Oct 2011 16:40:22 +0200 From: Carsten Dominik To: Michael Brand Cc: emacs-orgmode@gnu.org, S?bastien Delafond , Sanjoy Mahajan Subject: Re: [O] outline-demote incorrectly demotes leaf nodes Message-ID: Content-Type: text/plain; charset=us-ascii On Oct 19, 2011, at 5:39 PM, Michael Brand wrote: > Hi Carsten > > On 18.10.2011, at 20:03, Sanjoy Mahajan wrote: >> I do worry about one point, namely that C-c C-> (outline-demote) should still >> work. And it does work in regular outline mode. For example, if I rename my >> test file to c.otl and then use C-c C-> on the main heading, all the subtrees >> are demoted as I expected. Whereas in org mode the leaf subtree gets a space >> instead of a * when it is being demoted. > > On Wed, Oct 19, 2011 at 09:14, Carsten Dominik > wrote: >> Another option, if you prefer the C-> and C-< bindings is this: >> >> (add-hook 'org-mode-hook >> (lambda () >>(define-key org-mode-map [(control ?<)] 'org-promote-subtree) >>(define-key org-mode-map [(control ?>)] 'org-demote-subtree))) > > My suggestion is something like > > (define-key org-mode-map [remap outline-promote] 'org-promote-subtree) > (define-key org-mode-map [remap outline-demote] 'org-demote-subtree) > [...] > > permanently built into Org mode (not in org-mode-hook) for these and > maybe even a few more outline-* bindings to get the incompatible > outline-* bindings out of the way from within Org mode. > > This remap does not affect the bindings in Outline mode and resolves > the issue of the OP in Org mode, independent of, to which key any user > might have mapped outline-*mote. Would you like to carefully think about which other functions you might want to have remapped, and then prepare a patch? - Carsten -- Message: 2 Date: Fri, 21 Oct 2011 16:46:08 +0200 From: Rainer Stengele To: emacs-orgmode@gnu.org, public-emacs-orgmode-mXXj517/z...@lo.gmane.org Subject: Re: [O] Cannot display images inline any more => solved Message-ID: <4ea185b0.4090...@online.de> Content-Type: text/plain; charset=ISO-8859-15 Am 21.10.2011 16:19, schrieb Jambunathan K: > Rainer Stengele writes: > >> Am 21.10.2011 15:33, schrieb Sebastien Vauban: >>> Hi Suvayu and Rainer, >>> >>> suvayu ali wrote: On Fri, Oct 21, 2011 at 2:39 PM, Rainer Stengele wrote: > > I have for example > > [[file:c:/img.jpg]] > > which is exported correctly as html. > > In Emacs, after "C-c C-x v" Org says: "No images to display inline". > > Does anybody use Emacs 24.0.90.1 and is able to display images inline? My Emacs is 2 days older than yours and it works fine. >>> >>> I wonder if it's not related to some types of images (PNG, JPG) and Emacs 24 >>> under Windows. Have read such things, IIRC. >>> >>> Best regards, >>> Seb >>> >> >> Well, who is telling me "No images to display inline"? Is it Emacs or Org? >> How could I debug the funtion? > > C-h v dynamic-library-alist > C-h v image-library-alist > > You can copy the required dll to bin if you are on Windows. > >> Anybody? >> Rainer >> >> >> > Ok, that was it. I copied the libs from my old emacs w32 installation to my emacs bin folder and that did it. I never knew that Lennard Borgman did the nice job packaging these libs in his emacsw32 (which is out of date unfortunately - thanks Lennard anyway). Thank you for the hint Jambunathan, helped me to understand a bit more of how emacs is working. Rainer -- Message: 3 Date: Fri, 21 Oct 2011 16:46:08 +0200 From: Rainer Stengele To: emacs-orgmode@gnu.org Subject: Re: [O] Cannot display images inline any more => solved Message-ID: <4ea185b0.4090...@online.de> Content-Type: text/plain; charset=ISO-8859-15 Am 21.10.2011 16:19, schrieb Jambunathan K: > Rainer Stengele writes: > >> Am 21.10.2011 15:33, schrieb Sebastien Vauban: >>> Hi Suvayu and Rainer, >>> >>> suvayu ali wrote: On Fri, Oct 21, 2011 at 2:39 PM, Rainer S
Re: [O] About commit named "Allow multi-line properties to be specified in property blocks"
The attached patch implements this latest "propname+" suggestion. When applied it results in the behavior shown below. I'm inclined to go with this as a solution moving forward. Thoughts? #+property: varfoo=1 #+property: var+ , bar=2 #+begin_src emacs-lisp (+ foo bar) #+end_src #+results: : 3 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=1, bar=2 * overwriting a file-wide property :PROPERTIES: :var: foo=7 :END: #+begin_src emacs-lisp foo #+end_src #+results: : 7 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=7 * appending to a file-wide property :PROPERTIES: :var+: , baz=3 :END: #+begin_src emacs-lisp (+ foo bar baz) #+end_src #+results: : 6 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=1, bar=2, baz=3 >From 1bb2009c419e5ae6c912e863b13cb02a1f1ea720 Mon Sep 17 00:00:00 2001 From: Eric Schulte Date: Mon, 7 Nov 2011 14:49:42 -0700 Subject: [PATCH] property names ending in plus accumulate This results in the following behavior. #+property: varfoo=1 #+property: var+ , bar=2 #+begin_src emacs-lisp (+ foo bar) #+end_src #+results: : 3 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=1, bar=2 * overwriting a file-wide property :PROPERTIES: :var: foo=7 :END: #+begin_src emacs-lisp foo #+end_src #+results: : 7 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=7 * appending to a file-wide property :PROPERTIES: :var+: , baz=3 :END: #+begin_src emacs-lisp (+ foo bar baz) #+end_src #+results: : 6 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=1, bar=2, baz=3 * lisp/org.el (org-update-property-plist): Updates a given property list with a property name and a property value. (org-set-regexps-and-options): Use org-update-property-plist. (org-entry-get): Use org-update-property-plist. * testing/examples/property-inheritance.org: Example file for testing appending property behavior. * testing/lisp/test-property-inheritance.el: Tests of appending property behavior. properties with names ending in "+" accumulate rather than overwrite This results in the following behavior. #+property: varfoo=1 #+property: var+ , bar=2 #+begin_src emacs-lisp (+ foo bar) #+end_src #+results: : 3 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=1, bar=2 * overwriting a file-wide property :PROPERTIES: :var: foo=7 :END: #+begin_src emacs-lisp foo #+end_src #+results: : 7 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=7 * appending to a file-wide property :PROPERTIES: :var+: , baz=3 :END: #+begin_src emacs-lisp (+ foo bar baz) #+end_src #+results: : 6 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=1, bar=2, baz=3 * lisp/org.el (org-update-property-plist): Updates a given property list with a property name and a property value. (org-set-regexps-and-options): Use org-update-property-plist. (org-entry-get): Use org-update-property-plist. * testing/examples/property-inheritance.org: Example file for testing appending property behavior. * testing/lisp/test-property-inheritance.el: Tests of appending property behavior. properties with names ending in "+" accumulate rather than overwrite This results in the following behavior. #+property: varfoo=1 #+property: var+ , bar=2 #+begin_src emacs-lisp (+ foo bar) #+end_src #+results: : 3 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=1, bar=2 * overwriting a file-wide property :PROPERTIES: :var: foo=7 :END: #+begin_src emacs-lisp foo #+end_src #+results: : 7 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=7 * appending to a file-wide property :PROPERTIES: :var+: , baz=3 :END: #+begin_src emacs-lisp (+ foo bar baz) #+end_src #+results: : 6 #+begin_src emacs-lisp (org-entry-get (point) "var" t) #+end_src #+results: : foo=1, bar=2, baz=3 * lisp/org.el (org-update-property-plist): Updates a given property list with a property name and a property value. (org-set-regexps-and-options): Use org-update-property-plist. (org-entry-get): Use org-update-property-plist. * testing/examples/property-inheritance.org: Example file for testing appending property behavior. * testing/lisp/test-property-inheritance.el: Tests of appending property behavior. --- lisp/org.el | 47 +++--- testing/examples/property-inheritance.org | 36
Re: [O] problems with mathjax CDN and HTML export
On 11/7/11 5:02 PM, Giovanni Ridolfi wrote: the math snippets are always "converted" in HTML format e.g.:α = \frac{1}{L0} Do I understand correctly that this is your problem? (Not very clear from your long example, which starts with the CDN service.) If so, I can't reproduce it. Your $$ \alpha = \frac{1}{L_{0}} \left( \frac{L_2-L_1}{T_2-T_1} \right) = \frac{1}{L_0}\frac{\Delta L}{\Delta T} $$ exports verbatim for me, and is correctly formatted. Yours, Christian
Re: [O] [OT] Scanning for archiving
Hi! Inspired by «Total Recall»[3], a book of two MS Research guys, I started life logging on my own two months ago. For this purpose I bought an HP OfficeJet Pro 8500A Plus which costs € 250 and has a decent scanner. Is can scan and print full duplex. The scanner as a 30 page ADF which is quite reliable when the paper was not bend or stapled before. * Pieter Praet wrote: > > Using PDF for scanned documents results in *huge* files with a seriously > disappointing image quality. I can not copy that at all: , | vk@gary ~2d % l 2011-11-02_13-22-45.png | -rw--- 1 vk vk 103150 2011-11-02 13:22 2011-11-02_13-22-45.png | vk@gary ~2d % convert 2011-11-02_13-22-45.png 2011-11-02_13-22-45.pdf | vk@gary ~2d % l 2011-11-02_13-22-45.pdf | -rw-r--r-- 1 vk vk 96457 2011-11-07 18:12 2011-11-02_13-22-45.pdf | vk@gary ~2d % ` In this example, the compression of PDF is much better than the original PNG one. PDF is only a container format. > Consider storing your scans in DjVu format > [1], which was developed specifically for this purpose. PDF is a common standard whereas DjVu is something I - as an advanced computer user - never faced before in real life. I am not sure whether any of my computers can handle DjVu files at all. The goals of DjVu sound great but I get everything with PDF too. Although I like the idea of OGG Vorbis, I re-ripped all my CDs using mp3 again because I could not use many music devices or music management software packages. I stick to the format *any* computer can handle without special software products. And I do think that I get a higher chance of being able to read my documents twenty years from now. For scanned images I'd prefer PNG instead but the OS X Software of my OfficeJet offers me the ability to generate PDF files where an OCR software adds a searchable text layer above the scanned text. This is *very* important to me since I am able to do full text search on the content of my archived documents. And I plan to archive *all* of my documents. Really all of them. Storage space does not matter (any more) to me since I have more disk space now already than I could possible fill with my lifetime paper correspondence. And I do think that my disk space continues to grow in future. > I scan all docs @ 600dpi, predominantly gray-scale (only in colour when > it's *really* necessary) and store in DjVu format, all using gscan2pdf [2]. > > Even at that seemingly overkill resolution, single-page documents are > generally (if they aren't too "grainy") only a few 100 KiB in size. My HP software uses 300 dpi per default and it is OK to me too. Funny side fact: grayscale scan document settings produces slightly larger files than colored ones. > gscan2pdf also supports a number of OCR utils, but the UI for this is > clumsy (aren't they all...), so you're better off using the CLI tools > directly. Tesseract is recommended. I played around with ocropus, tesseract, ocroscript, hocr2pdf, exactimage, ppa:gezakovacs/pdfocr, ... to generate those sandwitch PDF documents (OCR text above the scanned images) on GNU/Linux. Unfortunately none of those (very cool projects) produced reliable results on my side. The results vary from «no error but overlay font size is incorrect and produces loss of layout» to «library error messages I can not read or handle». Whereas the HP OfficeJet bundles its OS X software with OCR from Readiris which produces perfect results even in different languages and using a usable user interface. > NOTE: When attempting something like this, a fast scanner with a *reliable* > automatic document feeder will help prevent premature hair loss ;) I have found several scanner products I was interested in: "Canon imageFORMULA P-150": very small form factor with basic Linux support. Price tag starts with € 260. Neat form factor and very portable. Different version "P-150m" for Mac OS X. The authors of [3] use Fujitsu ScanSnap starting at € 400. I ended up with the Office Jet Pro (mentioned above) at € 250 because I got flatbed scanner *and* ADF-scanner *and* a full-duplex/full-color network printer with a very good price-per-printed-page-ratio (better than many laser printers!). And all of this with a cheaper price tag than any scan-only-product I was interested in. So far I am almost satisfied. «Almost»? Well, HP did a good job with this printer but they made only a 90% solution on almost all levels. Whereas 100% would be possible with small additional effort when creating the printer. But those resulting 90% are pretty usable. 3. http://qr.cx/sAHU -- Karl Voit
Re: [O] [PATCH] Category filtering in the agenda
Hi Bastien, do I see it correctly that I cannot filter both by tag and by effort? - Carsten On 6.11.2011, at 19:34, Bastien wrote: > Dear all, > > here is a patch implementing category filtering in the agenda. > > The patch is not 100% clean wrt documentation, but I throw it > now to get some feedback and some testing done. > > Press "<" in the agenda to filter by category. > > Press "< <" to filter by the category of the entry point. > Another "/ /" removes the filter. "/" + " " filters by the > default category ("General") since everything is in a category. > > I find this last function quick and useful, so I also implemented > it for tag filtering: pressing "/ /" filters by tags from the entry > on the current line. A second "/ /" removes the filter. > > Let me know if the category filtering works ok with you, and > if you find the new "/ /" behavior useful. > > There is one limitation for now: it does not combine with Effort > filtering. > > Thanks, > > <0001-Implement-agenda-filtering-by-category.patch> > -- > Bastien
Re: [O] Journal versus clock tables: Opposing requirements?
> OK, that might be what I need then. I thought clock tables grouped > things by headings, not by tags. I'll have a look at the manual. I'm trying the tagging thing within clock tables, but I can't get it working at all. I've attached a tag to a single headline, and checked that I've got that right by using "C-c a m". Then I added a :tags item to my clock table block but it seems to have no effect. Is this valid: #+BEGIN: clocktable :maxlevel 2 :scope file :block thisweek :step week :indent :tags test_tag #+END: I've also tried :tags 'test_tag', :tags '+test_tag' and a bunch of other things, but nothing seems to do anything. What I was expecting was that my clock table, currently filled with lots of items, would be reduced to looking only at the single headline that I've tagged. But it's not -- it just stays as it was before. What am I doing wrong? thx, Tommy
Re: [O] org-taskjuggler export problems
Hi Christian and thanks for your response. Christian Egli writes: > >> I am trying to export a simple project plan from org to taskjuggler >> through org-taskjuggler.el. I cannot get the behavour I expect and >> need do some manual tweaks to get the taskjuggler file working. What >> am I doing wrong? > > You're not doing anything wrong. You've hit some bugs in the taskjuggler > exporter. > >> 1) The 'end' date specified in the ':taskjuggler_project' base is ignored and >> the default 280d is used. Because the project duration is long this >> throws an error. The 'start' date however seems properly picked up. > > Indeed the end date is not picked up. I remember to have tried to fix > this once, but the problem is that the root task serves as both a > container for the project attributes and is a task at the same time. So > if you define the end, you'll both define the end of the project and the > task, which might not be what you want. Can you try to increase the > org-export-taskjuggler-default-project-duration instead? > That is an acceptable solution. I guess the minor tradeoff is that by having a large default value which is necessary for only one project will transfer to others as well making the taskjuggler work harder. This is not a major issue at all, but being able to specify on a per file basis would be convenient. >> 2) The 'task_id' fields are not exported properly. > > The taskjuggler exporter uses the task_ids you define just for > dependency resolution. Other than that it creates automatic ids based on > the title of the task. The assumption is that you are not that > interested in defining ids. What do you need them for? > Well, dependency resolution is what I was after, but as the 'precedes' is not exported that is the major culprit. >> 3) The 'precedes' property is not exported at all > > Yes, this is not implemented. Could you use 'depends' instead? And > possibly use alap scheduling? It is not as transparent to use 'depends', as I have one milestone with many tasks to be completed before. By using 'depends', I will (not really) see in column view e.g. 20 tasks in the depends column. By using 'precedes', each task will be (much more) clearly mapped to the milestone. > > Hope that helps Yes, thanks for explaining how the export handles the fields. Best, -- Johnny
[O] Todo balance motivation
Hi! I am using a shell script to generate a simple todo overview showing these information: ,[ results of today and yesterday ] | vk@gary ~all/org-mode (git)-[master] % ./vkorgtaskratio.sh | 2011-11-07: 3 created - 7 done = -4 sum | Congratulations! More solved than generated! | vk@gary ~all/org-mode (git)-[master] % ./vkorgtaskratio.sh 2011-11-06 | 2011-11-06: 4 created - 0 done = 4 sum | Sorry, you still have to solve 4 issues to get even! | vk@gary ~all/org-mode (git)-[master] % ` My general goal ist to close more issues than open new one per day. Is this kind of functionality available in Org-mode somewhere or should I stick to my script? To all those who want to use my script: ,[ vkorgbalance.sh ] | #!/bin/sh | | FILEPATTERN="*org *archive" ## which files to search in | ORGMODEDIR="~/share/all/org-mode/" ## where org-mode files life | | if [ "${1}x" = "x" ]; then | ## set day to today | DAY=`date +%Y-%m-%d` | else | ## using $1 as daystamp | DAY="${1}" | ## FIXXME: add check, if $1 is a valid daystamp | fi | | cd "${ORGMODEDIR}" | created=`egrep ":CREATED: .${DAY}" ${FILEPATTERN}|wc -l` | closed=`egrep "CLOSED: .${DAY}" ${FILEPATTERN}|wc -l` | sum=$(($created-$closed)) | | echo "${DAY}: ${created} created - ${closed} done = ${sum} sum" | | ## generating the motivation messages | if [ "${sum}" -lt 0 ]; then | echo "Congratulations! More solved than generated!" | else | echo "Sorry, you still have to solve ${sum} issues to get even!" | fi | | #end ` -- Karl Voit
Re: [O] Encrypting archived files
I started archiving a bunch of pdf and jpg scans of some important documents. I currently use the org-crypt package + gnupg to encrypt org entries, I'm thinking about using gnupg to encrypt the files as well. Is there any integration with org for encryption/decryption of attached files? Any insights appreciated! Not an org solution, but you could put te whole file inside a Truecrypt container. If you are using linux you can also use the ecrypt-fs utilities to encrypt your whole /home folder, or a selected sub folder. Ian.
Re: [O] org-taskjuggler export problems
Hi Johnny writes: > I am trying to export a simple project plan from org to taskjuggler > through org-taskjuggler.el. I cannot get the behavour I expect and > need do some manual tweaks to get the taskjuggler file working. What > am I doing wrong? You're not doing anything wrong. You've hit some bugs in the taskjuggler exporter. > 1) The 'end' date specified in the ':taskjuggler_project' base is ignored and > the default 280d is used. Because the project duration is long this > throws an error. The 'start' date however seems properly picked up. Indeed the end date is not picked up. I remember to have tried to fix this once, but the problem is that the root task serves as both a container for the project attributes and is a task at the same time. So if you define the end, you'll both define the end of the project and the task, which might not be what you want. Can you try to increase the org-export-taskjuggler-default-project-duration instead? > 2) The 'task_id' fields are not exported properly. The taskjuggler exporter uses the task_ids you define just for dependency resolution. Other than that it creates automatic ids based on the title of the task. The assumption is that you are not that interested in defining ids. What do you need them for? > 3) The 'precedes' property is not exported at all Yes, this is not implemented. Could you use 'depends' instead? And possibly use alap scheduling? Hope that helps Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
Re: [O] [SOLVED] Bug: :tags: in title [7.7 f8168144a]
suvayu ali writes: Hi suvayu > > Since you CC'd me, did my patch to org-exp.el introduce this > behaviour? I thought so > Anyway, I can't reproduce this. I see "mathjax test" as the title, > which is expected behaviour. uh??? I cannot reproduce as well !! I don't know what happened, but I saw it twice ?-/ Let's consider it as solved. Thank you for checking, Giovanni
Re: [O] Bug: :tags: in title [7.7 f8168144a]
Hi Giovanni, On Mon, Nov 7, 2011 at 15:31, Giovanni Ridolfi wrote: > > When I export the subtree "mathjax test": C-c @ C-c C-e B of the example file > below, > (please note that the PROPERTY "EXPORT_TITLE" does not have a value!!) > the exported HTML file (00-b.html) has > > the "tag" :EXPORTFILENAME: 00-b.html as a title. > > --- > -*- mode: org -*- > * some data > * mathjax test > :PROPERTIES: > :EXPORT_TITLE: > :EXPORT_FILE_NAME: 00-b.html > :EXPORT_OPTIONS: H:3 num:nil toc:nil \n:t @:t ::t |:t ^:t f:nil *:t tags:nil > TeX:t LaTeX:nil skip:t p:nil author:nil email:nil creator:nil timestamp:nil > :END: > ** test one > ** Test > http://www.mathjax.org/docs/1.1/start.html#putting-mathematics-in-a-web-page > -- > Since you CC'd me, did my patch to org-exp.el introduce this behaviour? Anyway, I can't reproduce this. I see "mathjax test" as the title, which is expected behaviour. Can you replicate this with emacs started with -Q? $ emacs -Q -l ~/.emacs.d/minimal-org.el bug.org > > cheers, > Giovanni > Thanks, -- Suvayu Open source is the future. It sets us free.
Re: [O] Journal versus clock tables: Opposing requirements?
Bernt wrote: > For item 1) can you use the display of inactive timestamps to get part > of the information you want in the agenda and then visit the items with > either follow mode (F) or manually visit each item with SPC to get more > detail? Thanks. That's pretty much exactly my workaround now. So I enter data all over the place in my file, so as to preserve position with respect to headings (so my clock table is correct). Therefore the only way to get the journal-style output seems to be as you suggest. The problem is, at the end of the week, when I want to output a report of what I did, it's a fairly manual task. It's true that even with a chronological report I wouldn't necessarily leave the chronological output as-is, with no editing or grouping. But it will be *much* easier to get what I want if I can start with a simple linear-time report of everything, than if I have to work my way through the weekly agenda in follow mode. Tommy
Re: [O] Journal versus clock tables: Opposing requirements?
Olaf wrote: > Maybe I misunderstand what you want to accomplish, but if you put your > journal into a separate file (e.g. journal.org), ... That's pretty much what I want. But if I do that I then have trouble with getting sensible clock tables. For example, suppose I had: *** Headline about some activity on Project A CLOCK: [from]--[to] => duration notes notes notes *** Headline about some activity on Project B CLOCK: [from]--[to] => duration more notes notes note *** Headline about some other activity on Project A CLOCK: [from]--[to] => duration yet more notes notes Adding those as a chronological journal lets me get a report of chronology, but it won't let me have a clock table with the times for the two "on Project A" activities combined into one. Will it? Of course I could shove the Project A activities under one single higher-level headline, but that than violates the chronology side of things (in the sense that I want to enter things into my journal in chronological order, just as I would in a paper log book). > You can create clock tables and select reported items by tags. So, if > you tag your journal entries, you can create clock tables made up of a > few entries only. OK, that might be what I need then. I thought clock tables grouped things by headings, not by tags. I'll have a look at the manual. thanks, Tommy
[O] Bug: :tags: in title [7.7 f8168144a]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. Hello everybody, Emacs : GNU Emacs 23.3.1 (i386-mingw-nt5.1.2600) of 2011-03-10 on 3249CTO Package: Org-mode version 7.7 f8168144a95136ab93650a3c80ac28bb0b69fd90 I know this is a corner case... When I export the subtree "mathjax test": C-c @ C-c C-e B of the example file below, (please note that the PROPERTY "EXPORT_TITLE" does not have a value!!) the exported HTML file (00-b.html) has the "tag" :EXPORTFILENAME: 00-b.html as a title. --- -*- mode: org -*- * some data * mathjax test :PROPERTIES: :EXPORT_TITLE: :EXPORT_FILE_NAME: 00-b.html :EXPORT_OPTIONS: H:3 num:nil toc:nil \n:t @:t ::t |:t ^:t f:nil *:t tags:nil TeX:t LaTeX:nil skip:t p:nil author:nil email:nil creator:nil timestamp:nil :END: ** test one ** Test http://www.mathjax.org/docs/1.1/start.html#putting-mathematics-in-a-web-page -- cheers, Giovanni current state: == (setq org-log-done 'time org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars) org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook) org-agenda-custom-commands '(("3" "c3i" agenda "" ((org-agenda-ndays 7) (org-agenda-start-on-weekday 0) (org-agenda-time-grid nil) (org-agenda-repeating-timestamp-show-all t) (org-agenda-entry-types (quote (:todo :scheduled :timestamp :sexp))) (org-agenda-files (quote ("c:/Documents and Settings/a.txt" "c:/Documents and Settings/c.txt") ) ) (org-agenda-text-search-extra-files nil)) ) ) org-agenda-files '("" "") org-blocker-hook '(org-block-todo-from-children-or-siblings-or-parent) org-babel-load-languages '((gnuplot . t) (emacs-lisp . t) (calc . t) (sh . t) (ditaa . t)) org-metaup-hook '(org-babel-load-in-session-maybe) org-after-todo-state-change-hook '(org-clock-out-if-current) org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup) org-export-latex-format-toc-function 'org-export-latex-format-toc-default org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe) org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-finalize-agenda-hook '(my-org-agenda-to-appt) org-confirm-shell-link-function 'yes-or-no-p org-export-first-hook '(org-beamer-initialize-open-trackers) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-use-property-inheritance '("DEADLINE") org-blank-before-new-entry nil org-babel-pre-tangle-hook '(save-buffer) org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-export-preprocess-before-normalizing-links-hook '(org-remove-file-link-modifiers) org-mode-hook '((lambda nil (org-add-hook (quote change-major-mode-hook) (quote org-show-block-all) (quote append) (quote local))) (lambda nil (org-add-hook (quote change-major-mode-hook) (quote org-babel-show-result-all) (quote append) (quote local)) ) org-babel-result-hide-spec org-babel-hide-all-hashes) org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe) org-confirm-elisp-link-function 'yes-or-no-p org-export-interblocks '((lob org-babel-exp-lob-one-liners) (src org-babel-exp-inline-src-blocks)) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) org-enforce-todo-dependencies t org-occur-hook '(org-first-headline-recenter) org-from-is-user-regexp nil org-export-preprocess-before-selecting-backend-code-hook '(org-beamer-select-beamer-code) org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc org-beamer-auto-fragile-frames org-beamer-place-default-actions-for-lists) org-metadown-hook '(org-babel-pop-to-session-maybe) org-export-blocks '((src org-babel-exp-src-block nil) (comment org-export-blocks-format-comment t) (ditaa org-export-blocks-format-ditaa nil) (dot org-export-blocks-format-dot nil)) )
Re: [O] View inherited DEADLINEs in agenda
On Nov 7, 2011, at 1:19 PM, Giovanni Ridolfi wrote: > Fabrizio Chiarello writes: > > >> I have many tasks with a DEADLINE, and I wish to have their subtasks to >> inherit such DEADLINE. To this aim, I set: >> >> (setq org-use-property-inheritance (quote ("DEADLINE"))) >> > >> The problem is that the agenda only shows deadlines for the tasks that >> define them > > is DEADLINE a property that can be inherited? Deadlines can currently *not* be inherited. I would probably advice against implementing this because of performance issues that would result for the construction of the agenda. - Carsten > > would you please post an example file? > Thanks, > > Giovanni > > > - Carsten
Re: [O] #+begin_src LaTeX blocks export to literal LaTeX
Just for reference, I found that I need to load `ob-latex.el'. With that it works nicely.
Re: [O] View inherited DEADLINEs in agenda
I second this. Tt would seem logical (to me at least) that the deadline should be inherited. I.e. in order to finish the project in time one has to also finish the subtasks in time. Right now the following property is illogical from this point of view: (setq org-agenda-dim-blocked-tasks 'invisible) since it hides the parent in the agenda even if the date is in the past! /Gustav On Mon, Nov 7, 2011 at 2:16 PM, Fabrizio Chiarello wrote: > On Mon, Nov 07, 2011 at 01:22:31PM +0100, suvayu ali wrote: >> On Mon, Nov 7, 2011 at 13:19, Giovanni Ridolfi >> wrote: >> > Fabrizio Chiarello writes: >> > >> > >> >> I have many tasks with a DEADLINE, and I wish to have their subtasks to >> >> inherit such DEADLINE. To this aim, I set: >> >> >> >> (setq org-use-property-inheritance (quote ("DEADLINE"))) >> >> >> > >> >> The problem is that the agenda only shows deadlines for the tasks that >> >> define them >> > >> > is DEADLINE a property that can be inherited? >> > >> > would you please post an example file? >> >> I don't think DEADLINE is a property at all. >> > > In my org 7.7 manual, in section "7.2 Special properties", DEADLINE is > defined as a (special) property. > > By the way, consider the following example: > > * TODO parent > DEADLINE: <2011-12-31 Sat> > ** TODO child A > ** TODO child B > DEADLINE: <2011-11-30 Wed> > ** TODO child C > > In my workflow, to mark "parent" as DONE i have to complete "child" A,B > and C. And it would be nice to have child A and C inherit the DEADLINE > from the parent, and to show up in the agenda. Any idea? > > -- > Fabrizio Chiarello > Photonics and Electromagnetics Group > Department of Information Engineering > University of Padova, Italy > > Intelligence is quickness to apprehend as distinct form ability, which > is capacity to act wisely on the thing apprehended. > -- Alfred North Whitehead > >
Re: [O] View inherited DEADLINEs in agenda
On Mon, Nov 7, 2011 at 13:19, Giovanni Ridolfi wrote: > Fabrizio Chiarello writes: > > >> I have many tasks with a DEADLINE, and I wish to have their subtasks to >> inherit such DEADLINE. To this aim, I set: >> >> (setq org-use-property-inheritance (quote ("DEADLINE"))) >> > >> The problem is that the agenda only shows deadlines for the tasks that >> define them > > is DEADLINE a property that can be inherited? > > would you please post an example file? I don't think DEADLINE is a property at all. -- Suvayu Open source is the future. It sets us free.
Re: [O] View inherited DEADLINEs in agenda
Fabrizio Chiarello writes: > I have many tasks with a DEADLINE, and I wish to have their subtasks to > inherit such DEADLINE. To this aim, I set: > > (setq org-use-property-inheritance (quote ("DEADLINE"))) > > The problem is that the agenda only shows deadlines for the tasks that > define them is DEADLINE a property that can be inherited? would you please post an example file? Thanks, Giovanni
[O] View inherited DEADLINEs in agenda
Hi all, I have many tasks with a DEADLINE, and I wish to have their subtasks to inherit such DEADLINE. To this aim, I set: (setq org-use-property-inheritance (quote ("DEADLINE"))) The problem is that the agenda only shows deadlines for the tasks that define them (the parent tasks) and not for the subtasks. Is there a way to view the inherited deadlines in the agenda? Thanks in advance, fc -- Fabrizio Chiarello Photonics and Electromagnetics Group Department of Information Engineering University of Padova, Italy Planets are too dim to be detected with existing equipment, far away, except in these very special circumstances where they're seen by their gravitational effect. -- Murray Gell-Mann
Re: [O] Journal versus clock tables: Opposing requirements?
Tommy Kelly writes: > I'm trying to get org-mode to provide me with two things, but haven't > found a way to do it. > > 1. First, I want to be able to use it like a daily engineering or > science journal, logging notes as they occur, in pretty much linear > fashion chronologically. Or, more to the point, I want to be able to > report and look at items as they occurred, in pretty much linear > fashion chronologically. Essentially I want to be able to report on > activity by time of occurrence, not topic. > > 2. But second, I want to see clock tables covering a period of time, > which groups related items together regardless of when (within the > given period) they happened. Essentially I want to be able to report > on actrivity by topic, not time of occurrence. > > I'm using some of Bernt Hansen's excellent setup, but it still isn't > getting me quite where I want to be. > > I'll note also that the agenda's log mode doesn't really give me point > 1. It simply lists the *headlines* which have a clock entry or > timestamp at a given time. I want to see my entire journal -- a la a > blog. (*Ideally* I'd like to be able to control the depth to which > that entire journal output went to, but seeing the whole shebang would > be a good start.) Maybe I misunderstand what you want to accomplish, but if you put your journal into a separate file (e.g. journal.org), you could load it as any other file into emacs and look at it. With org-cycle (C-u TAB) you can fold everything and open selected entries (TAB on a single headline) if you want. You can create clock tables and select reported items by tags. So, if you tag your journal entries, you can create clock tables made up of a few entries only. See the org manual: "The clock table". Regards, Olaf
Re: [O] BUG: org-todo-yesterday logs wrong date
Hi all, On Wed, Oct 19, 2011 at 1:17 AM, Viktor Rosenfeld wrote: > > org-todo-yesterday and org-agenda-todo-yesterday log a note using the > current timestamp and not a timestamp of 23:59 of yesterday's date. > > I'm using Org-Mode 7.7 pulled today from the git repository. > > I'm experiencing the same problem with the org-mode version I pulled from git today. Switching back to the 7.7 tarball fixes the problem. Best regards, Geert Kloosterman
Re: [O] Journal versus clock tables: Opposing requirements?
Tommy Kelly writes: > I'm trying to get org-mode to provide me with two things, but haven't > found a way to do it. > > 1. First, I want to be able to use it like a daily engineering or > science journal, logging notes as they occur, in pretty much linear > fashion chronologically. Or, more to the point, I want to be able to > report and look at items as they occurred, in pretty much linear > fashion chronologically. Essentially I want to be able to report on > activity by time of occurrence, not topic. > > 2. But second, I want to see clock tables covering a period of time, > which groups related items together regardless of when (within the > given period) they happened. Essentially I want to be able to report > on actrivity by topic, not time of occurrence. > > I'm using some of Bernt Hansen's excellent setup, but it still isn't > getting me quite where I want to be. > > I'll note also that the agenda's log mode doesn't really give me point > 1. It simply lists the *headlines* which have a clock entry or > timestamp at a given time. I want to see my entire journal -- a la a > blog. (*Ideally* I'd like to be able to control the depth to which > that entire journal output went to, but seeing the whole shebang would > be a good start.) > > Anyone have any ideas how to do this. Hi Tommy, For item 1) can you use the display of inactive timestamps to get part of the information you want in the agenda and then visit the items with either follow mode (F) or manually visit each item with SPC to get more detail? If you create an inactive timestamp for every new note you log you can display that timestamp with [ or ] in the agenda. This is what I do. For item 2) I would use agenda clock reports R while displaying the agenda time frame you are interested in. You can limit the agenda to certain tags and use C-u R to limit the clock report to only those tags. HTH, Bernt
Re: [O] [test] Failure on GNU Emacs 22.3.2 (i686-pc-linux-gnu) of 2011-05-28 on x60s
David Maus writes: > Running the test suit on > > GNU Emacs 22.3.2 (i686-pc-linux-gnu) of 2011-05-28 on x60s > > currently fails with the backtrace below. > > Somehwere/somehow Babel ends up calling `member' with the second > argument not being a list. In Emacs22 this triggers an error, but not > so in Emacs23 and upwards. > > Devs don't consider this a bug: > > http://debbugs.gnu.org/cgi/bugreport.cgi?bug=264 > > Best, > -- David > [...] Hi David I don't actually see this on my continuous test server, although I did see regression on 29th October which appeared to be fixed the same day ( see http://martynjago.co.uk:/builds/org-mode_Emacs_22 ). Personally I've pretty much given up even monitoring such things since there seems to be such little appetite by most of the maintainers to test anything, or even to run tests, or monitor test results. From my experience, threads like this tend to go unanswered. Best, Martyn
[O] org-mode are these two entries identical for org-mode?
* aptitude install emacs -r get emacs text editor. * aptitude install emacs -r get emacs text editor. Jude When people ask do you believe in Numerology, the proper reply for me at least is do you believe in a hammer? The proper answer for me for both questions is no, they're both tools and to be used under appropriate circumstances.
[O] Journal versus clock tables: Opposing requirements?
I'm trying to get org-mode to provide me with two things, but haven't found a way to do it. 1. First, I want to be able to use it like a daily engineering or science journal, logging notes as they occur, in pretty much linear fashion chronologically. Or, more to the point, I want to be able to report and look at items as they occurred, in pretty much linear fashion chronologically. Essentially I want to be able to report on activity by time of occurrence, not topic. 2. But second, I want to see clock tables covering a period of time, which groups related items together regardless of when (within the given period) they happened. Essentially I want to be able to report on actrivity by topic, not time of occurrence. I'm using some of Bernt Hansen's excellent setup, but it still isn't getting me quite where I want to be. I'll note also that the agenda's log mode doesn't really give me point 1. It simply lists the *headlines* which have a clock entry or timestamp at a given time. I want to see my entire journal -- a la a blog. (*Ideally* I'd like to be able to control the depth to which that entire journal output went to, but seeing the whole shebang would be a good start.) Anyone have any ideas how to do this. thanks, Tommy