[O] C-u C-c C-q bug (I presume)
Hi, Org maintainers. For a long while, I've been redoing C-u C-c C-q from time to time for realigning tags, not understanding why or when they stop to be aligned. I just got a clue. I'm not sure it covers everything, but at least, it is a start and seems reproducible here. If I do C-u C-c C-q, all visible tags are getting aligned as expected. However, tags on collapsed entries lose the correct alignment they already have, not always, but for those sub-headers containing a link, and only those. If I expand all again, I see the misalignment, which C-u C-c C-q corrects. If I close once more, repeat C-u C-c C-q, the alignment is lost again within the headers (having links) now invisible. Another small detail, which might be another problem in the same area. I noticed that C-d between the end of header and a tag does not remove a space as I expected. This is nice actually, it protects the tag alignment. However, if the header is not top-level, C-d /adds/ one or more spaces and consequently shifts the tag to the right. One space is added per header-level. That is, for top level headers, things are OK. For headers just under top level, one space is added. For headers one level deeper, two spaces are added. Etc. The fact that the header contains a link or not seems irrelevant for this second problem. François
[O] bug/feature request: refiling and creation of non-existing nodes
Hi I often use refile to move nodes around in my org-file. I recently learned about org-refile-allow-creating-parent-nodes, but it seems to be limited to one level, e.g. if I have set the variable to t and have the following tree * A * to refile I can move the second node to A/ or A/B/ but not to A/B/C/ is it possible to add this to org (I'm using 7.8.02)? This would also enable (I assume) to retain the tree structure during archiving (i.e. moving it to the same path in the archive file), which is another feature that I think would be great to have ;) Unfortunately my lisp skill is not good enough to supply a patch for this... any ideas on how this could be done would be helpful though. cheers ARUN
[O] [PATCH] org-clock-modify-effort-estimate: display a message when no clock is active
--- lisp/org-clock.el | 57 +++-- 1 files changed, 29 insertions(+), 28 deletions(-) diff --git a/lisp/org-clock.el b/lisp/org-clock.el index 9206608..1613f77 100644 --- a/lisp/org-clock.el +++ b/lisp/org-clock.el @@ -563,39 +563,40 @@ previous clocking intervals." (+ currently-clocked-time (or org-clock-total-time 0 (defun org-clock-modify-effort-estimate (&optional value) - "Add to or set the effort estimate of the item currently being clocked. + "Add to or set the effort estimate of the item currently being clocked. VALUE can be a number of minutes, or a string with format hh:mm or mm. When the string starts with a + or a - sign, the current value of the effort property will be changed by that amount. This will update the \"Effort\" property of currently clocked item, and the mode line." - (interactive) - (when (org-clock-is-active) - (let ((current org-clock-effort) sign) - (unless value - ;; Prompt user for a value or a change - (setq value -(read-string - (format "Set effort (hh:mm or mm%s): " - (if current - (format ", prefix + to add to %s" org-clock-effort) - "") - (when (stringp value) - ;; A string. See if it is a delta - (setq sign (string-to-char value)) - (if (member sign '(?- ?+)) - (setq current (org-duration-string-to-minutes current) -value (substring value 1)) -(setq current 0)) - (setq value (org-duration-string-to-minutes value)) - (if (equal ?- sign) - (setq value (- current value)) -(if (equal ?+ sign) (setq value (+ current value) - (setq value (max 0 value) - org-clock-effort (org-minutes-to-hh:mm-string value)) - (org-entry-put org-clock-marker "Effort" org-clock-effort) - (org-clock-update-mode-line) - (message "Effort is now %s" org-clock-effort + (interactive) + (if (org-clock-is-active) + (let ((current org-clock-effort) sign) + (unless value + ;; Prompt user for a value or a change + (setq value + (read-string +(format "Set effort (hh:mm or mm%s): " +(if current +(format ", prefix + to add to %s" org-clock-effort) + "") + (when (stringp value) + ;; A string. See if it is a delta + (setq sign (string-to-char value)) + (if (member sign '(?- ?+)) + (setq current (org-duration-string-to-minutes current) + value (substring value 1)) + (setq current 0)) + (setq value (org-duration-string-to-minutes value)) + (if (equal ?- sign) + (setq value (- current value)) + (if (equal ?+ sign) (setq value (+ current value) + (setq value (max 0 value) + org-clock-effort (org-minutes-to-hh:mm-string value)) + (org-entry-put org-clock-marker "Effort" org-clock-effort) + (org-clock-update-mode-line) + (message "Effort is now %s" org-clock-effort)) +(message "Clock is not currently active"))) (defvar org-clock-notification-was-shown nil "Shows if we have shown notification already.") -- 1.7.8.206.g71406
[O] [PATCH] Fix typos
--- lisp/org-agenda.el |2 +- lisp/org-list.el |2 +- lisp/org.el|2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 4efb332..7b4bc04 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -408,7 +408,7 @@ where desc A description string to be displayed in the dispatcher menu. cmdAn agenda command, similar to the above. However, tree commands - are no allowed, but instead you can get agenda and global todo list. + are not allowed, but instead you can get agenda and global todo list. So valid commands for a set are: (agenda \"\" settings) (alltodo \"\" settings) diff --git a/lisp/org-list.el b/lisp/org-list.el index 531cdd5..b865aed 100644 --- a/lisp/org-list.el +++ b/lisp/org-list.el @@ -207,7 +207,7 @@ Valid values are ?. and ?\). To get both terminators, use t." :group 'org-plain-lists :type '(choice (const :tag "dot like in \"2.\"" ?.) (const :tag "paren like in \"2)\"" ?\)) -(const :tab "both" t))) +(const :tag "both" t))) (defcustom org-alphabetical-lists nil "Non-nil means single character alphabetical bullets are allowed. diff --git a/lisp/org.el b/lisp/org.el index 859748a..22d2208 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -6844,7 +6844,7 @@ This command works around this by showing a copy of the current buffer in an indirect buffer, in overview mode. You can dive into the tree in that copy, use org-occur and incremental search to find a location. When pressing RET or `Q', the command returns to the original buffer in -which the visibility is still unchanged. After RET is will also jump to +which the visibility is still unchanged. After RET it will also jump to the location selected in the indirect buffer and expose the headline hierarchy above." (interactive "P") -- 1.7.8.206.g71406
[O] my setup for "remember the milk" (one way import to org-mode via org-feed.el)
Hi
I recently needed to add entries from "remember the milk"(RTM)[1] to my
org files... I found a script that converts to an orgfile[2], but also
the standard org-feed.el that can handle atom feeds. I played around a
bit with the latter and came up with the functions below that parse the
atom feed from RTM and also parse things like the due-date, tags, etc.
I also filter the feed by only including items that have a due date set
via the filter function.
Perhaps this is interesting for someone else, so I thought I post it
here. I could also upload it to Worg if there is interest, but am not
sure where it would go (don't use Worg that much lately).
cheers
Arun
[1] www.rememberthemilk.com/
[2] https://gist.github.com/1379125
; set up RTM
(defun org-feed-parse-RTM-entry (entry)
"Parse the `:item-full-text' as a sexp and create new properties."
(let ((xml (car (read-from-string (plist-get entry :item-full-text)
;; Get first .
(setq entry (plist-put entry :link
(xml-get-attribute
(car (xml-get-children xml 'link))
'href)))
;; Add as :title.
(setq entry (plist-put entry :title
(xml-substitute-special
(car (xml-node-children
(car (xml-get-children xml 'title)))
;; look for some other information that's in the content of the entry
;; the structure looks something like:
;; ...
(let* ((content (car (xml-get-children xml 'content)))
(main (car (xml-get-children content 'div)))
(items (xml-get-children main 'div)))
(when items
; iterate over all items and check for certain classes
(while items
(setq item (car items))
; get the second span entry
(setq valuesub (car (cdr (xml-node-children item
(cond
((string= (xml-get-attribute item 'class) "rtm_due")
(setq entry (plist-put entry :due (car (xml-node-children
valuesub
(setq mydate (car (xml-node-children valuesub)))
(if (string= mydate "never")
nil
(progn
(string-match "^\\([a-zA-Z]*\\) \\([0-9]*\\) \\([a-zA-Z]*\\)
\\([0-9]*\\)$" mydate)
(setq mydate (concat "20" (match-string 4 mydate) " "
(match-string
3 mydate) " " (match-string 2 mydate) " 00:00:01"))
(setq mydate (parse-time-string mydate))
(setq mydate (apply #'encode-time mydate))
(setq mydate (format-time-string (car org-time-stamp-formats)
mydate))
(setq entry (plist-put entry :dueorgformat mydate)
((string= (xml-get-attribute item 'class) "rtm_tags")
(setq entry (plist-put entry :tags (car (xml-node-children
valuesub)
((string= (xml-get-attribute item 'class) "rtm_time_estimate")
(setq entry (plist-put entry :timeestimate (car
(xml-node-children valuesub)
((string= (xml-get-attribute item 'class) "rtm_priority")
(setq entry (plist-put entry :priority (car (xml-node-children
valuesub)
((string= (xml-get-attribute item 'class) "rtm_location")
(setq entry (plist-put entry :location (car (xml-node-children
valuesub))
(setq items (cdr items))
)))
entry))
(defun org-feed-RTM-filter-non-scheduled (entry)
"filter out all entries that don't have a due date set"
(if (string= (plist-get entry :due) "never")
nil
entry))
(setq org-feed-alist
'(("Remember The Milk"
""
"~/org/RTM.org"
"Remember The Milk"
:parse-feed org-feed-parse-atom-feed
:parse-entry org-feed-parse-RTM-entry
:template "* TODO %title\n SCHEDULED:%dueorgformat\n Due:
%due\n Location: %location\n Priority:%priority\n Tags:%tags\n %a\n "
:filter org-feed-RTM-filter-non-scheduled
)))
;;* rtm feed timer
(run-at-time 3600 3600 'org-feed-update-all)
[O] [PATCH] Fix (wrong-type-argument integer-or-marker-p nil) in org-agenda-get-todos.
org-get-category can sometimes invoke org-refresh-category-properties which can perform a re-search-forward which destroys the existing match data. When called from org-agenda-get-todos, this can result in its subsequent call to (match-beginning 2) to return nil, which when passed as the first parameter to buffer-string causes the above error. --- lisp/org-agenda.el |9 + 1 files changed, 5 insertions(+), 4 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index ac1b5b1..4efb332 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -4664,10 +4664,11 @@ the documentation of `org-diary'." (or org-agenda-todo-list-sublevels (org-end-of-subtree 'invisible)) (throw :skip nil))) (goto-char (match-beginning 2)) - (setq marker (org-agenda-new-marker (match-beginning 0)) - category (org-get-category) - org-category-pos (get-text-property (point) 'org-category-position) - txt (org-trim + (setq marker (org-agenda-new-marker (match-beginning 0))) + (save-match-data + (setq category (org-get-category) + org-category-pos (get-text-property (point) 'org-category-position))) + (setq txt (org-trim (buffer-substring (match-beginning 2) (match-end 0))) tags (org-get-tags-at (point)) txt (org-agenda-format-item "" txt category tags) -- 1.7.8.206.g71406
Re: [O] optimisation of org-notify
On Sun, Feb 26 2012, Peter Münster wrote: > On Sun, Feb 26 2012, Nick Dokos wrote: > >> So orgntf-todo-list takes the lion's share of the time but >> most of it is the 15 calls to org-element-parse-buffer > > Ok, then I could process only one file at a time. This would divide the > processing time by 15, in your case. But perhaps others would have the > 7000 lines in one file only, then it would not work... > So, is it worth the effort? The effort was quite small, so I've done it. :) -- Peter
Re: [O] [PATCH] org-agenda-list (from git) giving "args-out-of-range error"
David Maus writes: >I pushed the fix with some small cleanup of the commit >message. Somehow the patchtracker included the mailbody in the commit >message. Thank you! FWIW, I used 'git format-patch' to generate the patch; not sure if that had anything to do with the resulting patchtracker behavior. pgp315l3hxmAF.pgp Description: PGP signature
Re: [O] Selectively export RESULTS
Hi Achim, Achim Gratz wrote: > "Sebastien Vauban" writes: >> Not sure to understand why you would prefer to have something that you just >> wrote not taken into account, unlike one would expect? > > Because I might not have finished editing that part and just moving the > cursor away from that line doesn't mean it should be acted upon. I dislike > any software that makes guesses as to when I might have finished something > or worse, tries to act upon my change _while I change it_ (that's especially > bad if the things it does take a long time or produce errors that I have to > deal with). I certainly never said that the "automagic C-c C-c" should be done after each key press or some such. That certainly would be a killer feature, in its real acception: performance would be unbearable. In my mind, automatically (re-)parsing the meta options should be each time the user presses `C-c C-v C-e' (eval code blocks); that is, when the user expects his options to be taken into account. I guess this makes much sense, but... Best regards, Seb -- Sebastien Vauban
[O] Small patch for pw client, fix typo in error message
Hi,
Not sure what the commit policy for the pw client in UTITLITES is, so
this patch first over the list: It fixes a confusing typo in an error
message.
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber dmj...@jabber.org
Email. dm...@ictsoc.de
From ad7d01046cd08675fd95a266b1397e6c2172f750 Mon Sep 17 00:00:00 2001
From: David Maus
Date: Sun, 4 Mar 2012 21:31:11 +0100
Subject: [PATCH] UTILITIES/pw: Fix type in error message
* pw (action_update_patch): Fix type in error message.
---
UTILITIES/pw |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/UTILITIES/pw b/UTILITIES/pw
index 0cf4bfa..1e2f44f 100755
--- a/UTILITIES/pw
+++ b/UTILITIES/pw
@@ -314,7 +314,7 @@ def action_update_patch(rpc, patch_id, state = None, commit
= None,
if state.lower() in notify_on_state_change:
if not delegate_id:
-sys.stderr.write("Error: Delete (-d) required for this
update\n")
+sys.stderr.write("Error: Delegate (-d) required for this
update\n")
sys.exit(1)
person = rpc.person_get(delegate_id)
--
1.7.2.5
pgph6H3AvOF85.pgp
Description: OpenPGP Digital Signature
[O] Possible bug in parsing / clarification of syntax
Hi all, I have found some irritating behaviour, potentially a bug. I have a block agenda which goes like: tags-todo "@home&TODO=\"TODO\" and it displays a certain org line that reads TODO_ state triggers Which is just a heading for dealing with TODO state triggers, and I appended the _ as I don't want it to be a TODO. For example, the global TODO list and syntax highlighting does not consider it a todo, but C-c a m TODO="TODO" does. TODO="T" does not, so it's not very grave. Most likely, it's simply an inconsistency arising from not having a real parser. I just wanted to report it here so it may get fixed. Cheers, Simon
Re: [O] [PATCH] org-agenda-list (from git) giving "args-out-of-range error"
Hi Karl, At Wed, 29 Feb 2012 13:45:05 -0600, Karl Fogel wrote: > > [1 ] > Nick Dokos writes: > >Exactly what you've done: send the patch to the list. > > > >Modulo possible changelog formatting issues (see > >http://orgmode.org/worg/org-contribute.html#sec-5 for the gory details), > >the patch looks good to me. Thanks for submitting it! > > Oh, thanks -- I should have looked for those guidelines first. Here is > the same patch, but with a properly-done log message this time. I pushed the fix with some small cleanup of the commit message. Somehow the patchtracker included the mailbody in the commit message. Best and thanks for the patch, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgpbs9CEJlZsT.pgp Description: OpenPGP Digital Signature
[O] [accepted] Fix task cloning for repeating tasks
Patch 1185 (http://patchwork.newartisans.com/patch/1185/) is now "accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C1330137796-18986-1-git-send-email-bernt%40norang.ca%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] Fix task cloning for repeating tasks > Date: Sat, 25 Feb 2012 07:43:16 - > From: Bernt Hansen > X-Patchwork-Id: 1185 > Message-Id: <1330137796-18986-1-git-send-email-be...@norang.ca> > To: emacs-orgmode@gnu.org > Cc: Bernt Hansen > > * org.el (org-clone-subtree-with-time-shift): Fix task cloning for > repeating tasks using .+n and ++n syntax > > Tasks with repeaters using .+n and ++n syntax retain the repeater in > all of the clones causing duplicate tasks. These tasks are now > handled the same as the regular repeating task using +n syntax. > > --- > Doh! Let's fix the changelog entry... (missing * in the previous version) > > -Bernt > > lisp/org.el |6 +++--- > 1 files changed, 3 insertions(+), 3 deletions(-) > > diff --git a/lisp/org.el b/lisp/org.el > index a81f7fc..f24c69f 100644 > --- a/lisp/org.el > +++ b/lisp/org.el > @@ -7946,7 +7946,7 @@ the following will happen: >repeater intact. > - the start days in the repeater in the original entry will be shifted >to past the last clone. > -I this way you can spell out a number of instances of a repeating task, > +In this way you can spell out a number of instances of a repeating task, > and still retain the repeater to cover future instances of the task." >(interactive "nNumber of clones to produce: \nsDate shift per clone (e.g. > +1w, empty to copy unchanged): ") >(let (beg end template task idprop > @@ -7973,7 +7973,7 @@ and still retain the repeater to cover future instances > of the task." > (setq end (point)) > (setq template (buffer-substring beg end)) > (when (and doshift > -(string-match "<[^<>\n]+ \\+[0-9]+[dwmy][^<>\n]*>" template)) > +(string-match "<[^<>\n]+ [.+]?\\+[0-9]+[dwmy][^<>\n]*>" > template)) >(delete-region beg end) >(setq end beg) >(setq nmin 0 nmax (1+ nmax) n-no-remove nmax)) > @@ -8004,7 +8004,7 @@ and still retain the repeater to cover future instances > of the task." > (while (re-search-forward org-ts-regexp nil t) > (save-excursion > (goto-char (match-beginning 0)) > - (if (looking-at "<[^<>\n]+\\( +\\+[0-9]+[dwmy]\\)") > + (if (looking-at "<[^<>\n]+\\( +[.+]?\\+[0-9]+[dwmy]\\)") > (delete-region (match-beginning 1) (match-end 1))) > (setq task (buffer-string))) > (insert task)) >
Re: [O] org-yank improvement?
Memnon Anon writes: > Bernt Hansen writes: > (I'm using clean mode, as probably everybody does!) >>> No. >> What's this 'clean mode' you're taking about? I can't find any >> reference to that on worg. > > ,[ (info "(org)Clean view") ] > | 15.8 A cleaner outline view > | === > | > | Some people find it noisy and distracting that the Org headlines start > | with a potentially large number of stars, and that text below the > | headlines is not indented. While this is no problem when writing a > | _book-like_ document where the outline headings are really section > | headings, in a more _list-oriented_ outline, indented structure is a > | lot cleaner: > ` Ah org-indent-mode :) Thanks, Bernt
[O] [Feature Request] org-mobile edit:add nodes
Hi everyone, I am currently trying to allow mobileorg-android to capture new headings into files other than mobileorg.org. It seems to me that org-mobile does not support refiling of nodes. As my experience with lisp programming is very limited, I was hoping someone on this list could add this feature. I was thinking of something along the lines of an add edit node: F(edit:add) [[node path to parent (olp or id)][Title]] ** Old value ** New value *** TODO New node :tag1:tag2: initial payload ** End of edit Which would result in a new heading to be created under the parent when org-mobile-apply is run. Having "delete nodes" would also be great. Having those would make capturing much more convenient. Everything to support this feature is added to mobileorg-android, it simply needs to be extended to generate the appropriate "add edit nodes". Thanks in advance for any help, Henning Weiss
Re: [O] Is it possible to run shell script src blocks as root or to export individual blocks?
Under Gnome, I'm using this at the beginning of a sh source block: echo -e "#! /bin/bash\n/usr/bin/gksudo -p -m Password" > /tmp/gksudo-stdout chmod +x /tmp/gksudo-stdout SUDO_ASKPASS="/tmp/gksudo-stdout" sudo -A -s Sylvain.
Re: [O] [Bug] Tests for experimental org-features should expect to fail if not activated by the user
Nicolas Goaziou writes:
> So, indeed, the second failing test appears. It should pass now (at
> least it does even on my compiled Org installation).
I confirm the fix, thank you very much.
> I think the others come from a file-error ("Opening output file").
I can see now why this happens: the temporary directory for the test
should already exist — make usually takes care of that, but running it
by hand does not. So these failures should go away if you "mkdir
/tmp/tmp-orgtest" before starting the tests and you should also get a
clean test run.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] org-yank improvement?
Bernt Hansen writes: >>> (I'm using clean mode, as probably everybody does!) >> No. > What's this 'clean mode' you're taking about? I can't find any > reference to that on worg. ,[ (info "(org)Clean view") ] | 15.8 A cleaner outline view | === | | Some people find it noisy and distracting that the Org headlines start | with a potentially large number of stars, and that text below the | headlines is not indented. While this is no problem when writing a | _book-like_ document where the outline headings are really section | headings, in a more _list-oriented_ outline, indented structure is a | lot cleaner: ` Memnon
Re: [O] org-yank improvement?
Memnon Anon writes: > pin...@iro.umontreal.ca (François Pinard) writes: > >> (I'm using clean mode, as probably everybody does!) > > No. What's this 'clean mode' you're taking about? I can't find any reference to that on worg. -Bernt
Re: [O] Export to multiple HTML files?
On 02/27/2012 12:19 PM, Avdi Grimm wrote: > Is there a way to export a single Org file to a bunch of HTML files, > one for each heading of a given level? E.g. the way the Org manual is > presented at http://orgmode.org/manual ? (yes, I realize that's Info > not org-mode)I thought I remembered that being possible, but now I > can't find it. This would be a really nice feature to have. I would use it instead of the convoluted process I use now. Scott Randby
Re: [O] [Bug] Tests for experimental org-features should expect to fail if not activated by the user
Achim Gratz writes:
> Well, that is likely because you run the test on uncompiled source,
> while I am running it on compiled orgmode... maybe one of these pesky
> byte-compiler warnings shouldn't have been ignored. I can't reproduce
> the 24 unexpected results, but they probably have a similar origin
> (partially compiled orgmode?).
It's possible. I have two different Org installations. One compiled for
my work, and the other, uncompiled for development. Both are latest git
version.
When batch running tests on my compiled Org, I get:
--8<---cut here---start->8---
Ran 130 tests, 105 results as expected, 25 unexpected (2012-03-04 15:42:25+0100)
9 expected failures
25 unexpected results:
FAILED ob-emacs-lisp/commented-last-block-line-no-var
FAILED ob-emacs-lisp/commented-last-block-line-with-var
FAILED ob-exp/exports-both
FAILED ob-exp/mixed-blocks-with-exports-both
FAILED ob-exp/noweb-no-export-and-exports-both
FAILED ob-exp/noweb-on-export
FAILED ob-exp/noweb-on-export-with-exports-results
FAILED ob-exp/noweb-strip-export-ensure-strips
FAILED test-ob-lob/do-not-eval-lob-lines-in-example-blocks-on-export
FAILED test-ob-sh/dont-error-on-empty-results
FAILED test-ob/commented-last-block-line-no-var
FAILED test-ob/commented-last-block-line-with-var
FAILED test-ob/org-babel-remove-result--results-default
FAILED test-org-babel/combining-scalar-and-raw-result-types
FAILED test-org-babel/elisp-in-header-arguments
FAILED test-org-babel/inline-src-blocks
FAILED test-org-babel/inline-src_blk-default-results-replace-line-1
FAILED test-org-babel/just-one-results-block
FAILED test-org-babel/multi-line-header-arguments
FAILED test-org-babel/parse-header-args
FAILED test-org-babel/parse-header-args2
FAILED test-org-babel/simple-named-code-block
FAILED test-org-babel/simple-variable-resolution
FAILED test-org-footnote/normalize-outside-org
FAILED test-org-table/simple-formula
--8<---cut here---end--->8---
So, indeed, the second failing test appears. It should pass now (at
least it does even on my compiled Org installation).
I think the others come from a file-error ("Opening output file").
Thanks for your help.
Regards,
--
Nicolas Goaziou
Re: [O] org-yank improvement?
Memnon Anon writes: > pin...@iro.umontreal.ca (François Pinard) writes: >> However, by mistake, it happens that the cursor is on the only visible >> bullet star of the next heading instead of really being at the start >> of the line. I recently edited some org files in clean mode for the first time (It might be the default mode on Worg?) and was surprised and a bit confused that my cursor(point) was invisible when on the invisible bullet stars at the beginning of the line. I had to move point to the (only) visible bullet star on the line to find out where I am in the buffer. Maybe only a peculiarity of my color-settings, but nevertheless convincing me not to use clean mode. -- cheers, Thorsten
Re: [O] org-yank improvement?
pin...@iro.umontreal.ca (François Pinard) writes: > I often cut a list item (or a hierarchy of list items) to reinsert it > into another heading which I know contains only list items. All the > headings are collapsed, so what I usually do is position the cursor at > the beginning of the /next/ heading and yank the list item there, this > has the effect of inserting it at the end of the previous heading, no > need to open it. Mhh, why don't you just insert a newline above the next heading and yank then? > (I'm using clean mode, as probably everybody does!) No. > However, by mistake, it happens that the cursor is on the only visible > bullet star of the next heading instead of really being at the start > of the line. I wonder how you end up "between two stars" in the first place... With `org-special-ctrl-a/e' t, I would not expect this to be an issue. But as indicated above, I don't use clean mode aka org-indent-mode. > Of course, it is my error. Yet, Org mode could be friendlier, here! Lets say 'safer'. But while "..." indicating folded content at the end of a line is an integral part of org, things like org-hide-leading-stars seemed to me always to be purely cosmetic. Nice to have, but if one really edits org files by hand (it is all plain text, right), potentially a problem. Memnon
Re: [O] Participating in Google Summer of Code 2012
On 2 mars 2012, at 18:12, Jambunathan K wrote: > Sometime back while looking at change tracking within OpenDocument > files, I stumbled upon the following two entries. > > http://wiki.documentfoundation.org/Track_changes#Google_Summer_of_Code_2009:_Improve_Writer.27s_compare_function > > http://gsoc-tzvetelina.blogspot.in/ > > In the above blog, the author is talking about paragraphs as a unit and > makes a note of the algorithms he uses to narrow down the paragraphs of > interest. I think in Org's context, outline could (also) be considered > as a unit. If I may advertise some things I did a while back, which may be useful to convert between textual formats: http://www.seas.upenn.edu/~harmony/ We also worked on a synchronizing algorithm that mixed diff3 with our tree synchronizer. I could try to dig that up as well. Alan
Re: [O] org-yank improvement?
François Pinard sadly writes: > It never really make sense [...] whenever yanking into a start string > [...] Well, I should learn to re-read me better... s/make sense/makes sense/ s/a start string/a star string/ Gentle readers, I invite you to email me (privately) when I err so blatantly, and help me improve! :-) François
Re: [O] [Bug] Tests for experimental org-features should expect to fail if not activated by the user
Nicolas Goaziou writes: >> [...] >> 2 unexpected results: >>FAILED test-org-export/export-scope >>FAILED test-org-footnote/normalize-outside-org > > With your command, I was able to reproduce the first one (along with 24 > unexpected results), for which I have pushed a fix. I still don't see > the second one. Well, that is likely because you run the test on uncompiled source, while I am running it on compiled orgmode... maybe one of these pesky byte-compiler warnings shouldn't have been ignored. I can't reproduce the 24 unexpected results, but they probably have a similar origin (partially compiled orgmode?). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] org-mode as an accountability system?
Hi Peter, Peter Salazar writes: > My committed actions for a day consist of: > > a) TODOs for the projects I'm working on > b) random errands that need to be done that day > c) daily habits (e.g. meditating, exercising) > > I don't believe org-agenda can support me in doing this, because I > require: > > a) a way to quickly enter the random tasks for that day (without > having to "schedule" each one for today) > b) more importantly: a way to record, store, and e-mail my list of > which tasks I've done and not done at the end of the night I am not sure why you don't use the agenda, there really should be no need to compile this data manually. Flow: - Enter your task with capture. This *is* a quick way, and you should be able to setup a binding that schedules the new task to today by default. Put the tasks wherever they should live in your org cosmos. - At the beginning of the day, start your agenda for today. Copy and paste it, export it to html, whatever. Send it to your college. - Work through your tasks. If you can't finish a task, don't mark it didnotdo, but simple reschedule it for tomorrow; the change will be reflected in your log drawer. - At the end of the day, or early next day, start the agenda and use org-agenda-log-mode, probably with C-u. - `C-u l' should show you all there is, given it is properly configured: Task you finished, tasks you did not finish and hence rescheduled for later, even your sections (teaching, habits, random tasks) can be reflected with categories. Just copy and paste it in your email and you are done. > Macro question: Is there a better way to manage my accountability > system, rather than doing it manually? Again, I don't see a way to do > it using agenda. hth Memnon
Re: [O] [Bug] Tests for experimental org-features should expect to fail if not activated by the user
Hello, Achim Gratz writes: > Nicolas Goaziou writes: >> I cannot reproduce any of them, interactively or in batch mode[1]. > > This is the invocation (to be run in bash, like make would do): > > TMPDIR=/tmp/tmp-orgtest /usr/local/bin/emacs -batch -Q \ > -L lisp/ -L testing/ -L contrib/lisp \ > --eval '(defconst org-release "7.8.03-Test")' -l testing/org-test.el \ > --eval '(require '"'"'org-element)' --eval '(require '"'"'org-export)' \ > --eval '(setq org-confirm-babel-evaluate nil)' -f org-test-run-batch-tests > > [...] > 2 unexpected results: >FAILED test-org-export/export-scope >FAILED test-org-footnote/normalize-outside-org With your command, I was able to reproduce the first one (along with 24 unexpected results), for which I have pushed a fix. I still don't see the second one. Regards, -- Nicolas Goaziou
Re: [O] Bug: Org-mode don't export to html footnotes references inside footnotes as such. [7.8.03]
Hello, Achim Gratz writes: >>> If one intends to export his Org file to ODT, then nested footnote >>> construction should be avoided like plague. >> >> It isn't really supported in LaTeX too, but there are workarounds. > > There are always workarounds, but footnotes within footnotes aren't > directly supported by any publishing system I know of, and with good > reason. A footnote, just like a marginal, is an expansion on the main > text that can be skipped without loss of information (but maybe loss of > detail). That's what I thought before the OP request. Though, it appears that it is a not so rare need. For example critical editions seem to use it quite often. > So whenever you feel that you need a footnote within a footnote, you > could just as well have two footnotes at the original place. I have never needed nested footnotes, so I feel like the Devil's advocate but anyway... Imagine a very large footnote, spanning over tens of lines. You would like to add a footnote next to a word in the middle of that text. I suppose it wouldn't make sense to get out of that footnote and be told there's another reference for a word you read many lines ago. >> If such thing isn't possible, ODT back-end will ignore any footnote >> contained in another footnote (i.e. whose genealogy contains an element >> with an `footnote-reference' or `footnote-definition' type) and send >> a message to the user. > > It would be better to not promote the idea of footnotes within footnotes > and those who insist on using that construct should be required to > explicitly request that feature and suffer the consequences. Note that Org inherently supports nested footnotes. Forbidding them would be much like an artificial limitation. I don't mind such limitation, but knowing that they may happen to be useful, it's worth pondering if it really should be so. > Much better would be if starting a footnote while within a footnote > would simply open a new footnote and add the reference at the same place > where the first one was opened. That's a possible workaround I was talking about earlier. And it's perfectly possible with the experimental exporter. ODT back-end may implement it. That's mostly what I did with the LaTeX back-end. Nested footnotes definitions are inserted right after the top level footnote definition containing them. Only footnotes markers are nested. Regards, -- Nicolas Goaziou
[O] org-yank improvement?
Hi again, Org people! I often cut a list item (or a hierarchy of list items) to reinsert it into another heading which I know contains only list items. All the headings are collapsed, so what I usually do is position the cursor at the beginning of the /next/ heading and yank the list item there, this has the effect of inserting it at the end of the previous heading, no need to open it. However, by mistake, it happens that the cursor is on the only visible bullet star of the next heading (I'm using clean mode, as probably everybody does!) instead of really being at the start of the line. In this case, yanking is physically done between two stars in the string of stars (all but the last being hidden) making the outline level, which breaks the layout of course. I just undo, reposition the cursor better with Ctrl-A and retry. It never really make sense, in my opinion, to yank in the middle of an invisible string. Luckily enough, yanking is done through a special org-yank function, so it is at least theoretically possible to prevent this. My suggestion would be that whenever yanking into a start string, that the yanking really occurs at the beginning of it. Of course, it is my error. Yet, Org mode could be friendlier, here! François
Re: [O] C-c a t doesn't give yield list of all TODO items
jeremiah.do...@gmail.com wrote: > "Christopher W. Ryan" writes: > > > But when I try to type C-c a > > > > I only get that far, and emacs tells me, "C-c a is undefined" > > > > There is a drop-down menu item under the Org item, called "Agenda > > Command..." > > which offers me lettered choices, and t will list all TODO entries. But > > what is > > the keyboard shortcut, if not C-a a t ? > > > > Thanks. > > You have to bind it yourself. Put > > (global-set-key "\C-ca" 'org-agenda) > > somewhere sensible. This *is* mentioned somewhere in the org docs, but I > can't remember where off the top of my head. > Section 1.3, Activation, in the org manual. Or do (info "(org) Activation") Nick
Re: [O] Selectively export RESULTS
"Sebastien Vauban" writes: > Not sure to understand why you would prefer to have something that you just > wrote not taken into account, unlike one would expect? Because I might not have finished editing that part and just moving the cursor away from that line doesn't mean it should be acted upon. I dislike any software that makes guesses as to when I might have finished something or worse, tries to act upon my change _while I change it_ (that's especially bad if the things it does take a long time or produce errors that I have to deal with). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Bug: Org-mode don't export to html footnotes references inside footnotes as such. [7.8.03]
Nicolas Goaziou writes: >> If one intends to export his Org file to ODT, then nested footnote >> construction should be avoided like plague. > > It isn't really supported in LaTeX too, but there are workarounds. There are always workarounds, but footnotes within footnotes aren't directly supported by any publishing system I know of, and with good reason. A footnote, just like a marginal, is an expansion on the main text that can be skipped without loss of information (but maybe loss of detail). So whenever you feel that you need a footnote within a footnote, you could just as well have two footnotes at the original place. > If such thing isn't possible, ODT back-end will ignore any footnote > contained in another footnote (i.e. whose genealogy contains an element > with an `footnote-reference' or `footnote-definition' type) and send > a message to the user. It would be better to not promote the idea of footnotes within footnotes and those who insist on using that construct should be required to explicitly request that feature and suffer the consequences. Much better would be if starting a footnote while within a footnote would simply open a new footnote and add the reference at the same place where the first one was opened. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] org-mode as an accountability system?
Rather than "did not do" perhaps "pending" might be a little shorter. On Sat, 3 Mar 2012, John Hendy wrote: > On Sat, Mar 3, 2012 at 1:18 PM, Peter Salazar wrote: > > Hi Thorsten, > > > > Thanks for the thoughts. > > > > Clarification: I send my accountability partner a summary of MY committed > > actions for the day for him to review. We dont' collaborate, and he does not > > touch or change my tasks. (Although he does send me a list of his own tasks, > > and how well he did each day.) > > > > He doesn't have to change them, just be able to view the up to date > state of your todos. I think that was the point. =git pull= is not > significantly more work than opening an email. > > > It's important to send the tasks by e-mail so I know he'll see them right > > away (and that will keep me accountable). If I send him a link, I know he > > may or may not view the file if and when he has time. > > > > Whether he opens his browser/email client and reads the email or opens > a terminal and does =git pull=, again, does not seem horridly > different. Then again, for a non git user, you are correct that one > more step might make the difference between reading and not. > > > As for using Agenda and hitting > to move a task to the next day, there are > > two problems with this: > > > > 1. this does not change the state of a @didnotdo task to @todo > > Have a look at: http://orgmode.org/manual/Agenda-commands.html > > I, too, am not a power user, however it seems like you could do the following: > -- `C-a t` (show all todos) > -- `m` on each one you did not complete > -- `B` (shift+b, conduct bulk action on all marked entries) > -- `t` to change todo state for each marked item > -- Type in 'didnotdo' to change the state > -- `C-a T` (agenda search based on todo state) > -- Type in 'didnotdo' (gives you all the items you just marked since > you didn't do them) > -- Copy the current agenda view into an email and send it > Alternative do `C-x C-w` and write it to a file you can push to a git > repo > -- `m` on all the shown entries (all are state `didnotdo` at this point) > -- `B` (conduct a bulk action) > -- `s` (schedule new date for all actions) > -- Use the minibuffer calendar to schedule them to a new day > > Looks like a lot, but this should go pretty fast once you get the hang of it. > > Also, Bernt Hanson has a diddy on his website for creating a timestamp > for every new headline. Perhaps you could use it to create a timestamp > with today's date for every new todo headline? See his elisp code > here: > -- http://doc.norang.ca/org-mode.html#sec-15-21 > > > 2. for habits (using the format SCHEDULED: <2012-03-03 Sat +1d>), if I miss > > a day and then try to mark a habit DONE today, it stamps the habit done for > > the day I missed, rather than stamping it done today and recording that I > > did not do it on the day I was supposed to do it. > > > > I don't use habit, but I know there's a graph that's supposed to show > color coded bars based on whether you did or did not do the task > according to how you scheduled the habit. > -- http://orgmode.org/manual/Tracking-your-habits.html > > Hope this gives you some ideas or even helps you directly! > > > John > > > > > On Sat, Mar 3, 2012 at 1:56 PM, Thorsten wrote: > >> > >> Peter Salazar writes: > >> > >> Hi Peter, > >> without claiming being an expert org-mode user, I had the following > >> thoughts when reading your post: > >> > >> > I have an accountability partner with whom I exchange daily "committed > >> > actions." Every morning, I e-mail him a list of the tasks I commit to > >> > completing that day. > >> > >> Why sending per email? Why not getting a free private(!) git repo (1GB) > >> at assembla.com and cooperatively work on one or several org file(s) in > >> that repo? > >> > >> > When I complete a task, I mark it DONE. If I don't complete a task > >> > that day, I mark it @didnotdo and manually cut and paste it to the > >> > next day. > >> > > >> > Every night, I send him a report of which actions I did and which ones > >> > I did not do. (I find I get so much more done since I started making > >> > daily commitments to someone other than myself.) > >> > >> If you both work on the same file using git, the current state of > >> affairs will always be clear, as well as who did what at what time (and > >> pushed it to the repo). > >> > >> > 1. Given that I'm creating my daily task list manually, is there an > >> > easy way, when I mark a task @didnotdo, to automatically move it to > >> > the next day's list and change its state to @todo? > >> > >> When I have a TODO task in the agenda that I did not complete today, I > >> just change the date to tomorrow in the agenda using '>'. > >> If you don't do that, it will appear anyway in the agenda as overdue > >> task. > >> > >> > >> -- > >> cheers, > >> Thorsten > >> > >> > > > > Jude
Re: [O] Participating in Google Summer of Code 2012
Nicolas Goaziou writes: > Hello, > > Rasmus writes: > >> * Better item handling >> >> At the moment it is hard to change lists. Often I need inline items >> and interrupted list. This is hard to do with Org at the moment. > > There is support for inline lists in the experimental LaTeX back-end. > > Also, I'm not sure about what you mean with "interrupted lists", but > counters may be the answer, i.e.: > > 6. [@6] Start at 6 > 7. Following item >From OpenDocument side of things, I am inclined to cite the attached example. See comments in the attachment. Talking of migration to org-export.el/org-e-odt.el, indented tables pose special challenges because a list has to be broken and continued. It poses *more* challenges if I add "listified headlines" to the mix. Nicolas, Given the above context, one enhancmenet request that I have for you is this: Can the org-export driver make listified headings transparent to the backend? Currently listified headings are handled within org-e-backend-headline through first-sibling and last sibling checks and the backends *do know* that it is handling a headline in a special way. If you have reservations in considering the above request, I believe handling of indented tables will be fragmented across plain-list/item callbacks and headline callbacks. Note that I am not saying that it is not doable but only that it requires some deliberate effort and extra code. > Regards, -- * Table within a Table Indented tables in ODT discontinue and continue a list. - Item1 - Item2 - Item2.1 | 1 | 2 | | 3 | 4 | - Item2.2 - Item3 * COMMENT XML for above table Here you can see table is syntactically outside of a list. There is a special list-header tag that is used for continuing an item. #+begin_src nxml Item1 Item2 Item2.1 1 2 3 4 Item2.2 Item3 #+end_src
Re: [O] [Bug] Tests for experimental org-features should expect to fail if not activated by the user
Nicolas Goaziou writes: > I cannot reproduce any of them, interactively or in batch mode[1]. This is the invocation (to be run in bash, like make would do): TMPDIR=/tmp/tmp-orgtest /usr/local/bin/emacs -batch -Q \ -L lisp/ -L testing/ -L contrib/lisp \ --eval '(defconst org-release "7.8.03-Test")' -l testing/org-test.el \ --eval '(require '"'"'org-element)' --eval '(require '"'"'org-export)' \ --eval '(setq org-confirm-babel-evaluate nil)' -f org-test-run-batch-tests [...] 2 unexpected results: FAILED test-org-export/export-scope FAILED test-org-footnote/normalize-outside-org > I'm not sure where they could come from. Since I run this with "-Q", I suspect that you implicitly rely on some customization someplace. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] [Bug] Tests for experimental org-features should expect to fail if not activated by the user
"Sebastien Vauban" writes: > I don't understand why once there are 192 tests, once 130. I thought that the > second figure was the total number of tests, hence should be stable over the > test runs? The number of available tests depend on the Babel languages that are activated. One of those failures was with a test run that had all languages (except R) activated, the other one with no languages (except emacs-lisp, which is always active), but org-element and org-export made active. Those two also seem to pull in ob-sh and maybe other Babel languages, I would have to check. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ DIY Stuff: http://Synth.Stromeko.net/DIY.html
Re: [O] Participating in Google Summer of Code 2012
Hello, Rasmus writes: > * Better item handling > > At the moment it is hard to change lists. Often I need inline items > and interrupted list. This is hard to do with Org at the moment. There is support for inline lists in the experimental LaTeX back-end. Also, I'm not sure about what you mean with "interrupted lists", but counters may be the answer, i.e.: 6. [@6] Start at 6 7. Following item Regards, -- Nicolas Goaziou
Re: [O] Export to multiple HTML files?
Hello, Christian Moe writes: > On 3/3/12 9:28 PM, Nicolas Goaziou wrote: > (...) >> Christian Moe writes: On Mon, Feb 27, 2012 at 5:19 PM, Avdi Grimm wrote: > Is there a way to export a single Org file to a bunch of HTML files, > one for each heading of a given level? > (...) >>> I don't think there's been any way to do this directly. Would be >>> a neat option to have, though. >> >> You can probably achieve this by setting an appropriate publishing >> function. > > But is there such a function ready to use? I don't think so. Ready to use, no. But since you can specify your own publishing function, it should be doable. Regards, -- Nicolas Goaziou
Re: [O] Japanese strings for Org-mode export
I was looking at those. Those seems to be table for replacement table for special characters and symbols. Are you suggesting placing those characters in this and reference from main code? (that will be 8 characters which will not have any Latin1 and ASCII representations...) Hideki Saito On Sun, Mar 4, 2012 at 12:34 AM, Jambunathan K wrote: > Hideki Saito writes: > >> If UTF-8 strings are acceptable in org-mode source tree, I guess doing >> it so will make it most compatible. > > M-x find-library RET org-entities RET > > C-s lambda > > will land you in a structure that has utf-8 strings. > --
Re: [O] Japanese strings for Org-mode export
Hideki Saito writes: > If UTF-8 strings are acceptable in org-mode source tree, I guess doing > it so will make it most compatible. M-x find-library RET org-entities RET C-s lambda will land you in a structure that has utf-8 strings. --
Re: [O] Japanese strings for Org-mode export
Dear Saito-san,
Thanks for making an alternative patch.
I'll follow up why I cannot apply the original patch.
Best regards,
Takaaki Ishikawa
On 2012/03/04, at 16:29, Hideki Saito wrote:
> The attached is alternative of the patch using utf-8 encoding.
>
> Hideki Saito
>
>
>
> On Sat, Mar 3, 2012 at 10:26 PM, Hideki Saito wrote:
>> Hello Ishikiawa-san
>> It is OSX at work, and it's still on Snow Leopard -- I haven't updated
>> the console version of it, so I will have to check to see which
>> version was it. It is now sound like to me that the way I've done on
>> the patch is platform dependent at best -- which is strange as this
>> notation was used in other languages in same entry, but not as
>> extensive as in case for Japanese...
>>
>> Hideki Saito
>>
>>
>>
>>
>> 2012/3/3 Takaaki ISHIKAWA :
>>> Dear Saito-san,
>>>
>>> Thank you for comment.
>>> You mean OSX+emacs23 users cannot compile using the patch, right?
>>> (Or something wrong with me...)
>>> And I can compile it in SuSE Linux :-)
>>>
>>> Best regards,
>>> Takaaki Ishikawa
>>>
>>> On 2012/03/04, at 14:37, Hideki Saito wrote:
>>>
Ishikawa-san,
I've had that problem when I tried to do "make' on Mac OS X, which I
realized it was compiling in obsolete version of emacs. (like emacs
22) I believe it was happening when (require 'org-exp.el)
In fact, I did see this would work if UTF-8ed in your example even in
the above environment, but I thought it was inappropriate as coding
wasn't encoded in UTF-8. If UTF-8 strings are acceptable in org-mode
source tree, I guess doing it so will make it most compatible.
I verified the patch worked under Emacs 24 and in fact, I am right now
using the code on my Mac and on Windows.
Hideki Saito
2012/3/3 Takaaki ISHIKAWA :
> Dear Saito-san,
>
> I've tried to compile your patch with the latest org-mode.
> I got an error message:
> Error: Invalid character: 33879, #o102127, #x8457
>
> I can apply the following line directly under UTF-8 env.:
> ("ja" "著者" "日付" "目次" "脚注")
>
> Emacs 23.4 (nextstep)
> Org-version 7.8.03
>
>
> Could you give me your environment around Emacs?
>
> Best regards,
> Takaaki Ishikawa
>
>
> On 2012/03/03, at 16:06, Hideki Saito wrote:
>
>> I think Gmail did bad to the patch snippet. Obviously, I haven't done
>> much of patch contributions :-)
>>
>> I've attached one, or you can refer to:
>> https://gist.github.com/1964802
>>
>> Thank you.
>>
>> Hideki Saito
>>
>>
>> On Fri, Mar 2, 2012 at 5:55 PM, Hideki Saito wrote:
>>> diff --git a/lisp/org-exp.el b/lisp/org-exp.el
>>> index 174619a..43c54b5 100644
>>> --- a/lisp/org-exp.el
>>> +++ b/lisp/org-exp.el
>>> @@ -194,6 +194,7 @@ This option can also be set with the +OPTIONS
>>> line, e.g. \"-:nil\"."
>>> ("hu" "Szerzõ" "Dátum" "Tartalomjegyzék"
>>> "Lábjegyzet")
>>> ("is" "Höfundur" "Dagsetning" "Efnisyfirlit"
>>> "Aftanmálsgreinar")
>>> ("it" "Autore" "Data" "Indice" "Note a piè di pagina")
>>> +("ja" "\x8457\x8005" "\x65e5\x4ed8" "\x76ee\x6b21" "\x811a\x6ce8")
>>> ("nl" "Auteur" "Datum" "Inhoudsopgave" "Voetnoten")
>>> ("no" "Forfatter" "Dato" "Innhold" "Fotnoter")
>>> ("nb" "Forfatter" "Dato" "Innhold" "Fotnoter") ;; nb = Norsk
>>> (bokm.l)
>>
>
>>>
>
Re: [O] C-c a t doesn't give yield list of all TODO items
"Christopher W. Ryan" writes: > But when I try to type C-c a > > I only get that far, and emacs tells me, "C-c a is undefined" > > There is a drop-down menu item under the Org item, called "Agenda Command..." > which offers me lettered choices, and t will list all TODO entries. But what > is > the keyboard shortcut, if not C-a a t ? > > Thanks. You have to bind it yourself. Put (global-set-key "\C-ca" 'org-agenda) somewhere sensible. This *is* mentioned somewhere in the org docs, but I can't remember where off the top of my head.
