[O] Archiving logged work time
Hi, I have been using org-mode for 6 months to track my working time, but now I am stepping my usage up a bit since I have found it useful to have all my to-dos in one tool. Until now I have had a template file with the things I work on, so that I can easily create a new file every week. This is drive by a need to report time every week to a fixed set of activities. So far I have just moved the old file and then created a new file with all my tasks in. However, now that I am using more of org-mode I am not so sure that this monolithic time tracking file is a good idea, but I am not sure about how I can archive just the logged time entries, but keep the activity for logging time on next week. When I stand on a line with a CLOCK entry the archive function will archive the whole sub-tree that I am standing in. It might be that I should just create a number of files for the major things I am working on and then archive the task as well as the time logged against it every week. This means that I would have to retype the task for the next week, but if that is the best way of doing it I will start doing that. Advice most welcome - I am in learning mode and want to improve my usage of org-mode. Cheers, __ /orben -- http://www.linkedin.com/in/torbenhoffmann
Re: [O] Opening (for the first time) a 10-line Org doc takes 4 seconds
Hi Bastien, Bastien wrote: Sebastien Vauban writes: (if (locate-library org-loaddefs) (require 'org-loaddefs) ^ You don't need this, there is (load org-loaddefs.el t t) in org.el. OK. And `org.el' is loaded[1] because of the major-mode association to the `.org' files, then, right? Anyway, that does not have impacts here. Are your org elisp files compiled? Nope. Never. What results do you have without the advice on `require'? I've now ran 5 tests with each config: | without advice | with advice | |+-| | 3.78 |3.95 | | 3.73 |3.86 | | 3.76 |3.83 | | 3.80 |3.83 | | 3.81 |3.94 | |+-| | 3.78 |3.88 | #+TBLFM: @7$1..@7$2=vmean(@I..@-I);%.2f That is less than 3% time penalty for the logs done during the execution of all the `require'. Best regards, Seb [1] BTW, why not a `require' instead? -- Sebastien Vauban
Re: [O] Emacs 22 compatibility
Bastien writes: I just tried building. it was successful although there are lot of warnings. Good to know it builds fine, even with all those warnings. That's a definition of builds fine that I wasn't previously aware of. As to the question does it run, yes — sort of. You'll get a bunch of warning messages each time you open an Org document and I wouldn't trust it to handle any real data. But that's only a very superficial look I've had and I certainly didn't use any advance functionality in Org. As I said, I've already looked into some of these errors and there are several affecting core functionality. I've been ignoring when some packages are entirely missing in Emacs 22 (like VM and wanderlust) and assumed that the associated functionality was unlikely to be used from it. If this is expected to be normal however, then we should check for the existence of these packages and conditionalize on the result. There is another bunch of warnings that is triggered by the fact that declare-function is doing nothing in Emacs 22. This is used extensively in the new exporter to avoid circular requires, but there seem to be a few places where a require or an autoload should have been used instead. Then comes a longish list of variables and functions that Emacs 22 doesn't yet have (window-system-default-frame-alist) or have a different signature (like using delete-directory with more than one argument or kill-buffer with none). Also things like the use of internal or undocumented variables and functions (e.g. timer--time) that should be fixed anyway. The seemingly most serious I've found is that using a defaliased special form (org-condition-case-unless-debug) inside a macro doesn't seem to be recognized by the byte compiler and it tries to compile a symbol list as a function call. Short of yanking out the defalias and replacing with condition-case, nothing seems to work (maybe another macro expansion too, haven't had time for this yet). If I fix things enough so that the test suite will run I'll get this: Ran 401 tests, 388 results as expected, 13 unexpected 3 expected failures 13 unexpected results: FAILED ob-exp/evaluate-all-executables-in-order FAILED ob-exp/export-call-line-information FAILED ob-exp/exports-both FAILED ob-exp/exports-inline 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 test-org-element/headline-comment-keyword FAILED test-org-element/headline-interpreter FAILED test-org/beginning-of-line FAILED test-org/comment-dwim FAILED test-org/end-of-line While this doesn't look so bad on first sight, it will still require a significant effort to fix and we know that the test suite coverage is nowhere near complete. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Emacs 22 compatibility
Hi Achim, Achim Gratz strom...@nexgo.de writes: That's a definition of builds fine that I wasn't previously aware of. My definition of building fine is that the build process does not break and that it produces the target files. Warnings are not errors in the process of building, they are pointers to potential problems in the code that has been built. As I said, I've already looked into some of these errors and there are several affecting core functionality. If you or anyone can fix those error, please have a go. There is another bunch of warnings that is triggered by the fact that declare-function is doing nothing in Emacs 22. This is used extensively in the new exporter to avoid circular requires, but there seem to be a few places where a require or an autoload should have been used instead. Yes, I want to clean this up a bit for 8.0. If I fix things enough so that the test suite will run I'll get this: Ran 401 tests, 388 results as expected, 13 unexpected 3 expected failures Well, It's not that bad :) 13 unexpected results: FAILED ob-exp/evaluate-all-executables-in-order FAILED ob-exp/export-call-line-information FAILED ob-exp/exports-both FAILED ob-exp/exports-inline 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 So, this is mostly babel. FAILED test-org-element/headline-comment-keyword FAILED test-org-element/headline-interpreter FAILED test-org/beginning-of-line FAILED test-org/comment-dwim FAILED test-org/end-of-line None of the above really counts as core feature for me. While this doesn't look so bad on first sight, it will still require a significant effort to fix and we know that the test suite coverage is nowhere near complete. Yes, agreed. My time will first go to actual bugs with Emacs 23/24 reported by users, then to actual bugs in Emacs 22 reported by the users, then to potential bugs in Emacs 24/23, then to potential bugs in Emacs 22... meaning that there is little chance for me to work on potential bugs with Emacs 22 (or to review patches for this very quickly.) Thanks, -- Bastien
Re: [O] Emacs 22 compatibility
Hi Yagnesh, thanks for replying. Yagnesh Raghava Yakkala h...@yagnesh.org writes: Since I don't use that version, I am afraid I can not assure. No problem. Let's wait for a real Emacs 22 user to come up and complain if he dares! :) -- Bastien
Re: [O] Dramatic slowdown in org mode
Fraga, Eric e.fr...@ucl.ac.uk writes: this has definitely been fixed! Thank you very much. Thanks for confirming! -- Bastien
Re: [O] Emacs 22 compatibility
Bastien writes: If you or anyone can fix those error, please have a go. I've pushed 9a71174348 for org-find-invisible-foreground, which at least lets the test suite run. BTW, I don't quite understand the logic of that function. It seems that (face-background 'default nil 'default) would be all that is needed in GNU Emacs to avoid getting unspecified-bg back from that function. Once that function always returns a color specification, the values further down the list would not even be considered, so I'm not sure why these are produced in the first place? For XEmacs, we don't even get a string back, so only the result of (face-background 'default) is ever used. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] new exporter: link abbrev
Hi Nicolas On Tue, Dec 18, 2012 at 10:21 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: The problem should now be fixed without using any trick It is, thank you. (and no, `org-export-normalize-links' will not survive the old exporter). Thanks to your change above I like this cleanup. Michael
Re: [O] Table sorting hack
William R. Greene william.r.gre...@gmail.com writes: I recently wrote a blog post concerning sorting of org-mode tables. Nice! -- Bastien
Re: [O] Exchange calendar to orgmode
Hi Chris, Chris Raschl c...@kautsig.org writes: I recently wrote a python script to fetch my calendar from the corporate exchange server into an orgmode file to view it in my agenda. It uses the exchange webservices (ews). There are lots of things that could be added, but I thought I'd share it as-is. Maybe somebody can use it... https://github.com/kautsig/ews-orgmode Thanks for sharing this, I've added a link to Worg: http://orgmode.org/worg/org-tools/ -- Bastien
Re: [O] Bibtex export
Hi Mohamed,
mohamed writes:
Usually I write
---
* Section a
...
* Bibliograpy :noheading:
\clearpage
\bibliographystyle{acm}
\bibliography{biblio.bib}
If you use this function then the Bibliography heading won't be
duplicated:
#+begin_src emacs-lisp
(defun my-export-delete-headlines-tagged-noheading (backend)
(dolist (hl (nreverse (org-element-map (org-element-parse-buffer 'headline)
'headline
'identity)))
(when (member noheading (org-element-property :tags hl))
(goto-char (org-element-property :begin hl))
(delete-region (point) (progn (forward-line) (point))
#+end_src
You need to be a bit careful because the Bibliography section will then
inherit any properties from the section above so if you then do:
* Section a:noexport:
then both that section and the Bibliography section would not be
exported.
Myles
Regards,
Mohamed
Re: [O] Opening (for the first time) a 10-line Org doc takes 4 seconds
Bastien writes: (if (locate-library org-loaddefs) (require 'org-loaddefs) ^ You don't need this, there is (load org-loaddefs.el t t) in org.el. Well, yes he does when he is using Org from Git. It's a wash when he's using builtin Org from Emacs and potentially wrong when he's using Org from ELPA, depending on if he does it before or after package-initialize. You've expressed before that you want to know why this is so. As a reminder, Org from Git currently has all its autoload definitions in org-loaddefs. Lets look at this for all possible Emacs versions: XEmacs and Emacs 22 don't come with a builtin Org version. You have no autoloads including none for the entry point for the major mode until you load org-loaddefs (or org). Emacs 23, 24.1 and 24.2 comes with older versions of Org that don't even have org-loaddefs. All autoloads for the builtin version are in loaddefs from Emacs and they are already loaded when the user initialization stuff is run. Some things in those autoloads happen to point to the correct libraries, but only by chance. Generally one has to assume that the autoloads that are present have the wrong docstring, point to the wrong file and present an outdated API. To fix this, one must load org-loaddefs (or org). Emacs 24.3 will come with a newer version of Org, but still older than the one from Git. Only part of the autoloads are present in loaddefs, the rest would be pulled in from the bundled org-loaddefs when org is loaded. That is the reason why one does not need to do that when only using the builtin Org version. Again however, these builtin autoload definitions from loaddefs must be presumed outdated for Org from Git, so it is still necessary to load org-loaddefs (or org) in the initalization code to make sure the correct first-level autoloads take precedence even when it is assured that all autoload code-paths also trigger loading of org (I don't think that this can be easily guaranteed and I know of no tool that would allow one to analyse). Last but not least, if one uses Org from ELPA, then it must be arranged that org-loaddefs gets loaded only after package-initialize, otherwise you'll end up with the correct first-level autoloads, but outdated second-level autoloads (that get replaced with the current ones when org gets loaded). Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ DIY Stuff: http://Synth.Stromeko.net/DIY.html
Re: [O] Exchange calendar to orgmode
On 12/19/2012 01:24 PM, Bastien wrote: Hi Chris, Chris Raschlc...@kautsig.org writes: I recently wrote a python script to fetch my calendar from the corporate exchange server into an orgmode file to view it in my agenda. It uses the exchange webservices (ews). There are lots of things that could be added, but I thought I'd share it as-is. Maybe somebody can use it... https://github.com/kautsig/ews-orgmode Thanks for sharing this, I've added a link to Worg: http://orgmode.org/worg/org-tools/ Thanks a lot! - chris
[O] LOGBOOK Drawer Position in Capture Templates
Hi, If I have a capture template as follows: (sm Start a meeting and clock entry (file ~/org/notes.org) * %c %U ** %? :clock-in t :clock-resume t) What happens is that the sub-heading where the point is left is where the LOGBOOK drawer is inserted. like this: * Meeting Title [date] ** point is here :LOGBOOK: CLOCK [date] :END: I want the clock to be associated with the top level heading. Is there a way to construct the template so that it results in the LOGBOOK drawer being part of the primary heading? Like so: * Meeting TItle [date] :LOGBOOK: CLOCK [date] :END: ** point is here Thanks, ~Bill
Re: [O] org-mobile-push vs. symlinks
Bastien b...@altern.org writes: James Harkins jamshar...@gmail.com writes: Anyway, I still don't understand the rationale for the current behavior. Does anyone know why org-mobile-push resolves the agenda files' names to symlink targets? The problem is that there is no active maintainer on org-mobile.el right now... by default this is me, but I'm a bit swamped. I'll have a look, but anyone faster than me is welcome! How would we do that? Are there instructions somewhere on the proper way to create a patch file for this? The proper mode for diff? What has to be in a changelog? There are a few changes I'd like to see in mobile.el myself, and I'm willing to make them, if I know how to submit. Dave
Re: [O] org-mobile-push vs. symlinks
Hi David, da...@adboyd.com (J. David Boyd) writes: How would we do that? Are there instructions somewhere on the proper way to create a patch file for this? The proper mode for diff? What has to be in a changelog? There are a few changes I'd like to see in mobile.el myself, and I'm willing to make them, if I know how to submit. http://orgmode.org/worg/org-contribute.html HTH, -- Bastien
Re: [O] Emacs 22 compatibility
Bastien writes: If you or anyone can fix those error, please have a go. Here is another one that may need further work. The byte-compiler of Emacs 22 does not seem to handle defaliased special forms correctly when expanding macros. This can be circumvented with a defmacro, but then the decision becomes compile-time rather than load time (one could make it run-time by quoteing more broadly). For the current uses this should be OK. Also, ODT export now compiles correctly, but still doesn't work in Emacs 22 since delete-directory doesn't have a second argument (recursive delete) in Emacs 22. This would need to be worked around or at least the error caught. From e459dde441932d95d157648519fc2768262fd1e8 Mon Sep 17 00:00:00 2001 From: Achim Gratz strom...@stromeko.de Date: Wed, 19 Dec 2012 19:35:19 +0100 Subject: [PATCH] Backwards compatibility: don't defalias special forms * lisp/org-compat.el (org-condition-case-unless-debug): Do not use defalias for special forms, the Emacs 22 byte-compiler does not recognize them correctly when compiling macros. Use a macro instead and rely on macro expansion. That however makes the decision at compile time, which should be acceptable in this case since it only affects debugging. --- lisp/org-compat.el | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/lisp/org-compat.el b/lisp/org-compat.el index 1f330b1..292a777 100644 --- a/lisp/org-compat.el +++ b/lisp/org-compat.el @@ -438,12 +438,13 @@ (defun org-pop-to-buffer-same-window ;; `condition-case-unless-debug' has been introduced in Emacs 24.1 ;; `condition-case-no-debug' has been introduced in Emacs 23.1 -(defalias 'org-condition-case-unless-debug +(defmacro org-condition-case-unless-debug (var bodyform rest handlers) + (declare (debug condition-case) (indent 2)) (or (and (fboundp 'condition-case-unless-debug) - 'condition-case-unless-debug) + `(condition-case-unless-debug ,var ,bodyform ,@handlers)) (and (fboundp 'condition-case-no-debug) - 'condition-case-no-debug) - 'condition-case)) + `(condition-case-no-debug ,var ,bodyform ,@handlers)) + `(condition-case ,var ,bodyform ,@handlers))) ;;;###autoload (defmacro org-check-version () -- 1.8.0.1 With all fixes in, Emacs 24 can run the tests for an the Org compiled by Emacs 22 now with just one error remaining, on master this is: Test ob-exp/mixed-blocks-with-exports-both condition: (wrong-type-argument number-or-marker-p nil) FAILED 19/403 ob-exp/mixed-blocks-with-exports-both and this one on maint: Test test-org-src/blank-line-block condition: (error No special environment to edit here) FAILED 346/378 test-org-src/blank-line-block One of the 13 errors when Emacs 22 runs the testsuite itself is due to an unconditional use of visual-line-mode, which Emacs 22 does not have. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Emacs 22 compatibility
Bastien writes: FAILED test-org-element/headline-comment-keyword FAILED test-org-element/headline-interpreter FAILED test-org/beginning-of-line FAILED test-org/comment-dwim FAILED test-org/end-of-line None of the above really counts as core feature for me. Don't tell Nicolas that org-element is not a core feature... :-) beginning-of-line/end-of-line tests should be fixable, at least EOL fails from trying to set visual-line-mode. Haven't looked at the others. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Emacs 22 compatibility
Achim Gratz strom...@nexgo.de writes: For the current uses this should be OK. Also, ODT export now compiles correctly, but still doesn't work in Emacs 22 since delete-directory doesn't have a second argument (recursive delete) in Emacs 22. See http://lists.gnu.org/archive/html/emacs-orgmode/2010-08/msg01056.html We need to move that fix to compatibility and have babel and ODT use it --
Re: [O] Emacs 22 compatibility
Achim Gratz writes: With all fixes in, Emacs 24 can run the tests for an the Org compiled by Emacs 22 now with just one error remaining, on master this is: Test ob-exp/mixed-blocks-with-exports-both condition: (wrong-type-argument number-or-marker-p nil) FAILED 19/403 ob-exp/mixed-blocks-with-exports-both This test actually fails the same way when compiled with Emacs 24 and without that fix, so this must be some other recent change. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Emacs 22 compatibility
Jambunathan K writes: http://lists.gnu.org/archive/html/emacs-orgmode/2010-08/msg01056.html We need to move that fix to compatibility and have babel and ODT use it I guess that would circumvent the crash, but a proper compatibility fix should actually do the recursion, I'd think. In the case of Babel it actually might be a remote directory. 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
[O] Compilation warnings and a test failure
Just pulled Org-mode version 7.9.2 (release_7.9.2-762-gc74c62 @ /home/nick/elisp/org-mode/lisp/) and running under GNU Emacs 24.2.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.4) of 2012-09-21 I get compilation warnings: , | Compiling /home/nick/src/emacs/org/org-mode/lisp/org.el... | | In org-get-location: | org.el:6989:10:Warning: `special-display-function' is an obsolete variable (as | of 24.3); use `display-buffer-alist' instead. | org.el:6988:10:Warning: `special-display-regexps' is an obsolete variable (as | of 24.3); use `display-buffer-alist' instead. | org.el:6987:10:Warning: `special-display-buffer-names' is an obsolete variable | (as of 24.3); use `display-buffer-alist' instead. | | In org-shiftcontrolup: | org.el:19234:11:Warning: org-clock-timestamps-up called with 1 argument, but | accepts only 0 | | In org-shiftcontroldown: | org.el:19244:11:Warning: org-clock-timestamps-down called with 1 argument, but | accepts only 0 | | In org-switch-to-buffer-other-window: | org.el:20957:23:Warning: `special-display-function' is an obsolete variable | (as of 24.3); use `display-buffer-alist' instead. | org.el:20956:52:Warning: `special-display-regexps' is an obsolete variable (as | of 24.3); use `display-buffer-alist' instead. | org.el:20956:23:Warning: `special-display-buffer-names' is an obsolete | variable (as of 24.3); use `display-buffer-alist' instead. | Wrote /home/nick/src/emacs/org/org-mode/lisp/org.elc ` and a test failure: , | Test ob-exp/mixed-blocks-with-exports-both backtrace: | (149 nil) | apply( (149 nil)) | (setq value-4627 (apply fn-4625 args-4626)) | (unwind-protect (setq value-4627 (apply fn-4625 args-4626)) (setq fo | (if (unwind-protect (setq value-4627 (apply fn-4625 args-4626)) (set | (unless (unwind-protect (setq value-4627 (apply fn-4625 args-4626)) | (let (form-description-4629) (unless (unwind-protect (setq value-462 | (let ((value-4627 (quote ert-form-evaluation-aborted-4628))) (let (f | (let ((fn-4625 (function )) (args-4626 (list test-point (re-search- | (should ( test-point (re-search-forward x nil t))) | (lambda (x) (should ( test-point (re-search-forward x nil t))) (set | mapcar((lambda (x) (should ( test-point (re-search-forward x nil t) | (progn (mapcar (lambda (x) (should ( test-point (re-search-forward | (setq G48327 (progn (mapcar (lambda (x) (should ( test-point (re-se | (let ((kill-buffer-query-functions nil) G48327) (with-temp-file /tm | (org-test-with-temp-text-in-file exported-html (mapcar (lambda (x) ( | (let ((exported-html (org-export-as-html nil nil nil (quote string) | (save-restriction (org-narrow-to-subtree) (let ((exported-html (org- | (progn (org-id-goto 5daa4d03-e3ea-46b7-b093-62c1b7632df3) (setq to | (unwind-protect (progn (org-id-goto 5daa4d03-e3ea-46b7-b093-62c1b76 | (let ((save-match-data-internal (match-data))) (unwind-protect (prog | (save-match-data (org-id-goto 5daa4d03-e3ea-46b7-b093-62c1b7632df3 | (progn (save-match-data (org-id-goto 5daa4d03-e3ea-46b7-b093-62c1b7 | (unwind-protect (progn (save-match-data (org-id-goto 5daa4d03-e3ea- | (let ((wconfig (current-window-configuration))) (unwind-protect (pro | (save-window-excursion (save-match-data (org-id-goto 5daa4d03-e3ea- | (let* ((id-location (org-id-find 5daa4d03-e3ea-46b7-b093-62c1b7632d | (org-test-at-id 5daa4d03-e3ea-46b7-b093-62c1b7632df3 (org-narrow-t | (lambda nil (org-test-at-id 5daa4d03-e3ea-46b7-b093-62c1b7632df3 ( | byte-code(\306\307!q\210\310\216\311 \312\216\313\314\315\316\3 | ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc | byte-code(\306\307!\211\211r\310\311!q\210\312 d\313\223)L\210)\3 | ert-run-test([cl-struct-ert-test ob-exp/mixed-blocks-with-exports-bo | ert-run-or-rerun-test([cl-struct-ert--stats \\(org\\|ob\\) [[cl-st | ert-run-tests(\\(org\\|ob\\) #[(event-type rest event-args) \306 | ert-run-tests-batch(\\(org\\|ob\\)) | ert-run-tests-batch-and-exit(\\(org\\|ob\\)) | (let ((org-id-track-globally t) (org-id-locations-file (convert-stan | org-test-run-batch-tests() | call-interactively(org-test-run-batch-tests nil nil) | command-execute(org-test-run-batch-tests) | command-line-1((--eval (add-to-list 'load-path \./lisp\) --ev | command-line() | normal-top-level() | Test ob-exp/mixed-blocks-with-exports-both condition: | (wrong-type-argument number-or-marker-p nil) |FAILED 19/334 ob-exp/mixed-blocks-with-exports-both ` Thanks, Nick
Re: [O] [PATCH] Babel: Fix the #+END_ directive from the :wrap param
Hello, Michael Gauland mikely...@no8wireless.co.nz writes: * lisp/ob.el: Only use the :wrap argument up to the first space when creating the #+END_ directive. Applied. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Extend (org-shiftcontrolup) and (org-shiftcontroldown) with numeric arguments?
Am 18.12.2012 15:00, schrieb Bastien: Hi Rainer and Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: I think it would be a welcomed improvement, since there's already support for that in `org-timestamp-up' and `org-timestamp-down'. Do you want to do it? I just implemented this. It's now in master. Thanks, Bastien, thanks a lot! Rainer
Re: [O] Compilation warnings and a test failure
Hi Nick, Nick Dokos nicholas.do...@hp.com writes: | In org-get-location: | org.el:6989:10:Warning: `special-display-function' is an obsolete variable (as | of 24.3); use `display-buffer-alist' instead. | org.el:6988:10:Warning: `special-display-regexps' is an obsolete variable (as | of 24.3); use `display-buffer-alist' instead. | org.el:6987:10:Warning: `special-display-buffer-names' is an obsolete variable | (as of 24.3); use `display-buffer-alist' instead. These are not trivial to fix. If someone wants to have a look, please go ahead. | In org-shiftcontrolup: | org.el:19234:11:Warning: org-clock-timestamps-up called with 1 argument, but | accepts only 0 | | In org-shiftcontroldown: | org.el:19244:11:Warning: org-clock-timestamps-down called with 1 argument, but | accepts only 0 Fixed, thanks. | In org-switch-to-buffer-other-window: | org.el:20957:23:Warning: `special-display-function' is an obsolete variable | (as of 24.3); use `display-buffer-alist' instead. | org.el:20956:52:Warning: `special-display-regexps' is an obsolete variable (as | of 24.3); use `display-buffer-alist' instead. | org.el:20956:23:Warning: `special-display-buffer-names' is an obsolete | variable (as of 24.3); use `display-buffer-alist' instead. | Wrote /home/nick/src/emacs/org/org-mode/lisp/org.elc Same as above. and a test failure: Fixed too, thanks! -- Bastien
Re: [O] date function in table formula does not understand German date stamps
Hi Viktor, Viktor Rosenfeld listuse...@gmail.com writes: I use the function `date' in a table formula to convert org date stamps to integers for further processing. However, after switching Emacs to a German locale, this no longer works. Consider the table below: | Stamp| date | |--+| | [2012-10-31 Wed] | 734808 | | [2012-10-31 Mi] | #ERROR | #+TBLFM: $2=date($1) From current master, this table now returns correct results. Please test and let me know if this is okay for you. Thanks for pointing this! -- Bastien
[O] org bingo
I have exactly 386 TODO entries and may as well introduce some randomness to get to them. org-random-entry: select and goto a random todo entry. Prefix allows you to select which todo keyword. https://gist.github.com/4343164
Re: [O] export_file_name problem with new exporter
Nicolas Goaziou writes: By validating, do you mean that I have received them back signed from the FSF? (I signed and sent them a few weeks ago, still waiting to get them back ...) Yes. We have to wait for confirmation from the FSF. It shouldn't be too long now. I have received the confirmation from the FSF (the scanned papers with their signature). I'll commit as soon as I can find the magic git incantations to get rid of the merge commits that happened as I was pulling changes from the repository. Alan
