Re: [O] Hiding future tasks in tags-todo agenda view
Neilen, One of my favorite agenda custom commands is the following: ---snipstart--snip-- ((s Startup View ((agenda ((org-agenda-ndays 3) (org-deadline-warning-days 1))) (agenda ((org-agenda-time-grid nil) (org-deadline-warning-days 365) (org-agenda-entry-types (quote (:deadline))) (org-agenda-skip-entry-if (quote scheduled)) (org-agenda-ndays 1) (org-agenda-overriding-header Unscheduled upcoming deadlines:))) (todo (quote(org-agenda-overriding-header Unscheduled No Deadline TODO: )) ---snipend--snip-- (org-agenda-ndays 3) gives me a 3 day calendar for this view (org-deadline-warning-days 1) gives me a 1 day warning for deadlines (you should be able to set it to 0 to get just today). Also, if you set a custom deadline warning on the individual task it overrides the 1 day. I also use a seperate section to show all my unscheduled TODO items down below so they are in a separate area but on the same agenda. If you had a custom command set to 0 and then added cut- (todo (quote(org-agenda-overriding-header Unscheduled No Deadline TODO: ))) -cut- it would give you a second section that has all your unscheduled TODO items at the bottom (at least it does for me in the agenda I have) Hope this helps. On Fri, Oct 14, 2011 at 3:09 PM, Neilen Marais nmar...@gmail.com wrote: Hi, I've recently switched from using tracks (http://getontracks.org/) to org mode for GTD task management. One neat tracks feature that I am struggling to reproduce is the show task from date. If you add a task with no date set, they show up immediately in the context next action lists, but if you have a show from date in the future, it only shows the task from that date onwards. Scheduling timestamps (http://orgmode.org/worg/org-faq.html#sec-16-9) seem like they should do exactly that, but they don't seem to work in my custom org-agenda that I use to show only items with a NEXT todo state and an assigned context. However, it shows all items irrespective of the scheduling setting. (setq org-agenda-custom-commands '( (c Context Next Tasks tags-todo (mapconcat 'car my-org-context-tag-alist |) ((org-agenda-skip-function '(org-agenda-skip-entry-if 'nottodo '(NEXT))) (org-agenda-sorting-strategy '(tag-up)) (org-agenda-overriding-header Context Next Tasks) )) )) How can I make this custom agenda skip items that are scheduled in the future, while also keeping unscheduled tasks? I have also tried adding (org-agenda-entry-types '(:scheduled)) but that did not seem to make any difference.
Re: [O] Can not export to LaTeX anymore
Hi! Well, in the meantime I found the error and a workaround. It resulted from an (require 'org-export-latex) somewhere in my .emacs because I wanted to add some LaTeX export definitions to org-export-latex-classes. The effect was the the very old org-latex.el (v 6.21) from the original Emacs distribution has been loaded and that didn't work with the rest of the 7.7 org-mode distribution. I was thinking, that the new org-mode gets rid of old parts. I changed the (require 'org-export-latex) to (require 'org-latex) and then it worked (because the newest org-latex exports org-latex as well as org-export-latex). Kind regards, Daniel
Re: [O] Hiding future tasks in tags-todo agenda view
On 14.10.2011, at 22:09, Neilen Marais wrote:
Hi,
I've recently switched from using tracks (http://getontracks.org/) to
org mode for GTD task management. One neat tracks feature that I am
struggling to reproduce is the show task from date. If you add a
task with no date set, they show up immediately in the context next
action lists, but if you have a show from date in the future, it
only shows the task from that date onwards.
Scheduling timestamps (http://orgmode.org/worg/org-faq.html#sec-16-9)
seem like they should do exactly that, but they don't seem to work in
my custom org-agenda that I use to show only items with a NEXT todo
state and an assigned context. However, it shows all items
irrespective of the scheduling setting.
(setq org-agenda-custom-commands
'(
(c Context Next Tasks
tags-todo (mapconcat 'car my-org-context-tag-alist |)
((org-agenda-skip-function '(org-agenda-skip-entry-if
'nottodo '(NEXT)))
(org-agenda-sorting-strategy '(tag-up))
(org-agenda-overriding-header Context Next Tasks)
))
))
How can I make this custom agenda skip items that are scheduled in the
future, while also keeping unscheduled tasks? I have also tried adding
(org-agenda-entry-types '(:scheduled))
but that did not seem to make any difference.
Hi Neilen,
this was a pretty good attempt for someone who says he is new to org!
Scheduling normally has the purpose to make an item show up in your daily
agenda on a specified date. But you can use is also to hide items scheduled
in the future from the task list. Here is how:
(setq org-agenda-custom-commands
'(
(c Context Next Tasks
tags-todo
TODO=\NEXT\+SCHEDULED=\\|TODO=\NEXT\+SCHEDULED=\today\
((org-agenda-sorting-strategy '(tag-up))
(org-agenda-overriding-header Context Next Tasks)
You can use a regexp match TODO={^\\(NEXT\\|...\\|...\\)$} to check for several
TODO keywords as once.
Another, more compact possibility that is also more easily extended to your
longer list of tasks in my-org-context-tags-alist is:
(setq org-agenda-custom-commands
'(
(c Context Next Tasks
tags-todo SCHEDULED=\\|SCHEDULED=\today\/NEXT
((org-agenda-sorting-strategy '(tag-up))
(org-agenda-overriding-header Context Next Tasks)
Let me know if I need to further explain why these works - but I
guess you can figure it out?
Cheers
- Carsten
[O] Wish: babel for python3
Hi, I’d love to have babel for python3. My first shot at it would just be ob-python.el with each mention of python replaced by python3, but I hope that there is a more elegant way… Is there a way to get python3 support for Babel into org-mode cleanly? Best wishes, Arne
[O] Export as HTML does not preserve nonstandard entities as TODO signs
Hi, I started using ✔ and ❢ as replacement for DONE und TODO and I realized that they get replaced by an underscore (_) in HTML output. Since I really like using symbols for TODO and DONE¹, I wanted to ask, if this is a bug. Best wishes, Arne ¹: Just compare: * ✔ Sent bug question * ❢ check for response and * DONE Sent bug question * TODO check for response PS: I actually have ✔ on my keyboard, and C-c C-t makes it easy to use any kind of symbol for TODO states which is supported by the font.
[O] Cannot insert a footnote after certain verbatim text?
I am using org to write a document correcting some of my students' more
common LaTeX blunders, and I keep running into places where I am not able to
insert a footnote (Cannot insert a footnote here.). Some of these problems
I am unable to reproduce consistently, but I think it usually occurs when a
paragraph (or list item) contains verbatim or code text with a backslash
(\), and only after the verbatim text. Here is one such example. Create an
.org file with the following three paragraphs (including the two blank
likes):
Blah, blah, blah.
Woof, woof, =\begin{document}=, woof.
Cry, cry, cry.
If you're me, then you can insert a footnote after any word or punctuation
in the first and third paragraphs, and after the first two words and the
first comma in the second paragraph, but nowhere past the second comma in
the second paragraph.
I'm running the latest org (7.7) from the git repository in GNU emacs
23.1.1.
As long as I'm here, I'll mention one more buglet, or maybe it's a
question: how can I get something like =\LaTeX\ = to be formatted
correctly? I'd like the second backslash (and maybe the space as well) to
be visible as verbatim text.
[O] Background color for literal examples in LaTeX export
Hi all, I would like to include some lines in an example block and upon LaTeX export give the block a colored background, analogous to HTML export. For src blocks, this is easy using =listings=, but the lines I want to include are not necessarily source code. By default an example block is exported in a LaTeX =verbatim= environment. There are LaTeX ways of changing the verbatim environment to have a background and colors, but I'm curious if there is a way to do this within org-mode with a flag or different type of block? Another option would be to define a new language for the =src= block, which can then use the =lstset= for listings, but this seems like more work than just adding the LaTeX to renew the =verbatim= environment. Chris
Re: [O] How to get numbered lists (1), (2), … ?
Carsten Dominik carsten.domi...@gmail.com writes: On 14.10.2011, at 13:31, Nicolas Goaziou wrote: [...] I have nothing against (1) as item bullets, as it doesn't interfere with any existing Org syntax. That is not the only criterion. Adding new syntax elements make more ASCII sequences special. The Org markup is a heuristic set of special elements, and there is merrit in keeping it small. We already have more bullets and in particular numbered types - and so far I have not seen a compelling reason to add more. - Carsten I am in the keep it simple school. So long as org allows me to distinguish between numbered and unnumbered itemised lists, I am happy. I actually would prefer less choices than there are currently because I would like to get to my choice more quickly when I do use C-c - to change the type! To me, org is about information and time management, not about formatting. YMMV, of course! To be blunt, I would be happy with - and 1. in org, knowing that I can customise upon export if necessary! I'm not suggesting we go this far, however ;-) -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.7 (release_7.7.381.g05ea)
Re: [O] How to get numbered lists (1), (2), … ?
I'm 100% with Eric, just that I would say - and (1) are enough. On 2011-10-15, at 16:14 , Eric S Fraga wrote: Carsten Dominik carsten.domi...@gmail.com writes: On 14.10.2011, at 13:31, Nicolas Goaziou wrote: [...] I have nothing against (1) as item bullets, as it doesn't interfere with any existing Org syntax. That is not the only criterion. Adding new syntax elements make more ASCII sequences special. The Org markup is a heuristic set of special elements, and there is merrit in keeping it small. We already have more bullets and in particular numbered types - and so far I have not seen a compelling reason to add more. - Carsten I am in the keep it simple school. So long as org allows me to distinguish between numbered and unnumbered itemised lists, I am happy. I actually would prefer less choices than there are currently because I would like to get to my choice more quickly when I do use C-c - to change the type! To me, org is about information and time management, not about formatting. YMMV, of course! To be blunt, I would be happy with - and 1. in org, knowing that I can customise upon export if necessary! I'm not suggesting we go this far, however ;-) -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.7 (release_7.7.381.g05ea) ETH Zurich Dr. Marius Hofert RiskLab, Department of Mathematics HG E 65.2 Rämistrasse 101 8092 Zurich Switzerland Phone +41 44 632 2423 marius.hof...@math.ethz.ch http://www.math.ethz.ch/~hofertj
Re: [O] How to get numbered lists (1), (2), … ?
Eric S Fraga e.fr...@ucl.ac.uk writes: I am in the keep it simple school. So long as org allows me to distinguish between numbered and unnumbered itemised lists, I am happy. I actually would prefer less choices than there are currently because I would like to get to my choice more quickly when I do use C-c - to change the type! You can switch (a little faster) with S-right and S-left arrows anywhere on the list item. HTH, Bernt
Re: [O] How to get numbered lists (1), (2), … ?
On 15.10.2011, at 16:14, Eric S Fraga wrote: Carsten Dominik carsten.domi...@gmail.com writes: On 14.10.2011, at 13:31, Nicolas Goaziou wrote: [...] I have nothing against (1) as item bullets, as it doesn't interfere with any existing Org syntax. That is not the only criterion. Adding new syntax elements make more ASCII sequences special. The Org markup is a heuristic set of special elements, and there is merrit in keeping it small. We already have more bullets and in particular numbered types - and so far I have not seen a compelling reason to add more. - Carsten I am in the keep it simple school. So long as org allows me to distinguish between numbered and unnumbered itemised lists, I am happy. I actually would prefer less choices than there are currently because I would like to get to my choice more quickly when I do use C-c - to change the type! To me, org is about information and time management, not about formatting. YMMV, of course! To be blunt, I would be happy with - and 1. in org, knowing that I can customise upon export if necessary! I'm not suggesting we go this far, however ;-) Since backward compatibility is necessary, this counts as a vote for a customizable sequence, as proposed by Nicolas, do I see this right? So maybe this *is* a good idea, but I would be agains adding new list types. - Carsten -- : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1 : using Org-mode version 7.7 (release_7.7.381.g05ea)
[O] Invisible Blocked Tasks and Tag Searches
Hello! I just spent nearly two hours figuring out why (setq org-stuck-projects '(/PROJECT nil nil (SCHEDULED\\|DEADLINE\\): )) wouldn't work for me. It would only display some projects. In fact, it would only show projects without any subentries. Turns out, that is because I have `org-agenda-dim-blocked-tasks' set to 'invisible. Doesn't seem right to me. Manual and docstring give the impression, the variable would only affect the agenda (as in »C-c a a«). Admittedly, it makes also sense for the todo list. But not for tag searches or stuck projects. By the way, I solved the problem by advising `org-agenda-list-stuck-projects' and `org-tags-view'. Is there an easier way to override variables for a specific agenda command? -- Florian Beck
Re: [O] Wish: babel for python3
Hi Arne, I think you can simply add the following to your configuration to use python3 as your python executable. (setq org-babel-python-command python3) Best -- Eric Arne Babenhauserheide arne_...@web.de writes: Hi, I’d love to have babel for python3. My first shot at it would just be ob-python.el with each mention of python replaced by python3, but I hope that there is a more elegant way… Is there a way to get python3 support for Babel into org-mode cleanly? Best wishes, Arne -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Wish: babel for python3
Hi Eric, Can I then still use babel for python 2.x? I need it for both, because I have python3 and python2 projects. Best wishes, Arne Am Samstag, 15. Oktober 2011, 12:36:52 schrieb Eric Schulte: Hi Arne, I think you can simply add the following to your configuration to use python3 as your python executable. (setq org-babel-python-command python3) Best -- Eric Arne Babenhauserheide arne_...@web.de writes: Hi, I’d love to have babel for python3. My first shot at it would just be ob-python.el with each mention of python replaced by python3, but I hope that there is a more elegant way… Is there a way to get python3 support for Babel into org-mode cleanly? Best wishes, Arne -- Ein Würfel System - einfach saubere Regeln: - http://1w6.org signature.asc Description: This is a digitally signed message part.
Re: [O] Wish: babel for python3
Arne Babenhauserheide arne_...@web.de writes: Hi Eric, Can I then still use babel for python 2.x? I need it for both, because I have python3 and python2 projects. Best wishes, Arne Aloha Arne, If your projects are in different files, then you should be able to use file variables: http://www.gnu.org/s/libtool/manual/emacs/Specifying-File-Variables.html#Specifying-File-Variables. Something like: -*- org-babel-python-command: python3 hth, Tom Am Samstag, 15. Oktober 2011, 12:36:52 schrieb Eric Schulte: Hi Arne, I think you can simply add the following to your configuration to use python3 as your python executable. (setq org-babel-python-command python3) Best -- Eric Arne Babenhauserheide arne_...@web.de writes: Hi, I’d love to have babel for python3. My first shot at it would just be ob-python.el with each mention of python replaced by python3, but I hope that there is a more elegant way… Is there a way to get python3 support for Babel into org-mode cleanly? Best wishes, Arne -- Ein Würfel System - einfach saubere Regeln: - http://1w6.org -- Thomas S. Dye http://www.tsdye.com
[O] [DEV] New package org-refer-by-number
Hello All ! I would like to present the new package org-refer-by-number. The package allows to refer to things outside of Org, that cannot be linked to directly. An example would be a piece of paper, you get handed over. Within Org you write something about it and want to refer to it in an unambiguous way. A common solution would be to simply write a unique number on this document (e.g. 277) and to use this number within your notes in Org. Through this reference number 277 you can later easily make a connection between your Org-notes and the piece of paper. This use case and others are supported by org-refer-by-number. The package makes it easy to keep a table of such reference numbers (277, 278, ...) and allows you to look up or search those numbers later on. Citing the head of its documentation (which you may also find in the attached source file): ;; Purpose: ;; ;; Refer to things by number, when direct links are not possible. This is done by ;; keeping a table with increasing numbers in the first column and a timestamp in the ;; second. ;; ;; These numbers may then be used to refer to things outside of Org (e.g. you may write ;; them on a piece of paper or use them as part of a directory name). Within Org you may ;; then refer to these things by their number (e.g. R277). ;; ;; ;; Setup: ;; ;; (require 'org-refer-by-number) ;; (setq org-refer-by-number-id 7f480c3e-312f-4b9b-b833-6a7a253d1404) ;; (global-set-key (kbd C-c C-x r) 'org-refer-by-number) ;; ;; Further reading: ;; ;; Setup: See the variable `org-refer-by-number-id' ;; Usage: See the function `org-refer-by-number' Hope, you will find it useful. with kind regards, Marc-Oliver Ihm ;;; org-refer-by-number.el --- Refer by number, where linking is not possible ;; Copyright (C) 2011 ;; Free Software Foundation, Inc. ;; Author: Marc-Oliver Ihm ;; Keywords: Org-mode, references ;; Version: 0.99 ;;; License: ;; This program is free software; you can redistribute it and/or modify ;; it under the terms of the GNU General Public License as published by ;; the Free Software Foundation; either version 3, or (at your option) ;; any later version. ;; ;; This program is distributed in the hope that it will be useful, ;; but WITHOUT ANY WARRANTY; without even the implied warranty of ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the ;; GNU General Public License for more details. ;; ;; You should have received a copy of the GNU General Public License ;; along with GNU Emacs; see the file COPYING. If not, write to the ;; Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, ;; Boston, MA 02110-1301, USA. ;;; Commentary: ;; Purpose: ;; ;; Refer to things by number, when direct links are not possible. This is done by ;; keeping a table with increasing numbers in the first column and a timestamp in the ;; second. ;; ;; These numbers may then be used to refer to things outside of Org (e.g. you may write ;; them on a piece of paper or use them as part of a directory name). Within Org you may ;; then refer to these things by their number (e.g. R277). ;; ;; ;; Setup: ;; ;; (require 'org-refer-by-number) ;; (setq org-refer-by-number-id 7f480c3e-312f-4b9b-b833-6a7a253d1404) ;; (global-set-key (kbd C-c C-x r) 'org-refer-by-number) ;; ;; Further reading: ;; ;; Setup: See the variable `org-refer-by-number-id' ;; Usage: See the function `org-refer-by-number' ;; ;;; Code: (require 'org-table) (defvar org-refer-by-number-id nil Id of the node, that contains the table with reference numbers. Read below on how to set up things. See the documentation of `org-refer-by-number' for normal usage after setup. To create the Org-mode structure for `org-refer-by-number', you need to: - Create an Org-mode node, anywhere, any level. - Get or create the Org-mode id of this node with `org-id-get-create'. - Store this Id within `org-refer-by-number-id'; within your .emacs you may have a line like this: (setq org-refer-by-number-id \7f480c3e-312f-4b9b-b833-6a7a253d1404\) your id, of course, will be different. The easiest way to get your id, is to copy it from the property drawer of your reference node. - Within your node: Add a table, that has at least two columns: a number and a timstamp. - Add one initial row to your table. As an Example, your node may look like this: *** My node for org-refer-by-number :PROPERTIES: :ID: 7f480c3e-312f-4b9b-b833-6a7a253d1404 :END: | Number | Date| Commentary | |+-+-| | R277 | [2011-09-03 Sa] | My first number | Now you may invoke `org-refer-by-number' to create a new reference number. For convenience, you might like to bind it to a key like this: (global-set-key (kbd \C-c C-x r\) 'org-refer-by-number) So, putting it all together, your setup may look like this: (require 'org-refer-by-number) (setq org-refer-by-number-id \7f480c3e-312f-4b9b-b833-6a7a253d1404\)
Re: [O] Wish: babel for python3
Hi Tom, Am Samstag, 15. Oktober 2011, 10:09:24 schrieb Thomas S. Dye: Arne Babenhauserheide arne_...@web.de writes: Is there a way to get python3 support for Babel into org-mode cleanly? If your projects are in different files, then you should be able to use file variables: http://www.gnu.org/s/libtool/manual/emacs/Specifying-File-Variables.html#Spe cifying-File-Variables. Something like: -*- org-babel-python-command: python3 It works! Many thanks (this is damn cool!) # -*- org-babel-python-command: python3; -*- Best wishes, Arne signature.asc Description: This is a digitally signed message part.
