Recommendation: use something like GIT (or one of the other fine source control
systems out there) to checkpoint your work, and save the history of your org
files. It can even be set up in emacs to periodically save all org files and
check in a snapshot.
HTH,
Brian
_
d? Will this
behavior be stable in the future?
Brian
- Original Message -
From: MidLifeXis at PerlMonks
To: Eric Schulte
Cc: emacs-orgmode
Sent: Friday, July 1, 2011 3:40 PM
Subject: Re: [O] Regression bug in tangle/weave
I am still getting prompted with the 'Evaluate this tex
n two weeks ago. I will refresh my org-mode setup over
the weekend and see if that takes care of it.
Brian
- Original Message -
From: Eric Schulte
To: MidLifeXis at PerlMonks
Cc: emacs-orgmode
Sent: Friday, July 1, 2011 2:14 PM
Subject: Re: [O] Regression bug in tangle/weave
-
From: Eric Schulte
To: MidLifeXis at PerlMonks
Cc: emacs-orgmode
Sent: Thursday, June 30, 2011 1:30 PM
Subject: Re: [O] Regression bug in tangle/weave
Hi,
Indeed this example below no longer works, however I believe the new
behavior is both desired and permanent. I'll explain and in
It appears that there may be a regression problem with the current tangle/weave
process. I used to be able to have a noweb section for the name of the file,
another for the version of the file, and then have an autogenerated header
section that included those two pieces of information on a sing
#+BEGIN: clocktable :block today :scope agenda :maxlevel 4 :link 2
#+END: clocktable
You can also use agenda-with-archives for the scope if needed.
- Original Message
From: Robert Inder
To: Puneeth Chaganti
Cc: emacs-orgmode@gnu.org
Sent: Tue, April 19, 2011 10:06:12 AM
Subject: Re:
This is something I would like to see adopted by the org community as well.
One
of my main reasons is to allow other languages to be able to at least, given
the
proper configuration information (for TODO keywords, etc), to be able to deal
with org files. I am not quite sure where the lines s
As a heavy Perl user, writing /automated/ tests is a large part of my dev work.
I would suggest / plea / encourage that whatever framework is used can be
automated. If it cannot be run as part of an automated process it is not going
to be run. Also consider a set of testing platforms (emacs ve
I have seen this happen when I have largish files with tables. I also have a
file
setting of:
#+begin_src org
#+STARTUP: align
#+end_src
which turns on automatic alignment of things recognized as table-like. If I
remove
this startup directive, things tend to run more smoothly.
I have not
> * Convert iCalendar recurrences to org recurrences[2]
>[2] And I'm quite sure it can't be done because orgmode has no concept
> of a recurrence end like iCalendar does.
Just as a possibility, what about using the diary syntax for dates in this
case? I have successfully done repeating tasks f
Hello,
org-read-prop treats strings beginning with digits as numbers.
contrib/lisp/org-collector.el: (line 124ish:
http://repo.or.cz/w/org-mode.git/blob/5f77fd6a81a4241ce5a8e346acb9df089d65b462:/contrib/lisp/org-collector.el#l124)
(org-read-prop "123abc-def543") returns 123, should return "1
11 matches
Mail list logo
