Re: [O] How to turn off visibility-state messages from 'org-cycle?
Jambunathan K kjambunat...@gmail.com writes: Try this: (defadvice org-cycle-internal-local (around org-cycle-internal-local-suppress-messages activate) Do the local cycling action, but suppress messages. (letf (((symbol-function 'message) (symbol-function 'ignore))) ad-do-it)) (defadvice org-cycle-internal-global (around org-cycle-internal-global-suppress-messages activate) Do the global cycling action, but suppress messages. (letf (((symbol-function 'message) (symbol-function 'ignore))) ad-do-it)) You can also use `flet' form to `ignore' the `message'. Thats nice, thank you. On the other hand, I wonder if it wouldn't make sense to add my patch to org.el, since unconditionally writing messages for every visibility-state change produces quite a lot of clutter, so the user should be able to turn this off IMO. Thorsten Jolitz tjol...@gmail.com writes: Hi List, when calling Org-mode functionality form an external program, some functions seem to make use of 'org-cycle', what results in a lot of OVERVIEW messages arriving at stdout/stderr ,- | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | OVERVIEW | `- that are not really helpful and a bit of a hassle. ,- | (org-cycle optional ARG) | | | - When this function is called with a prefix argument, rotate the entire | buffer through 3 states (global cycling) | 1. OVERVIEW: Show only top-level headlines. | 2. CONTENTS: Show all headlines of all levels, but no body text. | 3. SHOW ALL: Show everything. `- Is there a way to turn these message off? I found things like 'org-no-popups or 'org-no-warnings but nothing like org-no-visibility-state-messages or so. Its not really a big problem, rather an inconvenience, but maybe its easy to solve when knowing where to look. -- cheers, Thorsten
[O] inline R source code breaks latex itemize environment
Dear () please have a look at the self-contained test case. I'm using the latest org-mode... Thanks in advance -- Best wishes H. Dieter Wilhelm Darmstadt Germany
Re: [O] english automatically option added to latex's babel package
Renato renn...@gmail.com writes:
Hi, I've customized org-latex-packages-alist and added the package
babel, with option italian, however in my latex exports I get:
\usepackage[italian, english]{babel}
I don't want the english option to be there (latex gives it priority
over the italian one it seems). What could be wrong? I have english as
default language on my system (archlinux), so maybe I should change some
variable in emacs?
From the documentation of `org-latex-classes'.
Likewise, if your header contains \\\usepackage[AUTO]{babel}\,
AUTO will be replaced with the language related to the language
code specified by `org-export-default-language', which see. Note
that constructions such as \\\usepackage[french,AUTO,english]{babel}\
are permitted.
So the correct way is to set `org-export-default-language'. None the
less I'd be interested in seeing a minimal example (from emacs -q)
that reproduce your error. There may be a bug in
`org-latex-guess-babel-language'.
–Rasmus
--
Summon the Mothership!
Re: [O] Simplifying the weekly agenda a tiny bit, howto?
François Pinard pin...@iro.umontreal.ca writes: Eric Abrahamsen e...@ericabrahamsen.net writes: First of all, if your event is a meeting, it should only be timestamped, not deadlined or scheduled. Then it will just show up where it's supposed to, and not before (or after). How do I get it quickly rescheduled then, when it is a regular activity? I find fairly convenient using t d to push an activity at its next slot in the future. Could I do something equivalent with mere time stamps? Hmm, I hadn't tried that with repeating events. There are a pile of commands for shifting timestamps/scheduled/deadline from the Agenda (either , or variously-prefixed versions of S-right and S-left. Changing the date/time of any event applies the same relative shift to all the events, which might not be what you want, but then that would also be the case if you're using deadlines to represent meetings. If t d is your current solution, you're not actually re-scheduling meetings, just canceling them, right? It's true there's not a lot of flexibility in plain old repeating timestamps. Maybe use a SCHEDULED tag instead of DEADLINE (which makes a little more semantic sense, and also doesn't produce coming-up warnings), or else use 'org-clone-subtree-with-time-shift' to just create a whole new heading for each meeting, with timestamps that can be adjusted individually. It probably shouldn't even be a TODO. Otherwise, scheduled TODOs show up on their schedule, and deadlined TODOs show up on their deadline, and also today's agenda, if you're coming up on the deadline. There are many Org commands able to find, display and otherwise handle TODOs. If I stop using such keywords, wouldn't I give up the tools? Maybe there are ways to reformulate them all using other commands, but at fist, it would require some searching, and acquiring new habits, presuming that there are alternative ways for all such tools. It does take a bit of fooling to make the best use of the tools available... In this case I'd say Richard's right: tags are what you should be using. They're just as easy to search for as TODOs, and they're considerably more flexible: you can make them up on the fly, or nest them in tag groups. The key nature of the TODO -- that you can shift it among several linked states -- isn't really what you need here. There are a host of variables [...] Check out variables starting org-agenda-skip-*, org-agenda-ignore-*, org-agenda-include-*, org-deadline-*, org-scheduled-* [...] Hope that helps, Undoubtedly :-). Thanks! François
Re: [O] inline R source code breaks latex itemize environment
Hi Dieter, Dieter Wilhelm, H. die...@duenenhof-wilhelm.de writes: Dear () please have a look at the self-contained test case. which apparently did not get through. If it got stripped by the list, make sure to either - have text attachments of mime-type text (e.g. text/plain) or - include text attachments inline Best, Andreas
Re: [O] english automatically option added to latex's babel package
Renato renn...@gmail.com writes: Hi, I've customized org-latex-packages-alist and added the package babel, with option italian, however in my latex exports I get: Add it with AUTO instead of italian and then specify the language in your document using #+language: it If you want Italian for all documents by default, set org-export-default-language: ,[ C-h v org-export-default-language RET ] | org-export-default-language is a variable defined in `ox.el'. | Its value is en | | Documentation: | The default language for export and clocktable translations, as a string. | This may have an association in | `org-clock-clocktable-language-setup', | `org-export-smart-quotes-alist' and `org-export-dictionary'. | This option can also be set with the LANGUAGE keyword. | | You can customize this variable. ` HTH, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.0.6-341-g338603
Re: [O] How to turn off visibility-state messages from 'org-cycle?
Would you wrap it all up in a patch and submit it? It would be great to have incorporated. Thanks, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.0.6-341-g338603
[O] [PATCH] [TINYCHANGE] optional `bookmark-set'
Hi all, I've added an option to customize the bookmark names that org-mode sets. I'm new to this list and I'd appreciate some feedback. I've posted yesterday, but there was no reply. regards, Oleh 0001-Capture-Refile-use-bookmark-set-conditionally.patch Description: Binary data
Re: [O] Switch for exported file types when evaluating code blocks
On Thu, Jul 18, 2013 at 09:02:41PM -0400, Nick Dokos wrote:
#+BEGIN_LaTeX
\includesvg{foo}
#+END_LaTeX
I believe even this can be integrated with Org using a filter. How
about something like this:
(defun my-svg-graphics (contents backend info)
(when (eq backend 'latex)
(replace-regexp-in-string \\`includegraphics.+\\({.+\.svg}\\)
includesvg\1 contents)))
(add-to-list 'org-export-filter-link-functions 'my-svg-graphics)
Of course the above ignores the options since I do not know if
\includesvg takes the same options. But that is a detail that can be
fixed by changing the regexp.
What do you think?
--
Suvayu
Open source is the future. It sets us free.
Re: [O] table references in org-babel AND latex
Hi there, sorry for the junk I sent regarding table references in org-babel AND latex. Org-mode is awesome. In such a case, it is not necessary to identify something by what it is in the classical LaTeX way and just label it (#+name:). Org-mode recognizes just what it is and the labels refer either to a table or figure, which have their class-based numberings. Sorry for the crap. It may still be helpful to include that code block header variables (#+HEADERS: :var) can't be assigned with a name including :. Best, Brian On 07/16/2013 10:00 PM, zenli...@gmail.com wrote: Hi There, it might be nice to include documentation about table references in org-babel AND latex, i.e.: +begin_example numbers in table [[tab:Table]] are important. #+CAPTION: Description of system #+NAME: tab:Table | Code | |--| |1 | |2 | |4 | |8 | | 16 | | 32 | | 64 | | 128 | | NaN | #+begin_src R :session :var FlaggingTable=tab:FlaggingTable :results silent :eval no-export write.csv(FlaggingTable, file=file.path(doc.dir, FlaggingTable.csv)) #+end_src Won't work, but #+begin_src R :session :var FlaggingTable=tab:FlaggingTable :results silent :eval no-export write.csv(FlaggingTable, file=file.path(doc.dir, FlaggingTable.csv)) #+end_src will! +end_example Maybe I missed something somewhere, it would be nice to see it as a footnote, to keep others sane :). Best, Brian GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw3d scroll bars) of 2013-05-15 on DDM03958 Org-mode version 8.0.5 (8.0.5-6-g426917-elpa @ ~/.emacs.d/elpa/org-20130708/)
Re: [O] english automatically option added to latex's babel package
Eric S Fraga e.fr...@ucl.ac.uk writes: Renato renn...@gmail.com writes: Hi, I've customized org-latex-packages-alist and added the package babel, with option italian, however in my latex exports I get: Add it with AUTO instead of italian and then specify the language in your document using #+language: it If you want Italian for all documents by default, set org-export-default-language: These are the recommend instructions, yes, and indeed how I imagined people to use it. I looked at it and while I can reproduce there's no bug. Start from emacs -q and eval (require 'ox-latex) (add-to-list 'org-latex-default-packages-alist '(italian babel nil)) When I export the document #+begin_src org * titel #+end_src the language defaults to org-export-default-language which is en. So it does what you'd expect and loads English in front of Italian 'cause it's the document language. Compare to what Eric says: #+begin_src org #+LANGUAGE: it * titel #+end_src You get only Italian. So it guesses the language correctly. –Rasmus -- Got mashed potatoes. Ain't got no T-Bone. No T-Bone
Re: [O] [babel] Problems assigning tables as variables using #+CALL and using properties in code blocks and sbe calls
Hi Eric, thanks you so much for always being so responsive to my silly questions :) I apologize, I wrote that mail 2 am after fiddling around with that problem for about 3 hours. Trying to reduce the problem to a minimal example, I almost built in stupid errors. I was holding back to send examples as org-file attachment because I believe that attachments can't be parsed by the different mailing list archives and thus, any infos there are not searchable. However, I guess in the future I will simple paste the example and attach a org-file (which in turn I can really test before sending). Ok back on track. My problem seems to be quite strange. It is not exactly related to babel but more about the interface babel + python. Taking your example, I modified it to reflect my problem //-- content of table-calls.org #+TBLNAME: tablename | | Name | StudentID | 1.1 | 1.2 | 1.3 | 1.4 | 2.1 | 2.2 | 2.3 | 2.4 | 2.5 | Sum 1 | Sum 2 | Total Sum | Mark | Remark | |---+--+---+-+-+-+-+-+-+-+-+-+---+---+---+--+| | # | Mr A | 1 | 0 | 12 | 0 | 0 | 17 | 8 | 10 | 0 | 0 |12 |35 |47 |5 || | # | Ms B | 2 | 1 | 2 | 3 | 4 | 5 | 2 | 3 | 4 | 5 |10 |19 |29 |5 | second | I have the following code block #+name: test #+begin_src python :var table=tablename :exports results return type(table[1]) #+end_src #+RESULTS: test : class 'list' If I call that function the result is correct However using #+CALL: test[:var table=tablename]() :exports results #+RESULTS: test[:var table=tablename]():exports results : class 'NoneType' #+CALL: test(table=tablename) :exports results #+RESULTS: test(table=tablename):exports results : class 'NoneType' // --end I think I get a bit further with the trouble shooting. As you can see, the problem seems to be Calling the source code block directly table seems to be of type list which is (I guess) correct However, calling the code via a #+CALL line, the input data (table) is of type 'NoneType'. This hoax the later operation in a very strange way. E.g. plan return of the table is fine, even table[i] works, more complex operations don't. The question for me is, why is there a difference of the data (table) type depending on the call? As for the second part of the email, again sorry I was kind of tired. Take I have this property drawer *** Exam evaluation :intern: :PROPERTIES: :passscore: 50 :extrapoints: 1 :END: and within a table formula line e.g. '(sbe score2mark (score $15) (passscore $PROP_passscore) This works well, now I want to use the same property as value of a source code block Those fail: #+CALL: createscoretable(passscore=passscore) :exports results #+CALL: createscoretable(passscore) :exports results #+CALL: createscoretable($PROP_passscore) :exports results #+CALL: createscoretable(passscore=$PROPpassscore) :exports results I can see how to assign a property defined variable to a code block call. I tried modifications like *** Exam evaluation :intern: :PROPERTIES: :var: passscore=50 :extrapoints: 1 :END: and #+PROPERTY: var passscore=50 But none of them seem to work for me. Even if one work, would it work together with the way sbe calls property values? Basically, I want to use a variable defined in a Property-Drawer for both the sbe function within table formulars and as value for functions calls of source code blocks Thanks again for all your help! All the best Torsten On 19 July 2013 03:06, Eric Schulte schulte.e...@gmail.com wrote: Torsten Wagner torsten.wag...@gmail.com writes: Hi, I have a tables like this: #+TBLNAME: tablename | a | b |c | d | | 1 | 2 |3 |4 | | z | x | y |w| #+TBLNAME: othertablename | a | b |c | d | | 1 | 2 |3 |4 | | z | x | y |w| I have the following code block #+name: test #+begin_src python :var table=tablename :exports results import numpy as np tab = np.array(table) return np.array([tab[:,1], tab[:,-1]]).T #+end_src If I call that function the result is correct However using #+CALL: aushang[:var table=othertablename]() :exports results or #+CALL: aushang(table=othertablename) :exports results does not work. It seem the babel block does not get the table but something else in case its called by #+CALL:. In general, how-to refer to a table in #+CALL blocks? Your tables are identical, and you're not calling the test function in your call blocks. A more reasonable (to me) version of your example works as expected. On a similar line: I used $PROP_name to use property values within the sbe function. However, how to use the same property as input to a
[O] [PATCH] Enable silent visibility cycling (was: How to turn off visibility-state messages from 'org-cycle?)
Eric S Fraga e.fr...@ucl.ac.uk writes: Would you wrap it all up in a patch and submit it? It would be great to have incorporated. ok, done. PS I included this into `outshine.el' too, since outline-cycle showed the same behaviour. From 0a4dad9119af9aed8e5160a05e81ac35f2bb0044 Mon Sep 17 00:00:00 2001 From: tj t...@data-driven.de Date: Fri, 19 Jul 2013 13:47:20 +0200 Subject: [PATCH] Org: Enable silent visibility cycling * lisp/org.el: add boolean variable `org-cycle-silently'. add function `org-toggle-silent-cycling'. (org-cycle-internal-global): make visibility-state-change messages conditional on `org-cycle-silently'. The problem here was that, especially in batch use, unconditionally writing a message for each visibility-state-change might send a lot of clutter to stdout. Modified from a patch proposal by Thorsten Jolitz. --- lisp/org.el | 30 ++ 1 file changed, 26 insertions(+), 4 deletions(-) diff --git a/lisp/org.el b/lisp/org.el index fb5099e..1eb511d 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -6494,6 +6494,9 @@ and subscripts. (defvar org-inlinetask-min-level) +(defvar org-cycle-silently nil + Suppress visibility-state-change messages when non-nil.) + ;;;###autoload (defun org-cycle (optional arg) TAB-action and visibility cycling for Org-mode. @@ -6661,6 +6664,21 @@ in special contexts. (org-back-to-heading) (org-cycle))) +(defun org-toggle-silent-cycling (optional arg) + Toggle silent cycling between visibility states. + + When silent cycling is off, visibility state-change messages are + written to stdout (i.e. the *Messages* buffer), otherwise these + messages are suppressed. With prefix argument ARG, cycle silently + if ARG is positive, otherwise write state-change messages. + (interactive P) + (setq org-cycle-silently + (if (null arg) + (not org-cycle-silently) + ( (prefix-numeric-value arg) 0))) + (message Silent visibility cycling %s + (if org-cycle-silently enabled disabled))) + (defun org-cycle-internal-global () Do the global cycling action. ;; Hack to avoid display of messages for .org attachments in Gnus @@ -6672,9 +6690,11 @@ in special contexts. ;; We just created the overview - now do table of contents ;; This can be slow in very large buffers, so indicate action (run-hook-with-args 'org-pre-cycle-hook 'contents) - (unless ga (message CONTENTS...)) + (unless (or ga org-cycle-silently) + (message CONTENTS...)) (org-content) - (unless ga (message CONTENTS...done)) + (unless (or ga org-cycle-silently) + (message CONTENTS...done)) (setq org-cycle-global-status 'contents) (run-hook-with-args 'org-cycle-hook 'contents)) @@ -6683,7 +6703,8 @@ in special contexts. ;; We just showed the table of contents - now show everything (run-hook-with-args 'org-pre-cycle-hook 'all) (show-all) - (unless ga (message SHOW ALL)) + (unless (or ga org-cycle-silently) + (message SHOW ALL)) (setq org-cycle-global-status 'all) (run-hook-with-args 'org-cycle-hook 'all)) @@ -6691,7 +6712,8 @@ in special contexts. ;; Default action: go to overview (run-hook-with-args 'org-pre-cycle-hook 'overview) (org-overview) - (unless ga (message OVERVIEW)) + (unless (or ga org-cycle-silently) + (message OVERVIEW)) (setq org-cycle-global-status 'overview) (run-hook-with-args 'org-cycle-hook 'overview) -- 1.8.2.3 -- cheers, Thorsten
[O] Sorry: inline R source code breaks latex itemize environment
Sorry, the previous mail was sent inadvertently without attachments ... Dear () please have a look at the self-contained test case. I'm using the latest org-mode... Thanks in advance Dieter test.org Description: Binary data test.pdf Description: Adobe PDF document test.tex Description: TeX document
Re: [O] koma letter exporter: changing the priority of options
Hello,
ras...@gmx.us writes:
Viktor Rosenfeld listuse...@gmail.com writes:
,
| \KOMAoption{backaddress}{true}
| \KOMAoption{foldmarks}{true}
| \KOMAoption{fromphone}{true}
| \KOMAoption{fromemail}{true}
`
Perhaps the best option would be to change the default value of these
variables to nil? We have almost every option that personalizes
a letter, e.g., opening and closing, set to nil already. The only
benefit of having default values is to show off the features of
org-koma-letter. But it seems to be interfering with people's workflow
so best turn them off.
Doesn't this also more or less correspond to the default value of
scrlttr2? If so there's no reason to add it to the tex file and nil
is indeed a better default.
It took me a while to look at this (basically until I had to write
another letter), but here is a patch I propose to commit to do this.
--8---cut here---start-8---
diff --git a/contrib/lisp/ox-koma-letter.el b/contrib/lisp/ox-koma-letter.el
index 44626a9..8a98689 100644
--- a/contrib/lisp/ox-koma-letter.el
+++ b/contrib/lisp/ox-koma-letter.el
@@ -228,7 +228,7 @@ English manual of 2012-07-22)
-(defcustom org-koma-letter-use-backaddress t
+(defcustom org-koma-letter-use-backaddress nil
Print return address in small line above to address.
:group 'org-export-koma-letter
:type 'boolean)
@@ -243,12 +243,12 @@ Use `foldmarks:true' to activate default fold marks or
:group 'org-export-koma-letter
:type 'string)
-(defcustom org-koma-letter-use-phone t
+(defcustom org-koma-letter-use-phone nil
Print sender's phone number.
:group 'org-export-koma-letter
:type 'boolean)
-(defcustom org-koma-letter-use-email t
+(defcustom org-koma-letter-use-email nil
Print sender's email address.
:group 'org-export-koma-letter
:type 'boolean)
@@ -554,10 +554,10 @@ holding export options.
(with-phone (plist-get info :with-phone))
(with-email (plist-get info :with-email)))
(concat
- (format \\KOMAoption{backaddress}{%s}\n (if with-backaddress true
false))
- (format \\KOMAoption{foldmarks}{%s}\n (if with-foldmarks
with-foldmarks false))
- (format \\KOMAoption{fromphone}{%s}\n (if with-phone true false))
- (format \\KOMAoption{fromemail}{%s}\n (if with-email true false
+ (if with-backaddress (format \\KOMAoption{backaddress}{true}\n) )
+ (if (not (equal with-foldmarks true)) (format
\\KOMAoption{foldmarks}{%s}\n with-foldmarks) )
+ (if with-phone (format \\KOMAoption{fromphone}{true}\n) )
+ (if with-email (format \\KOMAoption{fromemail}{true}\n) )))
;; Document start
\\begin{document}\n\n
;; Subject
--8---cut here---end---8---
I did some experiments and it seems that by default foldmarks is
true. The idea behind the patch is that, if we don't change the default
values, then things are not output. Let me know if this is fine with you
and I'll commit this. (I'll also edit the work with the new default
values.)
I still have an issue with the default value for email. I have set-up my
email address in emacs, and it's picked up by the koma exporter. I want
to use a different address in my work letters (which use a custom lco
file), but the email address is overridden by the one picked up by the
following function:
(defun org-koma-letter-email ()
Return the current `user-mail-address'
user-mail-address)
What I propose is the following:
- we leave the default AUTHOR and EMAIL at nil
- if they are still nil, we output the default values _before_ inputting
the lco file
- if they are no longer nil, we output their values _after_ inputting
the lco file
This way, if they are not defined in the file, then the lco can override
them, otherwise the local option will be the one used.
What do you think?
Alan
Re: [O] Sorry: inline R source code breaks latex itemize environment
Try this:
- The average measured axial compression force \(F\) of 4 bearings
is src_R[:results value :exports results]{round(Fo,1)} kN
(relative stddev:
src_R[:results value :exports results]{round(Fs,1)} %)
(Switch to =:results value= instead of raw.)
I seem to recall asking about changing the fontification from
code/verbatim for the result, but don't recall the solution. Maybe it
is raw, since it's another variant of value, in which case there does
seem to be a bug since value doesn't break itemize.
John
On Fri, Jul 19, 2013 at 3:47 AM, Dieter Wilhelm, H.
dieter.wilh...@gmail.com wrote:
Sorry, the previous mail was sent inadvertently without attachments ...
Dear ()
please have a look at the self-contained test case. I'm using the
latest org-mode...
Thanks in advance
Dieter
[O] ox-freemind exporter
Dear org-mode Users and Developers, I checked out org-mode from today and tried the ox-freemind exporter. It fails with the error: `cond: Keyword argument :translations not one of (:name :parent :transcoders :options :filters :blocks :menu)'. I searched around and found a post[1] by Nicolas Goaziou who seems to maintain this exporter and a message that he fixed it after a change to the internal representation of back-ends. Am I missing something? Best Regards, Michael [1] http://lists.nongnu.org/archive/html/emacs-orgmode/2013-07/msg00241.html
Re: [O] ox-freemind exporter
On Fri, Jul 19, 2013 at 8:54 AM, Michael Bach pha...@gmail.com wrote: Dear org-mode Users and Developers, I checked out org-mode from today and tried the ox-freemind exporter. It fails with the error: `cond: Keyword argument :translations not one of (:name :parent :transcoders :options :filters :blocks :menu)'. I searched around and found a post[1] by Nicolas Goaziou who seems to maintain this exporter and a message that he fixed it after a change to the internal representation of back-ends. I can confirm, assuming I haven't missed an obvious setup step other than adding: (require 'ox-freemind) to my config. I get the same error. John Am I missing something? Best Regards, Michael [1] http://lists.nongnu.org/archive/html/emacs-orgmode/2013-07/msg00241.html
Re: [O] Simplifying the weekly agenda a tiny bit, howto?
Eric Abrahamsen e...@ericabrahamsen.net writes: How do I get it quickly rescheduled then, when it is a regular activity? I find fairly convenient using t d to push an activity at its next slot in the future. Could I do something equivalent with mere time stamps? Hmm, I hadn't tried that with repeating events. I stole a few minutes this morning to make tries. Unless there are operator errors :-), I got the impression that t d over a simple time stamp with a repeating part dynamically turns in into a TODO entry, which would defeat the purpose of removing TODO. But, and this is where I'm still under the effect of surprise and some incredulity, it seems that I do not even have to use t d, the repeating nature of the time stamp being automatically taken into account while computing the agenda. In any case, I decided to follow your advice and see where it brings me: I removed the TODO keyword ans scheduling clauses the most I could, and merely doing that yields a cleaner agenda (cleaner by my own criteria, taste varies of course). There are a pile of commands for shifting timestamps/scheduled/deadline Which I often use. The annoyance of doing explicit shifting is that I have to look at the repeater to decide the shifting amount. I much prefer if it could be automatic, not requiring human scrutiny each time. If t d is your current solution, you're not actually re-scheduling meetings, just canceling them, right? Well, Org turns TODO into DONE. But if there is a repeating clause in the time stamp, the time stamp is advanced appropriately and the DONE gets immediately turned back into TODO again, all by magic. [...] or else use 'org-clone-subtree-with-time-shift' to just create a whole new heading for each meeting, with timestamps that can be adjusted individually. Oh! I found this command a bit polluting, enough to avoid it until now. Maybe I did not get how it could genuinely serve me? I do not feel the need yet! :-) There are many Org commands able to find, display and otherwise handle TODOs. If I stop using such keywords, wouldn't I give up the tools? It does take a bit of fooling to make the best use of the tools available... I'll try avoiding TODO in most cases, finding my way around without them and developing new habits as needed. I'll see where it will bring me... Thanks to you, and Richard as well, for the feedback! François
Re: [O] Switch for exported file types when evaluating code blocks
Great Example, Nick, Thanks, will push on with this approach
~ malcolm_c...@stowers.org
From: emacs-orgmode-bounces+mec=stowers@gnu.org
[emacs-orgmode-bounces+mec=stowers@gnu.org] on behalf of Nick Dokos
[ndo...@gmail.com]
Sent: Thursday, July 18, 2013 8:02 PM
To: emacs-orgmode@gnu.org
Subject: Re: [O] Switch for exported file types when evaluating code blocks
Cook, Malcolm m...@stowers.org writes:
Hi Nick, I'm not sure how to use this ctan package in concert with
orgmode's export to tex-pdf.
Here's a simplfied example of what I did with it. The source block uses
dot to produce an SVG file for illustration - if you already have one
then you can ignore it:
--8---cut here---start-8---
#+LATEX_HEADER: \usepackage{svg}
* foo
#+name: foo
#+BEGIN_SRC dot :file foo.svg :exports results :results none
digraph foo {
a - b
}
#+END_SRC
#+BEGIN_LaTeX
\includesvg{foo}
#+END_LaTeX
--8---cut here---end---8---
Perhaps there is a way to use orgmode's export filtering capability to
swap in a up-to-date png when exporting to tex
PNG is a raster format whereas SVG is a vector format. I was trying to
produce some slides and I did use PNG at first because it's easier to
fit into the pdflatex workflow. But when I made the slides full screen,
the PNG got fuzzy. Sticking with SVG got rid of the fuzzies for me.
Hmmm
Anyone?
Thx!
-Original Message-
From: emacs-orgmode-bounces+mec=stowers@gnu.org
[mailto:emacs-orgmode-bounces+mec=stowers@gnu.org] On
Behalf Of Nick Dokos
Sent: Wednesday, July 17, 2013 11:02 PM
To: emacs-orgmode@gnu.org
Subject: Re: [O] Switch for exported file types when evaluating code blocks
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Hello again Malcolm,
On Thu, Jul 18, 2013 at 12:45:36AM +, Cook, Malcolm wrote:
I tend to work with org-export-babel-evaluate set to nil. Thus, my
code blocks are not evaled in the context of an export. Thus at
eval time there is no way of knowing what the eventual backend is
going to be.
I think I need an approach that auto converts svg to png
on-demand/on-the-fly during export.
In that case just use another source block with shell source. In that
block you can call inkscape to do the conversion. For an example, see
here:
http://ctan.mirrorcatalogs.com/info/svg-inkscape/InkscapePDFLaTeX.pdf#subsubsection.2.3.1
OT for the OP (say that three times fast!) but maybe of some use to
somebody:
For SVG, there is a latex package that is an evolutionary offshoot of
the above link. It does the inkscape dance so you don't have to:
http://www.tex.ac.uk/ctan/graphics/svg/
--
Nick
--
Nick
Re: [O] Switch for exported file types when evaluating code blocks
Suvayu,
This is splendid news! I will try it immediately upon return from gone
fishin in a week...
(erhm, that is, right after I figure out haw to migrate my orgmode SETUPFILE
to comport with new export backend I just upgraded to my fancy TOC and
org-export-html-table-tag javascript have gone missin)
Future is looking bright!,
~ malcolm_c...@stowers.org
From: emacs-orgmode-bounces+mec=stowers@gnu.org
[emacs-orgmode-bounces+mec=stowers@gnu.org] on behalf of Suvayu Ali
[fatkasuvayu+li...@gmail.com]
Sent: Friday, July 19, 2013 5:23 AM
To: emacs-orgmode@gnu.org
Subject: Re: [O] Switch for exported file types when evaluating code blocks
On Thu, Jul 18, 2013 at 09:02:41PM -0400, Nick Dokos wrote:
#+BEGIN_LaTeX
\includesvg{foo}
#+END_LaTeX
I believe even this can be integrated with Org using a filter. How
about something like this:
(defun my-svg-graphics (contents backend info)
(when (eq backend 'latex)
(replace-regexp-in-string \\`includegraphics.+\\({.+\.svg}\\)
includesvg\1 contents)))
(add-to-list 'org-export-filter-link-functions 'my-svg-graphics)
Of course the above ignores the options since I do not know if
\includesvg takes the same options. But that is a detail that can be
fixed by changing the regexp.
What do you think?
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Simplifying the weekly agenda a tiny bit, howto?
Richard Lawrence richard.lawre...@berkeley.edu writes: If it's a regular activity, you can use a repeater in the timestamp, like: * Weekly meeting 2013-07-18 Thu 15:00 +1w Hi, Richard. I also noticed I may even write: * Weekly meeting 2013-07-18 Thu 15:00 +1w and the time stamp gets automatically hidden in the agenda. Nice! :-) For non-regular meetings, I have a capture template that allows me to easily enter them; Same here! you can do things like tag all your meetings with a :meeting: or :appointment: tag [...] I tried that too for a long while, tagging meeting and duties according to where I am, travelling between customers, and later understood that I could go without tags and still be happy, and even happier. The real truth is that I'm not much comfortable with the tag approach, just not in Org context, but in general. I once (a that has been quite a long once) tried Delicious, to found out that proper maintenance of tags requires a lot of energy when the collection grows significantly. The feeling of adding a tag and forgetting an item gives an impression of immediate speed, but one has to pay for it sooner or later, so all totaled, I now think I'm better to sort out information immediately where it should land in some hierarchical structure, and learn to do that efficiently, than to go the tag way. I do use tags with Org, but in small and specific ways; I try to avoid them otherwise. Hope that's helpful! Surely. Exchange of ideas and methods with nice and spekable people is always helpful, would it be only for the pleasure it gives! Keep happy! François
[O] emacs org mode suggestion: read org content from buffers (not files)
I check my agenda, all the .org files are open in buffer, agenda shows up fineI open some buffers from network share, which then became unavailable out of homeI try to update my agendaagenda gets empty because those files are not available but the buffers are available in Emacsso I suggest to read from buffers if files are already open in buffers instead of insisting files being available this is my setup: (setq org-agenda-skip-unavailable-files t)
Re: [O] [babel] Problems assigning tables as variables using #+CALL and using properties in code blocks and sbe calls
Hi Eric, one mini-step forward. The #+CALL function does not work if the table has a horizontal line like in #+TBLNAME: othertablename | a | b | c | d | |---+---+---+---| | 4 | 3 | 2 | 1 | | z | x | y | w | however, it works for #+TBLNAME: othertablename | a | b | c | d | | 4 | 3 | 2 | 1 | | z | x | y | w | I guess we come closer to the problem ;) Thanks for all the help Torsten On 19 July 2013 13:06, Torsten Wagner torsten.wag...@gmail.com wrote: Hi Eric, thanks you so much for always being so responsive to my silly questions :) I apologize, I wrote that mail 2 am after fiddling around with that problem for about 3 hours. Trying to reduce the problem to a minimal example, I almost built in stupid errors. I was holding back to send examples as org-file attachment because I believe that attachments can't be parsed by the different mailing list archives and thus, any infos there are not searchable. However, I guess in the future I will simple paste the example and attach a org-file (which in turn I can really test before sending). Ok back on track. My problem seems to be quite strange. It is not exactly related to babel but more about the interface babel + python. Taking your example, I modified it to reflect my problem //-- content of table-calls.org #+TBLNAME: tablename | | Name | StudentID | 1.1 | 1.2 | 1.3 | 1.4 | 2.1 | 2.2 | 2.3 | 2.4 | 2.5 | Sum 1 | Sum 2 | Total Sum | Mark | Remark | |---+--+---+-+-+-+-+-+-+-+-+-+---+---+---+--+| | # | Mr A | 1 | 0 | 12 | 0 | 0 | 17 | 8 | 10 | 0 | 0 |12 |35 |47 |5 || | # | Ms B | 2 | 1 | 2 | 3 | 4 | 5 | 2 | 3 | 4 | 5 |10 |19 |29 |5 | second | I have the following code block #+name: test #+begin_src python :var table=tablename :exports results return type(table[1]) #+end_src #+RESULTS: test : class 'list' If I call that function the result is correct However using #+CALL: test[:var table=tablename]() :exports results #+RESULTS: test[:var table=tablename]():exports results : class 'NoneType' #+CALL: test(table=tablename) :exports results #+RESULTS: test(table=tablename):exports results : class 'NoneType' // --end I think I get a bit further with the trouble shooting. As you can see, the problem seems to be Calling the source code block directly table seems to be of type list which is (I guess) correct However, calling the code via a #+CALL line, the input data (table) is of type 'NoneType'. This hoax the later operation in a very strange way. E.g. plan return of the table is fine, even table[i] works, more complex operations don't. The question for me is, why is there a difference of the data (table) type depending on the call? As for the second part of the email, again sorry I was kind of tired. Take I have this property drawer *** Exam evaluation :intern: :PROPERTIES: :passscore: 50 :extrapoints: 1 :END: and within a table formula line e.g. '(sbe score2mark (score $15) (passscore $PROP_passscore) This works well, now I want to use the same property as value of a source code block Those fail: #+CALL: createscoretable(passscore=passscore) :exports results #+CALL: createscoretable(passscore) :exports results #+CALL: createscoretable($PROP_passscore) :exports results #+CALL: createscoretable(passscore=$PROPpassscore) :exports results I can see how to assign a property defined variable to a code block call. I tried modifications like *** Exam evaluation :intern: :PROPERTIES: :var: passscore=50 :extrapoints: 1 :END: and #+PROPERTY: var passscore=50 But none of them seem to work for me. Even if one work, would it work together with the way sbe calls property values? Basically, I want to use a variable defined in a Property-Drawer for both the sbe function within table formulars and as value for functions calls of source code blocks Thanks again for all your help! All the best Torsten On 19 July 2013 03:06, Eric Schulte schulte.e...@gmail.com wrote: Torsten Wagner torsten.wag...@gmail.com writes: Hi, I have a tables like this: #+TBLNAME: tablename | a | b |c | d | | 1 | 2 |3 |4 | | z | x | y |w| #+TBLNAME: othertablename | a | b |c | d | | 1 | 2 |3 |4 | | z | x | y |w| I have the following code block #+name: test #+begin_src python :var table=tablename :exports results import numpy as np tab = np.array(table) return np.array([tab[:,1], tab[:,-1]]).T #+end_src If I call that function the result is correct However using #+CALL: aushang[:var table=othertablename]() :exports results or
[O] process diagrams with dot and some glue using org
Dear Karl, a couple of weeks ago you developed some code to convert a pair of tables to a graphviz digraph and you wrote a very useful Worg page about it: http://article.gmane.org/gmane.emacs.orgmode/74280 http://orgmode.org/worg/org-tutorials/org-dot-diagrams.html I have today had a real need for this so I copied the code and used it. Worked like a charm! Thanks for doing this. I just wanted to say two things about it: 1. if the typical use case is to use the code with #+call:, it would be more helpful to delete the #+header: line in the source code in the Worg page. This header line presumes that the particular tables in your first example exist. Deleting this line means that the code can only be used via a #+call statement but I think this is more logical. 2. I appended a column to my node table with a description of each node. You've written your code so that it doesn't care if there are extra columns. This is a bonus! My table not only provides the data for the graph but also explains the graph to a reader. Thanks again, eric -- : Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.0.6-341-g338603
Re: [O] process diagrams with dot and some glue using org
On 2013-07-19 13:23, Eric S Fraga wrote: a couple of weeks ago you developed some code to convert a pair of tables to a graphviz digraph and you wrote a very useful Worg page about it: http://article.gmane.org/gmane.emacs.orgmode/74280 http://orgmode.org/worg/org-tutorials/org-dot-diagrams.html I just wanted to say two things about it: 1. if the typical use case is to use the code with #+call:, it would be more helpful to delete the #+header: line in the source code in the Worg page. This header line presumes that the particular tables in your first example exist. Deleting this line means that the code can only be used via a #+call statement but I think this is more logical. I (sort of) disagree. I think specifying required arguments as header vars makes the calling requirements clearer. Perhaps: #+HEADER: :var nodes='() graph='() would be better... rick
Re: [O] bullets when exporting a list of checklists
da...@adboyd.com (J. David Boyd) writes: da...@adboyd.com (J. David Boyd) writes: Is there any way to turn off the solid and hollow bullet points when exporting a checklist of checklists? I want to make a checklist for my camping trips, and I don't want the bullet points, just the nice clean list. I've seen some options available for formatting, but nothing seems to control the generation of the bullet points. Any pointers on where to look in the docs or source for controlling this? Thanks, Dave in St. Petersburg, FL And sorry, I should have said When exporting to html, looking at M-x apropos-variable org-export-with RET I didn't see anything. But check it out. If nothing works you can add a filter. Here's something to get you started. You could add more robustness-check, e.g. making sure that only the first occurrence is removed etc. (defun me/org-export-remove-checkboxes-from-html (item backend info) Remove checkboxes from html via regexp. It's inheritantly unstable as it only recognizes checkboxes of the format code[something]/code. Info is ignored (when (org-export-derived-backend-p backend 'html) (replace-regexp-in-string code\\[.*?\\]/code ? item))) (add-to-list 'org-export-filter-item-functions 'me/org-export-remove-checkboxes-from-html) –Rasmus -- . . . The proofs are technical in nature and provides no real understanding.
Re: [O] bullets when exporting a list of checklists
da...@adboyd.com (J. David Boyd) writes: Is there any way to turn off the solid and hollow bullet points when exporting a checklist of checklists? I want to make a checklist for my camping trips, and I don't want the bullet points, just the nice clean list. I've seen some options available for formatting, but nothing seems to control the generation of the bullet points. Any pointers on where to look in the docs or source for controlling this? Thanks, Dave in St. Petersburg, FL And sorry, I should have said When exporting to html,
[O] bullets when exporting a list of checklists
Is there any way to turn off the solid and hollow bullet points when exporting a checklist of checklists? I want to make a checklist for my camping trips, and I don't want the bullet points, just the nice clean list. I've seen some options available for formatting, but nothing seems to control the generation of the bullet points. Any pointers on where to look in the docs or source for controlling this? Thanks, Dave in St. Petersburg, FL
Re: [O] [babel] Problems assigning tables as variables using #+CALL and using properties in code blocks and sbe calls
On 2013-07-19 11:57, Torsten Wagner wrote: Hi Eric, one mini-step forward. The #+CALL function does not work if the table has a horizontal line like in #+TBLNAME: othertablename | a | b | c | d | |---+---+---+---| | 4 | 3 | 2 | 1 | | z | x | y | w | however, it works for #+TBLNAME: othertablename | a | b | c | d | | 4 | 3 | 2 | 1 | | z | x | y | w | I guess we come closer to the problem ;) This is, i believe related to the general problems I have been seeing with the processing of tables passed as arguments to babel blocks vs. the same tables passed to `call' lines. For example: #+BEGIN_ORG #+name: ptable | head1 | head2 | |---+---| | a | 1 | | b | 2 | #+name: ptable-mirror #+BEGIN_SRC python :var t=ptable :results value :colnames no return t #+END_SRC #+RESULTS: ptable-mirror | head1 | head2 | | a | 1 | | b | 2 | #+call: ptable-mirror() #+RESULTS: | head1 | head2 | | a | 1 | | b | 2 | #+call: ptable-mirror(t=ptable) #+RESULTS: | head1 | head2 | |---+---| | a | 1 | | b | 2 | #+END_ORG As you can see, the handling of headers/colnames is different in a `call' depending on if the argument is specified explicitly or not. BTW, changing `colnames no' to `:colnames yes' results in: #+BEGIN_ORG #+call: ptable-mirror(t=ptable) #+RESULTS: | head1 | head2 | |---+---| | head1 | head2 | |---+---| | a | 1 | | b | 2 | #+END_ORG rick
Re: [O] Http pull/clone at orgmode.org is down?
On 2013-07-18 16:10, John Hendy wrote: When I try to issue git pull (since yesterday, replicated today), I'm getting this: $ git pull error: Unable to find 989923a140695aa87959bdc727666aeec48ec074 under http://orgmode.org/org-mode.git Cannot obtain needed tree 989923a140695aa87959bdc727666aeec48ec074 while processing commit 0b770b125ffaed8e21dfea523437f12c35dec334. error: Fetch failed. I am also behind a firewall, and i have the same issue regularly. I solve it by removing the current checkout and re-cloning the repository. rick
Re: [O] process diagrams with dot and some glue using org
Rick Frankel r...@rickster.com writes: [...] I (sort of) disagree. I think specifying required arguments as header vars makes the calling requirements clearer. Perhaps: #+HEADER: :var nodes='() graph='() would be better... Sure, that would be a good compromise. I agree it is nice to have a clear indication of the requirements. The reason for my suggestion for deleting the header line was that the call would not work with it in place as, for some reason, even though the variables have been defined in the call statement, babel still expects to find the tables the defaults point to. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.0.6-341-g338603
Re: [O] koma letter exporter: changing the priority of options
Alan Schmitt alan.schm...@polytechnique.org writes: I did some experiments and it seems that by default foldmarks is true. The idea behind the patch is that, if we don't change the default values, then things are not output. Let me know if this is fine with you and I'll commit this. (I'll also edit the work with the new default values.) Fine with me. I still have an issue with the default value for email. [...] What I propose is the following: - we leave the default AUTHOR and EMAIL at nil I like the default. . . - if they are still nil, we output the default values _before_ inputting the lco file - if they are no longer nil, we output their values _after_ inputting the lco file I think we need to treat koma variables more generally (I have some sketches locally) if anything. Not make their behavior more specialized. This way, if they are not defined in the file, then the lco can override them, otherwise the local option will be the one used. Just to summarize, we are talking about three emails, 1. the one set in the config file (defaults) 2. the one set in a lco file 3. the one set locally. You want the above ranking. But currently 1. and 3. are the same to the exporter. So you propose to /alter/ the sequence of the exporter depending on whether 1. or 3. occurred. But you'd still end up with two emails in your file, and if you lost the LCO file the other email would still be there. It seems you want to have 1 set to nil when an email is supplied via 2. If you really want to go down this patch, fine, I can check out your suggesting. But I'm skeptical! I slightly less mind-boggling approach would be to replace the default function with one that (1) fetches the LCO values from the file (but what if they are remote?); (2) obtains the path via kpsewhich (run from the current dir); (3) run grep on each of these files with some intelligent keyword. The only hard part is (1) and (2) and (3) are almost foolproof. –Rasmus -- ツ
Re: [O] bullets when exporting a list of checklists
[I tried following up earlier and I think I messed it up, so I'm
resending. Apologies if there is a second reply.]
da...@adboyd.com (J. David Boyd) writes:
da...@adboyd.com (J. David Boyd) writes:
Is there any way to turn off the solid and hollow bullet points when
exporting
a checklist of checklists?
I want to make a checklist for my camping trips, and I don't want the bullet
points, just the nice clean list.
I've seen some options available for formatting, but nothing seems to control
the generation of the bullet points.
Any pointers on where to look in the docs or source for controlling this?
Thanks,
Dave in St. Petersburg, FL
And sorry, I should have said When exporting to html,
I think this is more up CSS's alley. Try
--8---cut here---start-8---
#+HTML_HEAD: style.org-ul {list-style-type: none; } /style
* foo
- foo
- bar
- foo
--8---cut here---end---8---
--
Nick
Re: [O] bullets when exporting a list of checklists
Nick Dokos ndo...@gmail.com writes:
[I tried following up earlier and I think I messed it up, so I'm
resending. Apologies if there is a second reply.]
da...@adboyd.com (J. David Boyd) writes:
da...@adboyd.com (J. David Boyd) writes:
Is there any way to turn off the solid and hollow bullet points when
exporting
a checklist of checklists?
I want to make a checklist for my camping trips, and I don't want the bullet
points, just the nice clean list.
I've seen some options available for formatting, but nothing seems to
control
the generation of the bullet points.
Any pointers on where to look in the docs or source for controlling this?
Thanks,
Dave in St. Petersburg, FL
And sorry, I should have said When exporting to html,
I think this is more up CSS's alley. Try
#+HTML_HEAD: style.org-ul {list-style-type: none; } /style
* foo
- foo
- bar
- foo
Hmm, I'll check that out...
Re: [O] [PATCH] Enable silent visibility cycling
Thorsten Jolitz tjol...@gmail.com writes: Eric S Fraga e.fr...@ucl.ac.uk writes: Would you wrap it all up in a patch and submit it? It would be great to have incorporated. ok, done. Brilliant! Thanks. -- : Eric S Fraga (0xFFFCF67D), Emacs 24.3.50.1, Org release_8.0.6-341-g338603
Re: [O] ox-freemind exporter
Hello, Michael Bach pha...@gmail.com writes: I checked out org-mode from today and tried the ox-freemind exporter. It fails with the error: `cond: Keyword argument :translations not one of (:name :parent :transcoders :options :filters :blocks :menu)'. It should now be fixed. Thank you for reporting it. Regards, - Nicolas Goaziou
[O] Error while compiling
Hi, I tried compiling the git version on a Mac running Lion with emacs 24.3 and I get the error: make compile-dirall dirall Checking /Users/rc/elisp/org-mode/lisp... Compiling /Users/rc/elisp/org-mode/lisp/org-attach.el... In toplevel form: org-attach.el:42:1:Error: Symbol's value as variable is void: user-emacs-directory Compiling /Users/rc/elisp/org-mode/lisp/org-install.el... Compiling /Users/rc/elisp/org-mode/lisp/org-loaddefs.el... Compiling /Users/rc/elisp/org-mode/lisp/org-version.el... Compiling /Users/rc/elisp/org-mode/lisp/ox-odt.el... In toplevel form: ox-odt.el:369:1:Error: Cannot open load file: rng-loc Done (Total of 0 files compiled, 2 failed, 3 skipped) Is there a problem with the file in th git version o
[O] Error compiling file
Hi, I am trying to compile the git version on a Mac with emacs 24.3 and I get the error: make compile-dirall dirall Checking /Users/rc/elisp/org-mode/lisp... Compiling /Users/rc/elisp/org-mode/lisp/org-attach.el... In toplevel form: org-attach.el:42:1:Error: Symbol's value as variable is void: user-emacs-directory Compiling /Users/rc/elisp/org-mode/lisp/org-install.el... Compiling /Users/rc/elisp/org-mode/lisp/org-loaddefs.el... Compiling /Users/rc/elisp/org-mode/lisp/org-version.el... Compiling /Users/rc/elisp/org-mode/lisp/ox-odt.el... In toplevel form: ox-odt.el:369:1:Error: Cannot open load file: rng-loc Done (Total of 0 files compiled, 2 failed, 3 skipped) Is there a problem with the file or am I doing something wrong? Thanks, RC
Re: [O] Error compiling file
RCY re...@yahoo.com writes: Hi, I am trying to compile the git version on a Mac with emacs 24.3 and I get the error: make compile-dirall dirall Checking /Users/rc/elisp/org-mode/lisp... Compiling /Users/rc/elisp/org-mode/lisp/org-attach.el... In toplevel form: org-attach.el:42:1:Error: Symbol's value as variable is void: user-emacs-directory Compiling /Users/rc/elisp/org-mode/lisp/org-install.el... Compiling /Users/rc/elisp/org-mode/lisp/org-loaddefs.el... Compiling /Users/rc/elisp/org-mode/lisp/org-version.el... Compiling /Users/rc/elisp/org-mode/lisp/ox-odt.el... In toplevel form: ox-odt.el:369:1:Error: Cannot open load file: rng-loc Done (Total of 0 files compiled, 2 failed, 3 skipped) Is there a problem with the file or am I doing something wrong? Thanks, RC AFAIK, there is no such target in the makefile: , | $ make compile-dirall | make: *** No rule to make target `compile-dirall'. Stop. ` What happens if you just follow the installation directions in the org manual? -- Nick
