[Orgmode] Why can't use Chinese folder while publishing projects?
While I am publishing my projects under Windows, the target folder is a path with Chinese name. While I use M-x org-publish-current-project, Emacs will prompt me a error message like following Saving file e:/PixCoo/Jackfruit/02工作区域/01计算ç»/01计算组/林绪è/01计算组/林绪虹/ÏîÄ¿É걨/¹ãÖÝ¿ª·¢ÇøÁì¾üÈ˲ÅÉ걨.html... basic-save-buffer-2: e:/PixCoo/Jackfruit/02工作区域/01计算ç»/01计算组/林绪è/01计算组/林绪虹/ÏîÄ¿É걨/: no such directory I think it is very strange. If I publish my org project to a path without Chinese name, then it is OK. Why? Any solutions? Water Lin -- Water Lin's notes and pencils: http://en.waterlin.org Email: water...@ymail.com ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Question about beamer export
Beamer export offers BEAMER_HEADER_EXTRA as an option. Question: how does this differ from LATEX_HEADER_EXTRA? Why is it necessary? thanks, r ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [ANN] Exporter for taskjuggler
On Jun 8, 2010, at 4:03 PM, Christian Egli wrote: Christian Egli christian.e...@sbszh.ch writes: In org-export-as-taskjuggler-and-open: org-taskjuggler.el:330:6:Warning: start-process-shell-command called with 4 arguments, but accepts only 3 This I cannot reproduce using the command command you gave. Is this maybe only a problem in newer Emacs versions? I'm using Emacs 23.1.1 Digging some more I found the following in http://www.gnu.org/software/emacs/NEWS.23.2: *** start-process-shell-command and start-file-process-shell-command now only take a single `command' argument. i.e. Emacs 23.2 has a different api for start-process-shell-command. I'm not quite sure how to deal with this. Should I add a wrapper function in org-compat (say org-start-process-shell-command) that checks for emacs version 23.2 and calls start-process-shell-command accordingly? One possibility is to check for versions. Better is maybe to do it like this (condition-case nil (org-no-warnings (start-process-shell-command with four different args)) (error (start-process-shell-command with three args)) Thill try one version, and if that given an error, try the other one. To get rid of the compiler warning, wrap the call into org-no-warnings. - Carsten Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Timestamp format questions
On Jun 8, 2010, at 11:13 AM, Joost Kremers wrote: On Mon, Jun 07, 2010 at 02:40:30PM -0400, Matt Lundin wrote: You can use diary sexps to schedule more complex appointments. , (info (org) Timestamps) | DIARY-STYLE SEXP ENTRIES | For more complex date specifications, Org mode supports using the | special sexp diary entries implemented in the Emacs calendar/ diary | package. For example | | * The nerd meeting on every 2nd Thursday of the month | %%(diary-float t 4 2) ` See also the following FAQ entry: http://orgmode.org/worg/org-faq.php#diary-sexp-in-org-files Thanks! It seems, though, that this is a very new function, Aquamacs' Org-mode doesn't contain it... I guess I'll have to find out how to update the Org-mode that comes with Aquamacs... The function org-diary-class nicely covers the scenario above: --8---cut here---start-8--- * 12:00-14:00 Weekly class %%(org-diary-class 4 8 2010 7 8 2010 4) --8---cut here---end---8--- http://orgmode.org/worg/org-faq.php#org-diary-class Is it still possible to schedule the time of the event as well? It is already there, 12-14! (I'm a bit surprised, though, that the format is `Month Day Year', when normally Org-mode uses `Year Day Month'... ;-) I hate this as well, but the decision was to be consistent within sexp commands. Calendar date format applied to all other sexp commands from the diary Sometimes you have to make difficult choices :-) - Carsten Also, is there a way to say that a certain event that occurs every week does not occur on one specific date? For example, I teach a class every Thursday, but the Thu. 13th of May was Ascension Day, so the class was cancelled. I would like the event to not show up on such days. --8---cut here---start-8--- * 12:00-14:00 Weekly class %%(org-diary-class 4 8 2010 7 8 2010 4 19) ;; iso number of the week to skip --8---cut here---end---8--- Great, thanks! Joost -- Joost Kremers Life has its moments ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Removing (modify-syntax-entry ?# )
Hi Leo, thanks for this. I am off for a one-week vacation now - I will look at this patch when I com back. - Carsten On Jun 7, 2010, at 1:12 PM, Leo wrote: Hello Carsten, Setting a comment starter without a corresponding comment ender is problematic and the # creeps in mysteriously under auto-fill. For example, in my current running emacs, this happens almost certainly in all org files that has # in their header. The only (temporary) solution seems to reboot emacs (which is painful and disruptive). If you try eval (forward-comment 1) at the beginning of an org file that has some #+... it will move to the end of file (the whole file is regarded as one single comment). So when auto-fill a long text, it will find the common prefix to be #. In addition, I don't think org mode has clear comment syntax or ideas on what to do with it. I can't see any gain from (modify-syntax-entry ?# ) so I am proposing removing it entirely and get rid of this mysterious and annoying bug once and for all. The attached patch may (though I think it is quite safe) cause some bugs but those will be fixable unlike the one mentioned above. Best wishes, Leo diff --git a/lisp/org/org.el b/lisp/org/org.el index aae49fa..bb36ed8 100644 --- a/lisp/org/org.el +++ b/lisp/org/org.el @@ -4208,7 +4208,6 @@ The following commands are available: (org-set-tag-faces 'org-tag-faces org-tag-faces)) ;; Calc embedded (org-set-local 'calc-embedded-open-mode # ) - (modify-syntax-entry ?# ) (modify-syntax-entry ?@ w) (if org-startup-truncated (setq truncate-lines t)) (org-set-local 'font-lock-unfontify-region-function @@ -4237,7 +4236,7 @@ The following commands are available: 'org-block-todo-from-checkboxes)) ;; Comment characters -; (org-set-local 'comment-start #) ;; FIXME: this breaks wrapping + (org-set-local 'comment-start #) (org-set-local 'comment-padding ) ;; Align options lines -- CCL-USER (if you fail to plan (plan to fail)) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Question about beamer export
On Jun 8, 2010, at 4:51 PM, Robert Goldman wrote: Beamer export offers BEAMER_HEADER_EXTRA as an option. Question: how does this differ from LATEX_HEADER_EXTRA? Why is it necessary? Because you might want to export the file as a normal LaTeX file instead of a BEAMER presentation. Greetings - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [ANN] Exporter for taskjuggler
On 2010-06-08 14:30 +0100, Christian Egli wrote: In org-taskjuggler-close-maybe: org-taskjuggler.el:633:13:Warning: reference to free variable `old- level' org-taskjuggler.el:635:25:Warning: assignment to free variable `old- level' I just pushed a patch to the taskjuggler-export branch that should fix this. I suppose old-level is a let-bound dynamic variable. I have found code giving a seemingly global variable name to such variables confusing at times. Would be better just make it global or insert a form at the beginning of the body of those functions like this: (declare (special dynvar1 dynvar2 ...)) I usually use the latter approach. Cheers. Leo -- CCL-USER (if you fail to plan (plan to fail)) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [babel] grid-based R graphical output with :results value
Hello,
This is an FYI for those using org-babel-R with grid-based graphical
systems.
The documentation for org-babel-R says, If a :file filename.ext header
arg is provided to an R block, then graphical output from the source
block is captured on disk, and the output of the source block is a link
to the resulting file.
This is true for traditional R graphics, but needs a modifier for
grid-based R graphics, e.g., the lattice and ggplot2 packages.
The graphics functions from lattice and ggplot2 return objects that must
be explicitly printed to see them, using the print function. This
happens automatically when run interactively, e.g. :session, but when
called inside another function, it does not. The way :results value is
defined to operate, my device and ggplot2 function calls are wrapped in
a 'main' function, and unless I specifically print the object, no output
is produced.
Another solution is to use :results output in those source headers that
produce graphical output from these packages.
I believe the following org-mode file summarizes the different ways of
getting this working.
= org-mode code begins ==
* Note that my .Rprofile loads the lattice package, i.e., library(lattice)
* does /not/ produce a file
#+begin_src R :file 1.png :results value
xyplot(1:10 ~ 1:10)
#+end_src
* does produce a file, by printing object
#+begin_src R :file 2.png :results value
print(xyplot(1:10 ~ 1:10))
#+end_src
* does produce a file, by using :results output
#+begin_src R :file 3.png :results output
xyplot(1:10 ~ 1:10)
#+end_src
* does produce a file, by evaluating in :session
#+begin_src R :file 4.png :session
xyplot(1:10 ~ 1:10)
#+end_src
= end org-mode code
The following R code shows something potentially interesting
=== begin R code ==
## this produces a graphic when run with R CMD BATCH
myfun - function() {
xyplot(1:10 ~ 1:10)
}
png(with-function-wrapper-outside.png)
myfun()
dev.off()
## this does not produce a graphic with R CMD BATCH
myfun - function() {
png(with-function-wrapper-inside.png)
xyplot(1:10 ~ 1:10)
dev.off()
}
myfun()
== End R code =
In effect, :results value is doing the latter of the two things in the R
code above. If the process were reversed, i.e., the 'main' function
call was wrapped in the graphics function, as in example 1 above, I
believe it would work. Of course, this isn't how it is currently
implemented, and may introduce other complexities. There are also
solutions as I've posted above.
--Erik
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Meta-grouping properties?
Hi Juri Sorry for answering so late. I have been away from the PC for a while. Juri Krivov jkri...@gmail.com writes: I dont' think this can be done yet. But I am interested in this idea. How do you hope to define groups? In variable or in buffer with special group syntax? Should every search matching for a name alwasy automatically always include groups, or do you think there should be explicit call like +groups(John) in tags query? I want to lear more lisp, so maybe I will try my hand on his idea. Learning always goes better with project at hand. For my purpose, groups would mainly consist of teams, i.e. real people's names. Such teams could come into existence, vanish and change quite frequently. So it would be best, not to always define them in a complex Lisp expression in .emacs. I could think of buffer specific definitions as one of the most effective possibilities: #+METAGROUPS: (PR-Team(John Mary Sven)) (Website-Taskforce(Tom Fred Mary)) I think John's group(s) should always be matched when John is searched for, similar to tag inheritance. Thanks for trying (I wish I could) Sven ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Timestamp format questions
On Tue, Jun 08, 2010 at 06:32:46PM +0200, Carsten Dominik wrote: On Jun 8, 2010, at 11:13 AM, Joost Kremers wrote: On Mon, Jun 07, 2010 at 02:40:30PM -0400, Matt Lundin wrote: The function org-diary-class nicely covers the scenario above: --8---cut here---start-8--- * 12:00-14:00 Weekly class %%(org-diary-class 4 8 2010 7 8 2010 4) --8---cut here---end---8--- http://orgmode.org/worg/org-faq.php#org-diary-class Is it still possible to schedule the time of the event as well? It is already there, 12-14! Oh, cool! I didn't know the time in the header is also added in the agenda view. Now that I've actually tried it, it works beautifully. :-) (I'm a bit surprised, though, that the format is `Month Day Year', when normally Org-mode uses `Year Day Month'... ;-) Year Month Day, of course... ;-) I hate this as well, but the decision was to be consistent within sexp commands. Calendar date format applied to all other sexp commands from the diary Sometimes you have to make difficult choices :-) Yup, life's that way. Thanks for your reply. -- Joost Kremers Life has its moments ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Date Prompt Bug (or Anomoly)
Carsten, When I tried this last Saturday, I was reluctant to reply since the git server appeared to be down and your message made me think I did not have the latest git version. I tried it again today, and still no joy. I am using org-mode version 6.36a on emacs 23.1 on ubuntu. The latest entry in the Changelog file is , | 2010-06-08 Christian Egli christian.e...@sbszh.ch | | * org-taskjuggler.el (org-export-taskjuggler-old-level): | define local variable to avoid compiler warning. ` The following is straight from an org file: , | Attempted on: 2010-06-08 Tue. | Entering 3/21: 2021-07-03 Sat. | Entering 7/21: 2021-07-07 Wed. ` I assume that the fix would be in the function org-read-date-analyze, but I see no recent Changelog entries mentioning it. Is it possible this got lost while the git server was down? Regards, Dan Carsten On Jun 5, 2010, at 7:43 PM, Daniel E. Doherty wrote: Carsten, I pulled the latest git, and it looks like 3/21 and 5/21 work as expected. But when I put in 7/21, a date in the near future, it is interpreting it a 2021-07-21 rather than the 2010-07-21 that one would expect. Carsten I cannot reproduce this. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] image link inconsistency in org-mode 6.36c
Hi, I have observed an inconsistency with handling image links in org-mode 6.36c, in particular with the caption-option. Here is a minimal org-file to demonstrate my point: file:image1.png #+CAPTION: My Caption1. file:image1.png #+CAPTION: My Caption2. [[file:image1.png]] If displayed in org-mode, the image links all look the same. When exporting to HTML, the first image is rendered as expected, the second instance will be ignored and the third instance is displayed with a (combined!) caption text of My Caption1. My Caption2. Using org-toggle-inline-images, only the last instances will yield an image in Emacs. If one deletes the last line, org-toggle-inline-images comments No inline images to display. The problem came up today, when we added a caption in an older org-mode file which used the simple file:-syntax (no square brackets): the previously working image vanished and the caption text was found many paragraphs later in the next image caption (and only spotted by coincidence). This is potentially dangerous behaviour. As a consequence, we will change all our image links to the [[file:...]] syntax which will solve the problem for us. However, I would suggest that the simple file:-syntax should no longer be supported, except when explicitly enabled by a new flag (an option which might be desirable for backward compatibility). Or is there some hidden benefit in the file:-syntax other than being marginally shorter? Warm regards, Stefan -- Dr. Stefan Vollmar, Dipl.-Phys. Head of IT group Max-Planck-Institut für neurologische Forschung Gleuelerstr. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 Email: voll...@nf.mpg.de http://www.nf.mpg.de smime.p7s Description: S/MIME cryptographic signature ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Date Prompt Bug (or Anomoly)
Daniel E. Doherty ded-...@ddoherty.net wrote: Carsten, When I tried this last Saturday, I was reluctant to reply since the git server appeared to be down and your message made me think I did not have the latest git version. I tried it again today, and still no joy. I am using org-mode version 6.36a on emacs 23.1 on ubuntu. The latest entry in the Changelog file is , | 2010-06-08 Christian Egli christian.e...@sbszh.ch | | * org-taskjuggler.el (org-export-taskjuggler-old-level): | define local variable to avoid compiler warning. ` The following is straight from an org file: , | Attempted on: 2010-06-08 Tue. | Entering 3/21: 2021-07-03 Sat. | Entering 7/21: 2021-07-07 Wed. ` I assume that the fix would be in the function org-read-date-analyze, but I see no recent Changelog entries mentioning it. Is it possible this got lost while the git server was down? No, it is fixed by the following commit, but 6.36a is too old to include it. Either you did not get the updates you thought you did, or you did not remake your org, or you did not reload the newly made org. Try git show 420dd96768262cb15c8bcf4fa6386361e0327add in your git repository to see whether you have the update. If you don't, pull again. If you do have it, do make clean; make and in emacs M-x org-reload Then M-x org-version should say something like: Org-mode version 6.36trans (release_6.36.155.g420d) HTH, Nick --- commit 420dd96768262cb15c8bcf4fa6386361e0327add Author: Carsten Dominik carsten.domi...@gmail.com Date: Fri Jun 4 12:29:31 2010 +0200 Fix the date prompt for american-style dates * lisp/org.el (org-read-date-analyze): Fix regular expression for matching american dates Daniel E. Doherty writes: In playing around with the date prompt (C-.), I ran across the following puzzling behavior from rather simple inputs. I entered the following on June 1, 2010. Here is a date entered as 3/15: 2011-03-15 Tue. It interpreted it as the upcoming March 15 as expected. But here is a date entered as 5/21: 2021-06-05 Sat. Note how it interpreted the 21 as the year 2021, not at all what I expected from the documentation or the analogous 3/15 example. Maybe there is some underlying logic here that I'm not getting. Perhaps it has to do with how 2-digit years are interpreted? What's going on here? I am using org-version 6.36trans on emacs 23.1. What was going on here is that the regular expression for matching american-style dates was wrong. It was looking for month numbers in the second field and day numbers in the first field - wrong, of course. diff --git a/lisp/org.el b/lisp/org.el index 64044b4..48fd215 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -13942,10 +13942,15 @@ The prompt will suggest to enter an ISO date, but you can also enter anything which will at least partially be understood by `parse-time-string'. Unrecognized parts of the date will default to the current day, month, year, hour and minute. If this command is called to replace a timestamp at point, -of to enter the second timestamp of a range, the default time is taken from the -existing stamp. For example, +of to enter the second timestamp of a range, the default time is taken +from the existing stamp. Furthermore, the command prefers the future, +so if you are giving a date where the year is not given, and the day-month +combination is already past in the current year, it will assume you +mean next year. For details, see the manual. A few examples: + 3-2-5 -- 2003-02-05 feb 15-- currentyear-02-15 + 2/15 -- currentyear-02-15 sep 12 9 -- 2009-09-12 12:45 -- today 12:45 22 sept 0:34 -- currentyear-09-22 0:34 @@ -14191,7 +14196,7 @@ user. t nil ans))) ;; Help matching american dates, like 5/30 or 5/30/7 (when (string-match - ^ *\\([0-3]?[0-9]\\)/\\([0-1]?[0-9]\\)\\(/\\([0-9]+\\)\\)?\\([^/0-9]\\|$\\) ans) + ^ *\\(0?[1-9]\\|1[012]\\)/\\(0?[1-9]\\|[12][0-9]\\|3[01]\\)\\(/\\([0-9]+\\)\\)?\\([^/0-9]\\|$\\) ans) (setq year (if (match-end 4) (string-to-number (match-string 4 ans)) (progn (setq kill-year t) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Date Prompt Bug (or Anomoly)
On Jun 8, 2010, at 10:45 PM, Daniel E. Doherty wrote: Carsten, When I tried this last Saturday, I was reluctant to reply since the git server appeared to be down and your message made me think I did not have the latest git version. I tried it again today, and still no joy. I am using org-mode version 6.36a on emacs 23.1 on ubuntu. The latest entry in the Changelog file is , | 2010-06-08 Christian Egli christian.e...@sbszh.ch | | * org-taskjuggler.el (org-export-taskjuggler-old-level): | define local variable to avoid compiler warning. ` The following is straight from an org file: , | Attempted on: 2010-06-08 Tue. | Entering 3/21: 2021-07-03 Sat. | Entering 7/21: 2021-07-07 Wed. ` I assume that the fix would be in the function org-read-date-analyze, but I see no recent Changelog entries mentioning it. Is it possible this got lost while the git server was down? Hi Daniel, we have abondoned he ChangeLog file. The fix is in this commit: http://repo.or.cz/w/org-mode.git/commit/420dd96768262cb15c8bcf4fa6386361e0327add I get this: 2010-06-09 Wed 3/21: 2011-03-21 Mon 7/21: 2010-07-21 Wed I guess you are still loading an old version of Org somehow. - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Daily Habit in time range 23:00 04:00
How can I express a daily habit TODO item that I can fulfill from 11:00PM to 04:00AM? I'm an org-mode newbie, so this is pretty tricky for me. __ Alessandro ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Could inline footnotes be made to work with latex commands that have arguments?
If I put a LaTeX citation command inside one of org's inline footnotes, no
problem, thus:
Lorem ipsum dolor sit amet,\footnote{\cite{rowe_acts_2007} } consectetur
adipisicing elit,
But if I need an optional argument, no dice. This:
ex ea commodo consequat.[fn:: \cite[56]{fitzmyer_one_2007}] Duis aute irure
dolor
exports to LaTeX like this:
ex ea commodo consequat.[fn:: \cite[56]{fitzmyer_one_2007}] Duis aute irure
dolor
(i.e. there is no \footnote{} macro created)
For consistency in my markup, I would rather use org's inline footnotes for
citations like this (which sometimes number several inside a footnote). If
I can't, I'd just go ahead and use LaTeX \footnote{} macros right in my org
files.
Is the present behaviour likely to be fixable? Or should I just write my
footnotes as LaTeX \footnotes{}?
Scot
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Just discovered the date-tree capability of Remember
The org-mode documentation is very thorough and describes all the
features very well. But often the power of a feauture is not evident
until I start experimenting. Such a feature is the date-tree option of
Remember mode (section 9.1.2 Remember Templates).
I have a journal.org file which is my general purpose diary but I
manually create new headings each month and not worry about grouping
entries by day.
So what is a date tree?
It is a structure in an org-mode file that looks like:
* 2010
** 2010-05 May
** 2010-06 June
*** 2010-06-08 Tuesday
*** 2010-06-09 Wednesday
** This is my heading
And this it the content of each node.
I wasn't aware what headings are created but as you can see they are
parts of a date in the format -MM-DD annotated with a month or day name.
Here is my Remember template:
(Diary ?d \n* %^{topic} %^g\n%i%?\nAdded: %U\n
~/gtd/diary.org date-tree)
I also discovered you can add a property to a heading
namely the :DATE_TREE: property, then the remember filing is done
here. The documentation didnt tell me how to set the property value
so I used t.
* Project File
** Daily work log
:PROPERTIES:
:DATE_TREE: t
:END:
*** 2010
2010-06 June
* 2010-06-09 Wednesday
** This is my heading
Added: [2010-06-09 Wed 11:20]
Overall, this is a very useful feature of Remember mode
to make a versatile electronic diary/journal.
Well done! Maybe I will write a short tutorial.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: For Org-mode on the go?
Torsten Wagner wrote Thus, my suggestion please find out how well the hardware runs on GNU/Linux standard kernels and distributions (e.g., debian). If you know please report :D http://sharism.cc/2010/05/02/along-comes-debian/ ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
