Re: [O] Point jumps when changing timestamps
Matt Lundin m...@imapmail.org writes: I realize that I can change a scheduled timestamp with C-s C-s, and I often do. But I often find myself needing to move appointments such as the following back and forward a day: * An appointment 2011-08-04 Thu +1w If I am on the headline, the easiest way (for me) to navigate to the headline is C-n C-e. Then I can type S-left or S-right and quickly move through the dates; the cursor, moreover, will be in a convenient position for typing RET and adding a line of notes. This, for me, is a bit more convenient than typing C-n C-3 C-f or C-s , etc. Ok, it may be convenient in that specific case, but it still looks like a hack to me. Another solution would be to implement a function to navigate between time-stamps, similar to `org-next-link'. One can even generalize this function to move to the next non-structural element (time-stamp, link, footnote, latex snippet, emphasized text)[1]. From a UI perspective, however, I would suggest that a bit looser behavior adds some convenience to org-mode. For instance C-c C-o will currently open a link if the cursor is at the point before or after it. [[http://www.google.com]] ^ here^ here This is different. `org-open-at-point' is an end-user function, whereas `org-at-timestamp-p' isn't. I don't think predicates should be sloppy: I don't want to implement `org-really-at-timestamp-p'. Furthermore, being loose isn't always convenient. In the following example, where will I go if I use C-c C-o on the space between the two links? [[http://www.google.com][Google]] [[http://www.bing.com][Bing]] I'd suggest to fix `org-at-timestamp-p', and allow, if it must be, sloppiness in `org-shiftleft' and friends. Regards, Footnotes: [1] This and a convenient paragraph motion command could be the roots of an interesting Org parser. -- Nicolas Goaziou
Re: [O] Inline tasks in agenda search
Hello, suvayu ali fatkasuvayu+li...@gmail.com writes: Hi again, On Mon, Aug 1, 2011 at 6:49 PM, suvayu ali fatkasuvayu+li...@gmail.com wrote: On Mon, Aug 1, 2011 at 5:57 PM, suvayu ali fatkasuvayu+li...@gmail.com wrote: Hi Orgers, Is there any way to ignore the END entries in inline tasks in agenda search results? Strangely now this works! Don't know what I changed. I was mistaken, the problem is still there. The second search simply didn't have the END entries which I mistakenly thought the problem was resolved. Let me try to outline the issue clearly again. Lets say I have this subtree: ** Bs⁰ mass :mass: Bs⁰ mass is reconstructed for + Bs⁰-Dsπ using the π mass hypothesis + Bs⁰-DsK using both the K and π mass hypothesis _Questions_: *** π hypothesis:Qn: Why π hypothesis is considered only for DsK, and why not K hypothesis for Dsπ? *** END Now if I search for the tag mass (C-c a m mass RET), I get a search result like this: analysis: Bs⁰ mass :mass: analysis: π hypothesis :mass::Qn: analysis: END :mass:: The first 2 results are just what I expect. But the END from the inline task shows up in the agenda too! Is there anyway to get rid of that? You could add the following test, which will return a non-nil value for the closing of an inline-task, in `org-agenda-skip-function': #+begin_src org (and (featurep 'org-inlinetask) (let ((case-fold-search t)) (org-looking-at-p (concat (org-inlinetask-outline-regexp) end[ \t]*$ #+end_src Regards, -- Nicolas Goaziou
Re: [O] Inline tasks in agenda search
Hi Nicolas, Thanks a lot for your response. On Fri, 05 Aug 2011 10:53:43 +0200 Nicolas Goaziou n.goaz...@gmail.com wrote: #+begin_src org (and (featurep 'org-inlinetask) (let ((case-fold-search t)) (org-looking-at-p (concat (org-inlinetask-outline-regexp) end[ \t]*$ #+end_src I tried this: (setq org-agenda-skip-function '(and (featurep 'org-inlinetask) (let ((case-fold-search t)) (org-looking-at-p (concat (org-inlinetask-outline-regexp) end[ \t]*$) But performing a search where an END entry would otherwise show up causes the following error. A search without END in the result completes cleanly though. Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p t) org-agenda-skip() byte-code(..) org-scan-tags(agenda (and (progn (setq org-cached-props nil) (member Dsh tags-list)) t) nil) byte-code(..) org-tags-view(nil) call-interactively(org-tags-view) byte-code(..) org-agenda(nil) call-interactively(org-agenda nil nil) -- Suvayu Open source is the future. It sets us free.
Re: [O] Inline tasks in agenda search
Suvayu Ali fatkasuvayu+li...@gmail.com writes: I tried this: (setq org-agenda-skip-function '(and (featurep 'org-inlinetask) (let ((case-fold-search t)) (org-looking-at-p (concat (org-inlinetask-outline-regexp) end[ \t]*$) But performing a search where an END entry would otherwise show up causes the following error. A search without END in the result completes cleanly though. It's because I only gave you a part of the required function. Also, if you look at the doc-string, you'll see that: 1. it should return the position to continue the search from; 2. you should set `org-agenda-skip-function-global' instead. So, you can try: #+begin_src org (setq org-agenda-skip-function-global (lambda () (when (and (featurep 'org-inlinetask) (let ((case-fold-search t)) (org-looking-at-p (concat (org-inlinetask-outline-regexp) end[ \t]*$ (or (save-excursion (outline-next-heading)) (point-max) #+end_src Regards, -- Nicolas Goaziou
Re: [O] Inline tasks in agenda search
Hi Nicolas, On Fri, Aug 5, 2011 at 12:00 PM, Nicolas Goaziou n.goaz...@gmail.com wrote: It's because I only gave you a part of the required function. Also, if you look at the doc-string, you'll see that: 1. it should return the position to continue the search from; That was extremely dense of me. I wasn't thinking properly. 2. you should set `org-agenda-skip-function-global' instead. Yes, I tried that first but it didn't work (obviously because of not using the lambda!), so I tried the normal one. Thanks a lot, works great now. -- Suvayu Open source is the future. It sets us free.
Re: [O] Point jumps when changing timestamps
Nicolas Goaziou n.goaz...@gmail.com writes: Matt Lundin m...@imapmail.org writes: If I am on the headline, the easiest way (for me) to navigate to the headline is C-n C-e. Then I can type S-left or S-right and quickly move through the dates; the cursor, moreover, will be in a convenient position for typing RET and adding a line of notes. This, for me, is a bit more convenient than typing C-n C-3 C-f or C-s , etc. Ok, it may be convenient in that specific case, but it still looks like a hack to me. Another solution would be to implement a function to navigate between time-stamps, similar to `org-next-link'. One can even generalize this function to move to the next non-structural element (time-stamp, link, footnote, latex snippet, emphasized text)[1]. That sounds like a good idea. From a UI perspective, however, I would suggest that a bit looser behavior adds some convenience to org-mode. For instance C-c C-o will currently open a link if the cursor is at the point before or after it. [[http://www.google.com]] ^ here^ here This is different. `org-open-at-point' is an end-user function, whereas `org-at-timestamp-p' isn't. I don't think predicates should be sloppy: I don't want to implement `org-really-at-timestamp-p'. Furthermore, being loose isn't always convenient. In the following example, where will I go if I use C-c C-o on the space between the two links? [[http://www.google.com][Google]] [[http://www.bing.com][Bing]] It seems that google wins in this instance. :) I'd suggest to fix `org-at-timestamp-p', and allow, if it must be, sloppiness in `org-shiftleft' and friends. Thanks for the detailed explanation. That sounds fine. My concern here is not with the cleanness of the code but with usability. For years, org users have been able to use S-left and S-right when the cursor immediately follows the timestamp. This has felt, to me, both deliberate and natural -- it has become a fundamental part of the way I use org-mode. If the underlying code can be made cleaner, that's fine, so long as the usability remains. But it is also very likely that I am the only person who changes timestamps in this way. Are there any others? Best, Matt
Re: [O] Largest org file you have + performance
jiangzuo...@gmail.com jiangzuo...@gmail.com writes: My largest org file is QuanSongCi.org, contains ci poetry of Song dynasty, about 6MB size. Editing in emacs is very slow, save needs to wait about minutes. convert to html needs to wait about minutes, too. So, sometimes, sed like tools is preferred to do editing and converting. Thanks for these details. I can report similar experiences with large files. As far as I understand, large org-mode buffers are slow because there are many overlays, which (unlike text properties), don't scale well: (info (elisp) Overlays) This is right now an inescapable limitation of org-mode, since outline-mode relies on overlays. There was brief talk on emacs-dev of rewriting text-properties so that outline-mode could use them instead of overlays, but I do not believe the proposal was pursued further: http://permalink.gmane.org/gmane.emacs.devel/131304 Best, Matt
Re: [O] C-x n s no longer works in outline mode
Note: Broken by commit http://orgmode.org/w/?p=org-mode.git;a=commitdiff;h=1e59039f8cf93830f930f7dc99117c41586552e9
[O] Schedule event
In the Org manual, a distinction is made between items that have a timestamp with the SCHEDULED keyword and items that have a plain timestamp: Scheduling an item in Org-mode should not be understood in the same way that we understand scheduling a meeting. Setting a date for a meeting is just a simple appointment, you should mark this entry with a simple plain timestamp, to get this item shown on the date where it applies. This is a frequent misunderstanding by Org users. In Org-mode, scheduling means setting a date when you want to start working on an action item. http://orgmode.org/org.html#Deadlines-and-scheduling I call these items with plain timestamps events. These are items that come and go on the agenda whether or not I do anything. I add events to my agenda pretty often, so I'd like to schedule them using the same interface I use to schedule SCHEDULED items. Someone on IRC suggested that I use the following function: --8---cut here---start-8--- (defun org-schedule-event () (interactive) (let ((org-scheduled-string )) (org-schedule))) --8---cut here---end---8--- However, it inserts an extra space. Example: --8---cut here---start-8--- * Test 2011-08-05 Fri --8---cut here---end---8--- instead of: --8---cut here---start-8--- * Test 2011-08-05 Fri --8---cut here---end---8--- I could hack together a fix for this, but I was thinking that perhaps the org-schedule function should be made more general so that it can be combined with the org-deadline function, which has much of the same code, and used to insert plain timestamps as well. Thoughts?
Re: [O] [babel] tangle from within codeblock?
Rainer M Krug r.m.k...@gmail.com writes: Hi I have an R package in org, and would like to tangle it before I submit to svn. I commit via a code block: #+begin_src sh :results output svn commit -m edits #+end_src How can I tangle automatically before I commit? I could use batch execution as described in http://orgmode.org/manual/Batch-execution.html but I think it would be useless to start another emacs instance? I thought that I could put it into a header variable to have it evaluated, but I seem to be missing something: * test #+begin_src sh :tangle test.sh :var TANGLED=(org-babel-tangle) echo TEST'' #+end_src But I get an error: Saving file /home/rkrug/tmp/test.org... Wrote /home/rkrug/tmp/test.org (No changes need to be saved) [56 times] cons: Lisp nesting exceeds `max-lisp-eval-depth' I have the feeling, I am missing something small. Is there a different way to achieve this? Hi Rainer, You are very close, the problem is that the code block whose header argument initiates the tangling should not itself be tangled, otherwise you will wind up with the infinite recursion error you've noticed. A setup like the following should work... ** tangle before evaluating a code block #+begin_src sh :var TANGLED=(org-babel-tangle) :tangle no wc $TANGLED #+end_src #+results: : 2 2 11 it.sh #+begin_src sh :tangle it.sh echo TEST #+end_src Best -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] ebib configuration for org-bibtex
t...@tsdye.com (Thomas S. Dye) writes:
Aloha all,
I'm trying, partially successfully, to configure org-bibtex so it mimics
some useful features of ebib. In particular, I'm wanting to add several
optional fields that ebib uses.
I have this in .emacs:
#+begin_src emacs-lisp :tangle yes
(dolist (type org-bibtex-types)
(push :url (cdr (assoc :optional (cdr type
(push :annote (cdr (assoc :optional (cdr type
(push :abstract (cdr (assoc :optional (cdr type
(push :keywords (cdr (assoc :optional (cdr type
(push :file (cdr (assoc :optional (cdr type
)
(push (cons :url A URL for the reference) org-bibtex-fields)
(push (cons :annote Annotation is typically not exported)
org-bibtex-fields)
(push (cons :abstract Abstract for annotated bibliography)
org-bibtex-fields)
(push (cons :keywords Keywords for sorting with ebib) org-bibtex-fields)
(push (cons :file A local file path used by ebib to open the
reference in an appropriate application) org-bibtex-fields)
#+end_src
Most of it works fine, but the optional :file field doesn't respect its
argument. So, the following entry in the Org-mode file:
Hi Tom,
The :file property is treated in a special manner when Org-mode resolves
properties (notice it is an element of the `org-special-properties'
variable). I've just pushed up a change which temporarily removes :file
from this list while resolving bibtex entries. This change should fix
your reported problem -- please let me know if it doesn't. If any other
elements of `org-special-properties' seem likely to cause problems we
can temporarily remove them as well.
Best -- Eric
** Active Documents with Org-mode
:PROPERTIES:
:TITLE:Active Documents with Org-mode
:TYPE: article
:AUTHOR: Eric Schulte and Dan Davison
:JOURNAL: Computing in Science and Engineering
:YEAR: 2011
:VOLUME: 13
:NUMBER: 3
:PAGES:2--9
:MONTH:May/June
:URL: http://www.cs.unm.edu/~eschulte/data/CISE-13-3-SciProg.pdf
:FILE: Schulte-Davison-Babel.pdf
:CUSTOM_ID: schulte11:_activ_docum_org
:END:
is exported with org-bibtex like this:
@article{schulte11:_activ_docum_org,
author = {Eric Schulte and Dan Davison},
title ={Active Documents with Org-mode},
journal = {Computing in Science and Engineering},
year = 2011,
file = {/Users/dk/Public/projects/916-rr/rr.org},
url =
{http://www.cs.unm.edu/~eschulte/data/CISE-13-3-SciProg.pdf},
volume = 13,
number = 3,
pages ={2--9},
month ={May/June}
}
Pressing f in ebib now just takes me back to the Org-mode file, rather
than launching a pdf reader on my local copy of the article.
Any ideas how I can achieve my goal?
All the best,
Tom
--
Eric Schulte
http://cs.unm.edu/~eschulte/
Re: [O] [PATCH] testing/ort-test.el, regexp to find files
Applied, Thanks -- Eric Litvinov Sergey slitvi...@gmail.com writes: org-test picks up temporary and backup files. Please consider a patch the attachments to get rid of them. From 9b616baf0f3df63ea13ffde37c9c5aff903fac4e Mon Sep 17 00:00:00 2001 From: Sergey Litvinov slitvi...@gmail.com Date: Mon, 1 Aug 2011 00:47:32 +0200 Subject: [PATCH] Get rid of tmp and backup file in test load --- testing/org-test.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/testing/org-test.el b/testing/org-test.el index 96e693f..4e2f8e6 100644 --- a/testing/org-test.el +++ b/testing/org-test.el @@ -204,7 +204,7 @@ files. (lambda (path) (if (file-directory-p path) (rload path) (load-file path))) (directory-files base 'full - ^\\([^.]\\|\\.\\([^.]\\|\\..\\)\\).*\\.el + ^\\([^.]\\|\\.\\([^.]\\|\\..\\)\\).*\\.el$ (rload (expand-file-name lisp org-test-dir)) (rload (expand-file-name lisp (expand-file-name contrib org-test-dir) -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [BABEL,PATCH] cpp-c++-mode, ob-C mode tests
Litvinov Sergey slitvi...@gmail.com writes:
The first patch maps cpp language code to c++-mode. The second patch
adds tests for ob-C.
The first patch is applied, and the second patch will be applied once
your FSF assignment goes through.
Many thanks for these contributions!
-- Eric
From d0bc3554ec70138245289f1fabf78e2e86436c78 Mon Sep 17 00:00:00 2001
From: Sergey Litvinov slitvi...@gmail.com
Date: Wed, 3 Aug 2011 22:02:43 +0200
Subject: [PATCH 1/2] Map cpp to c++-mode
---
lisp/org-src.el |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lisp/org-src.el b/lisp/org-src.el
index 30ffc34..094ec09 100644
--- a/lisp/org-src.el
+++ b/lisp/org-src.el
@@ -155,7 +155,7 @@ but which mess up the display of a snippet in Org
exported files.)
(defcustom org-src-lang-modes
'((ocaml . tuareg) (elisp . emacs-lisp) (ditaa . artist)
(asymptote . asy) (dot . fundamental) (sqlite . sql)
-(calc . fundamental) (C . c))
+(calc . fundamental) (C . c) (cpp . c++))
Alist mapping languages to their major mode.
The key is the language name, the value is the string that should
be inserted as the name of the major mode. For many languages this is
--
1.7.1
From fba6eef6944766e675e4abe1d11d347b9a728031 Mon Sep 17 00:00:00 2001
From: Sergey Litvinov slitvi...@gmail.com
Date: Wed, 3 Aug 2011 22:03:19 +0200
Subject: [PATCH 2/2] Add tests for ob-C.el
---
testing/README.org |1 +
testing/examples/ob-C-test.org | 44
testing/lisp/test-ob-C.el | 43 +++
3 files changed, 88 insertions(+), 0 deletions(-)
create mode 100644 testing/examples/ob-C-test.org
create mode 100644 testing/lisp/test-ob-C.el
diff --git a/testing/README.org b/testing/README.org
index 2f16a55..cb408db 100644
--- a/testing/README.org
+++ b/testing/README.org
@@ -77,6 +77,7 @@ First tangle this file out to your desktop.
(require 'org-id)
(org-id-update-id-locations
(list (concat org-dir /testing/examples/babel.org)
+ (concat org-dir /testing/examples/ob-C-test.org)
(concat org-dir /testing/examples/normal.org)
(concat org-dir /testing/examples/ob-awk-test.org)
(concat org-dir /testing/examples/ob-fortran-test.org)
diff --git a/testing/examples/ob-C-test.org b/testing/examples/ob-C-test.org
new file mode 100644
index 000..4721c96
--- /dev/null
+++ b/testing/examples/ob-C-test.org
@@ -0,0 +1,44 @@
+#+Title: a collection of examples for ob-C tests
+#+OPTIONS: ^:nil
+* Simple tests
+ :PROPERTIES:
+ :ID: fa6db330-e960-4ea2-ac67-94bb845b8577
+ :END:
+#+source: simple
+#+begin_src cpp :includes iostream :results silent
+ std::cout 42;
+ return 0;
+#+end_src
+
+#+source: integer_var
+#+begin_src cpp :var q=12 :includes iostream :results silent
+ std::cout q;
+ return 0;
+#+end_src
+
+#+source: two_var
+#+begin_src cpp :var q=12 :var p=10 :includes iostream :results silent
+ std::cout p+q;
+ return 0;
+#+end_src
+
+#+source: string_var
+#+begin_src cpp :var q=word :includes '(iostream cstring) :results
silent
+ std::cout q ' ' strlen(q);
+ return 0;
+#+end_src
+
+#+source: define
+#+begin_src cpp :defines N 42 :includes iostream :results silent
+ std::cout N;
+ return 0;
+#+end_src
+
+* Array
+#+source: array
+#+begin_src cpp :includes iostream :results vector :results silent
+ for (int i=1; i3; i++) {
+std::cout i '\n';
+ }
+ return 0;
+#+end_src
diff --git a/testing/lisp/test-ob-C.el b/testing/lisp/test-ob-C.el
new file mode 100644
index 000..5ee7bec
--- /dev/null
+++ b/testing/lisp/test-ob-C.el
@@ -0,0 +1,43 @@
+(require 'ob-C)
+
+(ert-deftest ob-C/assert ()
+ (should t))
+
+(ert-deftest ob-C/simple-program ()
+ Hello world program.
+ (org-test-at-id fa6db330-e960-4ea2-ac67-94bb845b8577
+(org-babel-next-src-block)
+(should (= 42 (org-babel-execute-src-block)
+
+(ert-deftest ob-C/integer-var ()
+ Test of an integer variable.
+ (org-test-at-id fa6db330-e960-4ea2-ac67-94bb845b8577
+(org-babel-next-src-block 2)
+(should (= 12 (org-babel-execute-src-block)
+
+(ert-deftest ob-C/two-integer-var ()
+ Test of two input variables
+ (org-test-at-id fa6db330-e960-4ea2-ac67-94bb845b8577
+(org-babel-next-src-block 3)
+(should (= 22 (org-babel-execute-src-block)
+
+(ert-deftest ob-C/string-var ()
+ Test of a string input variable
+ (org-test-at-id fa6db330-e960-4ea2-ac67-94bb845b8577
+(org-babel-next-src-block 4)
+(should (equal word 4 (org-babel-execute-src-block)
+
+(ert-deftest ob-C/preprocessor ()
+ Test of a string variable
+ (org-test-at-id fa6db330-e960-4ea2-ac67-94bb845b8577
+(org-babel-next-src-block 5)
+(should (= 42 (org-babel-execute-src-block)
+
+(ert-deftest ob-C/table ()
+ Test of a table output
+
[O] How to uniformly configure multiple org files
In each org file I usually put several configuration lines such as #+STARTUP, #+OPTIONS, #+LINK, etc. Is there a way to keep these configurations in a single file and then include this file in each org file I want? This would be particularly useful for projects. What I have in mind is something like a #+INCLUDE_CONF keyword similar to #+INCLUDE, but while #+INCLUDE includes the content of one org-file into another, the #+INCLUDE_CONF would include the configuration comments while ignoring the content (so that we could use headings to separate the configuration comments, for instance). -- Darlan
Re: [O] How to uniformly configure multiple org files
Hi Darlan, Please check #SETUPFILE http://orgmode.org/manual/In_002dbuffer-settings.html Regards, .j. On Fri, Aug 05, 2011 at 02:54:30PM -0300, Darlan Cavalcante Moreira wrote: In each org file I usually put several configuration lines such as #+STARTUP, #+OPTIONS, #+LINK, etc. Is there a way to keep these configurations in a single file and then include this file in each org file I want? This would be particularly useful for projects. What I have in mind is something like a #+INCLUDE_CONF keyword similar to #+INCLUDE, but while #+INCLUDE includes the content of one org-file into another, the #+INCLUDE_CONF would include the configuration comments while ignoring the content (so that we could use headings to separate the configuration comments, for instance).
[O] bug: export of results in babel/R prevents export
Hi, when trying to export a file (example see below) with R code and the parameter :exports set to both or results Test babel #+BABEL: :exports both :session #+begin_src R 1:10 #+end_src to html or pdf, export fails with Symbol's function definition is void: copy-seq. This worked fine with release 7.5, and appeared first with the commit 6ddad0a: ob: not including export-variable headers in cache sha1 (and is still present with the latest version). Can anyone confirm this behavior? Best Julian
Re: [O] bug: export of results in babel/R prevents export
Julian Gehring julian.gehr...@googlemail.com writes: Hi, when trying to export a file (example see below) with R code and the parameter :exports set to both or results Test babel #+BABEL: :exports both :session #+begin_src R 1:10 #+end_src to html or pdf, export fails with Symbol's function definition is void: copy-seq. Hi Julian, I just pushed up a change which should fix this problem. Please let me know if this error persists. Best -- Eric -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] bug: export of results in babel/R prevents export
Hi Eric, thank you for the fast response. Everything is working fine now. Best Julian
Re: [O] How to uniformly configure multiple org files
Thanks, this is exactly what I need. At Fri, 5 Aug 2011 15:09:17 -0300, Juan Pechiar j...@pechiar.com wrote: Hi Darlan, Please check #SETUPFILE http://orgmode.org/manual/In_002dbuffer-settings.html Regards, .j. On Fri, Aug 05, 2011 at 02:54:30PM -0300, Darlan Cavalcante Moreira wrote: In each org file I usually put several configuration lines such as #+STARTUP, #+OPTIONS, #+LINK, etc. Is there a way to keep these configurations in a single file and then include this file in each org file I want? This would be particularly useful for projects. What I have in mind is something like a #+INCLUDE_CONF keyword similar to #+INCLUDE, but while #+INCLUDE includes the content of one org-file into another, the #+INCLUDE_CONF would include the configuration comments while ignoring the content (so that we could use headings to separate the configuration comments, for instance).
Re: [O] bug: export of results in babel/R prevents export
Eric Schulte schulte.e...@gmail.com writes: Julian Gehring julian.gehr...@googlemail.com writes: Symbol's function definition is void: copy-seq. I just pushed up a change which should fix this problem. Please let me know if this error persists. Alternatively, doing an M-x org-reload (bound to C-c C-x !) also gets rid of this error. 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] ebib configuration for org-bibtex
Eric Schulte schulte.e...@gmail.com writes: t...@tsdye.com (Thomas S. Dye) writes: Aloha all, I'm trying, partially successfully, to configure org-bibtex so it mimics some useful features of ebib. In particular, I'm wanting to add several optional fields that ebib uses. I have this in .emacs: #+begin_src emacs-lisp :tangle yes (dolist (type org-bibtex-types) (push :url (cdr (assoc :optional (cdr type (push :annote (cdr (assoc :optional (cdr type (push :abstract (cdr (assoc :optional (cdr type (push :keywords (cdr (assoc :optional (cdr type (push :file (cdr (assoc :optional (cdr type ) (push (cons :url A URL for the reference) org-bibtex-fields) (push (cons :annote Annotation is typically not exported) org-bibtex-fields) (push (cons :abstract Abstract for annotated bibliography) org-bibtex-fields) (push (cons :keywords Keywords for sorting with ebib) org-bibtex-fields) (push (cons :file A local file path used by ebib to open the reference in an appropriate application) org-bibtex-fields) #+end_src Most of it works fine, but the optional :file field doesn't respect its argument. So, the following entry in the Org-mode file: Hi Tom, The :file property is treated in a special manner when Org-mode resolves properties (notice it is an element of the `org-special-properties' variable). I've just pushed up a change which temporarily removes :file from this list while resolving bibtex entries. This change should fix your reported problem -- please let me know if it doesn't. If any other elements of `org-special-properties' seem likely to cause problems we can temporarily remove them as well. Best -- Eric Hi Eric, I looked up org-special-properties: org-special-properties is a variable defined in `org.el'. Its value is (TODO TAGS ALLTAGS DEADLINE SCHEDULED CLOCK CLOSED PRIORITY TIMESTAMP TIMESTAMP_IA BLOCKED FILE CLOCKSUM) It looks to me as if FILE is the only one likely to play mischief with bib files. Thanks for the fix, which works as expected here. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] Handling errors in command line exporting of agenda?
I have a custom view that I'm exporting to a text file and then displaying on my wallpaper with conky. I noticed that if I actually have emacs open and a file is autosaved but not saved for real, then the exported text file is blank. I use this command in cron: ,--- | emacs -batch -l ~/.emacs -eval '(org-batch-agenda w)' ~/org/aux/agenda-export.txt `--- I ran this from the command line after noticing the cron job was coming up empty, and saw the error: ,--- | ...file.org locked by jwhendy... (pid 27250): (s, q, p, ?)? `--- If I saved the offending file, it re-ran fine. As soon as enough time elapsed to generate an auto-save (I'm assuming), it failed again. Any suggestions on how to proceed? For example, I though of: 1) writing a script that could handle the failure and leave the current agenda exported text file if it happened 2) a way to respond to the emacs query (not sure what s, p, q, ? do) Anything else that would work? If it's frozen and not safe to run this command while a file is open/being modified, then just aborting and leaving the status quot in the text file is what I'd like to do. Thanks! John
Re: [O] Handling errors in command line exporting of agenda?
Hi John, On Sat, Aug 6, 2011 at 12:15 AM, John Hendy jw.he...@gmail.com wrote: 1) writing a script that could handle the failure and leave the current agenda exported text file if it happened Do you run into the same problem if you one the file before hand in read only mode? Something like this before the agenda command might work. (find-file-read-only FILENAME) -- Suvayu Open source is the future. It sets us free.
Re: [O] Handling errors in command line exporting of agenda?
On Sat, Aug 6, 2011 at 1:34 AM, suvayu ali fatkasuvayu+li...@gmail.com wrote: if you one the file if you open* the file Sorry for the typo. -- Suvayu Open source is the future. It sets us free.
[O] (no subject)
[O] org-babel-pop-to-session
I am having a strange problem. I would like session-based evaluation of my R src blocks. I have the following defined in the header. #+property: session harland However, when I press C-c, the source block is not sent to the session harland. When I do M-x org-babel-pop-to-session I get a message saying: if: No org-babel-initiate-session function for nil! When I do M-x org-babel-initiate-session I get a message saying: call-interactively: Autoloading failed to define function org-babel-initiate-session There is obviously something silly that I am missing. Can somebody come to help please. Best, Vikas
[O] Bug: aquamacs hangs when scrolling column view [7.7 (release_7.7.104.g8425)]
When I move the scroll bar down in column view, Aquamacs typically hangs. This is repeatable with the following minimal.emacs file: --8---cut here---start-8--- (add-to-list 'load-path (expand-file-name ~/Documents/elisp/org-mode/lisp)) (add-to-list 'auto-mode-alist '(\\.\\(org\\ |org_archive\\|txt\\)$ . org-mode)) (setq org-agenda-files '(/tmp/test.org)) (require 'org-install) (require 'org-habit) (global-set-key \C-cl 'org-store-link) (global-set-key \C-ca 'org-agenda) (global-set-key \C-cb 'org-iswitchb) --8---cut here---end---8--- orgbug.org: --8---cut here---start-8--- # * foo * bar * baz * qux * foo * bar * baz * qux * foo * bar * baz * qux * foo * bar * baz * qux --8---cut here---end---8--- /Applications/Aquamacs.app/Contents/MacOS/Aquamacs -Q -l ~/minimal.emacs ~/orgbug.org Emacs : GNU Emacs 24.0.50.3 (i386-apple-darwin10.8.0, NS apple-appkit-1038.36) of 2011-08-02 on colli Package: Org-mode version 7.7 (release_7.7.104.g8425) current state: == (setq org-export-preprocess-before-selecting-backend-code-hook '(org-beamer-select-beamer-code) org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe) org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook) org-occur-hook '(org-first-headline-recenter) org-metaup-hook '(org-babel-load-in-session-maybe) org-export-preprocess-before-normalizing-links-hook '(org-remove-file-link-modifiers) org-confirm-shell-link-function 'yes-or-no-p org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc org-beamer-auto-fragile-frames org-beamer-place-default-actions-for-lists) org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars) org-support-shift-select t org-after-todo-state-change-hook '(org-clock-out-if-current) org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-babel-pre-tangle-hook '(save-buffer) org-export-blocks-postblock-hook '(org-exp-res/src-name-cleanup) org-mode-hook '(#[nil \300\301\302\303\304$\207 [org-add-hook change-major-mode-hook org-show-block-all append local] 5] #[nil \300\301\302\303\304$\207 [org-add-hook change-major-mode-hook org-babel-show-result-all append local] 5] org-babel-result-hide-spec org-babel-hide-all-hashes) org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe) org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-export-latex-format-toc-function 'org-export-latex-format-toc-default org-export-blocks '((src org-babel-exp-src-block nil) (comment org-export-blocks-format-comment t) (ditaa org-export-blocks-format-ditaa nil) (dot org-export-blocks-format-dot nil)) org-export-first-hook '(org-beamer-initialize-open-trackers) org-export-interblocks '((lob org-babel-exp-lob-one-liners) (src org-babel-exp-inline-src-blocks)) org-confirm-elisp-link-function 'yes-or-no-p org-metadown-hook '(org-babel-pop-to-session-maybe) org-agenda-files '(/tmp/test.org) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) )
Re: [O] org-babel-pop-to-session
On Sat, Aug 6, 2011 at 3:23 AM, Vikas Rawal vikasli...@agrarianresearch.org wrote: #+property: session harland I'm not sure I recognise this syntax. Are you sure this is correct? According to my understanding it should be something like this: #+BABEL: :session *harland* http://orgmode.org/manual/Buffer_002dwide-header-arguments.html#Buffer_002dwide-header-arguments -- Suvayu Open source is the future. It sets us free.
