I am using Emacs Orgmode 9.1.3 to track habit and I saw a very useful habit template below. However I was not sure what the forward slash / meant in the date.
* NEXT HABIT
[2017-12-07 Thu 10:26]
SCHEDULED: <2017-12-07 Thu .+1d/3d>
:PROPERTIES:
:STYLE: habit
:REPEAT_TO_STATE: NEXT
:END:
I read through the org documentation but there is no mention of the forward slash in setting a repeated task.
There is a reference to some sort of reminder like this:
DEADLINE: <2005-10-01 Sat +1m -3d>.
which will provide a reminder three days in advance of a task due date.
Does anyone know what the forward slash does?
You looked in the wrong section of the documentation: this notation applies to habits where you find:
The TODO may also have minimum and maximum ranges specified by using the syntax ‘.+2d/3d’, which says that you want to do the task at least every three days, but at most every two days.
Related
If I want to export a itemized list from Org to LaTeX, is there a way to set arbitrary itemization? The usual Org plain list, i.e. - item will result in an \begin{itemize} environment, but I would like to set arbitrary itemization. For example, is there any kind of Org list markup that will output this kind of LaTeX list environment?
\begin{itemize}
\item[2013]
This item happened in 2013
\item[2012]
This item happened in 2012
\end{itemize}
Edit:
The problem is that Org is recognising the years as inactive timestamps or footnote references and this is screwing up the LaTeX export. Solution below.
I can't tell whether it's what you're looking for, but
- 2013 :: This happened in 2013
- 2012 :: This happened in 2012
will produce
\begin{description}
\item[2013] This happened in 2013
\item[2012] This happened in 2012
\end{description}
I haven't tried, but according to this WikiBook it seems as though there will be no dot trailing the year.
Following fniessen's suggestion below I found the solution to produce an itemize environment without having the years turn into inactive timestamps or footnote references. The key is to insert or surround the year with spaces, which will be ignored by the TeX conversion.
- [ 2013 ] This item happened in 2013
- [ 2012 ] This item happened in 2012
If there is a more official way to do this I'd like to here it.
The other answers provide great solutions for creating both enumerate and description environments, but it was specifically itemize I was after.
Use something such as:
1. [#2013] This item happened in 2013
2. [#2012] This item happened in 2012
The solution appointed by the org-mode manual is ::, so:
Important actors in this film are:
- Elijah Wood :: He plays Frodo
- Sean Astin :: He plays Sam, Frodo's friend.
by the way, [ text ] didn't work for me.
If as me you don't like the decription style with "- ::" syntax (that produces weird latex export) a workaround is simply to use
- ##latex:[2013]## This item happened in 2013
- ##latex:[2012]## This item happened in 2012
and, more generally,
- ##latex:[yourcustomitem]## blah blah
I use repeating tasks in the org-mode agenda for, for example, a daily checklist of things that need to be done. But if I go on vacation, for example, then all the dates are out of date, in which case I have to either mark them each done over and over in the agenda view, or else manually edit the dates in the actual .org file. Is there a "catch up" function that I just don't know about?
Well, if you use the ++1d or .+1d repeater, you'll just have to ack them once. While, by default, with the +1d repeater, you'll see them all 15x times...
I have a class that meets regularly on Mondays/Wednesdays from 12:00-12:50 and on Thursdays from 16:00-16:50. I'd like to keep all the notes together, because it's all for the same class, but I don't know how I would set up this recurring event.
There is an easy-enough way to define arbitrary date ranges, but nothing I can see for time ranges that would also show up correctly in the agenda. They're also in different rooms, so if it's possible I'd like to add something denoting the room number. If it were just dates (at the same time as well), I would go ahead and just
(and (org-class 2013 1 21 2013 5 9 1) (org-class 2013 1 21 2013 5 9 3))
and it would be fine. Is there a(n org-mode) function to describe times? Is there a way to add notes (like the room number)? I'm not quite aware of how this whole section of org-mode works (although my guess would be that if the sexp evaluates to non-nil, then the event is active).
So, in summary, I'd like a way to be able to assign arbitrary collections of date-time-range objects to org-mode events, ideally with the notes I was talking about.
EDIT
As a secondary (but obviously related) question, what's the sexp way of specifying time?
You can use multiple time-stamps within the same entry.
For example:
C-c.mon 12:00-12:50RET will produce <2013-01-28 Mon 12:00-12:50>. You can then edit it to add a repeater +1w. The final time-stamp looks like <2013-01-28 Mon 12:00-12:50 +1w>.
I don't know how you can manage the class room though.
Wouldn't creating subtrees for the two rooms and then a third subtree for the notes themselves?
For example (see Org-FAQ for details on putting time in the same line. I think adding the time within the <> will add it to the time, but not entirely sure, otherwise add it afterwards and it should still include it within the information.
* Math Class
:PROPERTIES:
:CATEGORY: Math Class
:END:
** Room #1
<%%(and (org-class 2013 1 21 2013 5 9 1) (org-class 2013 1 21 2013 5 9 3)) 12:00-- 12:50>
** Room #2
<%%(org-class 2013 1 21 2013 5 9 4) 16:00--16:50>
** Notes
Just recently, I made some changes to my org configuration as I had been making some changes in my daily work framework. That broke a part of my configuration.
(tags-todo "School"
((org-agenda-skip-fuction '(org-agenda-skip-entry-if 'scheduled))
(org-agenda-overriding-header "School Work for today: ")))
Particularly, agenda entries which are scheduled are not being skipped. A typical such entry is as follows:
** TODO Make weekly test papers for next week, classes 9-12, for Maths, Sci etc.
SCHEDULED: <2010-10-09 Sat +1w>
Earlier after a lot of effort, I had created a regular expression check which used to skip such entries. Of course, org-agenda-skip-entry-if 'scheduled is much better than that.
I know c#, but no lisp as such. Kindly help.
Super-old question, but just in case this helps you or someone else: the code you pasted in has org-agenda-skip-fuction instead of -function. =)
I am trying to have the "Birthday" and "Name" properties of an Org-mode entry added to the agenda automatically:
* John
:PROPERTIES:
:Name: John
:Birthday: (5 4 1900)
:END:
I found a way to add an entry at the correct anniversary date in the agenda by inserting the following line right after the properties:
%%(apply 'diary-anniversary (read (org-entry-get nil "Birthday"))) John
However, using this code, I still have to enter the name manually. Is there a way to have the value of the "Name" property added to the diary text automatically for all entries?
EDIT 1: the example did not work before, now added parantheses around the value of the birthday property
Maybe https://julien.danjou.info/projects/emacs-packages#org-contacts is the solution to your problem. org-contacts is a address book for org-mode.
It is probably better to ask this at the Org mailing list, they are very active, and Carsten Dominik (the creator of org-mode) usually answers posts on this list almost immediately (BTW, this is the main list email.
Perhaps you a taking a path which requires you to write some lisp to get what you want. The org-mode manual gives an example of something similar, but I'm guessing you wanted a simpler format, when it describes the calendar/agenda integration http://www.gnu.org/software/emacs/manual/html_node/org/Weekly_002fdaily-agenda.html
* Birthdays and similar stuff
#+CATEGORY: Holiday
%%(org-calendar-holiday) ; special function for holiday names
#+CATEGORY: Ann
%%(diary-anniversary 14 5 1956) Arthur Dent is %d years old
%%(diary-anniversary 2 10 1869) Mahatma Gandhi would be %d years old
I would think you have other options if you want a custom setup: either a new type of export or dynamic blocks might be used. This may highlight the different use-case of agenda over the diary. The agenda seems more geared towards day to day tasks.