This is probably documented somewhere but I was surprised that I
needed to add some white space in order to get special blocks
recognized as such.
Here is a simple example:
#+Options: num:nil toc:nil
#+TITLE:
#+AUTHOR:
#+BEGIN_CENTER
this is not handled correctly
#+END_CENTER
#+BEGIN_CENTER
bu
Hi John, almost solves the problem, the catch is entries like:
** Norton my office <2015-03-11 Wed 10:00 +1w>
The date range searches in either the sparse tree or the tag-property
match searches don't seem to calculate out repeating dates ... fair
enough that's probably quite an overhead. I'll loo
I keep my diary, action items, scheduled tasks etc in a single
org-mode file. It contains things like:
** Norton my office <2015-03-11 Wed 10:00 +1w>
** TODO power bill:home:
DEADLINE: <2015-12-29 Tue>
** TODO review business manager PD
S
In reality probably an embarrassing emacs-lisp error on my part.
I'm trying to make a capture template for turning the very frequent
invitations I get in .ics format (I think) into org agenda items.
The basis is the ical2org awk script maintained by Eric Fraga.
My template is defined as follows:
(
I am working with the accessibility system emacspeak to improve
eyes-free access to org-mode tables. Most of this can be done outside
the org-mode tree by advising existing functions but I've run into a
need for a new function. I need org-table-previous-row analogous to
org-table-next-row. Below is
I'm moving from using emacs-w3 to eww as my text-mode browser within
emacs. org-mode doesn't seem to integrate eww very well yet (e.g.
org-store-link). Most of the required changes seem within my elisp
capability so I'll try to add them ... provided noone else has done
it. Please let me know if so