[O] [BUG] LaTeX subtree export gives spurious "unbalanced begin/end_%s blocks" error
Hi, Here's a minimal document: BEGIN EXAMPLE #+title: Testing * Src blocks Here's some Lisp: #+begin_src emacs-lisp (message "Hello world!") #+end_src END EXAMPLE When I try to export the "Src blocks" subtree to PDF via LaTeX, I get the error: "unbalanced begin/end_src blocks" Export of the whole document to PDF via LaTeX is not affected. Neither, initially, is HTML export, including subtree export to HTML. However, after getting an error by trying to export the subtree to LaTeX, I get the same error when trying to export to HTML (whether subtree or the whole document). I can "clear" the HTML export error by exporting the whole document via LaTeX again. I'm using Org 7.7 (pulled this morning) on GNU Emacs 23.3.1 on a Mac. Yours, Christian
[O] Where do these backgroud colors come from?
Hi! Just updated to current git version of org: Org-mode version 7.7 (release_7.7.674.gc609) Running under emacs: GNU Emacs 23.3.1 (x86_64-suse-linux-gnu, GTK+ Version 2.22.1) of 2011-10-07 on build40 Suddenly I have some lines with colored backgrounds, some dark blue, some light blue in my agenda view?! (invoked using C-c a a) There are _no_ entries in my .emacs telling anything about colors at all. (AFAICT.) I like the good old white background for all my agenda lines and want it back. What has changed in recent versions of org and how can those background colors be disabled? Thx a lot Detlef
[O] Bug: Recurring TODO spuriously blocked [7.7]
Hi, people.
Whenever a TODO is scheduled with a recurrence (with .+ or ++), forcing
the state to DONE is a mere way to trigger Org into setting the state to
TODO again, yet with the scheduled date updated for the next repetition.
Setting to DONE merely means that this repetition is done, which is not
the same as being forever DONE. In fact, setting a repeated schedule to
DONE is really a way of updating the schedule; the intent relies on the
mechanics by which the DONE state is just a transient way to TODO again.
Now, within ~/.emacs, I have org-enforce-todo-dependencies set to t, for
good purposes. But then, I get spurious:
byte-code: TODO state change from TODO to DONE blocked
trying to schedule the next repetition. todo-dependencies should likely
never be enforced for repeated entries, even if enforced otherwise, as
enforcing for repetitions with the current Org mechanics has no meaning,
at least as I undestand Org so far.
François
P.S. This is my first report to Org mode people. To sent id, I tried
the "Org -> Send Bug Report" menu entry. This action took quite a long
time, mostly writing dots after "Formatting bug report buffer", and
produced a very long "current state" section, containing what might be
byte code, and very long lines which did not seem meaningful, and which
I edited out so this submission stays reasonable. As edited below, the
report is now of reasonable length, and hopefully, reasonable contents.
The bug report took too much time to generate, and too much time to
hand-edit afterwards, to the point of discouragement. I will likely
avoid that menu in next communications. In my opinion, to be usable,
the generation should be corrected to avoid byte-code, and other noise.
It might also solve the speed problem.
Emacs : GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.4)
of 2011-04-04 on rothera, modified by Debian
Package: Org-mode version 7.7
current state:
==
(setq
org-mouse-features '(context-menu move-tree yank-link activate-stars
activate-bullets activate-checkboxes)
org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars)
org-todo-keyword-faces '(("TODO" :foreground "orange" :weight bold)
("NEXT" . org-todo) ("DONE" . org-done)
("WAIT" :foreground "dark red" :weight bold)
("ISSUE" . org-todo)
("FORWARDED" :foreground "dark red" :weight
bold)
("REJECTED" :foreground "black" :weight bold)
("SOLVED" . org-done)
("Reclasser" :foreground "orange" :weight bold))
org-speed-command-hook '(org-speed-command-default-hook
org-babel-speed-command-hook)
org-agenda-files '("~/fp/notes/epsilon.org" "~/fp/notes/notes.org")
org-blocker-hook '(org-block-todo-from-checkboxes
org-block-todo-from-children-or-siblings-or-parent)
org-clock-in-hook '(fp-org-clock-in-routine)
org-metaup-hook '(org-babel-load-in-session-maybe)
org-after-todo-state-change-hook '(org-clock-out-if-current)
org-special-ctrl-k t
org-export-latex-format-toc-function 'org-export-latex-format-toc-default
org-stuck-projects '("+projet/-DONE" ("TODO" "NEXT") nil "")
org-clock-in-resume t
org-agenda-clock-consistency-checks '(:max-gap "0:05" :gap-ok-around
("4:00" "13:30" "19:30")
:max-duration "10:00"
:min-duration 2 :default-face
((:background "DarkRed")
(:foreground "white"))
:gap-face
((:background "light blue")
(:foreground "white"))
:no-end-time-face
((:background "salmon")
(:foreground "white"))
)
org-tab-first-hook '(org-hide-block-toggle-maybe
org-src-native-tab-command-maybe
org-babel-hide-result-toggle-maybe)
org-src-mode-hook '(org-src-babel-configure-edit-buffer
org-src-mode-configure-edit-buffer)
org-confirm-shell-link-function nil
org-export-first-hook '(org-beamer-initialize-open-trackers)
org-use-tag-inheritance nil
org-clock-persist t
org-startup-indented t
org-todo-keywords '((sequence "TODO(t)" "NEXT(n)" "|" "DONE(d)"
"WAIT(w@)")
(sequence "ISSUE(i)" "FORWARDED(f@)" "|"
"REJECTED(r@)" "SOLVED(s@)")
(sequence "Reclasser" "|"))
org-agenda-before-write-hook '(org-agenda-add-entry-text)
org-default-notes-file "~/fp/notes/notes.org"
org-directory "~/fp/
[O] Capture failure [7.7]
Hi, Org mode people. I had some misery trying to debug a special personal machinery to capture URLs from Chrome into Org. Not worth detailing here. And moreover, as it works now, I'm happy with this. However, I had to make the following modification to get it going. I'm not sure what are the meaning of "beg" and "end" in this function, so someone knowledgeable should check if (point) is appropriate as a value. One sure thing is that "beg" and "end" should be initialized, as they get later consulted in the function, and whenever :exact-position got a value, that initialization does not occur. François P.S. This is using a copy of the Git repository as updated yesterday. diff --git a/lisp/org-capture.el b/lisp/org-capture.el index 566fb96..783fe70 100644 --- a/lisp/org-capture.el +++ b/lisp/org-capture.el @@ -913,7 +913,8 @@ it. When it is a variable, retrieve the value. Return whatever we get." beg end) (cond ((org-capture-get :exact-position) - (goto-char (org-capture-get :exact-position))) + (goto-char (org-capture-get :exact-position)) + (setq beg (point) end (point))) ((not target-entry-p) ;; Insert as top-level entry, either at beginning or at end of file (setq beg (point-min) end (point-max)))
[O] Mouse clicks within org-goto
Hi again, Org people. Let me first say that I much like org-goto (C-c C-j), thanks for it! One thing which I miss in it is the capability of quick positioning within the goto window, using the mouse. If I click anywhere (using mouse-1), the Emacs cursor jumps to the mouse cursor indeed, but after a fraction of a second, it and immediately jumps back at the beginning of the Org buffer. It would be a nice feature to have, to make org-goto appear even more speedy, user-wise. François P.S. This is using a recent Org checkout. org-mouse.el is loaded, but I also tried without, and it does not seem to matter.
[O] [bug] Commit 6f8ea8e breaks the build
Commit 6f8ea8e breaks the build. > make clean > make ...returns the error: --8<---cut here---start->8--- emacs -batch -q -no-site-file -eval "(setq load-path (cons (expand-file-name \"./lisp/\") (cons \"/usr/local/share/emacs/site-lisp\" load-path)))" -f batch-byte-compile lisp/org-odt.el In toplevel form: lisp/org-odt.el:31:13:Error: Cannot open load file: htmlfontify make: *** [lisp/org-odt.elc] Error 1 --8<---cut here---end--->8--- Best, Martyn --- Org-mode version 7.7 (release_7.7.674.gc609) GNU Emacs 24.0.50.1 (x86_64-apple-darwin, NS apple-appkit-1038.35) of 2011-08-21 on virtualmac.porkrind.org
Re: [O] [BUG] LaTeX subtree export gives spurious "unbalanced begin/end_%s blocks" error
I have the same problem. It occurs on a 2nd pass through org-export-blocks-preprocess (in org-exp-blocks.el). 1st pass runs OK, 2nd pass gets the error condition. 1st pass processes the following: (buffer-substring match-start (point-max)) -> "#+begin_src emacs-lisp\n (message \"Hello, World!\")\n#+end_src\n" 2nd pass processes an emptied skeleton of the block (buffer-substring match-start (point-max)) -> "#+begin_src emacs-lisp\n#+end_src\n" And fails to balance begin with end. At this point in the code, the regular expression for matching begin/end contains (I made ^M and tab visible here): inner-re = "[\r\n][\t ]*#\\+\\(begin\\|end\\)_src" And this expression fails right away: (re-search-forward inner-re nil t) -> nil I'll try to dig further into what's goning on. Regards, .j. On Mon, Dec 12, 2011 at 09:54:18AM +0100, Christian Moe wrote: > Hi, > > Here's a minimal document: > > BEGIN EXAMPLE > > #+title: Testing > > * Src blocks > > Here's some Lisp: > > #+begin_src emacs-lisp > (message "Hello world!") > #+end_src > > END EXAMPLE > > When I try to export the "Src blocks" subtree to PDF via LaTeX, I > get the error: > > "unbalanced begin/end_src blocks" > > Export of the whole document to PDF via LaTeX is not affected. > > Neither, initially, is HTML export, including subtree export to > HTML. However, after getting an error by trying to export the > subtree to LaTeX, I get the same error when trying to export to HTML > (whether subtree or the whole document). I can "clear" the HTML > export error by exporting the whole document via LaTeX again.
Re: [O] [bug] Commit 6f8ea8e breaks the build
Martyn Jago writes: > Commit 6f8ea8e breaks the build. >> make clean >> make > > ...returns the error: > > > emacs -batch -q -no-site-file -eval "(setq load-path (cons (expand-file-name > \"./lisp/\") (cons \"/usr/local/share/emacs/site-lisp\" load-path)))" -f > batch-byte-compile lisp/org-odt.el > > In toplevel form: > lisp/org-odt.el:31:13:Error: Cannot open load file: htmlfontify > make: *** [lisp/org-odt.elc] Error 1 I am using Windows/Cygwin and Emacs-24 pretest builds. org-odt.el compiles just fine. --8<---cut here---start->8--- In toplevel form: org-mouse.el:320:1:Warning: global/dynamic var `rest' lacks a prefix org-mouse.el:1024:1:Warning: global/dynamic var `_cmd' lacks a prefix Wrote c:/Documents and Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-mouse.elc emacs -batch -q -no-site-file -eval "(setq load-path (cons (expand-file-name \"./lisp/\") (cons \"/usr/local/share/emacs/site-lisp\" load-path)))" -f batch-byte-compile lisp/org-odt.el Wrote c:/Documents and Settings/kjambunathan/My Documents/My Data/src/org-mode/lisp/org-odt.elc --8<---cut here---end--->8--- Don't you have htmlfontify.el in your version of Emacs? I thought it is part of regular Emacs. Could you please check why this is so? May be some adjustment of load path is required or htmlfontify.el has to be installed. > > Best, Martyn > > --- > Org-mode version 7.7 (release_7.7.674.gc609) > GNU Emacs 24.0.50.1 (x86_64-apple-darwin, NS apple-appkit-1038.35) > of 2011-08-21 on virtualmac.porkrind.org > > > --
[O] [BUG] Various problems with org-odt export
Hi, Either something's gone wrong with my setup, or there are a number of issues to straighten out after org-odt moved to core. Here's what I have so far (with Org 7.7 pulled this morning, Emacs 23.3.1, on a Mac). Issues 1 and 3 look urgent. 1. The org-export-odt-styles-file variable still points to "~/src/base/org-mode/contrib/odt/styles.xml" as the default style template. The defcustom comes with a FIXME note, and that has become urgent, as the lack of a default styles file in the default place would cause Org-odt export to fail out of the box for most users. I'm not sure where this should point, but I assume it should not point to anything in contrib any longer. 2. The #+ODT_STYLES_FILE directive does not seem to work. It's ignored and the value of org-export-odt-styles-file is used instead. 3. Current backend not set to 'odt? During ODT export, org-export-format-source-code-or-example fails while trying to load a file called "org-nil". So apparently org-export-current-backend fails to be passed the value 'odt on ODT export. The latter problem could also explain why, trying to export a file with verse environments, I got LaTeX mixed in with the ODT XML... Yours, Christian
Re: [O] [BUG] Various problems with org-odt export
Christian > Hi, > > Either something's gone wrong with my setup, or there are a number of > issues to straighten out after org-odt moved to core. > > Here's what I have so far (with Org 7.7 pulled this morning, Emacs > 23.3.1, on a Mac). Issues 1 and 3 look urgent. > > 1. The org-export-odt-styles-file variable > > still points to > "~/src/base/org-mode/contrib/odt/styles.xml" > as the default style template. The defcustom comes with a FIXME note, > and that has become urgent, as the lack of a default styles file in > the default place would cause Org-odt export to fail out of the box > for most users. I'm not sure where this should point, but I assume it > should not point to anything in contrib any longer. The default style files have been moved from contrib/odt/styles to etc/styles. Make sure that you are loading the right version of org-odt with M-x locate-library. Also the following variables: C-h v org-odt-lib-dir => "~/src/org-mode/lisp/" C-h v org-odt-styles-dir => "~/src/org-mode/etc/styles/" The first variable says wherefrom org-odt is loaded. The second variable -- which was newly introduced a 2-3 days ago -- should tell where the default style files come from. If you are unable to find the second variable, then it most postively suggests that it is the old org-odt that is loaded. > 2. The #+ODT_STYLES_FILE directive > > does not seem to work. It's ignored and the value of > org-export-odt-styles-file is used instead. May be related to (1). Is everything OK when there is *no* ODT_STYLES_FILE and org-export-odt-styles-file is *reset* to nil? > 3. Current backend not set to 'odt? > > During ODT export, org-export-format-source-code-or-example > fails while trying to load a file called "org-nil". So apparently > org-export-current-backend fails to be passed the value 'odt on ODT > export. > > The latter problem could also explain why, trying to export a file > with verse environments, I got LaTeX mixed in with the ODT XML... I hope org-odt loads fine... Does M-x load-library RET org-odt RET report any errors? > Yours, > Christian > > > --
Re: [O] [bug] Commit 6f8ea8e breaks the build
Hi Jambunathan Jambunathan K writes: > Martyn Jago writes: > >> Commit 6f8ea8e breaks the build. > >>> make clean >>> make >> >> ...returns the error: >> >> >> emacs -batch -q -no-site-file -eval "(setq load-path (cons (expand-file-name >> \"./lisp/\") (cons \"/usr/local/share/emacs/site-lisp\" load-path)))" -f >> batch-byte-compile lisp/org-odt.el >> >> In toplevel form: >> lisp/org-odt.el:31:13:Error: Cannot open load file: htmlfontify >> make: *** [lisp/org-odt.elc] Error 1 > > I am using Windows/Cygwin and Emacs-24 pretest builds. org-odt.el > compiles just fine. > The problem appears to be that htmlfontify.el was not present in Emacs-23 and Emacs-22 releases. This is a problem since Org-mode is supposed to build with releases back to Emacs-22. Since my build builds all versions to ensure against regression, the build failed. Best, Martyn > In toplevel form: > org-mouse.el:320:1:Warning: global/dynamic var `rest' lacks a prefix > org-mouse.el:1024:1:Warning: global/dynamic var `_cmd' lacks a prefix > Wrote c:/Documents and Settings/kjambunathan/My Documents/My > Data/src/org-mode/lisp/org-mouse.elc > emacs -batch -q -no-site-file -eval "(setq load-path (cons (expand-file-name > \"./lisp/\") (cons \"/usr/local/share/emacs/site-lisp\" load-path)))" -f > batch-byte-compile lisp/org-odt.el > Wrote c:/Documents and Settings/kjambunathan/My Documents/My > Data/src/org-mode/lisp/org-odt.elc > > Don't you have htmlfontify.el in your version of Emacs? I thought it is > part of regular Emacs. Could you please check why this is so? May be > some adjustment of load path is required or htmlfontify.el has to be > installed. > >> >> Best, Martyn >> >> --- >> Org-mode version 7.7 (release_7.7.674.gc609) >> GNU Emacs 24.0.50.1 (x86_64-apple-darwin, NS apple-appkit-1038.35) >> of 2011-08-21 on virtualmac.porkrind.org >> >> >>
Re: [O] Where do these backgroud colors come from?
Hi Detlef, Detlef Steuer writes: > Suddenly I have some lines with colored backgrounds, some dark > blue, some light blue in my agenda view?! (invoked using C-c a a) Don't panic :) > I like the good old white background for all my agenda lines and want it > back. What has changed in recent versions of org and how can > those background colors be disabled? Sébastien introduced two new faces: - org-agenda-calendar-event - org-agenda-calendar-sexp they are now inheriting the default face. Thanks, -- Bastien
Re: [O] Where do these backgroud colors come from?
On Mon, 12 Dec 2011 09:56:15 +0100 Detlef Steuer wrote: > Hi! > > Just updated to current git version of org: > Org-mode version 7.7 (release_7.7.674.gc609) > > Running under emacs: > GNU Emacs 23.3.1 (x86_64-suse-linux-gnu, GTK+ Version 2.22.1) of 2011-10-07 > on build40 > > Suddenly I have some lines with colored backgrounds, some dark > blue, some light blue in my agenda view?! (invoked using C-c a a) > > There are _no_ entries in my .emacs telling anything about colors at > all. (AFAICT.) > > I like the good old white background for all my agenda lines and want it > back. What has changed in recent versions of org and how can > those background colors be disabled? Ok, I could customize them away myself. Sorry for the noise. May be it`s just a question of taste and not to be discussed. But: was that change in default colouring announced somewhere? thx Detlef > > Thx a lot > Detlef > > >
Re: [O] [bug] Commit 6f8ea8e breaks the build
Jambunathan K writes: > Don't you have htmlfontify.el in your version of Emacs? I thought it is > part of regular Emacs. Could you please check why this is so? May be > some adjustment of load path is required or htmlfontify.el has to be > installed. htmlfontify.el is part of Emacs since version >= 23.2. See this log in the ChangeLog.15 file in Emacs: 2009-11-19 Vivek Dasmohapatra * htmlfontify.el, hfy-cmap.el: New files. I pushed a fix that checks whether the user is running Emacs >= 23.2 and require htmlfontify.el only if so. Thanks, -- Bastien
Re: [O] Simple reference card browser by Anything.el
Tassilo Horn writes: > First of all, in the mean time it's mostly Thierry Volpiatto and > Rubikitch doing all the work on anything.el. Oops -- sorry I forgot to mention this, thanks for clarifying! -- Bastien
Re: [O] Simple reference card browser by Anything.el
Bastien writes: >> First of all, in the mean time it's mostly Thierry Volpiatto and >> Rubikitch doing all the work on anything.el. > > Oops -- sorry I forgot to mention this, thanks for clarifying! No problem, I'm still capable of accepting patches. ;-) Bye, Tassilo
Re: [O] [bug] Commit 6f8ea8e breaks the build
Jambunathan K wrote: > Martyn Jago writes: > > > Commit 6f8ea8e breaks the build. > > ... > ... > Don't you have htmlfontify.el in your version of Emacs? I thought it is > part of regular Emacs. Could you please check why this is so? May be > some adjustment of load path is required or htmlfontify.el has to be > installed. > FWIW, M-x locate-library gives me Library is file /usr/local/share/emacs/24.0.90/lisp/htmlfontify.elc so it *is* part of emacs24. Nick
Re: [O] org-search-goto.el - full text search to go to locations in your org buffers
Takaaki ISHIKAWA ieee.org> writes: > > If this package can handle `org-directory' having org files, > or `org-agenda-files', it is more handy. org-agenda-files should be no problem, since this package searches in all opened org buffers, and org opens all agenda files when building the agenda. As for org-directory the simplest solution is to have all org files opened from there and then this tool will search in those too. Since the invention of iswitchb, ido and similar tools we don't travel the buffer list sequentialy anymore, so you can have all of your org files opened in emacs all the time, because it doesn't matter if 5 files are open or 20.
Re: [O] Simple reference card browser by Anything.el
Hi Tassilo, Thank you for your advice! I'm going to discuss this topic at emacs-anything ML. Thanks, -- SAKURAI, Masashi (family, given) m.saku...@kiwanami.net
Re: [O] [bug] Commit 6f8ea8e breaks the build
Bastien writes: > Jambunathan K writes: > >> Don't you have htmlfontify.el in your version of Emacs? I thought it is >> part of regular Emacs. Could you please check why this is so? May be >> some adjustment of load path is required or htmlfontify.el has to be >> installed. > > htmlfontify.el is part of Emacs since version >= 23.2. See this > log in the ChangeLog.15 file in Emacs: > > 2009-11-19 Vivek Dasmohapatra > > * htmlfontify.el, hfy-cmap.el: New files. > > I pushed a fix that checks whether the user is running Emacs >= 23.2 > and require htmlfontify.el only if so. Thanks Bastien. I pushed one more fix which does a (require 'htmlfontify nil t) instead of (require 'htmlfontify). > Thanks,
Re: [O] Where do these backgroud colors come from?
El Mon, 12 Dec 2011 09:56:15 +0100 Detlef Steuer va escriure: > Suddenly I have some lines with colored backgrounds, some dark > blue, some light blue in my agenda view?! (invoked using C-c a a) > > There are _no_ entries in my .emacs telling anything about colors at > all. (AFAICT.) > With C-u C-x = on that line you can see which faces are being applied and customize them.
Re: [O] Function for html-preamble and html-postamble in org-publish
Hi Bill, Bill Jackson writes: > In version 7.7, a function provided to org-publish via :html-preamble or > :html-postamble no longer accepts a property list of export options. I do > not know if this change is a bug, or if it is deliberate. This is deliberate: I think the average user should not worry about handling opt-plist if she doesn't know what it is for. Still, as the manual says, you can use opt-plist within your function. Can you use it so? There was a problem with inserting the output string of the function, I just fixed this. Let me know if things are fine on your side. > I was able to restore the previous behavior simply by editing org-html.el > to again pass opt-plist on the two lines, but am interested in what the > future direction is for customizing the HTML output for org-publish. Was > this change unintentional, a deliberate minor change, or is org-publish or > org-html undergoing significant re-design? If this was deliberate, is > there an alternate method for customization functions to access the > property list? Well, this area is definitely going to evolve in the next few months. I try not to break anything in the meantime. Best, -- Bastien
Re: [O] [bug] Commit 6f8ea8e breaks the build
Jambunathan K writes: > I pushed one more fix which does a (require 'htmlfontify nil t) instead > of (require 'htmlfontify). Indeed, thanks! -- Bastien
Re: [O] org-search-goto.el - full text search to go to locations in your org buffers
Dear Tom, Hi. Thanks for your comment. I have verified the `org-agenda-files' is available for org-search-goto once I call org-agenda command. The solution for `org-directory' is good for active buffers. But I actually don't want to keep opening archived org files only for searching. So I will find another solution :-) Best regards, Takaaki Ishikawa @takaxp On 2011/12/12, at 23:50, Tom wrote: > Takaaki ISHIKAWA ieee.org> writes: > >> >> If this package can handle `org-directory' having org files, >> or `org-agenda-files', it is more handy. > > org-agenda-files should be no problem, since this package searches in > all opened org buffers, and org opens all agenda files when building > the agenda. > > As for org-directory the simplest solution is to have all org files > opened from there and then this tool will search in those too. > > Since the invention of iswitchb, ido and similar tools we don't travel > the buffer list sequentialy anymore, so you can have all of your org files > opened in emacs all the time, because it doesn't matter if 5 files are > open or 20. > signature.asc Description: Message signed with OpenPGP using GPGMail
[O] Refile targets fail with certain filename
Hello,
This was a very tricky problem to work around. I have two directories
("notesmine" and "personal") that I use to refile stuff to. I refile to my
notesmine directory once every few months, so I was baffled last night
when I started getting "Wrong type argument:
stringp, nil" when I wanted to refile to my notesmine directory.
;; Setup
;; My /Users/nate/Documents/notesmine directory has a file called
"org-mode.org" in it.
;; Begin Code
(defun njn/personal-org-files()
(interactive)
(directory-files "/Users/nate/Documents/notesmine" 't "^[^.].*org$")
)
(defun njn/refile-targets-personal()
(interactive)
(setq org-refile-targets
(quote ((njn/personal-org-files :maxlevel . 5
)
;; I would then run M-x njn/refile-targets-personal, and
;; then press Ctrl-C Ctrl-W to refile a heading in one of my org files.
;; Then, I would see the "Wrong type argument: stringp nil"
I found that the problem *disappears* when I remove or re-name
the "org-mode.org" file from my notesmine directory!
I refile to my personal directory all the time, and I found that if
I move the "org-mode.org" file to my personal directory, (or create a blank
"org-mode.org" file in my personal directory then I would start
getting the same "Wrong type argument stringp, nil" error when refiling
to my personal directory.
So, as a geek, I'm interested in why the "org-mode.org" filename causes
this error. I've reproduced the problem with the simple code above, so
I hope someone else can say "Yes, I can reproduce the problem" and I will
have done some good :-)
Can anyone reproduce the error and tell me if "org-mode.org" is a keyword or
function or something, or is the problem in the regular expression I'm
using to select
my refile targets?
Thanks,
--Nate
[O] [Accepted] Improving bug reporting documentation
Patch 1033 (http://patchwork.newartisans.com/patch/1033/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3C2008000620.6fd433b6%40kuru.homelinux.net%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O] Improving bug reporting documentation
> Date: Tue, 08 Nov 2011 04:06:20 -
> From: suvayu ali
> X-Patchwork-Id: 1033
> Message-Id: <2008000620.6fd43...@kuru.homelinux.net>
> To: Org mode mailing list
>
> Hi Bastien and others,
>
> Lately I have been seeing a lot of bug reports sent using the
> org-submit-bug-report. The reporter usually reports the bug from a
> session they have been using with their full blown customisations. And
> often they are requested to reproduce the bug with emacs -Q. So I
> thought it would be easier if the manual mentioned this little detail.
> A patch is attached.
>
> Hope this helps.
>
> PS: I marked the patch as TINY CHANGE.
>
>
> diff --git a/doc/org.texi b/doc/org.texi
> index 4a547d0..1bc9a98 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -987,6 +987,36 @@ @section Feedback
> that you only need to add your description. If you re not sending the Email
> from within Emacs, please copy and paste the content into your Email program.
>
> +Sometimes you might face a problem due to an error in your Emacs or Org-mode
> +setup. Before reporting a bug, it is very helpful to start Emacs with
> minimal
> +customisations and reproduce the problem. Doing so often helps you determine
> +if the problem is with your customisation or with Org-mode itself. You can
> +start a typical minimal session with a command like the example below.
> +
> +@example
> +$ emacs -Q -l /path/to/minimal-org.el
> +@end example
> +
> +However if you are using Org-mode as distributed with Emacs, a minimal setup
> +is not necessary. In that case it is sufficient to start Emacs as
> @code{emacs
> +-Q}. The @code{minimal-org.el} setup file can have contents as shown below.
> +
> +@example
> +;;; Minimal setup to load latest `org-mode'
> +
> +;; activate debugging
> +(setq debug-on-error t
> + debug-on-signal nil
> + debug-on-quit nil)
> +
> +;; add latest org-mode to load path
> +(add-to-list 'load-path (expand-file-name "/path/to/org-mode/lisp"))
> +(add-to-list 'load-path (expand-file-name "/path/to/org-mode/contrib/lisp"))
> +
> +;; activate org
> +(require 'org-install)
> +@end example
> +
> If an error occurs, a backtrace can be very useful (see below on how to
> create one). Often a small example file helps, along with clear information
> about:
>
[O] [Accepted] Patch: maintain window configuration when org-agenda-follow-indirect is set
Patch 1004 (http://patchwork.newartisans.com/patch/1004/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3Cm2bot77c1a.fsf%40pluto.luannocracy.com%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [O] Patch: maintain window configuration when > org-agenda-follow-indirect is set > Date: Mon, 24 Oct 2011 00:17:37 - > From: Dave Abrahams > X-Patchwork-Id: 1004 > Message-Id: > To: emacs-orgmode@gnu.org > > > > > >From 5adafd491f520908c8ee180c1b0d63d877fa8547 Mon Sep 17 00:00:00 2001 > From: Dave Abrahams > Date: Sun, 23 Oct 2011 14:41:44 -0400 > Subject: [PATCH] Maintain stable window configuration when > org-agenda-follow-indirect is set > > Without this change, org-agenda-follow-indirect tends to cause the > window configration to bounce around chaotically as you move from item > to item. > --- > lisp/org-agenda.el | 17 + > 1 files changed, 17 insertions(+), 0 deletions(-) > > diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el > index e4b1ba5..639ee23 100644 > --- a/lisp/org-agenda.el > +++ b/lisp/org-agenda.el > @@ -7168,6 +7168,23 @@ With numerical prefix arg ARG, go up to this level and > then take that tree. > With a \\[universal-argument] prefix, make a separate frame for this tree > (i.e. don't > use the dedicated frame)." >(interactive) > + (if (and current-prefix-arg (listp current-prefix-arg)) > + (org-agenda-do-tree-to-indirect-buffer) > +(let ((agenda-window (selected-window)) > + (indirect-window (get-buffer-window org-last-indirect-buffer))) > + (save-window-excursion (org-agenda-do-tree-to-indirect-buffer)) > + (unwind-protect > + (progn > +(unless indirect-window > + (setq indirect-window (split-window agenda-window))) > +(select-window indirect-window) > +(switch-to-buffer org-last-indirect-buffer :norecord) > +(fit-window-to-buffer indirect-window)) > +(select-window agenda-window) > + > +(defun org-agenda-do-tree-to-indirect-buffer () > + "Implements org-agenda-tree-to-indirect-buffer, but > +doesn't attempt to manage stability of the window configuration." >(org-agenda-check-no-diary) >(let* ((marker (or (org-get-at-bol 'org-marker) >(org-agenda-error))) > -- > 1.7.6.1 > >
Re: [O] Patch: maintain window configuration when org-agenda-follow-indirect is set
Dave Abrahams writes: > Without this change, org-agenda-follow-indirect tends to cause the > window configration to bounce around chaotically as you move from item > to item. Applied, thanks. I had to update the commit message: it should contain an Emacs-ready ChangeLog message. -- Bastien
Re: [O] Improving bug reporting documentation
Suvayu Ali writes: > Lately I have been seeing a lot of bug reports sent using the > org-submit-bug-report. The reporter usually reports the bug from a > session they have been using with their full blown customisations. And > often they are requested to reproduce the bug with emacs -Q. So I > thought it would be easier if the manual mentioned this little detail. > A patch is attached. > > Hope this helps. It does! Sorry for being late in applying this, and thanks again. -- Bastien
Re: [O] Refile targets fail with certain filename
Nathan Neff wrote:
> Hello,
>
> This was a very tricky problem to work around. I have two directories
> ("notesmine" and "personal") that I use to refile stuff to. I refile to my
> notesmine directory once every few months, so I was baffled last night
> when I started getting "Wrong type argument:
> stringp, nil" when I wanted to refile to my notesmine directory.
>
> ;; Setup
> ;; My /Users/nate/Documents/notesmine directory has a file called
> "org-mode.org" in it.
>
> ;; Begin Code
> (defun njn/personal-org-files()
>(interactive)
>(directory-files "/Users/nate/Documents/notesmine" 't "^[^.].*org$")
> )
>
> (defun njn/refile-targets-personal()
> (interactive)
> (setq org-refile-targets
> (quote ((njn/personal-org-files :maxlevel . 5
> )
>
> ;; I would then run M-x njn/refile-targets-personal, and
> ;; then press Ctrl-C Ctrl-W to refile a heading in one of my org files.
> ;; Then, I would see the "Wrong type argument: stringp nil"
>
> I found that the problem *disappears* when I remove or re-name
> the "org-mode.org" file from my notesmine directory!
>
> I refile to my personal directory all the time, and I found that if
> I move the "org-mode.org" file to my personal directory, (or create a blank
> "org-mode.org" file in my personal directory then I would start
> getting the same "Wrong type argument stringp, nil" error when refiling
> to my personal directory.
>
> So, as a geek, I'm interested in why the "org-mode.org" filename causes
> this error. I've reproduced the problem with the simple code above, so
> I hope someone else can say "Yes, I can reproduce the problem" and I will
> have done some good :-)
>
> Can anyone reproduce the error and tell me if "org-mode.org" is a keyword or
> function or something, or is the problem in the regular expression I'm
> using to select
> my refile targets?
>
I cannot reproduce it, but the setup needed is probably sufficiently complicated
to make the attempt futile.
Here's the minimal .emacs I tried:
--8<---cut here---start->8---
;;; -*- mode: emacs-lisp -*-
;;; constant part
(add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/lisp"))
(add-to-list 'load-path (expand-file-name
"~/src/emacs/org/org-mode/contrib/lisp"))
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
(require 'org-install)
(setq debug-on-error t)
(setq eval-expression-print-length nil)
(setq eval-expression-print-level nil)
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
Nathan Neff's problem config.
;; Setup
;; My /Users/nate/Documents/notesmine directory has a file called
"org-mode.org" in it.
(setq org-agenda-files '("/home/nick/lib/notesmine"))
;; Begin Code
(defun njn/personal-org-files()
(interactive)
(directory-files "/home/nick/lib/notesmine" 't "^[^.].*org$")
)
(defun njn/refile-targets-personal()
(interactive)
(setq org-refile-targets
(quote ((njn/personal-org-files :maxlevel . 5
)
;; I would then run M-x njn/refile-targets-personal, and
;; then press Ctrl-C Ctrl-W to refile a heading in one of my org files.
;; Then, I would see the "Wrong type argument: stringp nil"
;;; end of Nathan Neff's problem config
--8<---cut here---end--->8---
and /home/nick/lib/notesmine contains two files, tasks.org and org-mode.org:
tasks.org:
--8<---cut here---start->8---
* TODO foo
SCHEDULED: <2011-12-12 Mon>
** DONE bar
SCHEDULED: <2011-12-12 Mon>
--8<---cut here---end--->8---
org-mode.org:
--8<---cut here---start->8---
* one
** two
*** three
four
* five
** TODO foo
SCHEDULED: <2011-12-12 Mon>
--8<---cut here---end--->8---
After doing M-x njn/refile-targets-personal, I can refile from tasks.org (to
either
tasks.org or org-mode.org) with C-c C-w with no problems.
I'd suggest you turn on debug-on-error and post the backtrace, preferably
with a minimal .emacs similar to the above and none of your other
customizations: emacs -q -l /path/to/minimal/dot/emacs
Nick
Re: [O] Bug: Recurring TODO spuriously blocked [7.7]
pin...@iro.umontreal.ca (François Pinard) writes: > > Whenever a TODO is scheduled with a recurrence (with .+ or ++), forcing > the state to DONE is a mere way to trigger Org into setting the state to > TODO again, yet with the scheduled date updated for the next repetition. > Setting to DONE merely means that this repetition is done, which is not > the same as being forever DONE. In fact, setting a repeated schedule to > DONE is really a way of updating the schedule; the intent relies on the > mechanics by which the DONE state is just a transient way to TODO again. > > Now, within ~/.emacs, I have org-enforce-todo-dependencies set to t, for > good purposes. But then, I get spurious: > >byte-code: TODO state change from TODO to DONE blocked > > trying to schedule the next repetition. todo-dependencies should likely > never be enforced for repeated entries, even if enforced otherwise, as > enforcing for repetitions with the current Org mechanics has no meaning, > at least as I undestand Org so far. You can set a NOBLOCKING property to t to skip the dependency check for repeated tasks. * TODO Some Repeating Task SCHEDULED: <2011-12-16 Fri 15:30 ++1w> :PROPERTY: :NOBLOCKING: t :END: Regards, Bernt
[O] A presentation tool for org-mode
Dear all, Hi. I'm writing a presentation tool for Org-mode named `org-tree-slide'. This elisp will help you when a live editable presentation is required. And it is also possible to access TODO items sequentially with narrowing. Since org-tree-slide treats a tree as a single slide by org-narrow-to-subtree, it is different from an exporter to HTML and other presentation tools customized for good visualization. To move between slides, just type and . Please find org-tree-slide and review it. You can download from the following direct link: https://raw.github.com/takaxp/org-tree-slide/master/org-tree-slide.el org-tree-slide is a minor mode for Org-mode. I recommend that these key bindings are set into your .emacs. (global-set-key (kbd "") 'org-tree-slide-mode) (global-set-key (kbd "S-") 'org-tree-slide-skip-done-toggle) Preset profiles are defined in org-tree-slide. 1. `org-tree-slide-simple-profile'; Simple use 2. `org-tree-slide-presentation-profile' ; Presentation use 3. `org-tree-slide-narrowing-control-profile' ; TODO Pursuit with narrowing These functions set user variables for each using scenario. You can find more detail in the file. I hope this will help you and I'm waiting for your comments. Best regards, Takaaki Ishikawa @takaxp signature.asc Description: Message signed with OpenPGP using GPGMail
[O] [PATCH] Orgcard: Correct markup in 'Timestamps' section
Orgcard: Correct markup in 'Timestamps' section
* doc/orgcard.tex: Correct one markup in 'Timestamps' section
>From 756e4eb6aca0e1b72f8fa55537005d2b617b83f8 Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Mon, 12 Dec 2011 12:29:46 +0100
Subject: [PATCH] Orgcard: Correct markup in 'Timestamps' section
* doc/orgcard.tex: Correct one markup in 'Timestamps' section
---
doc/orgcard.tex |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/doc/orgcard.tex b/doc/orgcard.tex
index 38df521..f543e91 100644
--- a/doc/orgcard.tex
+++ b/doc/orgcard.tex
@@ -526,7 +526,7 @@ after ``{\tt :}'', and dictionary words elsewhere.
\section{Timestamps}
\key{prompt for date and insert timestamp}{C-c .}
-\key{like \kbd{C-c} . but insert date and time format}{C-u C-c .}
+\key{like \kbd{C-c .} but insert date and time format}{C-u C-c .}
\key{like \kbd{C-c .} but make stamp inactive}{C-c !} % FIXME
\key{insert DEADLINE timestamp}{C-c C-d}
\key{insert SCHEDULED timestamp}{C-c C-s}
--
1.7.4.1
[O] [PATCH] Org manual: Fix double-spaces at the end of sentences
Org manual: Fix double-spaces at the end of sentences
* doc/org.texi: End sentences with two spaces.
>From 19e39b67f4a8dbee3f1015f636fac4f77e59d3c2 Mon Sep 17 00:00:00 2001
From: Julian Gehring
Date: Mon, 12 Dec 2011 19:19:20 +0100
Subject: [PATCH] Org manual: Fix double-spaces at the end of sentences
* doc/org.texi: End sentences with two spaces.
---
doc/org.texi | 36 ++--
1 files changed, 18 insertions(+), 18 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index ff9bb7e..2cbb7d1 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6023,7 +6023,7 @@ Insert a dynamic block (@pxref{Dynamic blocks}) containing a clock
report as an Org-mode table into the current file. When the cursor is
at an existing clock table, just update it. When called with a prefix
argument, jump to the first clock report in the current document and
-update it. The clock table always includes also trees with
+update it. The clock table always includes also trees with
@code{:ARCHIVE:} tag.
@orgcmdkkc{C-c C-c,C-c C-x C-u,org-dblock-update}
Update dynamic block at point. The cursor needs to be in the
@@ -6642,7 +6642,7 @@ buffer again after capture is completed.
In the template itself, special @kbd{%}-escapes@footnote{If you need one of
these sequences literally, escape the @kbd{%} with a backslash.} allow
-dynamic insertion of content. The templates are expanded in the order given here:
+dynamic insertion of content. The templates are expanded in the order given here:
@smallexample
%[@var{file}] @r{insert the contents of the file given by @var{file}.}
@@ -10896,7 +10896,7 @@ newly created file. For additional configuration options
@pxref{x-overriding-factory-styles,,Overriding factory styles}.
If you would like to choose a style on a per-file basis, you can use the
-@code{#+ODT_STYLES_FILE} option. A typical setting will look like
+@code{#+ODT_STYLES_FILE} option. A typical setting will look like
@example
#+ODT_STYLES_FILE: "/path/to/example.ott"
@@ -10932,7 +10932,7 @@ internal links. It creates Internet-style links for all other links.
Export of native Org-mode tables (@pxref{Tables}) and simple @file{table.el}
tables is supported. However, export of complex @file{table.el} tables -
-tables that have column or row spans - is not supported. Such tables are
+tables that have column or row spans - is not supported. Such tables are
stripped from the exported document.
By default, a table is exported with top and bottom frames and with
@@ -10944,7 +10944,7 @@ are interpreted as weighted ratios with the default weight being 1}
@cindex #+ATTR_ODT
If you are not satisfied with the default formatting of tables, you can
create custom table styles and associate them with a table using
-the @code{#+ATTR_ODT} line. @xref{Customizing tables in @acronym{ODT} export}.
+the @code{#+ATTR_ODT} line. @xref{Customizing tables in @acronym{ODT} export}.
@node Images in @acronym{ODT} export, Math formatting in @acronym{ODT} export, Tables in @acronym{ODT} export, OpenDocument Text export
@subsection Images in @acronym{ODT} export
@@ -11171,11 +11171,11 @@ that would be of interest to power users.
@cindex doc, docx
The @acronym{ODT} exporter adds support for exporting Org outlines to formats
-that are not supported natively by Org. It also adds support to convert
+that are not supported natively by Org. It also adds support to convert
document from one format to another. To use these features, you need to
configure a command-line converter. Once a command-line converter is
configured you can use it to extend the list of formats to which Org can
-export. @xref{x-export-to-other-formats,,Automatically exporting to other
+export. @xref{x-export-to-other-formats,,Automatically exporting to other
formats}. You can also use it to perform one-off document conversion as
detailed below.
@@ -11186,7 +11186,7 @@ detailed below.
Convert an existing document from one format to another as determined by the
variable @code{org-export-odt-convert-capabilities}
(@pxref{x-odt-converter-capabilities,,Configure converter
-capabilities}). @strong{Please note} that you can use this command to even
+capabilities}). @strong{Please note} that you can use this command to even
convert documents that are produced outside of Org and in other formats than
@acronym{ODT} format.
@end table
@@ -11209,7 +11209,7 @@ distribution.
@vindex org-odt-data-dir
This converter is distributed as a LibreOffice extension and can be found in
-your Org distribution. See the subdirectory pointed to by the variable
+your Org distribution. See the subdirectory pointed to by the variable
@code{org-odt-data-dir}.
@end enumerate
@@ -11360,11 +11360,11 @@ file. The use of this feature is better illustrated with couple of examples.
@item Embedding ODT tags as part of regular text
You can include simple OpenDocument tags by prefixing them with
-@samp{@@}. For example, to highlight a
Re: [O] What do you use to identify projects (in the GTD sense)
Hi Bernt, sorry, I wasn't more specific. My problem is with projects that consist of subprojects and simple tasks. Consider the following scenario: * TODO Project ** TODO Subproject A *** NEXT Task A1 *** TODO Task A2 ** NEXT Task B ** TODO Task C ** TODO ... Task B and C have to be done in order. However, Subproject A is somewhat independent and can be done in parallel, while working on Task B and C. When I mark Task B as DONE, the Project is still unstuck because of the a NEXT task in Subproject A. Meaning that I never get to schedule Task C or any following tasks until I'm done with Subproject A. One solution to this problem would be to trigger a state change in Task C automatically when Task B is done. But I'm afraid that is too much setup and also not flexible enough. Often, when I consider a stuck project I schedule next actions that I haven't thought of before or even put the project on a someday list. Another solution would be to implement a stale projects list, i.e. a list of projects that have defined next actions, but haven't seen any work in the last X days. Cheers, Viktor PS: Your org-mode site is generally the bomb! Bernt Hansen wrote: > Viktor Rosenfeld writes: > > > I use Bernt's approach with a few modifications. Basically I don't use > > subprojects. I think Bernt's handling of subprojects is broken, because > > a NEXT keyword burried in a subproject keeps the entire project off the > > stuck projects lists. (Please correct me if I'm wrong.) > > It's possible it's broken :) but subprojects are considered separately > for the stuck project list. It is true that if any subproject has a > NEXT task then the overall project is not stuck (but doesn't that makes > sense?) > > * TODO Project > ** TODO SubProject A > *** NEXT Task One > ** TODO SubProject B > *** TODO Task Two > > In the above layout Project is not stuck (it has Task One as a NEXT > task) but SubProject B is stuck (it has no next task and shows up on the > stuck project list) > > Also as soon as Task One is DONE than both SubProject A and Project are > both stuck until a new NEXT task is identified (or they are in turn > marked DONE) > > Regards, > Bernt >
[O] [Accepted] Orgcard: Correct markup in 'Timestamps' section
Patch 1068 (http://patchwork.newartisans.com/patch/1068/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3Cjc5fuu%24ppc%241%40dough.gmane.org%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O] Orgcard: Correct markup in 'Timestamps' section
> Date: Mon, 12 Dec 2011 23:08:30 -
> From: Julian Gehring
> X-Patchwork-Id: 1068
> Message-Id:
> To: emacs-orgmode@gnu.org
>
> Orgcard: Correct markup in 'Timestamps' section
>
> * doc/orgcard.tex: Correct one markup in 'Timestamps' section
>
>
> >From 756e4eb6aca0e1b72f8fa55537005d2b617b83f8 Mon Sep 17 00:00:00 2001
> From: Julian Gehring
> Date: Mon, 12 Dec 2011 12:29:46 +0100
> Subject: [PATCH] Orgcard: Correct markup in 'Timestamps' section
>
> * doc/orgcard.tex: Correct one markup in 'Timestamps' section
> ---
> doc/orgcard.tex |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/doc/orgcard.tex b/doc/orgcard.tex
> index 38df521..f543e91 100644
> --- a/doc/orgcard.tex
> +++ b/doc/orgcard.tex
> @@ -526,7 +526,7 @@ after ``{\tt :}'', and dictionary words elsewhere.
> \section{Timestamps}
>
> \key{prompt for date and insert timestamp}{C-c .}
> -\key{like \kbd{C-c} . but insert date and time format}{C-u C-c .}
> +\key{like \kbd{C-c .} but insert date and time format}{C-u C-c .}
> \key{like \kbd{C-c .} but make stamp inactive}{C-c !} % FIXME
> \key{insert DEADLINE timestamp}{C-c C-d}
> \key{insert SCHEDULED timestamp}{C-c C-s}
> --
> 1.7.4.1
>
>
[O] [Accepted] Org manual: Fix double-spaces at the end of sentences
Patch 1069 (http://patchwork.newartisans.com/patch/1069/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3Cjc5h3b%242jq%241%40dough.gmane.org%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [O] Org manual: Fix double-spaces at the end of sentences
> Date: Mon, 12 Dec 2011 23:27:55 -
> From: Julian Gehring
> X-Patchwork-Id: 1069
> Message-Id:
> To: emacs-orgmode@gnu.org
>
> Org manual: Fix double-spaces at the end of sentences
>
> * doc/org.texi: End sentences with two spaces.
>
>
> >From 19e39b67f4a8dbee3f1015f636fac4f77e59d3c2 Mon Sep 17 00:00:00 2001
> From: Julian Gehring
> Date: Mon, 12 Dec 2011 19:19:20 +0100
> Subject: [PATCH] Org manual: Fix double-spaces at the end of sentences
>
> * doc/org.texi: End sentences with two spaces.
> ---
> doc/org.texi | 36 ++--
> 1 files changed, 18 insertions(+), 18 deletions(-)
>
> diff --git a/doc/org.texi b/doc/org.texi
> index ff9bb7e..2cbb7d1 100644
> --- a/doc/org.texi
> +++ b/doc/org.texi
> @@ -6023,7 +6023,7 @@ Insert a dynamic block (@pxref{Dynamic blocks})
> containing a clock
> report as an Org-mode table into the current file. When the cursor is
> at an existing clock table, just update it. When called with a prefix
> argument, jump to the first clock report in the current document and
> -update it. The clock table always includes also trees with
> +update it. The clock table always includes also trees with
> @code{:ARCHIVE:} tag.
> @orgcmdkkc{C-c C-c,C-c C-x C-u,org-dblock-update}
> Update dynamic block at point. The cursor needs to be in the
> @@ -6642,7 +6642,7 @@ buffer again after capture is completed.
>
> In the template itself, special @kbd{%}-escapes@footnote{If you need one of
> these sequences literally, escape the @kbd{%} with a backslash.} allow
> -dynamic insertion of content. The templates are expanded in the order given
> here:
> +dynamic insertion of content. The templates are expanded in the order given
> here:
>
> @smallexample
> %[@var{file}] @r{insert the contents of the file given by @var{file}.}
> @@ -10896,7 +10896,7 @@ newly created file. For additional configuration
> options
> @pxref{x-overriding-factory-styles,,Overriding factory styles}.
>
> If you would like to choose a style on a per-file basis, you can use the
> -@code{#+ODT_STYLES_FILE} option. A typical setting will look like
> +@code{#+ODT_STYLES_FILE} option. A typical setting will look like
>
> @example
> #+ODT_STYLES_FILE: "/path/to/example.ott"
> @@ -10932,7 +10932,7 @@ internal links. It creates Internet-style links for
> all other links.
>
> Export of native Org-mode tables (@pxref{Tables}) and simple @file{table.el}
> tables is supported. However, export of complex @file{table.el} tables -
> -tables that have column or row spans - is not supported. Such tables are
> +tables that have column or row spans - is not supported. Such tables are
> stripped from the exported document.
>
> By default, a table is exported with top and bottom frames and with
> @@ -10944,7 +10944,7 @@ are interpreted as weighted ratios with the default
> weight being 1}
> @cindex #+ATTR_ODT
> If you are not satisfied with the default formatting of tables, you can
> create custom table styles and associate them with a table using
> -the @code{#+ATTR_ODT} line. @xref{Customizing tables in @acronym{ODT}
> export}.
> +the @code{#+ATTR_ODT} line. @xref{Customizing tables in @acronym{ODT}
> export}.
>
> @node Images in @acronym{ODT} export, Math formatting in @acronym{ODT}
> export, Tables in @acronym{ODT} export, OpenDocument Text export
> @subsection Images in @acronym{ODT} export
> @@ -11171,11 +11171,11 @@ that would be of interest to power users.
> @cindex doc, docx
>
> The @acronym{ODT} exporter adds support for exporting Org outlines to formats
> -that are not supported natively by Org. It also adds support to convert
> +that are not supported natively by Org. It also adds support to convert
> document from one format to another. To use these features, you need to
> configure a command-line converter. Once a command-line converter is
> configured you can use it to extend the list of formats to which Org can
> -export. @xref{x-export-to-other-formats,,Automatically exporting to other
> +export. @xref{x-export-to-other-formats,,Automatically exporting to other
> formats}. You can also use it to perform one-off document conversion as
> detailed below.
>
> @@ -11186,7 +11186,7 @@ detailed below.
> Convert an existing document from one format to another as determined by the
> variable @code{org-export-odt-convert-capabilities}
> (@pxref{x-odt-converter-capabilities,,Configure converter
> -capabilities}). @strong{Please note} that you can use this command to even
> +capabilities}). @strong{
Re: [O] Bug: Recurring TODO spuriously blocked [7.7]
Bernt Hansen writes: > pin...@iro.umontreal.ca (François Pinard) writes: >> todo-dependencies should likely never be enforced for repeated >> entries, even if enforced otherwise, as enforcing for repetitions >> with the current Org mechanics has no meaning, at least as I >> undestand Org so far. > You can set a NOBLOCKING property to t to skip the dependency check for > repeated tasks. > * TODO Some Repeating Task > SCHEDULED: <2011-12-16 Fri 15:30 ++1w> > :PROPERTY: > :NOBLOCKING: t > :END: Thanks for the hint, Bernt. I'll use it for now. I still think this is a work around a real problem, which would ideally be corrected. Regardless of blocking being configured or not for non-repeating tasks, repeated tasks should never be blocked, shouldn't they? François
[O] [PATCH] Dynamically demote included file relatively to the current heading level
Hello,
You can get the following patchset by pulling:
git pull git://git.baby-gnu.net/org-mode dad/add-level-to-headings
Regards.
This patch permits a more flexible usage than :minlevel.
It's possible to include files with their heading demoted by 'X' levels
relatively to the current one.
This is useful to make some glue documentation based on many little
parts:
- each little part starts its heading at level 1
- each part can include other parts:
* as children by setting ":addlevel 1"
* as same level by setting ":addlevel 0"
The test files are provided but 'org-test-compare-with-file' is TODO.
* lisp/org-exp.el (org-export-handle-include-files): Save heading level
of the parent of the included file as "currentlevel".
Included files are demoted relatively by "addlevel".
* lisp/org-exp.el (org-get-file-contents): Demote included file
relatively to "partentlevel" by "addlevel" increment.
* testing/examples/include-master.org: Entry point of the "addlevel" test
case.
* testing/examples/include-1.org: File included by include-master.org,
both at level1 (i.e. no addlevel) and level2.
* testing/examples/include-2.org: File included by include-1.org, level
incremented by one relatively to include-1.org
* testing/examples/include-addlevel.txt: Attended result to ASCII
export.
---
lisp/org-exp.el | 24 ++---
testing/examples/include-1.org|8
testing/examples/include-2.org|4 ++
testing/examples/include-addlevel.txt | 58 +
testing/examples/include-master.org | 15
5 files changed, 103 insertions(+), 6 deletions(-)
create mode 100644 testing/examples/include-1.org
create mode 100644 testing/examples/include-2.org
create mode 100644 testing/examples/include-addlevel.txt
create mode 100644 testing/examples/include-master.org
diff --git a/lisp/org-exp.el b/lisp/org-exp.el
index eae5be7..7e0512d 100644
--- a/lisp/org-exp.el
+++ b/lisp/org-exp.el
@@ -2381,13 +2381,14 @@ TYPE must be a string, any of:
(defun org-export-handle-include-files ()
"Include the contents of include files, with proper formatting."
(let ((case-fold-search t)
- params file markup lang start end prefix prefix1 switches all minlevel
lines)
+ params file markup lang start end prefix prefix1 switches all
currentlevel minlevel addlevel lines)
(goto-char (point-min))
(while (re-search-forward "^#\\+INCLUDE:?[ \t]+\\(.*\\)" nil t)
(setq params (read (concat "(" (match-string 1) ")"))
prefix (org-get-and-remove-property 'params :prefix)
prefix1 (org-get-and-remove-property 'params :prefix1)
minlevel (org-get-and-remove-property 'params :minlevel)
+ addlevel (org-get-and-remove-property 'params :addlevel)
lines (org-get-and-remove-property 'params :lines)
file (org-symname-or-string (pop params))
markup (org-symname-or-string (pop params))
@@ -2396,6 +2397,8 @@ TYPE must be a string, any of:
switches (mapconcat #'(lambda (x) (format "%s" x)) params " ")
start nil end nil)
(delete-region (match-beginning 0) (match-end 0))
+ (setq currentlevel (or (org-current-level)
+0))
(if (or (not file)
(not (file-exists-p file))
(not (file-readable-p file)))
@@ -2411,7 +2414,7 @@ TYPE must be a string, any of:
end (format "#+end_%s" markup
(insert (or start ""))
(insert (org-get-file-contents (expand-file-name file)
- prefix prefix1 markup minlevel lines))
+ prefix prefix1 markup currentlevel
minlevel addlevel lines))
(or (bolp) (newline))
(insert (or end ""
all))
@@ -2428,13 +2431,15 @@ TYPE must be a string, any of:
(when intersection
(error "Recursive #+INCLUDE: %S" intersection))
-(defun org-get-file-contents (file &optional prefix prefix1 markup minlevel
lines)
+(defun org-get-file-contents (file &optional prefix prefix1 markup parentlevel
minlevel addlevel lines)
"Get the contents of FILE and return them as a string.
If PREFIX is a string, prepend it to each line. If PREFIX1
is a string, prepend it to the first line instead of PREFIX.
If MARKUP, don't protect org-like lines, the exporter will
-take care of the block they are in. If LINES is a string
-specifying a range of lines, include only those lines ."
+take care of the block they are in. If ADDLEVEL is a number,
+demote included file to current heading level+ADDLEVEL.
+If LINES is a string specifying a range of lines,
+include only those lines."
(if (stringp markup) (setq markup (downcase markup)))
(with-temp-buffer
(insert-file-contents file)
@@ -2467,7 +2472,14 @@ specifying a range of lines, include only those lines ."
(when minlevel
(dotimes (lvl minlevel
[O] Search links in a list of files
Hello, As I want to write some documentation with org-mode, I'm looking for a way to manage an list of files in which org-mode will look for links, or better, a list or directory to scan. For example: - in file1.org, I link something like [[file:file2.org::#some-point][some point in some file]] - in file2.org I have a property "CUSTOM_ID: some-point" somewhere. If I reorganize my documentation and move file2.org in some subdirectory, like examples/file2.org, I would like to avoid changing all the references to "file2::#some-point". Maybe a link like [[search:PATH::SOMETHING]], with SOMETHING like in search-options[1]. We could define a per-org file PATH, with something like "#+LINK_SEARCH_PATH: path1, path2, ..." Any idea about this issue? Regards. Footnotes: [1] http://orgmode.org/manual/Search-options.html#Search-options -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1 pgpFOcRbi3DWm.pgp Description: PGP signature
Re: [O] What do you use to identify projects (in the GTD sense)
Viktor Rosenfeld writes: > Hi Bernt, > > sorry, I wasn't more specific. My problem is with projects that consist > of subprojects and simple tasks. Consider the following scenario: > > * TODO Project > ** TODO Subproject A > *** NEXT Task A1 > *** TODO Task A2 > ** NEXT Task B > ** TODO Task C > ** TODO ... > > Task B and C have to be done in order. However, Subproject A is somewhat > independent and can be done in parallel, while working on Task B and C. > > When I mark Task B as DONE, the Project is still unstuck because of the > a NEXT task in Subproject A. Meaning that I never get to schedule Task C > or any following tasks until I'm done with Subproject A. > > One solution to this problem would be to trigger a state change in Task > C automatically when Task B is done. But I'm afraid that is too much > setup and also not flexible enough. Often, when I consider a stuck > project I schedule next actions that I haven't thought of before or even > put the project on a someday list. > > Another solution would be to implement a stale projects list, i.e. a > list of projects that have defined next actions, but haven't seen any > work in the last X days. Okay - I have a custom skip function for identifying stuck projects. You should be able to create one that only looks at immediate subtasks to address the above example. This would make project independent of subprojects when determining if it is stuck or not without requiring you to rearrange your task hierarchy. > > Cheers, > Viktor > > PS: Your org-mode site is generally the bomb! Thanks :) HTH, Bernt
Re: [O] [BUG] Various problems with org-odt export
Hi, Thanks, the problem was indeed with setup and not with org-odt as such, so I'm really sorry about the noise. But I'm wondering if something needs to be done about the Makefile to make sure etc/styles installs. Background: I'm in the habit of compiling and installing Org each time I pull, and as I'm on a Mac, that means changing a couple of installation paths in the Makefile so as to install into Emacs.app. All this probably puts me in a small minority of users. The lisp files got installed all right, including the up-to-date org-odt.el and org-odt.elc. And yes, I did for some reason have an older org-odt.el in my loadpath that was interfering. Very embarrassing. But after I got rid of that, I was definitely running the new org-odt. However, things still did not work, and the reason seems to be that the etc/styles directory did not get installed into the appropriate etc directory in Emacs.app. Because the directory was missing, org-odt-styles-dir never got set; it kept throwing an error that it couldn't find the factory styles. I copied the etc/styles dir manually over into Emacs.app, and now everything seems to work. Could it be that, because there hasn't been anything to install from the etc directory before, the Org-mode Makefile doesn't take care of it? The only reference to "etc/" I've found in the Makefile is in connection with ELPA, which I don't use. Yours, Christian On 12/12/11 2:46 PM, Jambunathan K wrote: Christian Hi, Either something's gone wrong with my setup, or there are a number of issues to straighten out after org-odt moved to core. Here's what I have so far (with Org 7.7 pulled this morning, Emacs 23.3.1, on a Mac). Issues 1 and 3 look urgent. 1. The org-export-odt-styles-file variable still points to "~/src/base/org-mode/contrib/odt/styles.xml" as the default style template. The defcustom comes with a FIXME note, and that has become urgent, as the lack of a default styles file in the default place would cause Org-odt export to fail out of the box for most users. I'm not sure where this should point, but I assume it should not point to anything in contrib any longer. The default style files have been moved from contrib/odt/styles to etc/styles. Make sure that you are loading the right version of org-odt with M-x locate-library. Also the following variables: C-h v org-odt-lib-dir => "~/src/org-mode/lisp/" C-h v org-odt-styles-dir => "~/src/org-mode/etc/styles/" The first variable says wherefrom org-odt is loaded. The second variable -- which was newly introduced a 2-3 days ago -- should tell where the default style files come from. If you are unable to find the second variable, then it most postively suggests that it is the old org-odt that is loaded. 2. The #+ODT_STYLES_FILE directive does not seem to work. It's ignored and the value of org-export-odt-styles-file is used instead. May be related to (1). Is everything OK when there is *no* ODT_STYLES_FILE and org-export-odt-styles-file is *reset* to nil? 3. Current backend not set to 'odt? During ODT export, org-export-format-source-code-or-example fails while trying to load a file called "org-nil". So apparently org-export-current-backend fails to be passed the value 'odt on ODT export. The latter problem could also explain why, trying to export a file with verse environments, I got LaTeX mixed in with the ODT XML... I hope org-odt loads fine... Does M-x load-library RET org-odt RET report any errors? Yours, Christian
Re: [O] Refile targets fail with certain filename
Thanks Nick for your advice. I have posted a new e-mail
with the subject "Refile fails with blank * TODO"
On Mon, Dec 12, 2011 at 11:05 AM, Nick Dokos wrote:
> Nathan Neff wrote:
>
>> Hello,
>>
>> This was a very tricky problem to work around. I have two directories
>> ("notesmine" and "personal") that I use to refile stuff to. I refile to my
>> notesmine directory once every few months, so I was baffled last night
>> when I started getting "Wrong type argument:
>> stringp, nil" when I wanted to refile to my notesmine directory.
>>
>> ;; Setup
>> ;; My /Users/nate/Documents/notesmine directory has a file called
>> "org-mode.org" in it.
>>
>> ;; Begin Code
>> (defun njn/personal-org-files()
>> (interactive)
>> (directory-files "/Users/nate/Documents/notesmine" 't "^[^.].*org$")
>> )
>>
>> (defun njn/refile-targets-personal()
>> (interactive)
>> (setq org-refile-targets
>> (quote ((njn/personal-org-files :maxlevel . 5
>> )
>>
>> ;; I would then run M-x njn/refile-targets-personal, and
>> ;; then press Ctrl-C Ctrl-W to refile a heading in one of my org files.
>> ;; Then, I would see the "Wrong type argument: stringp nil"
>>
>> I found that the problem *disappears* when I remove or re-name
>> the "org-mode.org" file from my notesmine directory!
>>
>> I refile to my personal directory all the time, and I found that if
>> I move the "org-mode.org" file to my personal directory, (or create a blank
>> "org-mode.org" file in my personal directory then I would start
>> getting the same "Wrong type argument stringp, nil" error when refiling
>> to my personal directory.
>>
>> So, as a geek, I'm interested in why the "org-mode.org" filename causes
>> this error. I've reproduced the problem with the simple code above, so
>> I hope someone else can say "Yes, I can reproduce the problem" and I will
>> have done some good :-)
>>
>> Can anyone reproduce the error and tell me if "org-mode.org" is a keyword or
>> function or something, or is the problem in the regular expression I'm
>> using to select
>> my refile targets?
>>
>
> I cannot reproduce it, but the setup needed is probably sufficiently
> complicated
> to make the attempt futile.
>
> Here's the minimal .emacs I tried:
>
> --8<---cut here---start->8---
> ;;; -*- mode: emacs-lisp -*-
> ;;; constant part
> (add-to-list 'load-path (expand-file-name "~/src/emacs/org/org-mode/lisp"))
> (add-to-list 'load-path (expand-file-name
> "~/src/emacs/org/org-mode/contrib/lisp"))
> (add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" .
> org-mode))
> (require 'org-install)
>
> (setq debug-on-error t)
> (setq eval-expression-print-length nil)
> (setq eval-expression-print-level nil)
>
> (global-set-key "\C-cl" 'org-store-link)
> (global-set-key "\C-ca" 'org-agenda)
>
> Nathan Neff's problem config.
> ;; Setup
> ;; My /Users/nate/Documents/notesmine directory has a file called
> "org-mode.org" in it.
>
> (setq org-agenda-files '("/home/nick/lib/notesmine"))
>
> ;; Begin Code
> (defun njn/personal-org-files()
> (interactive)
> (directory-files "/home/nick/lib/notesmine" 't "^[^.].*org$")
> )
>
> (defun njn/refile-targets-personal()
> (interactive)
> (setq org-refile-targets
> (quote ((njn/personal-org-files :maxlevel . 5
> )
>
> ;; I would then run M-x njn/refile-targets-personal, and
> ;; then press Ctrl-C Ctrl-W to refile a heading in one of my org files.
> ;; Then, I would see the "Wrong type argument: stringp nil"
> ;;; end of Nathan Neff's problem config
>
> --8<---cut here---end--->8---
>
> and /home/nick/lib/notesmine contains two files, tasks.org and org-mode.org:
>
> tasks.org:
> --8<---cut here---start->8---
>
> * TODO foo
> SCHEDULED: <2011-12-12 Mon>
>
> ** DONE bar
> SCHEDULED: <2011-12-12 Mon>
> --8<---cut here---end--->8---
>
> org-mode.org:
>
> --8<---cut here---start->8---
>
> * one
> ** two
> *** three
> four
> * five
> ** TODO foo
> SCHEDULED: <2011-12-12 Mon>
> --8<---cut here---end--->8---
>
> After doing M-x njn/refile-targets-personal, I can refile from tasks.org (to
> either
> tasks.org or org-mode.org) with C-c C-w with no problems.
>
> I'd suggest you turn on debug-on-error and post the backtrace, preferably
> with a minimal .emacs similar to the above and none of your other
> customizations: emacs -q -l /path/to/minimal/dot/emacs
>
> Nick
[O] Refile fails with blank TODO
Hello,
With some help from Nick Dokos, I think I've found a
bug:
If you have a blank TODO entry in any of your refile targets,
you will get the error message below.
Here's a sample ~/Documents/notesmine/emacs.org file that will
reproduce the error:
* Emacs - auto fill mode
* TODO
* Rectangle
blah blah blah about rectangle
Here's the setup I used with the latest pull from org-mode:
-- begin init.el
;;; -*- mode: emacs-lisp -*-
;;; constant part
(add-to-list 'load-path (expand-file-name "~/.emacs.d/src/org/lisp"))
(add-to-list 'load-path (expand-file-name "~/.emacs.d/src/org/contrib/lisp"))
(add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
(require 'org-install)
(setq debug-on-error t)
(setq eval-expression-print-length nil)
(setq eval-expression-print-level nil)
(global-set-key "\C-cl" 'org-store-link)
(global-set-key "\C-ca" 'org-agenda)
Nathan Neff's problem config.
;; Setup
;; My /Users/nate/Documents/notesmine directory has a file called
"org-mode.org" in it.
(setq org-agenda-files '("~/Documents/personal"))
;; Begin Code
(defun njn/personal-org-files()
(interactive)
(directory-files "~/Documents/notesmine" 't "^[^.].*org$")
)
(defun njn/refile-targets-personal()
(interactive)
(setq org-refile-targets
(quote ((njn/personal-org-files :maxlevel . 5
)
-- end code ---
I'm able to replicate this bug by opening Emacs and
running M-x njn/refile-targets-personal
I've gone back at least as far back as commit
3e6ac9dfe2171fd84d95db4808fd024b1c95a8a3 -- But I don't think this commit
is the cause of the error, it's just as far back as I've gone when
trying to find
the actual cause of the error. Previously, I thought the error was caused by
the refile target file's name "org-mode.org", but this was not the case.
Thanks and hope someone else can replicate it :-)
Begin Error Message -
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match("\\[\\[\\(\\(http\\|https\\|ftp\\|mailto\\|file\\|news\\|shell\\|elisp\\|doi\\|message\\|file\\+sys\\|file\\+emacs\\|bbdb\\|bibtex\\|docview\\|gnus\\|info\\|irc\\|mew\\|mhe\\|rmail\\|vm\\|wl\\):\\)?\\([^]]+\\)\\]\\(\\[\\([^]]+\\)\\]\\)?\\]"
nil)
(if (string-match org-bracket-link-analytic-regexp link)
(replace-match (if ... ... ...) nil t link) link)
(progn (if (string-match org-bracket-link-analytic-regexp link)
(replace-match ... nil t link) link))
(unwind-protect (progn (if ... ... link)) (set-match-data
save-match-data-internal (quote evaporate)))
(let ((save-match-data-internal ...)) (unwind-protect (progn ...)
(set-match-data save-match-data-internal ...)))
(save-match-data (if (string-match org-bracket-link-analytic-regexp
link) (replace-match ... nil t link) link))
org-link-display-format(nil)
(setq level (org-reduced-level (- ... ...)) txt
(org-link-display-format (match-string 4)) txt
(replace-regexp-in-string "\\( *[[0-9]+/?[0-9]*%?]\\)+$" "" txt) re
(format org-complex-heading-regexp-format (regexp-quote ...)))
(progn (setq level (org-reduced-level ...) txt
(org-link-display-format ...) txt (replace-regexp-in-string "\\(
*[[0-9]+/?[0-9]*%?]\\)+$" "" txt) re (format
org-complex-heading-regexp-format ...)) (when
org-refile-use-outline-path (setq txt ...)) (push (list txt f re ...)
tgs))
(if (and (looking-at org-complex-heading-regexp) (not ...)) (progn
(setq level ... txt ... txt ... re ...) (when
org-refile-use-outline-path ...) (push ... tgs)))
(when (and (looking-at org-complex-heading-regexp) (not ...)) (setq
level (org-reduced-level ...) txt (org-link-display-format ...) txt
(replace-regexp-in-string "\\( *[[0-9]+/?[0-9]*%?]\\)+$" "" txt) re
(format org-complex-heading-regexp-format ...)) (when
org-refile-use-outline-path (setq txt ...)) (push (list txt f re ...)
tgs))
(catch (quote next) (when org-refile-target-verify-function
(save-match-data ...)) (when (and ... ...) (setq level ... txt ... txt
... re ...) (when org-refile-use-outline-path ...) (push ... tgs)))
(while (re-search-forward descre nil t) (goto-char (setq pos0 ...))
(catch (quote next) (when org-refile-target-verify-function ...) (when
... ... ... ...)) (when (= ... pos0) (goto-char ...)))
(save-restriction (widen) (goto-char (point-min)) (while
(re-search-forward descre nil t) (goto-char ...) (catch ... ... ...)
(when ... ...)))
(save-excursion (save-restriction (widen) (goto-char ...) (while ...
... ... ...)))
(progn (if (bufferp f) (setq f ...)) (setq f (and f ...)) (if (eq
org-refile-use-outline-path ...) (push ... tgs)) (save-excursion
(save-restriction ... ... ...)))
(or (setq tgs (org-refile-cache-get ... descre)) (progn (if ... ...)
(setq f ...) (if ... ...) (save-excursion ...)))
(save-current-buffer (set-buffer (if ... f ...)) (or (setq tgs ...)
(progn ... ... ... ...)) (when org-refile-use-cache
(org-refile-cache-put tgs ... descre)) (setq targets (append tgs
targets
Re: [O] [ANN] Org Mode parser v0.0.1 for NodeJs
Hi, sorry for my late response. I have little time right now, but I think org-mode could be integrated. The current node.js org-mode parser is not designed to take care of the content of a paragraph (for instance it will not be able to detect numbered lists), and I fear this is its major weak point. But for the rest, I have done some tests and the parser is quite robust. Please grab the last version from npm, it has a good set of unit tests On 12/dic/2011, at 00.21, Bastien wrote: > Eric Schulte writes: > >> This is the first I've seen of substance.io, it looks very interesting. >> I wonder how similar the substance document data structure is to the new >> org-parse data structure, and if it would be difficult or rewarding to >> write a translator between the two. > > I wonder the same -- I guess we'll all have more insight when we try > writing new exporter with the new export engine. Just though it was > good to throw this reference early enough... > > -- > Bastien
Re: [O] Refile fails with blank TODO
Nathan Neff wrote: > If you have a blank TODO entry in any of your refile targets, > you will get the error message below. > > ... > I'm able to replicate this bug by opening Emacs and > running M-x njn/refile-targets-personal > ... > Thanks and hope someone else can replicate it :-) > Yup, I can replicate it. You can work around it by adding a space (or something else) after the TODO, but I agree that it should be handled a bit more gracefully than with an obscure error message that does not point at the culprit. I think empty TODO lines and the problems they cause have been discussed on the list recently, but I wasn't paying much attention (and I don't have time to look atm) so I'm not sure what the resolution was. Nick
Re: [O] Bug: 2nd, 3rd, ... ext link in normal text NOT exported [7.7]
On Sun, Dec 11, 2011 at 11:01:13AM +0100, David Maus wrote: > At Mon, 5 Dec 2011 17:19:29 +0100, M. Bauer wrote: > > > > as in the last paragraph of the Org v7.7 manual section 4.3 > > about external links, "Org also finds external links in the > > normal text and activates them as links." While editing, > > this completely works as expected. > > > > But when it comes to exporting, Org will *not* recognize the > > second, third, etc. external link in normal text if it is > > *not* marked by square brackets. See below for some tests > > that will fail in ASCII, UTF8, and HTML export. > > > > Can you please consider this issue for one of the next > > versions of Org? > > Pushed a fix for this to master, all links in the example file > are now exported as expected. Thanks very much. Mathias
[O] [BUG] error if arg to #+call: contains a comma
Hello, There may be a problem with parsing arguments to the #+call function: #+name: A #+begin_src sh :var a="this, works" echo "$a" #+end_src #+results: A | this | works | #+call: A() #+results: A() | this | works | #+call: A(a="this also works") #+results: A(a="this also works") : this also works #+call: A(a="this, no work") Results in the message: reference 'no work"' not found in this buffer Myles
[O] Refresh of http://orgmode.org
Dear all, I made a small refresh of the website. http://orgmode.org - random quote (taken from worg/org-quotes.org) - random screenshot - twitter feed - g+/flattr/fb buttons - french translation (http://orgmode.org/fr/) If you want to help with the translation in your language, please send your public key and I will give you push access. This is just a bunch of .org files, only 1 hour needed to translate the whole website. Hope you like it! -- Bastien
[O] Release 7.8.01
Dear all,
I'm releasing 7.8.01. 7.8 has a bug about HTML publishing,
please don't use it.
http://orgmode.org/org-7.8.01.tar.gz
http://orgmode.org/org-7.8.01.zip
Below is the list of changes, also accessible on the website:
http://orgmode.org/Changes.html
Special thanks to Jambunathan, Nicolas, Eric and Carsten for
their work on this release. I won't tell how excited I am by
all these new changes: we waited long for the ODT exporter to
be in Org's core, and we can now celebrate this achievement!
Thanks again to Jambunathan for his steady support here. We
also waited long for having a new parser/exporter and this
is what Nicolas has been silently achieving: the promises of
this code will unfold as we will write new exporters and
rewrite old ones. Also thanks to Eric for his patience in
sorting out key standardization issues about code blocks.
Long life to Org!
Version 7.8
Summary
- Jambunathan's ODT exporter is now part of Org's core.
- Nicolas' new export engine is now part of =contrib/=
- Standard code block keywords
- 10 new committers
- Many bugfixes
See below for details.
New committers who signed the FSF copyright assigment
==
Here is the list of new contributors who signed the FSF papers
since Org 7.7 - welcome, and thanks for your contributions!
- Andreas Leha
- Christian Moe
- Julian Gehring
- Max Mikhanosha
- Michael Brand
- Niels Giessen
- Pieter Praet
- Sergey Litvinov
- Thomas Holst
- Thorsten Jolitz
The ODT exporter is now part of Org's core
===
- Full refresh of the OpenDocument Text section in the
manual. All new features listed below are fully-documented.
- Associate custom styles on per-file basis using
=#+ODT_STYLES_FILE:= directive.
- Fontify code listings using an enhanced version of
=htmlfontify.el= and generate line numbers natively.
- Embed MathML and OpenDocument formula files.
- Use LaTeX to MathML converter -- say MathToWeb
([http://www.mathtoweb.com/]) -- for handling LaTeX Math
fragments.
- In tables, use column width cookies to control relative width
of columns.
- Also for tables, you can specify custom styles using
=#+ATTR_ODT:= lines.
- Lots of bug fixes.
*Experimental*
The following features are /experimental/. These features are
specific to the ODT export engine and their implementation and
usage could change considerably in future versions.
- Support for list tables -- see this [message on the list].
- Support for annotation blocks -- see this [message on the list].
Special thanks to Jambunathan for his work and his patience
through the process of integrating this vital contribution into
Org's core.
[message on the list]:
http://lists.gnu.org/archive/html/emacs-orgmode/2011-09/msg00017.html
[message on the list]:
http://lists.gnu.org/archive/html/emacs-orgmode/2011-10/msg01251.html
New export engine by Nicolas
=
See the comment sections in org-element.el and in org-export.el
(in =contrib/lisp/=). Also check the experimental LaTeX exporter
using in =EXPERIMENTAL/org-e-latex.el=.
Check Nicolas' announcement [on the list] and hack around!
Thanks a lot to Nicolas for this great and promising achievement.
[on the list]: http://comments.gmane.org/gmane.emacs.orgmode/49416
Incompatible changes
=
Standardized code block keywords
~
Following a round of on-list discussion, many code block synonyms
have been removed. You can safely move forward the following
syntax:
- call lines are specified with #+call:
- code blocks are named with - results are named with code block may
still be labeled with named with #+tblname: will be considered to be
named results
The following function may be used to update an existing Org-mode
buffer to the new syntax:
(defun update-org-buffer ()
"Update an Org-mode buffer to the new data, code block and call line
syntax."
(interactive)
(save-excursion
(flet ((to-re (lst) (concat "^[ \t]*#\\+" (regexp-opt lst t)
"\\(\\[\\([:alnum:]+\\)\\]\\)?\\:[ \t]*"))
(update (re new)
(goto-char (point-min))
(while (re-search-forward re nil t)
(replace-match new nil nil nil 1
(let ((old-re (to-re '("RESULTS" "DATA" "SRCNAME" "SOURCE")))
(lob-re (to-re '("LOB")))
(case-fold-search t))
(update old-re "name")
(update lob-re "call")
*Note*: If an old version of Org-mode (e.g., the one shipped with
Emacs) is installed on your system, many of the important
variables will be pre-defined with a =defvar= and *will not* have
their values automatically updated -- these include the
following:
- =org-babel-data-names=
- =org-babel-result-regexp=
- =org-babel-src-block-regexp=
- =org-babel-src-name-regexp=
- =org-babel
[O] Google+ page for Org-mode
A while ago, I created a Google+ page for Org-mode: https://plus.google.com/b/102778904320752967064/ 63 people following Org from here -- don't hesitate to post comments, informations, etc. I posted the presentation I made in august here: http://goo.gl/hzFY7 Enjoy! -- Bastien
Re: [O] Bug: HTML export broken [7.8]
Mathias Bauer writes: > Can you please check this issue? This is now fixed in 7.8.01. Sorry for this. -- Bastien
Re: [O] [BUG] error if arg to #+call: contains a comma
Hi Myles, Thanks for reporting this issue, I just pushed up a fix and a protecting test case. Best, mylesengl...@gmail.com writes: > Hello, > > There may be a problem with parsing arguments to the #+call > function: > > #+name: A > #+begin_src sh :var a="this, works" > echo "$a" > #+end_src > > #+results: A > | this | works | > #+call: A() > > #+results: A() > | this | works | > #+call: A(a="this also works") > > #+results: A(a="this also works") > : this also works > #+call: A(a="this, no work") > > Results in the message: > > reference 'no work"' not found in this buffer > > > Myles > -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] Bug: HTML export broken [7.8]
Hello Bastien, On Tue, Dec 13, 2011 at 01:07:15AM +0100, Bastien wrote: > Mathias Bauer writes: > > > Can you please check this issue? > > This is now fixed in 7.8.01. Sorry for this. Never mind. Thanks for your quick response. But,... there is still a litte flaw at the website's org-mode-download.html page: The download links for the zip file and the gzipped tar archive both show the v7.6 files. However v7.8.01 is directly accessible via http://www.orgmode.org/org-7.8.01.tar.gz or http://www.orgmode.org/org-7.8.01.zip respectively Above all, with the new design the website really looks great and gives the text related Org a modern first impression. :-) Many thanks for the "renovation". Best, Mathias
Re: [O] Time tracking with MobileOrg
Hey Tobias, I think this would be a great feature for the Android version. It would be helpful if you could add this as a feature request in the issue tracker: https://github.com/matburt/mobileorg-android/issues As well as any ideas you have on how it should work... that will help us prioritize it as a feature. On Thu, Dec 8, 2011 at 2:40 PM, Tobias Kniep wrote: > A year ago, there has been a discussion on this list about tracking time > with MobileOrg (http://article.gmane.org/gmane.emacs.orgmode/31486) but > I couldn't find any more recent information. I'm using the Android > version of MobileOrg and would really like to do time tracking for my > orgmode tasks from my mobile. Is there any working solution out there? > > Best regards, > Tobias > > > > > >
Re: [O] Bug: Recurring TODO spuriously blocked [7.7]
pin...@iro.umontreal.ca (François Pinard) writes: > Bernt Hansen writes: > >> pin...@iro.umontreal.ca (François Pinard) writes: > >>> todo-dependencies should likely never be enforced for repeated >>> entries, even if enforced otherwise, as enforcing for repetitions >>> with the current Org mechanics has no meaning, at least as I >>> undestand Org so far. > >> You can set a NOBLOCKING property to t to skip the dependency check for >> repeated tasks. > >> * TODO Some Repeating Task >> SCHEDULED: <2011-12-16 Fri 15:30 ++1w> >> :PROPERTY: >> :NOBLOCKING: t >> :END: > > Thanks for the hint, Bernt. I'll use it for now. > > I still think this is a work around a real problem, which would ideally > be corrected. Regardless of blocking being configured or not for > non-repeating tasks, repeated tasks should never be blocked, shouldn't > they? > > François Hi François, I think the answer to that question is "it depends". I think there is a way to make check boxes block tasks too (but I've never used it) and in conjunction with resetting all of the checkboxes to unchecked you probably don't want to do that accidentally half way through your list of done items. I think this preference is very much workflow driven and shouldn't be globally assigned for everyone. I'm fine with an option that selects the behaviour globally so you can customize it the way you like. It would be nice if subtasks (that are DONE) get automatically moved back to TODO when the parent repeating task is marked DONE (and goes back to TODO). It's just not an itch anyone has scratched yet. If repeating tasks behaved this way (in the future) I think keeping the blocking functionality for repeating tasks makes sense. Regards, Bernt
Re: [O] Release 7.8.01
Bastien writes: > I'm releasing 7.8.01. 7.8 has a bug about HTML publishing, > please don't use it. 7.8.02 is now online, with the correct etc/ folder in it for the ODT exporter, and the commit Eric just pushed. -- Bastien
Re: [O] Search links in a list of files
Daniel Dehennin writes: > As I want to write some documentation with org-mode, I'm looking for a > way to manage an list of files in which org-mode will look for links, or > better, a list or directory to scan. > > For example: > > - in file1.org, I link something like > [[file:file2.org::#some-point][some point in some file]] > > - in file2.org I have a property "CUSTOM_ID: some-point" somewhere. > > If I reorganize my documentation and move file2.org in some > subdirectory, like examples/file2.org, I would like to avoid changing > all the references to "file2::#some-point". > > Maybe a link like [[search:PATH::SOMETHING]], with SOMETHING like in > search-options[1]. > > We could define a per-org file PATH, with something like > "#+LINK_SEARCH_PATH: path1, path2, ..." > > Any idea about this issue? Use global id's - then if you move headings around the links still work. See org-id.el for more info Regards, Bernt
Re: [O] Bug: HTML export broken [7.8]
Hi Mathias, Mathias Bauer writes: > But,... there is still a litte flaw at the website's > org-mode-download.html page: > > The download links for the zip file and the gzipped tar archive > both show the v7.6 files. However v7.8.01 is directly accessible > via http://www.orgmode.org/org-7.8.01.tar.gz or > http://www.orgmode.org/org-7.8.01.zip respectively Fixed, thanks for spotting this... > Above all, with the new design the website really looks great and > gives the text related Org a modern first impression. :-) > Many thanks for the "renovation". Hope so - thanks! -- Bastien
Re: [O] Bug: Recurring TODO spuriously blocked [7.7]
>>> pin...@iro.umontreal.ca (François Pinard) writes: todo-dependencies should likely never be enforced for repeated entries >> Bernt Hansen writes: >>> You can set a NOBLOCKING property to t to skip the dependency check >>> for repeated tasks. Bernt Hansen writes: > It would be nice if subtasks (that are DONE) get automatically moved > back to TODO when the parent repeating task is marked DONE (and goes > back to TODO). It's just not an itch anyone has scratched yet. [...] Bernt, I think I understand your point. You would prefer leaving the (currently unspecified) meaning opened for some later thinking and development. I will not cruisade for a change, as your suggestion gives me an usable work around. I thank you for having shared it. François
Re: [O] Release 7.8.01
Bastien writes: > Special thanks to Jambunathan, Nicolas, Eric and Carsten for > their work on this release. Thanks a bunch to Jambunathan! Great to see your work being part of Org. This seems like a very exciting release! Thanks to Bastien and other new and old contributors. Good job! –Rasmus -- Sent from my Emacs
[O] The reportmode report does not count the running clock
Hi, Org people. I'm noticing that the R (org-agenda-clockreport-mode) command with the *Org Agenda* buffer ignores the running clock. To get a result closer to the truth while I work, I have to clock-out and clock-in, then retry R. (Then edit out the spurious clock out and the following clock-in, to get rid of the short clocking gap.) Could the running clock merely be added / counted in the report? François
