[O] Multiple agenda buffers
I find if I accidentally return over an item's date, I get a second agenda buffer for that date. That seems fine, but what I don't like is that from now on, any org agenda commands go to THAT buffer, rather than going into the old agenda buffer, which I keep around all the time. So I have, for example *Org Agenda* and *Org Agenda(a:2014-03-25) Is there some way to kill the latter so that it does not come back? I did ^X-k in that buffer, and it disappeared, but my next org agenda command went into a buffer like that, instead of going into the original *Org Agenda* (and its frame). Is this related to org-agenda-this-buffer-is-sticky? I don't really understand the description of stickiness in org-agenda.el and it's not referenced in the index of the manual. thanks, r
[O] Alfred workflow for org-capture
Does anyone have a workflow for the Alfred Mac app launcher that will interact with org-capture? I know there have been versions before that worked with Quicksilver, which is quite similar. Thought I would ask before trying to roll my own. Thanks!
Re: [O] phone links...
Well, but note that we don't use file URLs -- we have special org hyperlinks with their own syntax... The reason I am reluctant to adopt tel: is that that would suggest we should adopt the phone number syntax of RFC 3966. I confess that I haven't slogged my way through it, nor am I likely to have time to in the near future It seems like false advertising to adopt a scheme without playing by its rules: I'd be happier doing this if I had an RFC 3966-compliant parser to use All I have done so far is trust that phone: is followed by something the org-phone-call can deal with. What do you all think? Am I being too fussy? On Apr 16, 2013, at 2:57, Eric S Fraga e.fr...@ucl.ac.uk wrote: Michael Strey mst...@strey.biz writes: Here is the most important part of Mat's reply: , | note that tel: is a common uri for indicating that something is a | telephone number (http://tools.ietf.org/html/rfc3966) ` Seems that we should prefer 'tel' as key for the phone link. +1 -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.3.50.1 and Org release_7.9.3f-1199-g3a0e55
[O] Question about reftex mode in org-mode
Quite some time ago, I incorporated reftex into my use of org mode, per a suggestion on Worg: ;;;--- ;;; Use reftex with org-mode, per Worg ;;;--- (autoload 'turn-on-reftx reftex Turn on RefTeX mode. t) (defun org-mode-reftex-setup () (turn-on-reftex)) (add-hook 'org-mode-hook 'org-mode-reftex-setup) Now I find that this has a bad behavior at least with Aquamacs: it can cause attempts to use the menu bar to be interrupted by a cryptic popup file selector that says Master file: This seems to be reftex trying to set a value for TeX-master. So maybe reftex is unhappy when it's not invoked inside of AucTeX (where TeX-master is defined and set). Anyone else seen this? Have a solution (e.g., have org files assume that TeX-master is t)? Thanks! r
Re: [O] phone links...
On 4/4/13 Apr 4 -7:15 AM, Bastien wrote: Hi Robert, Robert Goldman rpgold...@sift.info writes: The two files are below, in hopes of getting suggestions for improvement so that someday this could find itself into contrib/. Looks like a good start -- please keep us updated about your progress and your will to include this in contrib/, I'm sure many users would enjoy it. I will be happy to include this into contrib (and do the relevant assignment) at any time when people think that it is sufficiently ready to go. I have been testing it in contrib/ in a testing branch in my git repo. I think a minor refactoring would make it more general: split the phone handler into two components: a filter function (like the one for linphone), defaulting to identity; and a command, probably revised to be a format string (so that the dialed number could be place in an arbitrary location). I will try to have a new version with these changes very soon. Best, r
Re: [O] phone links...
On 4/4/13 Apr 4 -3:38 PM, Simon Thum wrote: Since you're at it: I keep the attached patch personally. I use it to sync org-contacts entries to my phone. I didn't sign up to the FSF so far, and suck at maintaining emacs commit msg conventions. If the patch is interesting I'll do what is required. I'm afraid I don't use org-contacts, so I don't exactly understand how this relates. Are phone: links desired? I.e., would you make the values of the phone fields be phone-type org hyperlinks? Or would you just expect to be able to push phone numbers directly into the org-phone-call function, without having to make the contact entries explicitly be hyperlinks? I suppose one should also attempt to make this compatible with the org/BBDB integration, another thing about which I'm quite ignorant Best, r P.S. I note that the contacts databases I have access typically have FAX and mobile entries as well as home and work. Many also allow custom phone number types.
[O] [PATCH 1/5] bind org-export-current-backend in generic exporter.
This is needed for org-export-preprocess-string to function correctly. --- contrib/lisp/org-export-generic.el |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index bb42b60..29e90b8 100644 --- a/contrib/lisp/org-export-generic.el +++ b/contrib/lisp/org-export-generic.el @@ -617,6 +617,7 @@ underlined headlines. The default is 3. (buffer-substring (if (org-region-active-p) (region-beginning) (point-min)) (if (org-region-active-p) (region-end) (point-max +(org-export-current-backend 'org-export-generic) (lines (org-split-string (org-export-preprocess-string region -- 1.7.3.5
[O] Patches for org-generic-export
Attached is a set of patches to the org-generic-exporter. They fix a change in the org-preprocess process that means that all uses of the org-generic export facility will crash. They also add rudimentary support for trac wiki and tikiwiki export. Finally, I have removed the HTML exporter from the org-generic export. I don't see any reason to struggle to support this, since it is done better by the core parts of org-mode. Cheers, r Table of contents: [PATCH 1/5] bind org-export-current-backend in generic exporter. [PATCH 2/5] Added trac-wiki and tikiwiki export settings. [PATCH 3/5] Kill the HTML exporter. [PATCH 4/5] Fixed section-header-prefix for trac wiki. [PATCH 5/5] Fix header prefixes for trac wiki.
[O] [PATCH 4/5] Fixed section-header-prefix for trac wiki.
--- contrib/lisp/org-export-generic.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index 15afe6a..5a5af14 100644 --- a/contrib/lisp/org-export-generic.el +++ b/contrib/lisp/org-export-generic.el @@ -405,8 +405,8 @@ in this way, it will be wrapped. :body-header-section-numbers nil :body-section-prefix \n - :body-section-header-prefix(== === -= == === ) + :body-section-header-prefix( == === + = == === ) :body-section-header-suffix( ==\n\n ===\n\n \n\n =\n\n ==\n\n ===\n\n) -- 1.7.3.5
[O] [PATCH 5/5] Fix header prefixes for trac wiki.
trac wiki has hard limit on number of headers. Need space before macro characters in trac wiki. Add a couple of TODO comments. --- contrib/lisp/org-export-generic.el |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index 5a5af14..12bbcdb 100644 --- a/contrib/lisp/org-export-generic.el +++ b/contrib/lisp/org-export-generic.el @@ -87,7 +87,9 @@ ;; *** allow different open/closing prefixes ;; * properties ;; * drawers -;; * oh my +;; * Escape camel-case for wiki exporters. +;; * Adjust to depth limits on headers --- need to roll-over from headers +;; to lists, as per other exporters ;; * optmization (many plist extracts should be in let vars) ;; * define defcustom spec for the specifier list ;; * fonts: at least monospace is not handled at all here. @@ -406,7 +408,7 @@ in this way, it will be wrapped. :body-section-prefix \n :body-section-header-prefix( == === - = == === ) + = ) :body-section-header-suffix( ==\n\n ===\n\n \n\n =\n\n ==\n\n ===\n\n) -- 1.7.3.5
[O] [PATCH 2/5] Added trac-wiki and tikiwiki export settings.
--- contrib/lisp/org-export-generic.el | 107 +++- 1 files changed, 93 insertions(+), 14 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index 29e90b8..e3a8680 100644 --- a/contrib/lisp/org-export-generic.el +++ b/contrib/lisp/org-export-generic.el @@ -187,8 +187,8 @@ in this way, it will be wrapped. ; section prefixes/suffixes can be direct strings or lists as well :body-section-prefix secprefix\n :body-section-suffix /secsuffix\n -; :body-section-prefix (sec1\n sec2\n sec3\n) -; :body-section-suffix (/sec1\n /sec2\n /sec3\n) + ;:body-section-prefix (sec1\n sec2\n sec3\n) + ;:body-section-suffix (/sec1\n /sec2\n /sec3\n) ; if preformated text should be included (eg, : prefixed) @@ -263,28 +263,28 @@ in this way, it will be wrapped. :body-header-section-numbers 3 :body-section-prefix \n -; :body-section-header-prefix \n -; :body-section-header-format %s\n -; :body-section-header-suffix (?\$ ?\# ?^ ?\~ ?\= ?\-) + ;:body-section-header-prefix \n + ;:body-section-header-format %s\n + ;:body-section-header-suffix (?\$ ?\# ?^ ?\~ ?\= ?\-) :body-section-header-prefix ( *+ - ) :body-section-header-format %s\n :body-section-header-suffix (?~ ?= ?- \n \n \n) -; :body-section-marker-prefix -; :body-section-marker-chars (?\$ ?\# ?^ ?\~ ?\= ?\-) -; :body-section-marker-suffix \n + ;:body-section-marker-prefix + ;:body-section-marker-chars (?\$ ?\# ?^ ?\~ ?\= ?\-) + ;:body-section-marker-suffix \n :body-line-export-preformated t :body-line-format %s\n :body-line-wrap 75 -; :body-text-prefix t\n -; :body-text-suffix /t\n + ;:body-text-prefix t\n + ;:body-text-suffix /t\n :body-bullet-list-prefix (?* ?+ ?-) -; :body-bullet-list-suffix (?* ?+ ?-) + ;:body-bullet-list-suffix (?* ?+ ?-) ) ;; @@ -350,8 +350,8 @@ in this way, it will be wrapped. :body-section-prefix secprefix\n :body-section-suffix /secsuffix\n -; :body-section-prefix (sec1\n sec2\n sec3\n) -; :body-section-suffix (/sec1\n /sec2\n /sec3\n) + ;:body-section-prefix (sec1\n sec2\n sec3\n) + ;:body-section-suffix (/sec1\n /sec2\n /sec3\n) :body-line-export-preformated t :body-line-format %s\n @@ -360,7 +360,7 @@ in this way, it will be wrapped. :body-text-suffix /p\n :body-bullet-list-prefix (?* ?+ ?-) -; :body-bullet-list-suffix (?* ?+ ?-) + ;:body-bullet-list-suffix (?* ?+ ?-) ) ;; @@ -429,6 +429,85 @@ in this way, it will be wrapped. :body-list-formatt%s/t\n ) +(trac-wiki + :file-suffix .txt + :key-binding ?T + + ;; lifted from wikipedia exporter + :header-prefix + :header-suffix + + :title-format = %s =\n + + :date-export nil + + :toc-exportnil + + :body-header-section-numbers nil + :body-section-prefix \n + + :body-section-header-prefix(== === += == === ) + :body-section-header-suffix( ==\n\n ===\n\n \n\n + =\n\n ==\n\n ===\n\n) + + :body-line-export-preformated t ;; yes/no/maybe??? + :body-line-format %s\n + :body-line-wrap75 + + :body-line-fixed-format%s\n + + :body-list-format * %s\n + :body-number-list-format# %s\n + ;;:body-list-prefix LISTSTART + ;;:body-list-suffix LISTEND + + ;; this is ignored! [2010/02/02:rpg] + :body-bullet-list-prefix (* ** *** * ) + ) +(tikiwiki + :file-suffix .txt + :key-binding ?U + + ;; lifted from wikipedia exporter + :header-prefix + :header-suffix
[O] [PATCH 3/5] Kill the HTML exporter.
This is done better in core org-mode. --- contrib/lisp/org-export-generic.el | 41 1 files changed, 0 insertions(+), 41 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index e3a8680..15afe6a 100644 --- a/contrib/lisp/org-export-generic.el +++ b/contrib/lisp/org-export-generic.el @@ -322,47 +322,6 @@ in this way, it will be wrapped. :body-bullet-list-prefix (* ** *** * ) ) - -;; -;; minimal html exporter -;; -(html - ;; simple html output - :file-suffix .html - :key-binding ?h - - :header-prefix body - - :title-format h1%s/h1\n\n - - :date-export t - :date-format br /bDate:/b i%s/ibr /\n\n - - :toc-exportnil - - :body-header-section-numbers 3 - - :body-section-header-prefix (h1 h2 h3 - h4 h5 h6) - :body-section-header-format %s - :body-section-header-suffix (/h1\n /h2\n /h3\n - /h4\n /h5\n /h6\n) - - :body-section-prefix secprefix\n - :body-section-suffix /secsuffix\n - ;:body-section-prefix (sec1\n sec2\n sec3\n) - ;:body-section-suffix (/sec1\n /sec2\n /sec3\n) - - :body-line-export-preformated t - :body-line-format %s\n - - :body-text-prefix p\n - :body-text-suffix /p\n - - :body-bullet-list-prefix (?* ?+ ?-) - ;:body-bullet-list-suffix (?* ?+ ?-) - ) - ;; ;; internet-draft .xml for xml2rfc exporter ;; -- 1.7.3.5
Re: [O] Org babel does not work properly with included files
Sorry, I think I have created a red herring here by leaving that code block in both files. To see what the problem really is, consider the case where the source code block appears ONLY in the included file. (I tested the source block in the master file to make sure it worked before I copied it into the included file and forgot to remove it from the master file.) Best, R -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Nick Dokos nicholas.do...@hp.com wrote: Robert Goldman rpgold...@sift.info wrote: foo.org: * Purpose This document is intended to demonstrate that src buffer evaluation in subsidiary, included files, does not work. * Demo #+include ~/src/org-test/bar.org bar.org: * Here's the demo #+begin_src sh :exports results :results output echo foo! #+end_src As a workaround, try making the headings identical, i.e. bar.org looks like this: --8---cut here---start-8--- * Demo #+begin_src sh :exports results :results output echo foo! #+end_src --8---cut here---end---8--- Nick
Re: [O] Org babel does not work properly with included files
Also note that if you have an included file with MULTIPLE code blocks, this approach won't generalize Best, -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Nick Dokos nicholas.do...@hp.com wrote: Robert Goldman rpgold...@sift.info wrote: foo.org: * Purpose This document is intended to demonstrate that src buffer evaluation in subsidiary, included files, does not work. * Demo #+include ~/src/org-test/bar.org bar.org: * Here's the demo #+begin_src sh :exports results :results output echo foo! #+end_src As a workaround, try making the headings identical, i.e. bar.org looks like this: --8---cut here---start-8--- * Demo #+begin_src sh :exports results :results output echo foo! #+end_src --8---cut here---end---8--- Nick
Re: [O] Org babel does not work properly with included files
Yes. That's right, the single source block was a simplification for the example. It was abstracted from a more complicated case with a dozen or so source blocks in the subordinate filter. But thanks for the suggestion. Hope we can find a fix! Best R -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Nick Dokos nicholas.do...@hp.com wrote: Robert P. Goldman rpgold...@sift.info wrote: Sorry, I think I have created a red herring here by leaving that code blo= ck in both files. To see what the problem really is, consider the case wh= ere the source code block appears ONLY in the included file. (I tested the source block in the master file to make sure it worked befo= re I copied it into the included file and forgot to remove it from the ma= ster file.) ?? There was no code block in foo.org: just the include. Only bar.org had the code block. As for multiple code blocks in the included file (your next message), yeah, probably. But my suggestion was just a (possible) workaround: it's definitely not a fix. Nick
[O] [PATCH] Fixed shell script example in Emacs Lisp evaluation of variables.
The variable names in the header arguments and in the sh code didn't line up. Made them agree. --- doc/org.texi |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/org.texi b/doc/org.texi index 17922d4..e68ed18 100644 --- a/doc/org.texi +++ b/doc/org.texi @@ -12072,8 +12072,8 @@ org-mode file, while there is no such guarantee for evaluation of the code block body. @example -#+begin_src sh :var file-name=(buffer-file-name) :exports both - wc -w $file +#+begin_src sh :var filename=(buffer-file-name) :exports both + wc -w $filename #+end_src @end example -- 1.7.3.5
[O] Patch for org-babel manual node
There was a bug in an example of argument passing in the org-babel part of the manual. Fixed in the following patch.
[Orgmode] Re: Request for suggestions: multiple revision control systems/repositories + org
That is what I had done originally, but I thought mobile org required that all the org files be in the same directory. Was I wrong about that? Thanks, R Bernt Hansen be...@norang.ca wrote: Robert Goldman rpgold...@sift.info writes: I am looking for hints. I have a number of org files, typically one for each major project plus two or three for my personal life. These must often live in different revision control systems: my work projects, in particular, have different repositories; I have a main set of org files for work in ~/org/, tracked by my employers' svn; occasionally, I do something outside, like work on a paper with someone outside my company in a dedicated git repo; and I'd like to stuff my personal materials off in a git repo of my own. I have been pulling all of these together into my ~/org directory, using symbolic links, for the benefit of mobile org. That is, my ~/org directory has my main work org files, plus links to a bunch of others. That works well for syncing with mobile org. Unfortunately, it's a mess for Emacs's version control mode. VC mode sees the .svn directory in that place, and can handle the local files, but gets horribly confused by the sym-linked files. Anyone have a similar need to gather together a mess of org files, and have a cleaner solution? Extra credit if you have a way of creating the same set of symlinks on more than one machine! ;-) How about keeping the separate projects in separate repositories and just add the files from those multiple projects to your org-agenda-files variable? Then you see a consolidated view of multiple org projects (and the files that contribute to that view can be individually set per machine - you don't need all projects for all machines - but any repositories that are available can contribute to your agenda. Each of the projects are completely independent and don't need to know about each other - just the org-agenda-files variable pulls them into your agenda view. Regards, Bernt -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. ___ 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] Trivial docstring patch
Following is a patch that fixes a misspelling in the docstring for org-todo-keywords. Also adds a little punctuation. ___ 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] [PATCH] Fixed typo in docstring for org-todo-keywords.
From: Robert P. Goldman rpgold...@real-time.com --- lisp/org.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index 8227ed9..18e7fc5 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -1958,7 +1958,7 @@ indicating if the keywords should be interpreted as a sequence of action steps, or as different types of TODO items. The first keywords are states requiring action - these states will select a headline for inclusion into the global TODO list Org-mode produces. If one of -the \keywords\ is the vertical bat \|\ the remaining keywords +the \keywords\ is the vertical bar, \|\, the remaining keywords signify that no further action is necessary. If \|\ is not found, the last keyword is treated as the only DONE state of the sequence. -- 1.7.2.2 ___ 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: Request for suggestions about best practices: tracking responses
On 9/22/10 Sep 22 -3:08 PM, Sébastien Vauban wrote: Hi Robert, Robert Goldman wrote: Often now I have org-mode tasks that I move to WAIT status when I send someone an email to get some next step done. I do that as well. Though, I'm still testing what my own process must be like. The problem is that I have a hard time getting back to those tasks when I get a response email (or phone call). There is nothing salient about these that means that when I get a response email, I see the task and can mark it as completed. Does anyone have a good solution for this? I have a hazy idea that always having a special agenda window open with a special agenda display of tasks awaiting responses might do the trick, but few ideas about how to accomplish this in practice. Presumably a special TODO status for awaiting response, and special agenda view... does that sound reasonable? I notice that the manual refers to THE agenda. Is it possible to have multiple agenda windows so that I could always have the waiting for response agenda up w/o cutting off my access to other views? As far as I fully understand your request, what you need is a custom agenda report: --8---cut here---start-8--- #+BEGIN_SRC emacs-lisp (setq org-agenda-custom-commands '((W Waiting todo WAIT nil))) #+END_SRC --8---cut here---end---8--- I know how to make a custom agenda for this; the problem is more how to have that custom agenda always open for me to glance at. I don't want to have to call up this agenda every time I get an email or a phone call to decide whether a waiting task is unwaiting... Should one open an org agenda buffer, and then rename it, so that following org-agenda commands don't wipe it? 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
[Orgmode] Re: bug with link following --- a (partial) solution
On 8/29/10 Aug 29 -10:36 AM, Robert Goldman wrote: I used org-store-link and org-insert-link to make a link in the attached document (I distilled it down from a real document). In my org-mode (pulled from git this morning), using Aquamacs 2.0 on Mac OSX Snow Leopard (10.6), org-mode cannot follow the link I inserted with o-i-l, and it pops up a dialog asking if I should add such a link target. A quick followup: I had a shot with git blame, and it seems like the only thing that might have interfered with this search recently is the commit with the SHA1 has starting a84c8a2c And, indeed, when I comment out the block that was introduced in this commit (starting at line 9389): ;; ((and (org-mode-p) org-link-search-must-match-exact-headline) ;; (and (equal (string-to-char s) ?*) (setq s (substring s 1))) ;; (goto-char (point-min)) ;; (cond ;; ((let (case-fold-search) ;; (re-search-forward (format org-complex-heading-regexp-format ;; (regexp-quote s)) ;; nil t)) ;; ;; OK, found a match ;; (goto-char (match-beginning 0))) ;; ((and (not org-link-search-inhibit-query) ;; (eq org-link-search-must-match-exact-headline 'query-to-create) ;; (y-or-n-p No match - create this as a new heading? )) ;; (goto-char (point-max)) ;; (or (bolp) (newline)) ;; (insert * s \n) ;; (beginning-of-line 0)) ;; (t ;; (goto-char pos) ;; (error No match ...then my link-following works again. Carsten, could this patch be reverted until it can be fixed? Best, 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
[Orgmode] org-export-generic patch
This patch adds handling of blockquotes and flowed output formats to org-export-generic per earlier email. ___ 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] [PATCH 4/4] Add handling of blockquote and output formats that must be flowed.
From: Robert P. Goldman rpgold...@real-time.com Added a handler for blockquotes. Also added :body-newline-paragraph to the org-set-generic-type. This is intended to help handling output formats (like tikiwiki) where newlines are treated as paragraph separators, instead of being used to fill (i.e., the destination is expected to do the word-wrapping). If this is set to T then org-export-generic will emit a newline character when it sees a blank line. This should be used in concert with a value like %s for :body-line-format and nil for :body-line-wrap. --- contrib/lisp/org-export-generic.el | 19 +-- 1 files changed, 17 insertions(+), 2 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index 11c37da..1b099dd 100644 --- a/contrib/lisp/org-export-generic.el +++ b/contrib/lisp/org-export-generic.el @@ -88,8 +88,9 @@ ;; * properties ;; * drawers ;; * oh my -;; * optmization (many plist extracts should be in (let) vars +;; * optmization (many plist extracts should be in let vars) ;; * define defcustom spec for the specifier list +;; * fonts: at least monospace is not handled at all here. ;; ; ;; @@ -638,10 +639,14 @@ underlined headlines. The default is 3. (or (plist-get export-plist :body-list-checkbox-done-end) )) (listcheckhalfend (or (plist-get export-plist :body-list-checkbox-half-end) )) + (bodynewline-paragraph (plist-get export-plist :body-newline-paragraph)) (bodytextpre (plist-get export-plist :body-text-prefix)) (bodytextsuf (plist-get export-plist :body-text-suffix)) (bodylinewrap (plist-get export-plist :body-line-wrap)) (bodylineform (or (plist-get export-plist :body-line-format) %s)) + (blockquotestart (or (plist-get export-plist :blockquote-start) \n\n\t)) + (blockquoteend (or (plist-get export-plist :blockquote-end) \n\n)) + thetoc toctags have-headings first-heading-pos table-open table-buffer link-buffer link desc desc0 rpl wrap) @@ -868,7 +873,7 @@ underlined headlines. The default is 3. ((string-match ^\\([ \t]*\\)\\(:\\( \\|$\\)\\) line) ;; - ;; pre-formated text + ;; pre-formatted text ;; (setq line (replace-match \\1 nil nil line)) @@ -933,6 +938,15 @@ underlined headlines. The default is 3. ) (insert (format numlistformat line))) + + ((equal line ORG-BLOCKQUOTE-START) +(setq line blockquotestart)) + ((equal line ORG-BLOCKQUOTE-END) +(setq line blockquoteend)) + ((string-match ^\\s-*$ line) +;; blank line +(if bodynewline-paragraph +(insert \n))) (t ;; ;; body @@ -1009,6 +1023,7 @@ underlined headlines. The default is 3. (goto-char beg))) (goto-char (point-min + (defun org-export-generic-format (export-plist prop optional len n reverse) converts a property specification to a string given types of properties -- 1.6.5.3 ___ 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] Repeating tasks in an interval
Is there some way to specify a repeating task over an interval? That is a task that is done, for example, every month, over a finite period? Here's an example that I tried: DEADLINE: 2009-12-01 Tue +1m--2009-11-01 Sun But this one doesn't work --- the tasks keep appearing after November ended. Is this possible? Do I just have the wrong syntax? Or must I do this with C-c C-x c (cloning)? thanks, Robert ___ 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] Can we make a refloc programmatically?
I find that when I'm refiling my MobileOrg tasks, I almost always want them to go to one particular place (my master todo list). I'd like to make a command that refiles to that location, specifically. The closest I've been able to get to this is to bind the org-refile-targets dynamic variable around a call to org-refile. This gives me a single candidate location, which I get if I press the tab key for completion. But it seems wrong to have to press that tab key. I believe I could avoid that, if I could pass a rfloc argument to org-refile, but I'm not sure how to make one of these data structures (not for the first time, I wish that defstruct was in elisp...). Is there some function to which one could pass a filename and a header regexp? thanks, Robert ___ 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: Minor buglet in orgmode Makefile
Noorul Islam gnukid at gmail.com writes: I got the same error. This is what I did. $ make clean make Everything went fine. Right you are. That fixed it. Thanks! No bug after all. ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Minor buglet in orgmode Makefile
I just pulled an update from git for the first time in a long while, and when I tried to build org-mode, it failed with an undefined function error for the function org-float-time in org-ascii. It only took me a moment to find the fix --- it seems like we just need to push org-compat up the list of lisp files ahead of org-ascii, since org-compat provides the function definition org-ascii craves. Cheers, R ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Request for advice on OrgMobile
I just installed OrgMobile and I'm delighted with it. But I was wondering --- it seems to create only my custom agendas by default. Is there any way to persuade it to create the daily and weekly agendas on export? I'd really like to have those at my fingertips. Thanks! ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Request for advice on OrgMobile
Robert P. Goldman rpgoldman at sift.info writes: I just installed OrgMobile and I'm delighted with it. But I was wondering --- it seems to create only my custom agendas by default. Is there any way to persuade it to create the daily and weekly agendas on export? I'd really like to have those at my fingertips. OK, I see --- never mind! I just create custom agenda commands that mirror what the normal 1-day and 7-day agendas (C-c a a) do, using the org-agenda-ndays to control them. This seems like a normal enough thing to want to do that one might simply add it as an option to org-mobile's configuration (in org-mobile-push, I assume). I might have a whack at providing a patch if no one better does it first ;-) ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: clearing the state of an org-mode subtree
Bernt Hansen bernt at norang.ca writes: Paul Mead paul.d.mead at gmail.com writes: Robert Goldman rpgoldman at sift.info writes: Andrew Stribblehill wrote: org-mode files are plain text. M-% to do a replacement: once you've entered your search term and its replacement, hit ! to replace all without question. Yes, one can do this, but note that it's not entirely a no-brainer. You need to: 1. clear all the check boxes and then recompute all checkbox counts in the region. [this isn't a simple tag replacement] 2. replace all non-TODO keywords with TODO. This is a replacement, but not a simple one to do with M-% 3. Wipe out all of the notes that were added with state changes. Again, this can be done with a replacement command, but it's not a trivial one. This is one of those cases where automating a task will not pay back the investment (at least not to me, individually), so I think I'd better just do it by hand. Thanks, everyone, Have you thought about using yasnippet? I have a repeating set of TODOs in a particular order that I have to do every month. Rather than reusing the old structure, I just insert it again from a snippet. That way I also have all my notes from last month too. Or copy the subtree _before_ you fill it in with details. Make a repeating task that is just to copy the subtree at the appropriate time so the subtree is available for the repeat after this one, and then proceed to use one of the copies for the current task iteration. Yes, this would clearly have been The Right Thing had I realized when I built the subtree that I might want to use it again. But I didn't (this seems like a specific case of the general code reuse problem --- it's nice if you can foresee that you'd like to reuse something but often that does not happen). The issue about copying, IIUC, is that the template from which one is to copy must be kept out of band with respect to the agenda. That is, it must be kept somewhere (perhaps in an org-templates.org file) where the agenda will not see it, and copied from the templates file into a file that is active wrt the agenda. The yasnippet approach fits this. But again, this is a different use case --- one in which the user has had the foresight to realize that a task will be used over and over. Note that no templating approach (automated by yasnippet or not) supports learning in the course of this code reuse. E.g., if I think of something this year when I am winterizing, and add that new TODO into my currently active copy of the template, then it won't appear next year if I reinvoke the template. In general, I'm inclined to think that this case is irregular enough that it's probably best to simply keep my one working copy and manually clear it every year when I need another. It's probably an AI-complete problem to clear an arbitrary hunk of org back to a pristine state! Thanks for the discussion, best, r ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
