Nikola supports org-mode last I checked though?
I use Nikola, and find the documentation frustratingly incomplete, but not so
frustrating as to change :)
Jeff
--
"The man who does not read good books has no advantage over
the man who cannot read them."
-- not Mark Twain, maybe a southen
On Tue, Apr 21, 2015 at 10:13:53AM +0200, Michael Brand wrote:
Hi Jeffrey
On Mon, Apr 20, 2015 at 3:35 PM, Jeffrey Brent McBeth mcb...@broggs.org
wrote:
I'm looking for a way to reference a row or column on both the left
side and right side of a table formula that is easily manipulable
I'm looking for a way to reference a row or column on both the left side and
right side of a table formula that is easily manipulable.
At first, I thought the hline references would work for me @I..@II, except they
cannot be used on the left side of an equation. I hoped that maybe named
On Mon, Apr 20, 2015 at 09:35:28AM -0400, Jeffrey Brent McBeth wrote:
I'm looking for a way to reference a row or column on both the left side and
right side of a table formula that is easily manipulable.
At first, I thought the hline references would work for me @I..@II, except
On Tue, Dec 09, 2014 at 10:36:52AM +0100, Nicolas Goaziou wrote:
Hello,
Jeffrey Brent McBeth mcb...@broggs.org writes:
I have a python function that can take a stripped down org file and
places an active date after each #block# (or inactive after
#[block]#), that I hacked up today
From time to time (each time I delve into using org-mode for deadlines before
my habits fall apart), I find the desire to have some form of relative
deadlines. By this I mean, that there are often sequences of tasks that I
know the time required to complete and when things are due. These
I have not been able to find a way to cache the results of a tangle.
I typically have a date+tree with lots of code snippets for ledger. I'm
giving an example code snippet below
* 2013 :noexport:
** 2013-05 May
*** 2013-05-23 Thursday
#+name: foo
#+begin_src ledger
2013-05-23 * Silly Stuff
On Fri, Mar 01, 2013 at 01:11:59PM +, Eric S Fraga wrote:
Harum Budi harumb...@gmail.com writes:
I was not being clear at all, sorry. Let me rephrase, but bear with me as
English is my secondary language.
That's fine!
I think I understand what you want. My view would be to avoid
On Mon, Feb 25, 2013 at 10:48:16AM +0100, Bastien wrote:
Hi Tim,
Tim Burt tcb...@rochester.rr.com writes:
* lisp/org-datetree.el (org-datetree-find-year-create):
Include regexp for tags. Syntax was taken directly
from org-todo-line-tags-regexp in org.el.
Applied, thanks
On Tue, Feb 19, 2013 at 07:25:29AM -0500, Jeffrey Brent McBeth wrote:
I'm trying to capture into a datetree using org-capture, but if my tree has a
tag on it (in particular noexport), then it creates a new datetree instead of
using the one I have.
I have verified that this still occurs under
I'm trying to capture into a datetree using org-capture, but if my tree has a
tag on it (in particular noexport), then it creates a new datetree instead of
using the one I have.
Example .emacs:
(global-set-key \C-cc 'org-capture)
(setq org-capture-templates
'((t Test plain (file+datetree
11 matches
Mail list logo
