[O] A little bug of Org capture?
Dear all,
Don't know if it is a little bug:
For org capture template, if I set an template like this:
("i" "INBOX" entry (file+olp (concat org-private-dir "/iPrv.org") "INBOX"
"test") "* %?" :prepend t)
And for the iPrv.org, I have this structure:
* INBOX
** test
Then it works.
But if the first level and the second level happen to have the same title
(it does happen to me sometimes), like:
* INBOX
** INBOX
("i" "INBOX" entry (file+olp (concat org-private-dir "/iPrv.org") "INBOX" "*
INBOX*") "* %?" :prepend t)
Then Org will prompt an error.
Thanks,
Chao
[O] Bug: Block agenda with tag limited clock report adds all tasks [7.5 (release_7.5.113.g9010a)]
Hi,
Here's another problem I noticed with block agendas and tag limited
clock reports.
This is the same setup as the previous report.
Generating a clock report including all of the clock times for today
works great. When I try to show a clock report limited to the current
tag filter with C-u R a new section is added in front of my agenda view
for "All currently open TODO items:".
Steps to reproduce:
$ minimal-emacs
| Step | Key | Details |
|--+-+---|
|1 | C-c a x | Load block agenda view|
|2 | R | Generate clock report |
|3 | C-u R | Load tag limited clock report |
My original agenda view looks like this after step 1,
,
| Week-agenda (W12):
| Monday 21 March 2011 W12
| Tuesday22 March 2011
| Wednesday 23 March 2011
| Thursday 24 March 2011
| Friday 25 March 2011
| Saturday 26 March 2011
| Sunday 27 March 2011
|
|
| Tasks to Refile
`
and after step 2 it looks like this:
,
| Week-agenda (W12):
| Monday 21 March 2011 W12
| Tuesday22 March 2011
| Wednesday 23 March 2011
| Thursday 24 March 2011
| Friday 25 March 2011
| Saturday 26 March 2011
| Sunday 27 March 2011
|
| | File | Headline | Time |
| |--+--+|
| | | ALL *Total time* | *0:00* |
|
|
| Tasks to Refile
`
but after step 3 I get the following unwanted list of TODO items in
front of the agenda.
,
| All currently open TODO items:
| org-scratch:TODO Do this
| org-scratch:TODO Do that
| org-scratch:TODO Do this other thing
| Week-agenda (W12):
| Monday 21 March 2011 W12
| Tuesday22 March 2011
| Wednesday 23 March 2011
| Thursday 24 March 2011
| Friday 25 March 2011
| Saturday 26 March 2011
| Sunday 27 March 2011
|
| | File | Headline | Time |
| |--+--+|
| | | ALL *Total time* | *0:00* |
|
|
| Tasks to Refile
`
The block agenda with "Tasks to Refile" is gone. I really want to keep
this block agenda view as my default agenda view.
My full block agenda view already includes all of these tasks and it
displays the details twice. The code that activates this 'All
currently open TODO items:' section seems to be related to mobile org.
~/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-custom-commands (quote (("x" "Weekly Review block agenda"
((agenda "" nil) (tags "LEVEL=1+REFILE" ((org-agenda-overriding-header "Notes
and Tasks to Refile") (org-agenda-todo-ignore-with-date nil)
(org-agenda-todo-ignore-deadlines nil) (org-agenda-todo-ignore-scheduled nil)
(org-agenda-todo-ignore-timestamp nil) (org-agenda-overriding-header "Tasks to
Refile"
(setq org-agenda-files '("/tmp/publish/org-scratch.org"))
--8<---cut here---end--->8---
/tmp/publish/org-scratch.org
--8<---cut here---start->8---
* Tasks
** TODO Do this
** TODO Do that
** TODO Do this other thing
** DONE Did that
--8<---cut here---end--->8---
Emacs : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
of 2010-12-11 on raven, modified by Debian
Package: Org-mode version 7.5 (release_7.5.113.g9010a)
Regards,
--
Bernt
[O] Re: [Orgmode] Daily Debian Builds
On Fri, Jul 30, 2010 at 11:03 PM, Mark A. Hershberger wrote: > suvayu ali writes: > >> I wanted to try it on Ubuntu Lucid but launchpad says failed build for >> the 26th of July. > > There is still a Lucid build available: > > https://code.launchpad.net/~org-mode/+archive/daily-ppa > > I'm a little frustrated with the “daily build” since it seems buggy. > I may start hosting my own cron job to do this. I'm just curious to know, what is the status of this. The last build was 24 weeks ago. Mark, did you disable daily builds? Is there a build for 7.5 available? Are the latest builds available elsewhere? Thanks, Puneeth ps: I don't use these builds, but I (sometimes) need to point others to them.
[O] Bug: Jumping to date in block agenda loses agenda view [7.5 (release_7.5.113.g9010a)]
Hi,
I'm finally getting around to trying block agendas and I've replaced
most of my custom agenda commands with a single block view. Below is a
simplified block agenda view which demonstrates the problem. I can move
forwards and backwards one day at a time with 'f' and 'b' and it works
great. If however I want to jump to a specific date the block view is
lost and it reverts back to the regular calendar agenda view.
Steps to reproduce:
$ minimal-emacs
| Step | Key | Details|
|--+---+|
|1 | C-c a x | Load block agenda view |
|2 | j 3-1 RET | Jump to March 1st |
My original agenda view looks like this after step 1,
,
| Week-agenda (W12):
| Monday 21 March 2011 W12
| Tuesday22 March 2011
| Wednesday 23 March 2011
| Thursday 24 March 2011
| Friday 25 March 2011
| Saturday 26 March 2011
| Sunday 27 March 2011
|
|
| Tasks to Refile
`
and after step 2 it looks like this:
,
| Week-agenda (W09):
| Monday 28 February 2011 W09
| Tuesday 1 March 2011
| Wednesday 2 March 2011
| Thursday3 March 2011
| Friday 4 March 2011
| Saturday5 March 2011
| Sunday 6 March 2011
`
The block agenda with "Tasks to Refile" is gone. I really want to keep
this block agenda view as my default agenda view.
~/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-custom-commands (quote (("x" "Weekly Review block agenda"
((agenda "" nil) (tags "LEVEL=1+REFILE" ((org-agenda-overriding-header "Notes
and Tasks to Refile") (org-agenda-todo-ignore-with-date nil)
(org-agenda-todo-ignore-deadlines nil) (org-agenda-todo-ignore-scheduled nil)
(org-agenda-todo-ignore-timestamp nil) (org-agenda-overriding-header "Tasks to
Refile"
(setq org-agenda-files '("/tmp/publish/org-scratch.org"))
--8<---cut here---end--->8---
/tmp/publish/org-scratch.org
--8<---cut here---start->8---
* Tasks
** TODO Do this
** TODO Do that
** TODO Do this other thing
** DONE Did that
--8<---cut here---end--->8---
Emacs : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0)
of 2010-12-11 on raven, modified by Debian
Package: Org-mode version 7.5 (release_7.5.113.g9010a)
--
Bernt
Re: [O] [Babel] How to find out export format in a babel plugin
On 03/24/2011 10:09 PM, Jianing Yang wrote: Hi, all I've recently written a babel plugin which does syntax highlighting using pygment. However, I have to specify a '-f html' option every time I use it. It looks like #+begin_src pygment :cmdline -l bash -O linenos -f html exec 3<&0 # copies STDIN, it prevents 'read' stealing STDIN from '$command' while read FN; do test -e "$FN" || rm -iv "$FN"<&3 done< <(find . $level -type l) #+end_src Therefore, my question is that is there a way that a babel plugin can be aware about the export format? If there is, not only I can omit the '-f html' but it could also support for other export format, like latex, transparently. In git pulls from within the last few weeks, see the variable: org-export-current-backend Does your pygment idea have any overlap with: http://comments.gmane.org/gmane.emacs.orgmode/28420
[O] [Babel] How to find out export format in a babel plugin
Hi, all I've recently written a babel plugin which does syntax highlighting using pygment. However, I have to specify a '-f html' option every time I use it. It looks like #+begin_src pygment :cmdline -l bash -O linenos -f html exec 3<&0 # copies STDIN, it prevents 'read' stealing STDIN from '$command' while read FN; do test -e "$FN" || rm -iv "$FN" <&3 done < <(find . $level -type l) #+end_src Therefore, my question is that is there a way that a babel plugin can be aware about the export format? If there is, not only I can omit the '-f html' but it could also support for other export format, like latex, transparently. The following is my code: (require 'ob) (require 'ob-eval) (defvar org-babel-default-header-args:pygment '((:results . "html") (:exports . "results")) "Default arguments to use when evaluating a pygment source block.") (defun org-babel-execute:pygment (body params) "Execute a block of Dot code with org-babel. This function is called by `org-babel-execute-src-block'." (let* ((result-params (split-string (or (cdr (assoc :results params)) ""))) (out-file (cdr (assoc :file params))) (cmdline (cdr (assoc :cmdline params))) (in-file (org-babel-temp-file "pygment-")) (cmd (concat org-pygment-path " " cmdline " " (org-babel-process-file-name in-file) ))) (unless (file-exists-p org-pygment-path) (error "Could not find pygment at %s" org-pygment-path)) (message (concat "Running Pygment: " cmd)) (with-temp-file in-file (insert body)) (org-babel-eval cmd "") )) (defun org-babel-prep-session:pygment (session params) "Return an error because Dot does not support sessions." (error "Dot does not support sessions")) (provide 'ob-pygment) Thanks very much Regards, Jianing Yang
Re: [O] Extracting pdf metadata
On Thu, Mar 24, 2011 at 8:21 PM, Marvin Doyley wrote: > Hi there, > > Does anybody have a lisp code that can extract metadata from pdf. There is > an interesting program called sciplpore > (http://www.sciplore.org/software/sciplore_mindmapping/ that does this for > freemind), it might be useful if were able to do the same with org (i.e., > important pdf meta data, bookmark and stickies directly into org). > Not that this what you asked for, but there's a small python application called stapler that can extract metadata. At the least, maybe somehow it could be useful to look at the code? Then again, it's built on a python library... so maybe there's nothing that will really translate to elisp. I just ran into it as an alternative to pdftk and thus it was fresh in my mind. At github: https://github.com/fwenzel/stapler Pertinent output from help: ,--- | $ stapler --help | ... | info: ... (no output needed) |Display PDF metadata | ... `--- Best regards, John > > Cheers > > M > > PS I think one of my goals this summer will be to learn lisp :) >
[O] Extracting pdf metadata
Hi there, Does anybody have a lisp code that can extract metadata from pdf. There is an interesting program called sciplpore ( http://www.sciplore.org/software/sciplore_mindmapping/ that does this for freemind), it might be useful if were able to do the same with org (i.e., important pdf meta data, bookmark and stickies directly into org). Cheers M PS I think one of my goals this summer will be to learn lisp :)
Re: [O] Re: unnumbered subsections in latex export
On Thu, 24 Mar 2011 15:25:02 -0400 Nick Dokos wrote: > > PS: Also note that I couldn't be as available as I wanted the 10 > > last days due to personal problems, but things look better now. > > > > I think I'm speaking for all of us: Nothing here is so urgent that it > cannot wait for a few days or a few weeks or a few months. If > something absolutely *needs* to be done *today* (I can't think of > anything that would be this urgent, but let us say that there is > something), and you cannot get to it, let the list know: we'll either > know to wait or somebody will up and do it. To put it in org languange, * WInP [#A] Real life * TODO [#B] Org tasks * TODO [#C] Other things Wishing you the best of luck in dealing with the problems Bastien. -- Suvayu Open source is the future. It sets us free.
[O] Re: "Tag hierarchy" idea
Thanks Jambunathan K. Your concise summary is correct. As it stands, selective export from Orgmode is already excellent -- combining both #+EXPORT_SELECT_TAGS: and #+EXPORT_EXCLUDE_TAGS: in various ways allows for very precise exporting; this is particularly apparent when dealing with tags at different heading levels. I am particularly thinking about largish publishing projects, where it would be less easy to add manage individual tags at the level of the heading. Building groups of composite tags from small groups of atomic tags, as needed, and then exporting/excluding those composite tags (plus other atomic tags) would be a neat way of managing this. The atomic tags could remain fairly static and the composite tags could be juggled as needed. Migrating stuff to Orgmode isn't a big deal -- the interesting part is using the information once it's there. As I hope is clear, I think Org is fantastic as it stands. For the type of thing I am (already) doing, the only other real solutions are DITA-based -- and Org is a whole lot more fun. John On Thu, Mar 24, 2011 at 11:34 AM, Jambunathan K wrote: > > IIUC, what you are saying is that you would like to define few atomic > tags and a few composite tag. A composite tag is presumably a union of > some of those atomic tags. You need an ability to selectively export of > the items that fall under the composite tag. > > Orgmode allows selective viewing (and exporting) of tagged documents. I > think all you need is to define a query and export only the visible > portion of the document. (I don't use tagging much but you can get > useful information from the manual) > > It still it beats me how would you solve the problem of migrating > existing word documents in to Orgmode. Looks like that is a much bigger > problem right there than the lack of facility for elaborate hierarchical > organization. > > Jambunathan K. > > > >
Re: [O] Using org-mode for recipes (i.e. cooking)
PS. Using Eric Schulte's new with-time macro (http://orgmode.org/worg/org-hacks.html#sec-1_2_6), part of the table formula in my above example can be written more compactly: $5 = '(if (string-match org-timer-re $3) (org-timer-secs-to-hms (- (org-timer-hms-to-secs $2) (org-timer-hms-to-secs $4))) "") becomes: $5='(if (string-match org-timer-re $3) (with-time t (- $2 $4)) "")
Re: [O] orgmode BEAMER scaling image
It worked great. Thanks a lot!!! Gilberto On 3/24/2011 9:26 AM, John Hendy wrote: On Thu, Mar 24, 2011 at 11:35 AM, Gilberto wrote: In his org-mode beamer tutorial, Eric Fraga (very useful tutorial BTW, thanks) gives an example of using an image, and writes I have added an attribute to the image to tell LaTeX to scale the image to the full width of the column. Can I add a similar attribute to my images without having to tweak the .tex file? In other words, can I directly do that in org beamer mode? You want the #+attr_latex feature to send export options to LaTeX[1]. Here's an example: - * Section ** Slide name *** Column 1 :BMCOL:B_ignoreheading: :PROPERTIES: :BEAMER_col: 0.45 :BEAMER_env: ignoreheading :END: Here's the text for column 1. *** Column 2 :BMCOL:B_ignoreheading: :PROPERTIES: :BEAMER_col: 0.45 :BEAMER_env: ignoreheading :END: #+ATTR_LaTeX: width=0.95\textwidth [[/here/is/the/path/to/your/image.jpg]] -- The width= option scales the image. \textwidth when used in the column environment applies to the width of the *column* textwidth, not that of the actual total page size. I've found that using 0.45 for the :BEAMER_col width made things look a little better, but that might have been due to my custom template. Use 0.5 if you want to make it bigger and it works for you. [1] http://orgmode.org/manual/Images-in-LaTeX-export.html Hope that helps, John Gilberto Conde ah.gilbert...@gmail.com ___
Re: [O] [OT] Another way org-mode is different
On Thu, Mar 24, 2011 at 12:44 AM, Jeff Horn wrote: > See http://cl.ly/5TwV. > > The relevant quote: > "There’s no perceived value in open source for mentoring, > facilitation, disciplining of unruly users, training of newcomers or > non-technical users, etc., which are needed to support both designers > of any gender and women in any role." > > This is definitely not true of org-mode. I have had more extensive > interactions with the Erics, Carsten, and Bastien, but *everyone* on > this list has been helpful in learning not just org-mode, but emacs, > literate programming and research, figuring out git, and becoming a > contributor as well as a user. Seconded! Though... I don't really count myself as a contributor so much... though I hope to be one day! This group is truly fantastic, supportive, and I've just been blown away by the level of assistance, personal investment of time to figure things out, etc. On top of that, I consider a non-existent rate of "RTFM"s an extreme positive! What a dynamic project with an incredible rate of development and incorporation of user-requested features. Most open source projects really can't say that as far as I can tell. Thanks all, John > > Thanks. You're all my mentors. > > -- > Jeffrey Horn > http://www.failuretorefrain.com/jeff/ > >
Re: [O] advice: how to export a list without exporting all entries
On 24.3.2011, at 21:45, Eric S Fraga wrote: > Carsten, > > one question about your workflow. I've actually implemented much of > what you have suggested but I am having one problem: > > Carsten Dominik writes: > > [...] > >> 3. I am not using an ordered list for the action items. Instead, I >> give them explicit numbers, in the sequence in which I am defining >> the actions. I am using some custom code (see end of this mail) to >> create these actions with unique numbers. Running >> `M-x org-maction-new-action' (this is `C-c n' in my setup) will >> insert a new action that looks like this: >> >> ** TODO Action #2: :#2: > > This is fine except that #x tags don't work in latex export! Obviously, > you must not export to latex. The # is not escaped when it is in a tag > although it is within the headline. My immediate easy solution is to > change the tag prefix (A) but I wonder if this is a bug in the latex > export? Yes, apparently this is a problem in LaTeX export. > > In any case, I'm liking this solution to my minutes+actions problem. This is good to hear! - Carsten
Re: [O] Using org-mode for recipes (i.e. cooking)
Hi, On 3/24/11 12:47 PM, Le Wang wrote: (...) > Is it possible to inline count-down timers in a cooking step? For > example "2. simmer sauce for 40 minutes on low heat. > ", so there is a button at the end of the line > that starts a count-down timer. > > Many timers from different steps can be started simultaneously, and > each timer should be able to be paused and restarted. And there > should be an easy way to get an overview of of all ongoing timers from > the current document. > > Is it possible to hack this together using existing org > functionality? I don't think Org has built-in support for concurrent countdown timers. But you can fake this pretty well with org-timer, properties, column view, a dynamic block, and some lisp table formulas. A ready-to-run example is attached, hopefully self-explanatory, probably buggy, and WITH ABSOLUTELY NO WARRANTY. This is a learning exercise for me. Instead of using a start timer button (for which you could use an `elisp:' link, like the one I've put in to make it easy to stop the timer), you can write a hook to start countdowns when the TODO state changes. That rather hackish function is the only code here that's not out of the box. Yours, Christian #+STARTUP: showeverything #+COLUMNS: %ITEM %For %Start %Elapsed %REMAINS %Message #+TODO: TODO RUNNING | DONE Recipe with timers * First evaluate this (or put in your .emacs) #+begin_src emacs-lisp (require 'org-timer) (defun my/recipe-timer-start () "When state is changed to `RUNNING', change the `Start' property of the entry to the current value of org-timer if this is a timed recipe entry, i.e. if it has a h:m:s-formatted duration in its `For' property. When state is changed to `DONE', reset `Start' to `-'." (when (string-match org-timer-re (or (org-entry-get (point) "For") "")) (cond ((string= state "RUNNING") (org-set-property "Start" (org-timer nil t))) ((string= state "DONE") (org-set-property "Start" "-") (setq org-after-todo-state-change-hook 'my/recipe-timer-start) #+end_src #+results: : my/recipe-timer-start * Recipe Here's the dynamic block with the overview. - Refresh manually with `C-c C-c' on the `begin' line. - Note that this will start the timer if it's not running. - The countdown is in the "REMAINS" column. #+begin: columnview :id local | ITEM | For | Start | Elapsed | REMAINS | Message | |---+-+---+-+-+-| | * Recipe | | | 0:00:00 | | | | ** TODO Let simmer| 0:40:00 | - | 0:00:00 | | | | ** TODO Let ferment | 2:00:00 | - | 0:00:00 | | | | ** TODO Leave in oven | 0:04:00 | - | 0:00:00 | | | #+tblfm: $4='(org-timer nil t)::$5='(if (string-match org-timer-re $3) (org-timer-secs-to-hms (- (org-timer-hms-to-secs $2) (org-timer-hms-to-secs $4))) "")::$6='(if (< (org-timer-hms-to-secs $5) 0) "STOP!" "") #+end: Below are a few tasks with durations in their `For' properties. - Start them by changing the task's state to `RUNNING' with `C-c C-t'. (If org-timer is not running, it will be started.) - When time's up for a task, it will message `STOP!'. Navigate to the task and change its state to `DONE' with `C-c C-t' (after taking stuff out of the oven, or whatever). - When you're done, you can [[elisp:org-timer-stop][stop the timer]] (click the link or press `C-u C-c C-x ,'). ** TODO Let simmer :PROPERTIES: :For: 0:40:00 :Start:- :END: ** TODO Let ferment :PROPERTIES: :For: 2:00:00 :Start:- :END: ** TODO Leave in oven :PROPERTIES: :For: 0:04:00 :Start:- :END:
Re: [O] advice: how to export a list without exporting all entries
Carsten, one question about your workflow. I've actually implemented much of what you have suggested but I am having one problem: Carsten Dominik writes: [...] > 3. I am not using an ordered list for the action items. Instead, I >give them explicit numbers, in the sequence in which I am defining >the actions. I am using some custom code (see end of this mail) to >create these actions with unique numbers. Running >`M-x org-maction-new-action' (this is `C-c n' in my setup) will >insert a new action that looks like this: > >** TODO Action #2: :#2: This is fine except that #x tags don't work in latex export! Obviously, you must not export to latex. The # is not escaped when it is in a tag although it is within the headline. My immediate easy solution is to change the tag prefix (A) but I wonder if this is a bug in the latex export? In any case, I'm liking this solution to my minutes+actions problem. Thanks again, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
[O] org-remember and lists
Hello, I'm trying to tweak remember templates to follow my needs but I fail. I want to do template for my shopping list entries like this: (setq org-remember-templates (list (list "shopping" ?s "- [ ] %?\n" (concat org-directory "notes.org") "Shopping List") )) However after saving, there is header prepended to this like: ** Thu Mar 24 21:32:49 2011 (- [ ] apples) - [ ] apples I don't want this - I already have heading with all the info I need "* Shopping List". ;) I don't know how to accomplish that. Any help? Thanks, Radek.
Re: [O] Re: Completing with anything
Can you separate out the gnus specific code at some point. If I ever get any time (two small children and a day job, so big if) I'd like to integrate it into Wanderlust. But currently the code assumes that you're using gnus. On Wed, Mar 23, 2011 at 3:05 PM, Julien Danjou wrote: > On Wed, Mar 23 2011, Eric S Fraga wrote: > >> Will you provide a means to capturing email addresses from emails >> directly into an org-contacts db, as bbdb does with ":" and ";" (the >> latter for annotation of the entry)? That would be necessary for any >> move away from bbdb, IMO. > > This is already provided. > > -- > Julien Danjou > ❱ http://julien.danjou.info >
[O] Re: s-tab not working as intended in kde's konsole
Izzie writes: > Wow! You just opened me to a whole new world of possibilities in advanced > window management I didn't suspect existed. Actually that's one of the reasons I still stick with KDE... indispensable when you have to work remotely and the other end beams a complete desktop over. Another neat-o thing is that you can make your windows frame-less and fix their geometries. > No luck though as disabling kde shortcuts didn't change a thing. With > both konsole shortcuts and kde shortcuts out of the way the problem is > still here. I've just tested it on my system and the problem is indeed with konsole itself and not any of the standard shortcuts. Qt takes over the Backtab to re-focus on the "New Tab" button while you are in the terminal window. You can actually work around by just not showing that button (it's an option in the profile editor). I consider this a bug in konsole (it looks like they correctly handle TAB, but forgot about BACKTAB), you should report this to the KDE folks. Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] Re: unnumbered subsections in latex export
Bastien wrote: > Here is a list of difficulties: > > 1. the syntax of the backends vary, and this means that all Org options >are not meaningful in all target formats; > >*Example*: #+XSLT is only meaninful for the Docbook export. The >variable `org-export-html-postamble' is only meaningful for the HTML >export. Etc. > > 2. exporters use various methods to export the file (e.g. the HTML >exporter goes line by line, the LaTeX exporter parses the file and >render each section); > >*Example*: users often ask why the LaTeX exporter cannot export a >headline of level 3 right after a headline of level 1: they ask that >because the HTML exporter can do this, while the LaTeX one cannot. >And the LaTeX one cannot because parsing an ill-structured Org buffer >is tricky for it. > > 3. exporters are maintained by various people: I know the HTML exporter >and the LaTeX one, others know the other exporters, etc. > > I need your help do deal with these issues. > > The first thing to do is to have a list of annoying inconsistencies that > need to be addressed in priority. > > The second thing would be to build a table (somewhere on Worg?) with the > list of options and the way they are taken care by each exporter. Such > a "synoptic view" would help developers know what they can work on, and > users know what they have to expect from options. On the long term, it > would also help make the documentation clearer about all these aspects. > > This will at least help with the first difficulty -- and motivate all > people working on the exporters to address the second one. The third > one can be turned into a *chance*: that of having several people working > in the same direction. > Excellent plan! If nobody beats me to it, I'll send out an initial draft of such a table to the list for comment over the weekend: not a complete thing, mind you - just something partially covering one or two exporters. We can modify it as necessary and then proceed to populate it over the next few weeks. Nick PS: > So, bare with me on this :) > I'm sorry to be so sophomoric about this, but the image that popped into my mind was a bunch of org developers dropping their pants and mooning the world. Bastien, I will have to undergo years of therapy for this: I'll send you the bill :-) > PS: Also note that I couldn't be as available as I wanted the 10 last > days due to personal problems, but things look better now. > I think I'm speaking for all of us: Nothing here is so urgent that it cannot wait for a few days or a few weeks or a few months. If something absolutely *needs* to be done *today* (I can't think of anything that would be this urgent, but let us say that there is something), and you cannot get to it, let the list know: we'll either know to wait or somebody will up and do it. So you do what you need to do when you need to do it: org can take care of itself for a while without much supervision. And you are not alone.
Re: [O] orgmode BEAMER scaling image
Gilberto writes: > In his org-mode beamer tutorial, Eric Fraga (very useful tutorial BTW, > thanks) gives an example of using an image, and writes You're very welcome! > >> I have added an attribute to the image to tell LaTeX to scale the >> image to the full width of the column. > > > Can I add a similar attribute to my images without having to tweak the > .tex file? In other words, can I directly do that in org beamer mode? John Hendy has already answered but I guess you are implying that the tutorial on Worg is not clear about how that is done. The example code snippet has the #+ATTR_LATEX line in it. I guess I should be more explicit in the text? Thanks for highlighting this! -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
Re: [O] advice: how to export a list without exporting all entries
Carsten Dominik writes: [...] > > Hi Eric, > > I guess you could use one of the export hooks to clean up your > exported file when you are done. However, the problem will always > be that if you take a list environment, the numbering of the list > items will change when you take out items. An I am sure you know > from experience how nice it is to be able to talk about the number > of an action item, in order to get everyone on the same page > quickly. I am afraid it will be hard to achieve this with the > path you are thinking about. Yes, I am coming to that conclusion as well! > Defining and tracking action items through a series of meetings where > I have to do the notes is a frequent tasks for me. Here is my workflow > for this - maybe you can pick and choose some stuff for yourself. > In particular, I use outline nodes for tasks, in order to keep access > to the machinery Org gives me for tracking stuff. Thanks for the *very* detailed workflow. Fantastic and I think it would work well with my mode of operation. I guess I was too stuck in the /list/ mode and didn't even think of using outline nodes. I don't mind numbering them manually as we're talking about tens of actions over several years (typically <10 per meeting with 3 meetings per year for each individual "committee"). But, in any case, your code looks like even this bit is easily automated. What will work particularly well in my workflow will be the todo-state-tag trigger part which I had not even realised could be done (silly of me, of course ;-). Tying the =closed= tag to the export exclusion is so obvious in hindsight. Again, many thanks for this and for your code as well. I'll be implementing it like right now! eric PS - your whole workflow description might be very useful on Worg... -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
Re: [O] Bug: Recurring items NEVER show up in timeline unaccompanied
Carsten Dominik wrote: > Dear all, > > Maybe I can add the following background information to Nick's > amazing analysis. I wouldn't call it "amazing", but thanks for the kind words! > > - The timeline was the first agenda-like view I implemented, > it used to be (many years ago) the only way to see what was > coming up. That is why it only listed the future, and included > the past when used with e prefix argument (I believe). > > - Since then the agenda view came along, with vastly better > properties for being used as a planning tool for the coming > day an d week. It also included the possibility to look > at several files, which made the timelines view of a single > file look poor. Since then, the timeline has been a more > or less orphaned feature, and this is why it does not > work well with stuff like repeaters (repeaters where added > MUCH later). > > - So the use-case of the timeline view became slowly redefined > as a way to look at the milestones and events of a single > project. One consequence was to always include the past. > > - For historic reasons, the timeline uses the same mechanics > as the agenda: Pick a date, find everything that is going > on on that date, move on to the next date. Lather, rinse, > repeat. However, when looking at a project that may have > dates spread over potentially many years, this mechanics > is not very practical. First, there will be many empty > days where nothing is going on. This will make the view > look very boring and will make it hard to find useful > dates. Second, constructing the view in this way > takes forever because of the inefficient pick-a-day, > scan-entire-file-to-see-what-fits-strategy. > > - To makes things more efficient, the timeline starts by > first making a list of relevant days in the project by > looking at all explicit dates, and at ranges. Here is > where the repeaters go wrong - they should return a whole > list of dates where they are important - but they only > add one, the starting date. With this list of dates, > it knows how to skip ranges of dates where nothing is > happening. > A very interesting history lesson: thanks very much for that. > Solutions for this problem are (these are alternatives) > > 1. Be satisfied with the way things are, just realize that >repeaters only show up on the first date when the >event happens for the first time. > > 2. Use the agenda, restricted to a single file, for a time >range you specify. This has the advantage that also >diary sexps will work properly - the timeline currently >has no way to deal with these. > > 3. Change the section of the timeline code that produces >the list of interesting dates. One strategy could be >to first make a list of explicit dates, in order to >define an overall range. Then find all repeaters and >add dates this repeater targets, restricted to >the range of explicit dates in the file. If done >like this, you could always put a target date >for conclusion of the project into the file, and that >far-into-the-future date would define the range of >the repeaters automatically. > > 4. Define a variable that will make the timeline always >look at *every* date in the range covered by the >file. And live with the fact that constructing the >view might take long. Maybe it will not even to >terribly long if you really use this view for single >projects. This would be easy to implement. > > 5. Rebuilt the entire timeline view to not use the >agendas mechanics of picking a date, scanning the file, >picking a date etc. Instead, do a single pass over the >file and build a list of dates with events in this way >and then format and display the list. Disadvantage >here would be that many things which now work easily, >like log view to include logging dates, would have to >be thought over and reimplemented specially for the >timeline. > And a very clear analysis of the situation. In these possibilities, there is the underlying assumption that the timeline is kept as a feature. What about the additional possibility of actually declaring it obsolete and getting rid of it? Can the agenda (possibly with some extension) cover the need of Mark S for omitting days where nothing happens? Is there anything else that the timeline offers? > Hope this helps. Extremely helpful, thanks! Nick
Re: [O] org table calc and lisp for hh:mm timetable
>> If we're not just looking for a neat workaround for some special cases >> anymore, but looking at making org-tables aware of time-like strings >> by default, a better strategy than to convert them into integers might >> be to translate them into Calc time format and back again. >> >> After all, Calc and hence the Org spreadsheet already handles time >> arithmetic perfectly well, it's just that it would be nice to have >> this functionality with the extra option to enter and display times as >> =12:45= rather than =12@ 45'= or =12h 45m=. >> > > I did not realize that calc (and hence Org) already supported operating > on time values. The =7@ 30'= format does indeed work well for time > table formulas (although the =12h 5m= format does not), e.g., > > | 1@ 20' | 2 | 0@ 40' 0." | > | 2@ 5' | 3 | 0@ 41' 40." | > #+TBLFM: $3=$1/$2 > > Maybe all that is needed is explicit mention of this syntax somewhere in > the table section of the Org-mode manual. > > The only remaining reason to support a %d:%d time format is that it is > what I (and I expect most users) would first think of to represent time, > and supporting such a format would allow time calculation in a table to > "just work" -- meaning users could likely manipulate time without having > to first look in the manual for the appropriate Calc format. > > However as Carsten mentioned such an automatic translation of e.g., > =7:20= to =7@ 20'= would be a bit bold, and (as mentioned elsewhere) it > would result in having to make some denomination decisions, namely does > =7:20= convert to =7@ 20'= or =7' 20"=. > > For now I've posted my `with-time' macro up to Worg. > > Cheers -- Eric Hi all, just came back on this thread and was amazed what you guys did with it.. amazing.. havent tried the patch yet but the with-time macro is great. Now it is even easy to sum up a whole column of timevalues. I use it like the following now: | start | lunch | back | leave | sum | |---+---+---+---+---| | 8:00 | 12:00 | 13:00 | 17:00 | 8:00 | | 8:00 | 12:00 | 13:00 | 17:00 | 8:00 | |---+---+---+---+---| | | | | | 16:00 | #+TBLFM: @>$5='(with-time t (+ @2..@>>)) Thanks a lot (also for making it to org hacks : ) Martin
[O] Re: unnumbered subsections in latex export
Bastien writes: > I fully agree with Nick and Thomas (and others who also agreed): Org's > export facilities need some real love and new export features need to be > introduced as complete and as consistent accross exporters as possible. > > I hope we'll make progress on this for 7.6. That would be very welcome news. I'm not sure at what level you want to tackle that problem -- just cleaning up some glaring inconsistencies or a full tear-down and re-build? I suspect that a (formal) document model for orgmode documents would be required. This ties neatly into a formal syntax for orgmode documents that Dominik has been asked for at FOSDEM. > Here is a list of difficulties: > > 1. the syntax of the backends vary, and this means that all Org options >are not meaningful in all target formats; This actually is meta-data for the export process. It would be neat if it were the same for each backend, but that probably doesn't make much sense. But at least the various backends shouldn't require different metadata for the same purpose as long as the capabilities are the same. > 2. exporters use various methods to export the file (e.g. the HTML >exporter goes line by line, the LaTeX exporter parses the file and >render each section); This is a question of the supported document model(s). Formally HTML doesn't support a lot of what the exporter may spit out, even if it renders as intended on many browsers. > 3. exporters are maintained by various people: I know the HTML exporter >and the LaTeX one, others know the other exporters, etc. This wouldn't be much of a problem (I think...) if there was a way to specify which parts of the org document model are supported by the exporter and have a generic exporter hook into the export backend with just the parts that the backend supports. Or the other way around, although I suppose it would be more efficient if the generic exporter didn't need to build structures that the backend doesn't then export due to lack of support anyway. Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Specifying \institute[short]{long] in Beamer presentations
On Wed, Mar 23, 2011 at 07:18:45PM -0400, Bernd Weiss wrote:
> I am currently preparing a Beamer presentation and I would like to
> include \institute[short]{long} into my org-file;
This works for me:
#+BEAMER_HEADER_EXTRA: \institute{My insitute}
Cheers,
Miklós
--
signature.asc
Description: Digital signature
Re: [O] orgmode BEAMER scaling image
On Thu, Mar 24, 2011 at 11:35 AM, Gilberto wrote: > In his org-mode beamer tutorial, Eric Fraga (very useful tutorial BTW, > thanks) gives an example of using an image, and writes > > I have added an attribute to the image to tell LaTeX to scale the image to > the full width of the column. > > Can I add a similar attribute to my images without having to tweak the .tex > file? In other words, can I directly do that in org beamer mode? You want the #+attr_latex feature to send export options to LaTeX[1]. Here's an example: - * Section ** Slide name *** Column 1 :BMCOL:B_ignoreheading: :PROPERTIES: :BEAMER_col: 0.45 :BEAMER_env: ignoreheading :END: Here's the text for column 1. *** Column 2 :BMCOL:B_ignoreheading: :PROPERTIES: :BEAMER_col: 0.45 :BEAMER_env: ignoreheading :END: #+ATTR_LaTeX: width=0.95\textwidth [[/here/is/the/path/to/your/image.jpg]] -- The width= option scales the image. \textwidth when used in the column environment applies to the width of the *column* textwidth, not that of the actual total page size. I've found that using 0.45 for the :BEAMER_col width made things look a little better, but that might have been due to my custom template. Use 0.5 if you want to make it bigger and it works for you. [1] http://orgmode.org/manual/Images-in-LaTeX-export.html Hope that helps, John > Gilberto Conde > ah.gilbert...@gmail.com > ___ > > >
Re: [O] advice: how to export a list without exporting all entries
On 21.3.2011, at 10:16, Eric S Fraga wrote:
> Hi,
>
> I chair a particular committee at work and am responsible for keeping
> track of any actions that arise from our meetings. I use org for this
> (obviously ;-). So far, so good.
>
> I would like to move to a system in which all the actions are numbered
> sequentially. At present, they are numbered sequentially within a list
> for each meeting. I would like to have a single list which grows over
> time. However, when I distribute the minutes of the latest meeting, I
> would like to only have those actions which are not yet complete listed
> in the document I circulate. The complication is that I want those
> actions that have actually been done still in the list but not exported.
>
> Is there any way to /comment/ out individual list items (whether bullet
> or enumerated) on export? I export typically to latex but this need not
> be a constraint. Simply putting [ ] versus [X] boxes on the items is not
> satisfactory as the list would be very long if all items were included in
> the export.
>
> Is there some hook that I can intercept that would enable this? Can I
> encapsulate individual list items into latex macros with the status of
> the [ ] or [X] boxes? I am more than happy to write latex code as
> required! Or even, at a push, elisp code...
>
> Thanks,
> eric
Hi Eric,
I guess you could use one of the export hooks to clean up your
exported file when you are done. However, the problem will always
be that if you take a list environment, the numbering of the list
items will change when you take out items. An I am sure you know
from experience how nice it is to be able to talk about the number
of an action item, in order to get everyone on the same page
quickly. I am afraid it will be hard to achieve this with the
path you are thinking about.
Defining and tracking action items through a series of meetings where
I have to do the notes is a frequent tasks for me. Here is my workflow
for this - maybe you can pick and choose some stuff for yourself.
In particular, I use outline nodes for tasks, in order to keep access
to the machinery Org gives me for tracking stuff.
1. I use a special Org file for each meeting series
2. In the file, I use the following setup (at the end of the file, for
the file variables):
* COMMENT SETUP
#+TODO: TODO | DELG CNCL DOME
#+EXPORT_EXCLUDE_TAGS: noexport closed
# Local Variables:
# org-todo-state-tags-triggers: ((done ("closed" . t)))
# End:
Your tags and TODO states may be different, of cause.
What is important here is that I define that some tags mark a
tree to be excluded from export. Also, I set a local value for
=org-todo-state-tags-triggers= which arranges for action items to
receive a "closed" tag when they are marked done. Since this tag
also excludes stuff from exporting, done items will automatically
not be exported.
3. I am not using an ordered list for the action items. Instead, I
give them explicit numbers, in the sequence in which I am defining
the actions. I am using some custom code (see end of this mail) to
create these actions with unique numbers. Running
`M-x org-maction-new-action' (this is `C-c n' in my setup) will
insert a new action that looks like this:
** TODO Action #2: :#2:
The action starts with "Action #2", and it is tagged by "#2" to that
I can tag other stuff relating to this action and search for it.
Once I mark this action as DONE, it will automatically become
** DONE Action #2: Do this and that :#2:Peter:closed:
In this way it will be excluded from export, unless you change
EXPORT_EXCLUDE_TAGS (remove the "closed" there) temporarily to
produce an export with all the DONE stuff included.
4. My workflow is then as follows:
a. For each meeting I start a new top-level section in the document
for the notes. In the notes I create new actions and leave them
there for the time being.
b. I also have a top-level section "ACTIONS" in the file. This
section contains all the actions from previous meetings, each
action identified by its unique number. I have this section
right after the meeting notes sections, so that I can easily
export the latest meeting notes together with the action list,
simply by selection the two sequential trees.
c. During the meeting, I create new actions inside the meeting
notes. I also tag each action with names of people who are
responsible for it, so that I can later easily make lists of
actions for individual people, to send around reminders.
d. After the meeting I export the current meeting notes and the
ACTIONS section (as a list of old actions) and send it around.
At this moment, I have the new actions only in the meeting
notes, and not in the general actions list, to highlight
them as new.
[O] orgmode BEAMER scaling image
In his org-mode beamer tutorial, Eric Fraga (very useful tutorial BTW, thanks) gives an example of using an image, and writes > I have added an attribute to the image to tell LaTeX to scale the image to > the full width of the column. Can I add a similar attribute to my images without having to tweak the .tex file? In other words, can I directly do that in org beamer mode? Gilberto Conde ah.gilbert...@gmail.com ___
Re: [O] Bug: Recurring items NEVER show up in timeline unaccompanied
Hello Carsten et al, --- On Thu, 3/24/11, Carsten Dominik wrote: 1. Be satisfied with the way things are, just realize that repeaters only show up on the first date when the event happens for the first time. This would mean that you could never *trust* the timeline when dealing with events more than a week or two out. You would always have that lingering worry that you forgot to bump one of the repeaters. 2. Use the agenda, restricted to a single file, for a time range you specify. This has the advantage that also diary sexps will work properly - the timeline currently has no way to deal with these. This would be great if there were a "sparse" agenda. There isn't a way to make the agenda not show empty days is there? As it is, if you make an agenda extending out a year, you will have to wade through several hundred lines worth of empty days. 3. Change the section of the timeline code that produces the list of interesting dates. That seems like a good solution. Is it difficult? 4. Define a variable that will make the timeline always look at *every* date in the range covered by the file. And live with the fact that constructing the view might take long. Maybe it will not even to terribly long if you really use this view for single projects. This would be easy to implement. This would work too, I think. Creating an agenda that goes out one year only took about 3 seconds on my not-state-of-the-art machine. Presumably the timeline would be faster, since it wouldn't produce all the extra gap lines. Actually, when I tried to make a year long agenda using v-y I spent just about as much getting past the "are you sure" screens as it took to build the agenda. The ideal solution would be that the Timeline view would process dates exactly like the agenda, including multiple-files, but display them like the traditional timeline, with ranges of dates omitted. Mark
[O] Org-capture does not work with "long" extracts of text
Hi, I'm using for months Org-capture, with a lot of interest. In the beginning, it was on Firefox/Ubuntu, now it is (for external reasons) on Firefox/Windows XP. I think I can relate the limitation I'll expose with the switch from Linux to Windows. However, that does not necessarily mean that Windows is the culprit, as there are so many (little) differences between the two systems. So, what's the limitation? I can only capture _short text_ extracts from the Web. Once it gets over 20 lines of text or so, the "Org-capture" button still does not do anything. On the same page (whichever, in fact) as the one exhibiting the above problem, selecting a shorter region of text makes the behavior of the button come back to life. So, it really is related somehow to the length of the copied text (words, lines, bytes, ...?). Any idea or workaround for this? Best regards, Seb -- Sébastien Vauban
Re: [O] error in tableformula or bug
Nick Dokos wrote: > > @>-1 was allowed only for a short time, this format is flawed. > > Please use @>> instead to mean the second to last row. > > > > I think he wants the penultimate line, not the second line. > ... and I see that's what you said and I misread it: sorry for the noise. Nick
Re: [O] error in tableformula or bug
Carsten Dominik wrote: > > On 24.3.2011, at 10:46, Martin Halder wrote: > > > Hi again, > > > > have traced it down to the following commit which introduces the problem > > (thanks to bisect): > > [3dd474575205d3808390fc6ea2d5feccdb3d4305] Tables: Make @< and $< point to > > row/column 1 in a stable way > > > > Was there a change in the format or is it really a bug ? > > > > Thanks for help, > > Martin > > > >> found some strange behavior which was working before as far as I > >> remember.. I am on commit 078c01b. > >> > >> this is working correctly: > >> | 10 | > >> | 10 | > >> | 20 | > >> || > >> | 40 | > >> #+TBLFM: @>$1=vsum(@1..@3) > >> > >> this one with relative indexing (@>-1) not: (value is changing every time > >> the formula is applied: 37, 73, 109 (+36 every time) > >> | 10 | > >> | 10 | > >> | 20 | > >> || > >> | 37 | > >> #+TBLFM: @>$1=vsum(@1..@>-1) > > @>-1 was allowed only for a short time, this format is flawed. > Please use @>> instead to mean the second to last row. > I think he wants the penultimate line, not the second line. Nick
[O] Re: Editing source code function name?
C-h k! Great tool... you learn something new every day. Thanks!! On Thu, Mar 24, 2011 at 12:16 PM, Jambunathan K wrote: > Julian Burgos writes: > >> Hello fellow org-moders, >> >> We use C-c ' to edit the current code block. I would like to use a >> different key combination, but I cannot figure out the name of >> function that is called when pressing C-c'. I (think) I need it to >> map the new key combination in my .emacs file. >> Thanks for the help, >> > > Try this in an orgmode buffer: > > C-h k C-c '. > > What do you see? > > >> Julian > > -- > -- Julian Mariano Burgos Hafrannsóknastofnunin/Marine Research Institute Skúlagata 4, 121 Reykjavík, Iceland Sími/Telephone : +354-5752037 Bréfsími/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is, jmbur...@uw.edu
Re: [O] Editing source code function name?
Julian Burgos writes: Hi, Julian, > We use C-c ' to edit the current code block. I would like to use a > different key combination, but I cannot figure out the name of > function that is called when pressing C-c'. C-h a org src (apropos) gives a new buffer, where you can find: org-edit-src-code ;-) hth, Giovanni
[O] Re: Editing source code function name?
Julian Burgos writes: > Hello fellow org-moders, > > We use C-c ' to edit the current code block. I would like to use a > different key combination, but I cannot figure out the name of > function that is called when pressing C-c'. I (think) I need it to > map the new key combination in my .emacs file. > Thanks for the help, > Try this in an orgmode buffer: C-h k C-c '. What do you see? > Julian --
[O] Editing source code function name?
Hello fellow org-moders, We use C-c ' to edit the current code block. I would like to use a different key combination, but I cannot figure out the name of function that is called when pressing C-c'. I (think) I need it to map the new key combination in my .emacs file. Thanks for the help, Julian -- Julian Mariano Burgos Hafrannsóknastofnunin/Marine Research Institute Skúlagata 4, 121 Reykjavík, Iceland Sími/Telephone : +354-5752037 Bréfsími/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is, jmbur...@uw.edu
Re: [O] error in tableformula or bug
On 24.3.2011, at 10:46, Martin Halder wrote: > Hi again, > > have traced it down to the following commit which introduces the problem > (thanks to bisect): > [3dd474575205d3808390fc6ea2d5feccdb3d4305] Tables: Make @< and $< point to > row/column 1 in a stable way > > Was there a change in the format or is it really a bug ? > > Thanks for help, > Martin > >> found some strange behavior which was working before as far as I remember.. >> I am on commit 078c01b. >> >> this is working correctly: >> | 10 | >> | 10 | >> | 20 | >> || >> | 40 | >> #+TBLFM: @>$1=vsum(@1..@3) >> >> this one with relative indexing (@>-1) not: (value is changing every time >> the formula is applied: 37, 73, 109 (+36 every time) >> | 10 | >> | 10 | >> | 20 | >> || >> | 37 | >> #+TBLFM: @>$1=vsum(@1..@>-1) @>-1 was allowed only for a short time, this format is flawed. Please use @>> instead to mean the second to last row. - Carsten > > >
[O] Using org-mode for recipes (i.e. cooking)
Hi all, I'm fairly new to org-mode, and I only use it as an outliner / note taking tool. It seems recipes, being a list of ingredients and a series of steps is a perfect match for org-mode. Out of the box, org already works pretty well for recipes, but I think there are some areas for improved integration around timers. I'm not familiar with all the facilities of org-mode, maybe someone who uses org-mode for scientific experiments or something similar will have some hints. Is it possible to inline count-down timers in a cooking step? For example "2. simmer sauce for 40 minutes on low heat. ", so there is a button at the end of the line that starts a count-down timer. Many timers from different steps can be started simultaneously, and each timer should be able to be paused and restarted. And there should be an easy way to get an overview of of all ongoing timers from the current document. Is it possible to hack this together using existing org functionality? Thanks. -- Le
[O] Re: "Tag hierarchy" idea
IIUC, what you are saying is that you would like to define few atomic
tags and a few composite tag. A composite tag is presumably a union of
some of those atomic tags. You need an ability to selectively export of
the items that fall under the composite tag.
Orgmode allows selective viewing (and exporting) of tagged documents. I
think all you need is to define a query and export only the visible
portion of the document. (I don't use tagging much but you can get
useful information from the manual)
It still it beats me how would you solve the problem of migrating
existing word documents in to Orgmode. Looks like that is a much bigger
problem right there than the lack of facility for elaborate hierarchical
organization.
Jambunathan K.
John Tait writes:
> Thanks for your replies.
>
>
>
> I'm using org-mode both as an organiser and also as a way of composing modular
> documents with conditional text (controlled by both tags and #+INCLUDE).
>
>
>
> The problem I am trying to solve is one I encounter in my day job. Basically,
> I am
> sitting on top on hundreds of legacy Word documents, each filled with
> technical
> requirements aimed at different audiences. Each document can itself be aimed
> at
> different people and contain various subjects. This is a typical legacy
> document
> problem. It is horrible.
>
>
>
> Occasionally, we have to update vast amounts of this stuff as a batch, to
> reflect
> organisational change or other initiative. It is a manual slog.
>
>
>
> I am naturally drawn to dealing with this via some kind of structured document
> solution. This main problem here is that the information is inherently
> unstructured. It awas never written with structure in mind. It is impossible
> to
> impose a structure upon it without starting again.
>
>
>
> Attempts by management to enter all this stuff into the IBM DOORS requirements
> "database" have been so far been of only "limited success".
>
>
>
> We still get asked to produce tailored, filtered summarised information. These
> requests usually aren't satisfactorily resolved because a mountain
> of crumbling
> Word documents isn't a good starting point.
>
>
>
> That's the problem. Structured documents are an ideal, but totally
> impractical.
>
>
>
> Examples of requests might be:
>
>
>
> -- show me all the (railway) level crossing requirements in one place.
>
> -- show all everything to do with track patrolling.
>
> -- show all everything to do with track patrolling that a track patroller
> needs to
> see (no process or other office stuff).
>
> -- show me everything a Senior Engineer needs to know about this.
>
>
>
> etc.
>
>
>
> So there is a certain concept hierarchy beginning to form, but one that is
> fluid
> and maybe only needed once.
>
>
>
> I don't want to apply lots of tags only to have to add fresh tags later if
> ideas
> change. On the other hand, some tags would be pretty stable
> (:level-crossings:),
> especially if I was to use an abstraction (":M123:") in place, so I could
> change
> the definition of the tags slightly without altering the tag. (The definition
> of
> ":M123:" could, say, change from "Level crossing" to "Level crossing and
> road--rail
> access points".)
>
>
>
> (I used to work for Derwent Patents, applying concept tags to patents for
> help with
> patent searches, so this actually works.)
>
>
>
> The power of a tag hierarchy could be that I could alter and create groups for
> export very easily. It hard to come up with concrete examples for something
> that is
> just an idea but I will try.
>
>
>
> Say there are tags called :level-crossing: and :road--rail-access: If I
> could have
> a meta tag called ":access: that I could assign :level-crossing: and
> :road--rail-access: to, I could just use a single tag.
>
>
>
> Later, I could add ":gates:" to ":access:." and include those.
>
>
>
> Later, I could have a new meta tag called :roads:, and include
> ":level-crossing:"
> and "road-bridge".
>
>
>
> Then I could have a meta tag called ":patrol:", and include tags for
> ":level-crossing:" and ":patroller:".
>
>
>
> I hope I am illustrating this well enough. The point is that adding
> individual tags
> to headings could be complimented by grouping them under top level tags. The
> top
> level tags could be added to heading as well for maximum flexibility.
>
>
>
> This would provide awesome control and flexibility!
>
>
>
> Thanks for your time!
>
>
>
> John
>
>
>
>
>
> On Tue, Mar 22, 2011 at 8:27 AM, Christian Moe wrote:
>
>
> Hi,
>
> There
> was
> some
> discussion
>
Re: [O] Customizing LaTeX-export, Beamer, \institute, and BEAMER_envargs
Am 24.03.2011 05:16, schrieb Eric S Fraga:
Bernd Weiss writes:
Dear all,
I am preparing a Beamer presentation and I am having some trouble with
side effects (?) due to my attempt to customize the LaTeX-export. My
minimum example can be found below.
The default LaTeX-export does not recognise the '\institute'-option (I
mean, as far as I know). For that reason, I run "(add-to-list
org-export-latex-classes ...)". Unfortunately, the export-function
does no longer recognice ":BEAMER_envargs: [plain]" (or
":BEAMER_envargs: [shrink=5]")[1].
yes, that is correct. the default entry uses =org-beamer-sectioning=
which is where headings are translated to latex section or frame or
block etc entries *and* where the special beamer properties are
processed. As you have replaced the sectioning section of
=org-export-latex-classes= with your own, you have lost all of that
functionality.
You seem to want to achieve two things:
1. added your macros into the latex preamble, and
2. add the [fragile] option to each frame.
I would suggest you do 1 as you have done but keep org-beamer-sectioning
as the second argument for the org-export-latex-classes entry. To add
[fragile] to each frame, I would recommend, instead, using some
automated form of input, such as a yasnippet snippet like this one
(untested):
--8<---cut here---start->8---
#name : frame
# --
** ${1:frame title}
:PROPERTIES:
:BEAMER_envargs: ${2:[fragile]}
:END:
$0
--8<---cut here---end--->8---
so that typing "frame" followed by TAB would define a new headline,
prompting for the title and possible arguments (with defaults).
Hi Eric,
Thanks for your help! Unfortunately, that's not what I was looking for
and, therefore, rephrased my unclear question ("Specifying
\institute[short]{long] in Beamer presentations"). As pointed out by
Miklós or Suvayu, the solution was embarrassingly simpel: Just include
#+BEAMER_HEADER_EXTRA: \institute{My insitute}
or
#+LaTeX_HEADER: \institute[short name]{My awesome institute}
Anyway, I really appreciate your help!
Bernd
Re: [O] Customizing LaTeX-export, Beamer, \institute, and BEAMER_envargs
Bernd Weiss writes:
[...]
> Hi Eric,
>
> Thanks for your help! Unfortunately, that's not what I was looking for
> and, therefore, rephrased my unclear question ("Specifying
> \institute[short]{long] in Beamer presentations"). As pointed out by
> Miklós or Suvayu, the solution was embarrassingly simpel: Just include
>
> #+BEAMER_HEADER_EXTRA: \institute{My insitute}
>
> or
>
> #+LaTeX_HEADER: \institute[short name]{My awesome institute}
Ah, okay; I did note, however, that you did seem to be wanting to add
the [fragile] option to every frame.
Glad you got a solution, in any case!
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
Re: [O] Specifying \institute[short]{long] in Beamer presentations
Am 24.03.2011 05:42, schrieb Camille persson:
Hi,
I'm not sure but maybe you could declare it in your org file as:
#+MACRO: BEAMERINSTITUTELONG My long and detailed Institute
#+MACRO: BEAMERINSTITUTESHORT Short Institute
And change the export code as follows:
\\institute[beamerinstituteshort]beamerinstitutelong\n
But I didn't tested it, it is just an idea that comes up reading your mail.
Hi Camille,
Thanks for your answer! That would not solve my problem since it blocks
the functionality of frame ":PROPERTIES: ". I was simply looking for
#+BEAMER_HEADER_EXTRA: \institute{My insitute}
or
#+LaTeX_HEADER: \institute[short name]{My awesome institute}
Thanks,
Bernd
Re: [O] Specifying \institute[short]{long] in Beamer presentations
Am 23.03.2011 22:51, schrieb Suvayu Ali:
On Wed, 23 Mar 2011 19:18:45 -0400 Bernd
[...]
I am currently preparing a Beamer presentation and I would like to
include \institute[short]{long} into my org-file; it is important
that I am able to define a short and a long entry for institute.
How can I do this?
Let me reword your issue, but my understanding of LaTeX is limited
so please correct me if I am wrong.
You want to specify your affiliation with the institute command.
AFAIU the \institute command is declared in the header of a tex file.
So I am a little confused by your use of properties in org. Shouldn't
something like this after the "#+NAME:" and "#+AUTHOR:" directives
work fine?
#+LaTeX_HEADER: \institute[short name]{My awesome institute}
Oh, yes, that helps and I cannot believe that I didn't realize it before.
Thanks,
Bernd
Re: [O] Specifying \institute[short]{long] in Beamer presentations
Am 24.03.2011 04:59, schrieb PASZTOR Miklos:
On Wed, Mar 23, 2011 at 07:18:45PM -0400, Bernd Weiss wrote:
I am currently preparing a Beamer presentation and I would like to
include \institute[short]{long} into my org-file;
This works for me:
#+BEAMER_HEADER_EXTRA: \institute{My insitute}
Cool, thanks a lot! That solved all my problems.
Bernd
[O] error in tableformula or bug
Hi again, have traced it down to the following commit which introduces the problem (thanks to bisect): [3dd474575205d3808390fc6ea2d5feccdb3d4305] Tables: Make @< and $< point to row/column 1 in a stable way Was there a change in the format or is it really a bug ? Thanks for help, Martin > found some strange behavior which was working before as far as I remember.. I > am on commit 078c01b. > > this is working correctly: > | 10 | > | 10 | > | 20 | > || > | 40 | > #+TBLFM: @>$1=vsum(@1..@3) > > this one with relative indexing (@>-1) not: (value is changing every time the > formula is applied: 37, 73, 109 (+36 every time) > | 10 | > | 10 | > | 20 | > || > | 37 | > #+TBLFM: @>$1=vsum(@1..@>-1)
Re: [O] Specifying \institute[short]{long] in Beamer presentations
Hi,
I'm not sure but maybe you could declare it in your org file as:
#+MACRO: BEAMERINSTITUTELONG My long and detailed Institute
#+MACRO: BEAMERINSTITUTESHORT Short Institute
And change the export code as follows:
\\institute[beamerinstituteshort]beamerinstitutelong\n
But I didn't tested it, it is just an idea that comes up reading your mail.
--
Camille
2011/3/24 Suvayu Ali
> On Wed, 23 Mar 2011 19:18:45 -0400
> Bernd Weiss wrote:
>
> > I assume that my first email[1], which I sent yesterday, was not
> > clear enough to draw any/enough attention.
> >
>
> Since orgmode is a volunteer effort and the list is a relatively low
> traffic list, often posts are answered after a few weeks. :)
>
> > I am currently preparing a Beamer presentation and I would like to
> > include \institute[short]{long} into my org-file; it is important
> > that I am able to define a short and a long entry for institute. How
> > can I do this?
>
> Let me reword your issue, but my understanding of LaTeX is limited so
> please correct me if I am wrong.
>
> You want to specify your affiliation with the institute command. AFAIU
> the \institute command is declared in the header of a tex file. So I am
> a little confused by your use of properties in org. Shouldn't something
> like this after the "#+NAME:" and "#+AUTHOR:" directives work fine?
>
> #+LaTeX_HEADER: \institute[short name]{My awesome institute}
>
> Hope this helps,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>
>
Re: [O] Specifying \institute[short]{long] in Beamer presentations
Bernd Weiss writes: > Dear all, > > I assume that my first email[1], which I sent yesterday, was not clear > enough to draw any/enough attention. No, it was clear enough but unfortunately most of us do have day jobs to attend to despite the attraction of playing with org and responding to the mailing list! A little patience goes a long ways when it comes to getting help from volunteer efforts like org ;-) (I'm not chastising, by the way -- just re-emphasising the nature of open source and collaborative volunteer based projects.) I have answered your original post to the list a few minutes ago. I hope it helps. -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
[O] [babel] Calling source blocks with arguments
Hi,
Is there a way to call a source-block with (positional) arguments, like
one would do on the command line?
I want to include some shell scripts in a paper and would prefer not
having to introduce some kind of artificial variables.
So I could just write my scripts inline, like
#+srcname: script.sh
#+begin_src sh
#!/bin/sh
echo $0: $@
#+end_src
and demonstrate their output by calling them
#+call: script.sh("arg1", "arg2") :results output
would produce something like
#+results:
: script.sh: arg1 arg2
Can this be done?
PS:
Is there a way to set «:results output» for the whole file?
thanks,
--
Philipp Haselwarter
Re: [O] orgmode and rss
Jude DaShiell writes: > A long-standing friend is looking for a platform he can use to write rss > and publish it. Earlier today I read about plannermode being able to do > this and don't yet have plannermode on my machine but do have orgmode. So > I'm curious if this can be done. He has to learn emacs along with orgmode > but already has a blog in operation. Both of us use screen readers on > Linux and both of us prefer command line environments to g.u.i. if that > makes things any easier. You can blog directly to, for instance, blogger or wordpress from org-mode. Check out the mailing list thread at http://comments.gmane.org/gmane.emacs.orgmode/36173 and other posts to the mailing list in the past year or two! -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
Re: [O] Customizing LaTeX-export, Beamer, \institute, and BEAMER_envargs
Bernd Weiss writes:
> Dear all,
>
> I am preparing a Beamer presentation and I am having some trouble with
> side effects (?) due to my attempt to customize the LaTeX-export. My
> minimum example can be found below.
>
> The default LaTeX-export does not recognise the '\institute'-option (I
> mean, as far as I know). For that reason, I run "(add-to-list
> org-export-latex-classes ...)". Unfortunately, the export-function
> does no longer recognice ":BEAMER_envargs: [plain]" (or
> ":BEAMER_envargs: [shrink=5]")[1].
yes, that is correct. the default entry uses =org-beamer-sectioning=
which is where headings are translated to latex section or frame or
block etc entries *and* where the special beamer properties are
processed. As you have replaced the sectioning section of
=org-export-latex-classes= with your own, you have lost all of that
functionality.
You seem to want to achieve two things:
1. added your macros into the latex preamble, and
2. add the [fragile] option to each frame.
I would suggest you do 1 as you have done but keep org-beamer-sectioning
as the second argument for the org-export-latex-classes entry. To add
[fragile] to each frame, I would recommend, instead, using some
automated form of input, such as a yasnippet snippet like this one
(untested):
--8<---cut here---start->8---
#name : frame
# --
** ${1:frame title}
:PROPERTIES:
:BEAMER_envargs: ${2:[fragile]}
:END:
$0
--8<---cut here---end--->8---
so that typing "frame" followed by TAB would define a new headline,
prompting for the title and possible arguments (with defaults).
HTH,
eric
--
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1
: using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
Re: [O] Re: s-tab not working as intended in kde's konsole
Izzie writes: [...] >> However, one must ask: why use emacs in console mode if you are running >> kde? This does limit what emacs can do. > > Remote editing of files through ssh often (but not always) inside screen is > the > reason. I know about tramp but haven't had time to look into it yet. I have > not > found an equivalent to screen though. Yes, that's a valid reason for sure! I have the opposite in that I use my phone to access my office desktop but I suffer from the same problem: on my phone there is no (easy?) way to send, for instance, M-S- (=org-shiftmetadown=) which I need to insert a new row in a table. Not the easiest command to type directly unfortunately. One of the options to access commands that are bound to keys you cannot use easily is to invoke the emacs menu. You can access the menu even in screen mode through M-` (tmm-menubar). So, for instance, to insert a row in the table, you can type "ESC ` T r i". Although I don't actually have the menu bar shown ever, org has an excellent menu structure which seems to provide access to all the important commands! Mind you, on my phone, accessing backtick is non-trivial, but that's another story. ;-) -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
[O] Re: advice: how to export a list without exporting all entries
Nicolas writes: > Hello, > > Eric S Fraga writes: > >> I would like to move to a system in which all the actions are numbered >> sequentially. At present, they are numbered sequentially within a list >> for each meeting. I would like to have a single list which grows over >> time. However, when I distribute the minutes of the latest meeting, I >> would like to only have those actions which are not yet complete listed >> in the document I circulate. The complication is that I want those >> actions that have actually been done still in the list but not exported. >> >> Is there any way to /comment/ out individual list items (whether bullet >> or enumerated) on export? I export typically to latex but this need not >> be a constraint. Simply putting [ ] versus [X] boxes on the items is not >> satisfactory as the list would be very long if all items were included in >> the export. >> >> Is there some hook that I can intercept that would enable this? Can I >> encapsulate individual list items into latex macros with the status of >> the [ ] or [X] boxes? I am more than happy to write latex code as >> required! Or even, at a push, elisp code... > > I'm not sure to fully understand what you want, but couldn't you > delete-matching-lines toggled check-boxes in a copy of the original > buffer, and export that? > > Regards, Thanks for the suggestion. I think you did understand me and, yes, that would work, but only *if* each list entry were a single line. Unfortunately, I tend to fill my list paragraphs so that each item in the list is often several lines and, in fact, often several paragraphs (especially when it concerns minutes of a meeting and resulting actions). delete-matching-lines would delete the first line of a list entry only. I need to be able to "delete" whole list entries automatically based on their status, whether in a copy or during export. Thanks again, eric -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.50.1 : using Org-mode version 7.5 (release_7.5.113.g9010a.dirty)
[O] Re: FR: broken links and footnote references
Not sure if this thread was clear enough to make it interesting. I am suggesting that when you export a subtree or a region, and you have a link to an anchor (e.g. a link to a <<...>>>), and that link is broken, because the referent is outside of the subtree or region, we can do this: Get the link referent normally (just as we do in the .org file) Append it to a URL provided in a property for the subtree that contains it That way, you can export one subtree as a blog entry, and another subtree as a blog entry, and if links point to the other subtree, they will get exported properly -- as long as you supply the base URL.
Re: [O] Re: unnumbered subsections in latex export
Dear all, I applied the patches too hastily, disregarding some inconsistency they could introduce between exporters -- sorry for that. I fully agree with Nick and Thomas (and others who also agreed): Org's export facilities need some real love and new export features need to be introduced as complete and as consistent accross exporters as possible. I hope we'll make progress on this for 7.6. Here is a list of difficulties: 1. the syntax of the backends vary, and this means that all Org options are not meaningful in all target formats; *Example*: #+XSLT is only meaninful for the Docbook export. The variable `org-export-html-postamble' is only meaningful for the HTML export. Etc. 2. exporters use various methods to export the file (e.g. the HTML exporter goes line by line, the LaTeX exporter parses the file and render each section); *Example*: users often ask why the LaTeX exporter cannot export a headline of level 3 right after a headline of level 1: they ask that because the HTML exporter can do this, while the LaTeX one cannot. And the LaTeX one cannot because parsing an ill-structured Org buffer is tricky for it. 3. exporters are maintained by various people: I know the HTML exporter and the LaTeX one, others know the other exporters, etc. I need your help do deal with these issues. The first thing to do is to have a list of annoying inconsistencies that need to be addressed in priority. The second thing would be to build a table (somewhere on Worg?) with the list of options and the way they are taken care by each exporter. Such a "synoptic view" would help developers know what they can work on, and users know what they have to expect from options. On the long term, it would also help make the documentation clearer about all these aspects. This will at least help with the first difficulty -- and motivate all people working on the exporters to address the second one. The third one can be turned into a *chance*: that of having several people working in the same direction. So, bare with me on this :) PS: Also note that I couldn't be as available as I wanted the 10 last days due to personal problems, but things look better now. -- Bastien
Re: [O] [babel] Variable support for ob-maxima
Hi Eric, · Eric Schulte wrote: > Thomas Holst writes: [... snip ...] > Great, thanks for sharing this patch, I'd very much like to apply this. > Have you seen the instructions for contributing to Org-mode [1]? Any > patch over 10 lines long requires signed FSF copyright attribution > papers. Please let me know if you are able to complete the copyright > assignment, once that is done I will apply this patch. I will look at the FSF papers this evening. I would be really happy to contribute to org-mode and babel. I will send a notice once the papers are signed. >> >> Now I can use the output from one maxima block and make a LaTeX equation >> out of it with one maxima code block and reuse the output and make further >> maipulations with it. I find it dificult to explain what I want to do, >> so here is an example: >> > > The example below like a nice application, you may also want to use > "begin_src latex" blocks to display equations resulting from maxima code > blocks. I will look into this. The example shows my first attempt to accomplish my goal of using maxima as math tool and pretty print the equations with LaTeX code. All within org mode - of course! Best regards ... Thomas
Re: [O] Bug: Recurring items NEVER show up in timeline unaccompanied
Hi everyone, On 22.3.2011, at 21:10, Nick Dokos wrote: > Some more comments and another bug in org-timeline: > > o a repeater always gets reported on its initial date - it only gets reported > on subsequent instances iff it coincides with some other entry that will be > reported on that date. > > o the initial comment of org-timeline says "Only entries with a time > stamp of today or later will be listed." However, in the let*, we have >(let* ((dopast t) > ... > so by default we get past dates as well. > > o [the additional bug] if dopast is set to nil in the let*, then we run the > following code to get rid of past dates: > >(if (not dopast) > ;; Remove past dates from the list of dates. > (setq day-numbers (delq nil (mapcar (lambda(x) > (if (>= x today) x nil)) > day-numbers > > But day-numbers isn't just numbers: it's a list of day numbers > interspersed with gap information: > > (733451 (:omitted . 28) 733479 (:omitted . 5) 733484 (:omitted . 21) 733505 > (:omitted . 15) 733520 ...) > and the mapcar function chokes when it has to deal with a gap argument. > > > Since there is no way to set dopast from the outside, perhaps the thing > to do is to remove both it and the above code (as well as one additional > instance of the variable) and declare that org-timeline will always do > both past and future. Or, given some global option variable, it can be > set to that value, in which case the code above needs to be fixed to > deal with the gaps. > > Also, some stopping point will need to be provided. Right now, that is > the last explicit date in the file, but in the presence of repeaters > (and assuming that org-timeline gets modified to deal with them), that > natural stopping point gets pushed all the way to infinity, so some > other way will need to be provided to stop the enumeration. Dear all, Maybe I can add the following background information to Nick's amazing analysis. - The timeline was the first agenda-like view I implemented, it used to be (many years ago) the only way to see what was coming up. That is why it only listed the future, and included the past when used with e prefix argument (I believe). - Since then the agenda view came along, with vastly better properties for being used as a planning tool for the coming day an d week. It also included the possibility to look at several files, which made the timelines view of a single file look poor. Since then, the timeline has been a more or less orphaned feature, and this is why it does not work well with stuff like repeaters (repeaters where added MUCH later). - So the use-case of the timeline view became slowly redefined as a way to look at the milestones and events of a single project. One consequence was to always include the past. - For historic reasons, the timeline uses the same mechanics as the agenda: Pick a date, find everything that is going on on that date, move on to the next date. Lather, rinse, repeat. However, when looking at a project that may have dates spread over potentially many years, this mechanics is not very practical. First, there will be many empty days where nothing is going on. This will make the view look very boring and will make it hard to find useful dates. Second, constructing the view in this way takes forever because of the inefficient pick-a-day, scan-entire-file-to-see-what-fits-strategy. - To makes things more efficient, the timeline starts by first making a list of relevant days in the project by looking at all explicit dates, and at ranges. Here is where the repeaters go wrong - they should return a whole list of dates where they are important - but they only add one, the starting date. With this list of dates, it knows how to skip ranges of dates where nothing is happening. Solutions for this problem are (these are alternatives) 1. Be satisfied with the way things are, just realize that repeaters only show up on the first date when the event happens for the first time. 2. Use the agenda, restricted to a single file, for a time range you specify. This has the advantage that also diary sexps will work properly - the timeline currently has no way to deal with these. 3. Change the section of the timeline code that produces the list of interesting dates. One strategy could be to first make a list of explicit dates, in order to define an overall range. Then find all repeaters and add dates this repeater targets, restricted to the range of explicit dates in the file. If done like this, you could always put a target date for conclusion of the project into the file, and that far-into-the-future date would define the range of the repeaters automatically. 4. Define a variable that will make the timeline always look at *every* date in the range cov
