Re: [O] Org release 7.8.04 (BUGFIX-only release)
Hi Achim, Achim Gratz strom...@nexgo.de writes: Curses... here are the two patches Thanks a lot. Can you tell me how you created this patches and what is the commit maint and master will correspond to after we apply it? Are there patches that have been applied and should be reapplied in case we use your patches to get a fresh start? Best, -- Bastien
Re: [O] Org release 7.8.04 (BUGFIX-only release)
Bastien b...@altern.org writes: Thanks a lot. Can you tell me how you created this patches and what is the commit maint and master will correspond to after we apply it? I've sent you a mail with the details. Are there patches that have been applied and should be reapplied in case we use your patches to get a fresh start? No, there's been no new commits since I made these patches and I've included everything commited during and after the faulty merge, so they should be good to go. But please check again, particularly for files that should or should not be in the respective branches. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] org-protocol in windows and Acrobat Reader
This indicates that .replace('|',':') didn't work out as expected and
org-protocol received
org-protocol://store-link://file%3A%2F%2F%2FC%7C%2FTemp%2Ffile.pdf
^^^
Maybe this could do the trick:
,
| app.addMenuItem({cName:org-store-link, cParent:File,
| cExec:app.launchURL('org-protocol://store-link://'+ unescape
| (encodeURIComponent(this.URL.replace('|',':';});
`
Indeed I get the corresponding character.
org-protocol://store-link://file:///C:/Temp/file.pdf
The problem of the bad interpretation of the character / still remains when
I go back to emacs. I get the following proposition when I use C-c C-l : file:
(C:).
Thank you for your help.
I.e. replace | by : in the original URL before encoding it.
Best,
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber dmjena at jabber.org
Email. dmaus at ictsoc.de
Re: [O] I'm tripping over #+BABEL: vs. #+PROPERTY:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/03/12 17:14, Nick Dokos wrote: Sebastien Vauban wxhgmqzgw...@spammotel.com wrote: Hi Nick and Eric, Nick Dokos wrote: Eric Schulte eric.schu...@gmx.com wrote: Did you press C-c C-c on each property line after it was written? Just to clarify: do I really have to C-c C-c on each line? If I add a bunch of them and then do C-c C-c on one of them, shouldn't that be enough to refresh the setup? I got no reaction on my idea of automagic C-c C-c (on 2012-03-04 Sun, see http://www.mail-archive.com/emacs-orgmode@gnu.org/msg52739.html): The automagic C-c C-c should be NOT[1] done after each key press or some such. That certainly would be a killer feature, in its real acception: performance would be unbearable. In my mind, automatically (re-)parsing the meta options should be each time the user presses `C-c C-v C-e' (eval code blocks); that is, when the user expects his options to be taken into account. Does it make sense? Best regards, Seb Footnotes: [1] This word was missing (in the original post)! Well, it might make sense but you can try it out and let us know: - make files with 10, 100, 1000 trivial (or even empty) code blocks, just enough to make sure that org-babel-execute-maybe is really called on them: I think that it will be called even on empty code blocks, but I'm not sure if there is some optimization in there. - measure the time it takes to export each one to html (say). - add a call to org-mode-restart into org-babel-execute-maybe, and time the same operation again: how significant is the slowdown? If the slowdown is bearable in these cases, then it will be bearable in realistic situations, where block execution is going to be a much more significant fraction of the total. BTW, what's the biggest file you (all, not just Seb) have in terms of the number of code blocks it contains? In my case, the largest one had about two dozen code blocks, so the 100 case would easily cover me, but I suspect there are much bigger ones out there. 142 - used in literal programming. Rainer Nick - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9m7JsACgkQoYgNqgF2egoV4ACeISeB8GZWSCDSkIPgqIHViqeh fokAn3cgygfMKr2VInkLkHHX3gIPe58G =S2uU -END PGP SIGNATURE-
Re: [O] Is it possible to run shell script src blocks as root or to export individual blocks?
On Mon, Mar 5, 2012 at 10:24 AM, Eric Schulte eric.schu...@gmx.com wrote: Andreas Leha andreas.l...@med.uni-goettingen.de writes: Eric Schulte eric.schu...@gmx.com writes: Leo Alekseyev dnqu...@gmail.com writes: I was wondering if there was an easy way to execute some shell commands contained in a src block as root. Alternatively, is there a quick way to export _just_ that one source block to a temp file so that I could run it as root manually? Just call org-babel-tangle with a prefix argument and it only tangles the current block Hi all, I just pulled a fresh version of org, and this tangling an individual block only works if there's a :tangle header argument present. I don't think this is the intended behavior! The problem, it seems, is that when :tangle is not present, the (or ...) in the code below always evaluates to true. #+begin_src emacs-lisp (unless (or (cdr (assoc :tangle (nth 2 (org-babel-get-src-block-info target-file) (setq target-file (read-from-minibuffer Tangle to: (buffer-file-name) #+end_src
[O] [babel] [bug] bug in R-specific header argument for graphics driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I did not get any response so far, so I hope that the email did not went out... Rainer - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When giving the header argument :title: the graph is not produced in a file: * This works Display boxplot of spread of Mff over time for each release strategy :PROPERTIES: :results: graphics :file: SpreadOverTime.pdf :width: 4 :height: 8 :pointsize: 8 :END: #+begin_src R plot(runif(100)) #+end_src * This doesn't Display boxplot of spread of Mff over time for each release strategy :PROPERTIES: :results: graphics :file: test.pdf :width: 4 :height: 8 :pointsize: 8 :title: test :END: #+begin_src R plot(runif(100)) #+end_src Error message: Error in pdf(file = test.pdf, width = 4, height = 8, pointsize = 8, : object 'test' not found Calls: Anonymous - Anonymous - pdf Execution halted Cheers, Rainer - - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug - -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9h34AACgkQoYgNqgF2egpEAgCfWUPrimW6av6/m7PU+KgBnNu+ BegAn2ZWnAhWvflhDKw8225qt9vCkqJg =4gNf - -END PGP SIGNATURE- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9m9IgACgkQoYgNqgF2egr3AgCdG1kEDQLSEuACtvhm8bnQNdhh 3FQAnjbMtLBd4nSOD5MNokTYb+YoiOic =xSBq -END PGP SIGNATURE-
Re: [O] [bug] org-agenda-write does not handle date stamps without day of week
On 17.3.2012, at 07:45, Nick Dokos wrote: Karl Voit devn...@karl-voit.at wrote: * Nick Dokos nicholas.do...@hp.com wrote: Karl Voit devn...@karl-voit.at wrote: For me, it was a no time to work on org - stash it... OK. I just wanted to make sure that it *is* on someone's todo list :-) * Karl Voit devn...@karl-voit.at wrote: * 2012-03-05 08:00-09:00 Wrong: ends up as full day event org-agenda-write calls org-export-icalendar which calls org-print-icalendar-entries which loops over all the entries and parses them, decomposing them into timestamps. Each timestamp is then passed to org-parse-time-string. It's this one that cannot handle non-standard formats: it uses a regexp and assumes that all the matched parts are going to be in fixed places: As to how to fix it, there are several possibilities: 1. fix your scripts that produce time stamps to include day-of-week. Sorry, deriving DOW from an arbitrary timestamps from arbitrary data sources is either pretty time consuming (calendar calculations) or simply hard to calculate. Outside Org-mode, DOW is seldom part of time-stamp data :-( 2. change the callers of org-parse-time-string to make sure that DOW is included. There are roughly three dozen callers, so 2. is possible but a pain. Ack. 3. change just one caller: org-print-icalendar-entries to make sure that DOW is included. 3. is simple but ugly as sin, Ouch, ack :-) 4. change org-parse-time-string to handle a missing DOW. 4. is the best way to handle it within org. Full ack. I vote for 1. where *you* have to do all the work ;-) YMMD :-) If my brain would be compatible to ELISP, I'd send a patch. Promised. But I'll take my chance and wait for someone else (you?) implementing 4. to resolve this issue for everybody. I really appreciate every second you guys invest in maintaining Org-mode! I don't know about you, but whenever I engage in hand-to-hand combat with a complicated regexp, I come out bruised, muddied and a lot worse for wear. In any case, I'm attaching an org file with my investigations. It contains a description and a code block for testing. I hope that the attachment will come through unscathed: it contains regexps, and munging a regexp that looks like hen scratchings in the first place through uncooperative mailers is not something to be relished. BTW, I'm not advocating a change: I'll leave it to Karl to do that if he really wants to and to the maintainers to decide whether it's worth doing. But it can be done (more or less). And maybe somebody will come up with a better way than the proof-of-concept that I'm attaching here. Hi Nick and Karl, since we did make a change to Org a while ago to allow date stamps without the name of the day, I think it is only consequent to also do it for this case. Must have slipped our attention back then. The only thing we must ensure is that this regexp matches fast as it is used a lot. Nick's proposal works, except for the fact that is also matches when the time is directly attached to day name. Maybe it is cleaner to not match in this case. If we are going to make the day name optional, then it is better to include matching of the whitespace after the date into the day-name part of the regexp. I am attaching Nick's file again, with a third proposal for an updated regexp. As far as speed is concerned, this regexp will, if there is name and time, match directly and straight. If the date name is missing, it will notice on the first digit belonging to the time and switch without backtracking (well, minimal backtracking when there are multiple spaces) to the regexp section for the time of day. Rematching the spaces after the date will be the only overhead. Cheers - Carsten reproducer.org Description: Binary data Nick PS. BTW, if you look at the attachment, it helps if you have a wide window, something like 165 characters wide. reproducer.org
Re: [O] [bug] org-agenda-write does not handle date stamps without day of week
On 17.3.2012, at 15:04, Simon Thum wrote: Hi Karl, why don't you add something like an xx day which will probably please org-mode - in my tests org ignored the weekday. Yes, the weekday is only expected, but never used, so writing xxx would work. However, see my other mail for another proposal along Nick's lines of argument. - Carsten I concluded it's there for viewing convenience, and editing (C-.) always got me the right DOW. I don't use org2ical, however. Cheers, Simon On 03/05/2012 03:44 PM, Karl Voit wrote: Hi! I verified the behavior below with the most current git version of Org-mode. Whenever I call my function to export the current agenda, it «converts» events that do have a beginning and end time to events that span the whole day (without begin and end times at all). ,[ my LISP command to export ] | (defun vk-export-agenda() | Exports monthly Org-mode agenda to agenda.ics file | (interactive) | (org-agenda-list nil nil 60) | (org-agenda-write ~/org/agenda.ics) | ) ` I traced down the problem to this: *2012-03-05 Mon 08:00-09:00 works fine *2012-03-05 Mon 8:00-9:00 works fine too *2012-03-05 08:00-09:00 Wrong: ends up as full day event Unfortunately, I do have certain mechanisms that generate parts of my Org-mode files where I skip the day of the week. Org-mode in general is able to handle date stamps without day of week pretty well. But whenever I export it to ics (in order to send it to Google), I end up with a messed up online agenda. I guess that org-agenda-write is the one to blame. It would be very handy to me if somebody could fix that issue. Let me know, if you need any further information! Thank you very much!
[O] [patch] Add three xelatex config items to org-latex-to-pdf-process
Xelatex should be pdflatex with enhanced font handling capability. and its fonts configure for Chinese is much much more simple than pdflatex, for it can use *ttf* *otf* fonts in the system easily. Add item: 1. 2 runs of xelatex 2. 3 runs of xelatex 3. xelatex,bibtex,xelatex,xelatex diff --git a/lisp/org-latex.el b/lisp/org-latex.el index 6d46501..189e206 100644 --- a/lisp/org-latex.el +++ b/lisp/org-latex.el @@ -657,6 +657,18 @@ This function should accept the file name as its single argument. bibtex %b pdflatex -interaction nonstopmode -output-directory %o %f pdflatex -interaction nonstopmode -output-directory %o %f)) + (const :tag 2 runs of xelatex +(xelatex -interaction nonstopmode -output-directory %o %f + xelatex -interaction nonstopmode -output-directory %o %f)) + (const :tag 3 runs of xelatex +(xelatex -interaction nonstopmode -output-directory %o %f + xelatex -interaction nonstopmode -output-directory %o %f + xelatex -interaction nonstopmode -output-directory %o %f)) + (const :tag xelatex,bibtex,xelatex,xelatex +(xelatex -interaction nonstopmode -output-directory %o %f + bibtex %b + xelatex -interaction nonstopmode -output-directory %o %f + xelatex -interaction nonstopmode -output-directory %o %f)) (const :tag texi2dvi (texi2dvi -p -b -c -V %f)) (const :tag rubber
[O] org-odt: protected (ie non-breakable) space
Hi, is it possible to have protected spaces in an odt exported from org.-mode? I tried ~ and \nbsp, but both come out literally. Thanks, Martin
[O] About org-babel menu
Hi: Could we add some org-babel menu items ,so using them we can enable and disable the computer languages ? for example: #+begin_example org = org-babel = * emacs-lisp sh * R ... * screen #+end_example
[O] Remaining Work Report
#+COLUMNS: %40ITEM(Task) %6Effort(Estim.){:}
* Context
The question I'm trying to give an answer to is: *what's the remaining number
of hours (or days) to finish my project*?
I don't see obvious solutions for that question. And trials I've done
hereunder did not lead yet to satisfactory results.
Am I passing next to some more obvious solution?
* Development tasks
:PROPERTIES:
:ID: fc314ab6-5bdc-4a2d-9c2d-d9aece03a864
:END:
** DONE Task 1 :Fred:
:PROPERTIES:
:Effort: 1:00
:END:
** TODO Task 2
*** DONE Task 2a:Fred:
:PROPERTIES:
:Effort: 2:00
:END:
*** TODO Task 2b:Sara:
:PROPERTIES:
:Effort: 4:00
:END:
** TODO Task 3 :Sara:
:PROPERTIES:
:Effort: 8:00
:END:
* Reporting
I'd like to report remaining work, among others.
** Columnview
From the columnview, we can't do that, as there is no way to exclude some
lines, and hence no way to get the right total.
#+BEGIN: columnview :hlines 1 :id fc314ab6-5bdc-4a2d-9c2d-d9aece03a864
:maxlevel 2
| Task | Estim. |
|---+|
| * Development tasks | 15:00 |
| ** DONE Task 1 :Fred: | 1:00 |
| ** TODO Task 2| 6:00 |
| ** TODO Task 3 :Sara: | 8:00 |
#+END:
** Propview
After a =(require 'org-collector)=, we can get a table similar to this one:
#+BEGIN: propview :id fc314ab6-5bdc-4a2d-9c2d-d9aece03a864 :conds ((string=
TODO TODO)) :cols (ITEM Effort)
| ITEM | Effort |
|+|
| TODO Task 2 | 6:00 |
| TODO Task 2b | 4:00 |
| TODO Task 3 | 8:00 |
|+|
|||
#+END:
There is a good step in the right direction, in that I don't have anymore
headlines with keyword DONE appearing.
Though,
1. There is no total available, and summing such a table give false results
(due to the string nature of the values?):
| ITEM | Effort |
|+|
| TODO Task 2 | 6:00 |
| TODO Task 2b | 4:00 |
| TODO Task 3 | 8:00 |
|+|
|| 624|
#+TBLFM: @5$2=vsum(@-I..-II)
2. Exclusion of lines can be tricky, as shown above:
- project 2 is task 2a (DONE, 2 hours) + task 2b (TODO, 4 hours)
- total of project 2 tasks is 6 hours, then
- project 2 is not DONE yet, as task 2b is still TODO
- but remaining time of project 2 is 4 hours, not 6
The fact that org-collector shows 6 hours is due to a mix:
- project is still in state TODO,
- we show tasks (or projects) up to level 2, with sub-tasks being /summed up/
3. Not giving a status keyword to the project 2 does not solve anything: in
this case, nothing would show up in org-collector's view.
I understand I could be misusing org-collector.
But that's not what I'm after: if there is an alternative way to be able to
report remaining work to be done on a project, please let me know.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [babel] [bug] bug in R-specific header argument for graphics driver
Hi Rainer, I see you CC'd me on this email. I personally do not know anything about how the graphics header argument to R code blocks works. I would recommend looking deeper into the behavior using the following tools - Look at the expanded code block body using org-babel-expand-src-block - Run the code block in a session, and then look into the session buffer to see what R code is being generated by Babel, then try to debug the R as you would normally - look into the temporary R scripts generated during execution, which will live in a directory with a name like /tmp/babel-XX If you are able to isolate a bug in Babel then I can help fix that bug in the elisp code. Thanks and sorry I can't be of more immediate, Rainer M Krug r.m.k...@gmail.com writes: I did not get any response so far, so I hope that the email did not went out... Rainer -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When giving the header argument :title: the graph is not produced in a file: * This works Display boxplot of spread of Mff over time for each release strategy :PROPERTIES: :results: graphics :file: SpreadOverTime.pdf :width: 4 :height: 8 :pointsize: 8 :END: #+begin_src R plot(runif(100)) #+end_src * This doesn't Display boxplot of spread of Mff over time for each release strategy :PROPERTIES: :results: graphics :file: test.pdf :width: 4 :height: 8 :pointsize: 8 :title: test :END: #+begin_src R plot(runif(100)) #+end_src Error message: Error in pdf(file = test.pdf, width = 4, height = 8, pointsize = 8, : object 'test' not found Calls: Anonymous - Anonymous - pdf Execution halted Cheers, Rainer - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9h34AACgkQoYgNqgF2egpEAgCfWUPrimW6av6/m7PU+KgBnNu+ BegAn2ZWnAhWvflhDKw8225qt9vCkqJg =4gNf -END PGP SIGNATURE- -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] org-map-entries broken?
I think this patch may have broken org-map-entries for me: e0072f79137bbfabdf848da6865d8e4de776a549 is the first bad commit commit e0072f79137bbfabdf848da6865d8e4de776a549 Author: David Maus dm...@ictsoc.de Date: Sun Mar 18 18:38:50 2012 +0100 Require one or more spaces (+) between keyword and headline * org.el (org-scan-tags): Require one or more spaces (+) between keyword and headline. Otherwise the re will match a line like: * TODO@ Foobar And assumes the @ to be part of the headline. This fixes a glitch reported by Simon Thum in 4f53def7.8080...@gmx.de. Hi all, I have found some irritating behaviour, potentially a bug. I have a block agenda which goes like: tags-todo @homeTODO=\TODO\ and it displays a certain org line that reads TODO_ state triggers Which is just a heading for dealing with TODO state triggers, and I appended the _ as I don't want it to be a TODO. For example, the global TODO list and syntax highlighting does not consider it a todo, but C-c a m TODO=TODO does. TODO=T does not, so it's not very grave. Most likely, it's simply an inconsistency arising from not having a real parser. I just wanted to report it here so it may get fixed. :04 04 8f5974f2dd7cf5f0ad10db56d223ba09a6dbca80 624cee5569de7ef8f240ad75943be215bb823ccc M lisp - Try the following before and after this patch was applied, for a test result: - * test one * test two * test three #+BEGIN_SRC emacs-lisp :results both (org-map-entries 'org-get-heading nil nil) #+END_SRC - The results ought to be the three test headings in a table output. After the patch it's blank. -- Charles Sebold Ego delendus sum
Re: [O] org-odt: protected (ie non-breakable) space
Hi, Martin -- is it possible to have protected spaces in an odt exported from org.-mode? I tried ~ and \nbsp, but both come out literally. I just tried inserting the non-breaking space in emacs with C-x, 8, space. It shows up as a non-breaking space in the odt file. -- John Rakestraw
Re: [O] About org-babel menu
Hi FengShu, I don't know much about the Emacs customization interface, but it is certainly the solution to this issue. There does currently exist a Babel specific customization group, the nesting is orgbabel. Through this interface there are menus like the one you mention below available. One way to access these menus is through the help interface, with M-x describe-variable RET org-babel-load-languages RET and then select the customize link. Best, FengShu tuma...@gmail.com writes: Hi: Could we add some org-babel menu items ,so using them we can enable and disable the computer languages ? for example: #+begin_example org = org-babel = * emacs-lisp sh * R ... * screen #+end_example -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] [bug] bug in R-specific header argument for graphics driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/03/12 15:17, Eric Schulte wrote: Hi Rainer, I see you CC'd me on this email. I personally do not know anything about how the graphics header argument to R code blocks works. Sorry - I thought it was part of babel, and when I hear babel, I think eric knows it... I would recommend looking deeper into the behavior using the following tools - Look at the expanded code block body using org-babel-expand-src-block - Run the code block in a session, and then look into the session buffer to see what R code is being generated by Babel, then try to debug the R as you would normally - look into the temporary R scripts generated during execution, which will live in a directory with a name like /tmp/babel-XX Good idea - I'll look into it and give you feedback. If you are able to isolate a bug in Babel then I can help fix that bug in the elisp code. Thanks - I still haven't managed to get into (e)lisp... Thanks and sorry I can't be of more immediate, No problem, Cheers, Rainer Rainer M Krug r.m.k...@gmail.com writes: I did not get any response so far, so I hope that the email did not went out... Rainer When giving the header argument :title: the graph is not produced in a file: * This works Display boxplot of spread of Mff over time for each release strategy :PROPERTIES: :results: graphics :file: SpreadOverTime.pdf :width: 4 :height: 8 :pointsize: 8 :END: #+begin_src R plot(runif(100)) #+end_src * This doesn't Display boxplot of spread of Mff over time for each release strategy :PROPERTIES: :results: graphics :file: test.pdf :width: 4 :height: 8 :pointsize: 8 :title: test :END: #+begin_src R plot(runif(100)) #+end_src Error message: Error in pdf(file = test.pdf, width = 4, height = 8, pointsize = 8, : object 'test' not found Calls: Anonymous - Anonymous - pdf Execution halted Cheers, Rainer - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9nRBsACgkQoYgNqgF2egqjLgCffCgBTR1Eo03E2au/ocUfSAWK f3UAn2zw0o9ApDpAuxScN3kRrWLWIUYc =Y5d+ -END PGP SIGNATURE-
Re: [O] About org-babel menu
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/03/12 15:22, Eric Schulte wrote: Hi FengShu, I don't know much about the Emacs customization interface, but it is certainly the solution to this issue. There does currently exist a Babel specific customization group, the nesting is orgbabel. Through this interface there are menus like the one you mention below available. One way to access these menus is through the help interface, with M-x describe-variable RET org-babel-load-languages RET and then select the customize link. Agreed on this point, but I am with FengShu regarding a babel menu. I likely would not use it that often (I know the shortcuts relevant to me right now), but 1) it would advertise the babel functionality a little bit more if it is shown in the org menu 2) for a beginner, it would be much easier to use org-babel if commands like execute source block or section, tangle, un-tangle, ... would be in the menu. So I would see it as a useful way of promoting babel (and therefore org-mode) and also as a nice reminder of less frequently (but nevertheless usefull) functionality. Cheers, Rainer Best, FengShu tuma...@gmail.com writes: Hi: Could we add some org-babel menu items ,so using them we can enable and disable the computer languages ? for example: #+begin_example org = org-babel = * emacs-lisp sh * R ... * screen #+end_example - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9nRY0ACgkQoYgNqgF2egqR+QCfd9JUHONesOzWv/GeVL1sdgAl J8UAn29QzxY9qxK9Du3n0brq7Orwo6yB =5vux -END PGP SIGNATURE-
Re: [O] Is it possible to run shell script src blocks as root or to export individual blocks?
Leo Alekseyev dnqu...@gmail.com writes: On Mon, Mar 5, 2012 at 10:24 AM, Eric Schulte eric.schu...@gmx.com wrote: Andreas Leha andreas.l...@med.uni-goettingen.de writes: Eric Schulte eric.schu...@gmx.com writes: Leo Alekseyev dnqu...@gmail.com writes: I was wondering if there was an easy way to execute some shell commands contained in a src block as root. Alternatively, is there a quick way to export _just_ that one source block to a temp file so that I could run it as root manually? Just call org-babel-tangle with a prefix argument and it only tangles the current block Hi all, I just pulled a fresh version of org, and this tangling an individual block only works if there's a :tangle header argument present. I don't think this is the intended behavior! The problem, it seems, is that when :tangle is not present, the (or ...) in the code below always evaluates to true. #+begin_src emacs-lisp (unless (or (cdr (assoc :tangle (nth 2 (org-babel-get-src-block-info target-file) (setq target-file (read-from-minibuffer Tangle to: (buffer-file-name) #+end_src Thanks for raising this issue. I can not apply patches to the git repository until the recent git issues are sorted, so I am attaching the patch to this email so that you can apply it locally if you like. I will push this up once our git repository is back in working order. Best, From bfacabb33acb4d2dbcfd87b10e3488e43cf5d84a Mon Sep 17 00:00:00 2001 From: Eric Schulte eric.schu...@gmx.com Date: Mon, 19 Mar 2012 10:44:43 -0400 Subject: [PATCH 2/2] Bring back prompt for single-block tangling. * lisp/ob-tangle.el (org-babel-tangle): Bring back prompt for single-block tangling. --- lisp/ob-tangle.el |5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/lisp/ob-tangle.el b/lisp/ob-tangle.el index 5e498ab..b57d89d 100644 --- a/lisp/ob-tangle.el +++ b/lisp/ob-tangle.el @@ -186,7 +186,10 @@ exported source code blocks by language. (unless (org-babel-where-is-src-block-head) (error Point is not currently inside of a code block)) (save-match-data - (unless (or (cdr (assoc :tangle (nth 2 (org-babel-get-src-block-info + (unless (or (not (string= + (cdr (assoc :tangle +(nth 2 (org-babel-get-src-block-info + no)) target-file) (setq target-file (read-from-minibuffer Tangle to: (buffer-file-name) -- 1.7.9.4 -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] [bug] org-babel-use-quick-and-dirty-noweb-expansion
Hi Nicolas, Thanks for bringing up this bug. I'm attaching a patch to this email, once the current repositories issues are resolved I'll apply this patch to the repository. In the interim, you can apply this patch to your local copy of the git repository with. $ cd your/path/to/org $ git am /tmp/0001-fix-bug-in-src-name-regexp-when-using-org-babel-use-.patch From 13a43222a0ab8594647584844f1765e6f130d69e Mon Sep 17 00:00:00 2001 From: Eric Schulte eric.schu...@gmx.com Date: Mon, 19 Mar 2012 10:37:04 -0400 Subject: [PATCH] fix bug in src name regexp when using *org-babel-use-quick-and-dirty-noweb-expansion* * lisp/ob.el (org-babel-expand-noweb-references): Fix bug in src name regexp when using *org-babel-use-quick-and-dirty-noweb-expansion*. --- lisp/ob.el |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/ob.el b/lisp/ob.el index 9205a20..2e48524 100644 --- a/lisp/ob.el +++ b/lisp/ob.el @@ -2186,7 +2186,7 @@ block but are passed literally to the \example-block\. (when (org-babel-ref-goto-headline-id source-name) (org-babel-ref-headline-body))) ;; find the expansion of reference in this buffer - (let ((rx (concat rx-prefix source-name)) + (let ((rx (concat rx-prefix source-name [ \t\n])) expansion) (save-excursion (goto-char (point-min)) -- 1.7.9.4 Best, Nicolas Girard girard.nico...@gmail.com writes: Hi all, I've been succesfully using babel to make various literate programming work. Unfortunately, tangling performance has dramatically decreased, to the point of being barely usable. I wish I could get advantage of the quick dirty noweb expansion Eric introduced in january, but it has an undesirable side effect. Consider the following minimal example: # #+name: abc #+begin_src latex Abcabc-d #+end_src #+name: abc-d #+begin_src latex Def #+end_src #+begin_src latex :noweb yes :tangle test.tex abc #+end_src # Tangling with *org-babel-use-quick-and-dirty-noweb-expansion* set to nil gives # AbcDef # while tangling with *org-babel-use-quick-and-dirty-noweb-expansion* set to t gives # AbcDef Def # I'd be very happy if this bug could be tracked down. Thanks very much in advance ! Cheers, Nicolas -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] About org-babel menu
Rainer M Krug r.m.k...@gmail.com writes: On 19/03/12 15:22, Eric Schulte wrote: Hi FengShu, I don't know much about the Emacs customization interface, but it is certainly the solution to this issue. There does currently exist a Babel specific customization group, the nesting is orgbabel. Through this interface there are menus like the one you mention below available. One way to access these menus is through the help interface, with M-x describe-variable RET org-babel-load-languages RET and then select the customize link. Agreed on this point, but I am with FengShu regarding a babel menu. I likely would not use it that often (I know the shortcuts relevant to me right now), but 1) it would advertise the babel functionality a little bit more if it is shown in the org menu 2) for a beginner, it would be much easier to use org-babel if commands like execute source block or section, tangle, un-tangle, ... would be in the menu. So I would see it as a useful way of promoting babel (and therefore org-mode) and also as a nice reminder of less frequently (but nevertheless usefull) functionality. I've had (setq menu-bar-mode nil) in my .emacs for years now and forget that Emacs even has support for menus. I don't know anything about how Emacs implements menus, but if anyone is interested in taking on this development I'm very happy to consult in the development of and to apply contributed patches which add Babel menu support. Best, Cheers, Rainer Best, FengShu tuma...@gmail.com writes: Hi: Could we add some org-babel menu items ,so using them we can enable and disable the computer languages ? for example: #+begin_example org = org-babel = * emacs-lisp sh * R ... * screen #+end_example -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] table spreadsheet problem
Hi all, question about table calculation. Found in the documentation that I could refer to e.g. first line after second hline with @II+2. Would like to calculate sum = vsum(@I..@II) and tax = sum * 0.08 Am I doing sth wrong ? Thanks for help, Martin | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum || | tax || |-+| | sum | 0 | #+TBLFM: @II+1$2=vsum(@I..@II);f2N::@II+2$2=@II+1$2*0.08;f2N::@$2=vsum(@II..@III);f2N
Re: [O] About org-babel menu
On Mon, Mar 19, 2012 at 10:41, Rainer M Krug r.m.k...@gmail.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/03/12 15:22, Eric Schulte wrote: Hi FengShu, I don't know much about the Emacs customization interface, but it is certainly the solution to this issue. There does currently exist a Babel specific customization group, the nesting is orgbabel. Through this interface there are menus like the one you mention below available. One way to access these menus is through the help interface, with M-x describe-variable RET org-babel-load-languages RET and then select the customize link. Agreed on this point, but I am with FengShu regarding a babel menu. I likely would not use it that often (I know the shortcuts relevant to me right now), but 1) it would advertise the babel functionality a little bit more if it is shown in the org menu 2) for a beginner, it would be much easier to use org-babel if commands like execute source block or section, tangle, un-tangle, ... would be in the menu. That would be useful, however I believe what FengShu means is a sub-menu specifically with a list of all the org-babel languages, where you can see which are active at the moment. I'm not sure how you could deactivate them once they are active however since the libraries would be loaded, however you could use that menu as a way to keep track of which languages require confirmation on code blocks and which will be evaluated without prompting. So I would see it as a useful way of promoting babel (and therefore org-mode) and also as a nice reminder of less frequently (but nevertheless usefull) functionality. Cheers, Rainer Best, FengShu tuma...@gmail.com writes: Hi: Could we add some org-babel menu items ,so using them we can enable and disable the computer languages ? for example: #+begin_example org = org-babel = * emacs-lisp sh * R ... * screen #+end_example - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D): +49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9nRY0ACgkQoYgNqgF2egqR+QCfd9JUHONesOzWv/GeVL1sdgAl J8UAn29QzxY9qxK9Du3n0brq7Orwo6yB =5vux -END PGP SIGNATURE-
Re: [O] org-odt: protected (ie non-breakable) space
Dear John, Am Montag, den 19.03.2012, 09:31 -0400 schrieb John Rakestraw: Hi, Martin -- is it possible to have protected spaces in an odt exported from org.-mode? I tried ~ and \nbsp, but both come out literally. I just tried inserting the non-breaking space in emacs with C-x, 8, space. It shows up as a non-breaking space in the odt file. thanks. I had not thought of this simple way. Works perfectly and even survives the export to MS Office. Martin
Re: [O] table spreadsheet problem
On Mon, Mar 19, 2012 at 04:01:42PM +0100, Martin Halder wrote: Hi all, question about table calculation. Found in the documentation that I could refer to e.g. first line after second hline with @II+2. Would like to calculate sum = vsum(@I..@II) and tax = sum * 0.08 Am I doing sth wrong ? Thanks for help, Martin | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum || | tax || |-+| | sum | 0 | #+TBLFM: @II+1$2=vsum(@I..@II);f2N::@II+2$2=@II+1$2*0.08;f2N::@$2=vsum(@II..@III);f2N | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum | 300.00 | | tax | 24.00 | |-+| | sum | 324.00 | #+TBLFM: @4$2=vsum(@-I..@-II);%.2f::@5$2=@4$2*0.08;%.2f::@6$2=vsum(@-I..@-II);%.2f I often use negative headline references for total lines in order to sum backward from the current cell. So vsum(@-I..@-II);%.2f means sum the cells between the first headline above the current cell to the second headline above the current cell, and then format the result as a decimal with two decimal places (%.2f). Looking at your formula, I think you manually wrote the TBLFM line. One thing I've found is that the TBLFM line doesn't support relative references for the cell specification, only in the formula. I used C-u C-c = to set mine. Good luck! -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] [babel] [bug] bug in R-specific header argument for graphics driver
Rainer M Krug r.m.k...@gmail.com writes: On 19/03/12 15:17, Eric Schulte wrote: Hi Rainer, I see you CC'd me on this email. I personally do not know anything about how the graphics header argument to R code blocks works. Sorry - I thought it was part of babel, and when I hear babel, I think eric knows it... It is part of Babel, but Dan Davison is the author of much of the R code, and in general there are increasingly language-specific authors who know more about support particular to a specific language than do I. I would recommend looking deeper into the behavior using the following tools - Look at the expanded code block body using org-babel-expand-src-block - Run the code block in a session, and then look into the session buffer to see what R code is being generated by Babel, then try to debug the R as you would normally - look into the temporary R scripts generated during execution, which will live in a directory with a name like /tmp/babel-XX Good idea - I'll look into it and give you feedback. Great, Thanks, If you are able to isolate a bug in Babel then I can help fix that bug in the elisp code. Thanks - I still haven't managed to get into (e)lisp... Thanks and sorry I can't be of more immediate, No problem, Cheers, Rainer Rainer M Krug r.m.k...@gmail.com writes: I did not get any response so far, so I hope that the email did not went out... Rainer When giving the header argument :title: the graph is not produced in a file: * This works Display boxplot of spread of Mff over time for each release strategy :PROPERTIES: :results: graphics :file: SpreadOverTime.pdf :width: 4 :height: 8 :pointsize: 8 :END: #+begin_src R plot(runif(100)) #+end_src * This doesn't Display boxplot of spread of Mff over time for each release strategy :PROPERTIES: :results: graphics :file: test.pdf :width: 4 :height: 8 :pointsize: 8 :title: test :END: #+begin_src R plot(runif(100)) #+end_src Error message: Error in pdf(file = test.pdf, width = 4, height = 8, pointsize = 8, : object 'test' not found Calls: Anonymous - Anonymous - pdf Execution halted Cheers, Rainer -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] table spreadsheet problem
Am 19.03.2012 um 16:32 schrieb Russell Adams: On Mon, Mar 19, 2012 at 04:01:42PM +0100, Martin Halder wrote: Hi all, question about table calculation. Found in the documentation that I could refer to e.g. first line after second hline with @II+2. Would like to calculate sum = vsum(@I..@II) and tax = sum * 0.08 Am I doing sth wrong ? Thanks for help, Martin | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum || | tax || |-+| | sum | 0 | #+TBLFM: @II+1$2=vsum(@I..@II);f2N::@II+2$2=@II+1$2*0.08;f2N::@$2=vsum(@II..@III);f2N | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum | 300.00 | | tax | 24.00 | |-+| | sum | 324.00 | #+TBLFM: @4$2=vsum(@-I..@-II);%.2f::@5$2=@4$2*0.08;%.2f::@6$2=vsum(@-I..@-II);%.2f I often use negative headline references for total lines in order to sum backward from the current cell. So vsum(@-I..@-II);%.2f means sum the cells between the first headline above the current cell to the second headline above the current cell, and then format the result as a decimal with two decimal places (%.2f). Looking at your formula, I think you manually wrote the TBLFM line. One thing I've found is that the TBLFM line doesn't support relative references for the cell specification, only in the formula. I used C-u C-c = to set mine. Good luck! Hi Russell, right, I wrote it manually. Thanks for your formula, the problem I have is that there could be an item 3 and therefore the sum, tax and second sum lines are not fixed. Is there a solution to specify them dynamically or do I have to modify the position every time I enter a new item ? Thanks, Martin -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] table spreadsheet problem
On Mon, Mar 19, 2012 at 04:45:14PM +0100, Martin Halder wrote: Am 19.03.2012 um 16:32 schrieb Russell Adams: | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum | 300.00 | | tax | 24.00 | |-+| | sum | 324.00 | #+TBLFM: @4$2=vsum(@-I..@-II);%.2f::@5$2=@4$2*0.08;%.2f::@6$2=vsum(@-I..@-II);%.2f I often use negative headline references for total lines in order to sum backward from the current cell. So vsum(@-I..@-II);%.2f means sum the cells between the first headline above the current cell to the second headline above the current cell, and then format the result as a decimal with two decimal places (%.2f). Looking at your formula, I think you manually wrote the TBLFM line. One thing I've found is that the TBLFM line doesn't support relative references for the cell specification, only in the formula. I used C-u C-c = to set mine. Good luck! Hi Russell, right, I wrote it manually. Thanks for your formula, the problem I have is that there could be an item 3 and therefore the sum, tax and second sum lines are not fixed. Is there a solution to specify them dynamically or do I have to modify the position every time I enter a new item ? If you use the table editor properly, it will keep the formulas up to date for you. For instance, if you place your cursor on item2 and press return, a new line should be created and the formulas cell references corrected to match. Beware commands line C-k that may delete a row as text instead of using the Org-Mode specific table editing commands. If you want to delete a line like C-k, use M-S-Up instead. -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] table spreadsheet problem
Russell Adams rlad...@adamsinfoserv.com wrote: On Mon, Mar 19, 2012 at 04:01:42PM +0100, Martin Halder wrote: Hi all, question about table calculation. Found in the documentation that I could refer to e.g. first line after second hline with @II+2. Would like to calculate sum = vsum(@I..@II) and tax = sum * 0.08 Am I doing sth wrong ? Thanks for help, Martin | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum || | tax || |-+| | sum | 0 | #+TBLFM: @II+1$2=vsum(@I..@II);f2N::@II+2$2=@II+1$2*0.08;f2N::@$2=vsum(@II..@III);f2N | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum | 300.00 | | tax | 24.00 | |-+| | sum | 324.00 | #+TBLFM: @4$2=vsum(@-I..@-II);%.2f::@5$2=@4$2*0.08;%.2f::@6$2=vsum(@-I..@-II);%.2f I often use negative headline references for total lines in order to sum backward from the current cell. So vsum(@-I..@-II);%.2f means sum the cells between the first headline above the current cell to the second headline above the current cell, and then format the result as a decimal with two decimal places (%.2f). Looking at your formula, I think you manually wrote the TBLFM line. One thing I've found is that the TBLFM line doesn't support relative references for the cell specification, only in the formula. I used C-u C-c = to set mine. Nowadays, you can use (both on the LHS and the RHS of the formula) symbolic references relative to the first, second, third ... row like this: @, @, @ ... and relative to the last, penultimate, antepenultimate (is there such a word?) row like this: @, @, @ ..., and similarly for columns, so you could write the formula, like this: #+TBLFM: @$=vsum(@-I..@-II);%.2f::@$=@$*0.08;%.2f::@$=vsum(@-I..@-II);%.2f This *does* require iterated evaluations, so C-u C-u C-c C-c is your best bet, to make sure everything is updated properly. Nick Good luck! -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] table spreadsheet problem
Nowadays, you can use (both on the LHS and the RHS of the formula) symbolic references relative to the first, second, third ... row like this: @, @, @ ... and relative to the last, penultimate, antepenultimate (is there such a word?) row like this: @, @, @ ..., and similarly for columns, so you could write the formula, like this: #+TBLFM: @$=vsum(@-I..@-II);%.2f::@$=@$*0.08;%.2f::@$=vsum(@-I..@-II);%.2f This *does* require iterated evaluations, so C-u C-u C-c C-c is your best bet, to make sure everything is updated properly. Nick What version was that introduced in? I know I haven't kept on the bleeding edge, and I tried that just this past week and it didn't work. I was hoping for it! -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] table spreadsheet problem
Am 19.03.2012 um 16:56 schrieb Nick Dokos: Russell Adams rlad...@adamsinfoserv.com wrote: On Mon, Mar 19, 2012 at 04:01:42PM +0100, Martin Halder wrote: Hi all, question about table calculation. Found in the documentation that I could refer to e.g. first line after second hline with @II+2. Would like to calculate sum = vsum(@I..@II) and tax = sum * 0.08 Am I doing sth wrong ? Thanks for help, Martin | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum || | tax || |-+| | sum | 0 | #+TBLFM: @II+1$2=vsum(@I..@II);f2N::@II+2$2=@II+1$2*0.08;f2N::@$2=vsum(@II..@III);f2N | article | price | |-+| | item1 | 100.00 | | item2 | 200.00 | |-+| | sum | 300.00 | | tax | 24.00 | |-+| | sum | 324.00 | #+TBLFM: @4$2=vsum(@-I..@-II);%.2f::@5$2=@4$2*0.08;%.2f::@6$2=vsum(@-I..@-II);%.2f I often use negative headline references for total lines in order to sum backward from the current cell. So vsum(@-I..@-II);%.2f means sum the cells between the first headline above the current cell to the second headline above the current cell, and then format the result as a decimal with two decimal places (%.2f). Looking at your formula, I think you manually wrote the TBLFM line. One thing I've found is that the TBLFM line doesn't support relative references for the cell specification, only in the formula. I used C-u C-c = to set mine. Nowadays, you can use (both on the LHS and the RHS of the formula) symbolic references relative to the first, second, third ... row like this: @, @, @ ... and relative to the last, penultimate, antepenultimate (is there such a word?) row like this: @, @, @ ..., and similarly for columns, so you could write the formula, like this: #+TBLFM: @$=vsum(@-I..@-II);%.2f::@$=@$*0.08;%.2f::@$=vsum(@-I..@-II);%.2f This *does* require iterated evaluations, so C-u C-u C-c C-c is your best bet, to make sure everything is updated properly. Nick that is fantastic, many thanks for you help to you both. Martin Good luck! -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] [babel] [bug] org-babel-use-quick-and-dirty-noweb-expansion
2012/3/19 Eric Schulte eric.schu...@gmx.com Thanks for bringing up this bug. I'm attaching a patch to this email, once the current repositories issues are resolved I'll apply this patch to the repository. In the interim, you can apply this patch to your local copy of the git repository with. Great ! It's such a relief to be able to tangle my stuff in 8 s vs 4 to 5 minutes ! Thanks so much ! Nicolas
Re: [O] table spreadsheet problem
Russell Adams rlad...@adamsinfoserv.com wrote: Nowadays, you can use (both on the LHS and the RHS of the formula) symbolic references relative to the first, second, third ... row like this: @, @, @ ... and relative to the last, penultimate, antepenultimate (is there such a word?) row like this: @, @, @ ..., and similarly for columns, so you could write the formula, like this: #+TBLFM: @$=vsum(@-I..@-II);%.2f::@$=@$*0.08;%.2f::@$=vsum(@-I..@-II);%.2f This *does* require iterated evaluations, so C-u C-u C-c C-c is your best bet, to make sure everything is updated properly. Nick What version was that introduced in? I know I haven't kept on the bleeding edge, and I tried that just this past week and it didn't work. I was hoping for it! It was introduced about a year ago, so it should be in 7.7 or later (possibly some earlier releases as well but I haven't checked in detail.) If you git, then the relevant commits are 5631a309ab567e0a6a059ce728f84c1637fd253f 3dd474575205d3808390fc6ea2d5feccdb3d4305 1432e4bc79f55ed21e8478284b6b7552736d0c22 The first two are the main ones - the last is a bug fix. Best bet is a fairly recent org (modulo all the git problems that people are trying to fix ATM). Nick
Re: [O] table spreadsheet problem
On Mon, Mar 19, 2012 at 01:42:50PM -0400, Nick Dokos wrote: It was introduced about a year ago, so it should be in 7.7 or later (possibly some earlier releases as well but I haven't checked in detail.) If you git, then the relevant commits are 5631a309ab567e0a6a059ce728f84c1637fd253f 3dd474575205d3808390fc6ea2d5feccdb3d4305 1432e4bc79f55ed21e8478284b6b7552736d0c22 The first two are the main ones - the last is a bug fix. Wow, I know Org advances quickly but I hadn't checked my version recently. I'm still on 7.01e! Perhaps I'll upgrade to this new bugfix-only release. Thanks for your input, that's a useful feature! -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
Re: [O] table spreadsheet problem
Russell Adams rlad...@adamsinfoserv.com wrote: On Mon, Mar 19, 2012 at 01:42:50PM -0400, Nick Dokos wrote: It was introduced about a year ago, so it should be in 7.7 or later (possibly some earlier releases as well but I haven't checked in detail.) If you git, then the relevant commits are 5631a309ab567e0a6a059ce728f84c1637fd253f 3dd474575205d3808390fc6ea2d5feccdb3d4305 1432e4bc79f55ed21e8478284b6b7552736d0c22 The first two are the main ones - the last is a bug fix. Wow, I know Org advances quickly but I hadn't checked my version recently. I'm still on 7.01e! Perhaps I'll upgrade to this new bugfix-only release. Thanks for your input, that's a useful feature! Be careful - you might run into problems (I don't know if you've seen Bastien's and Achim's emails about the git problems). It might be safer to wait a bit until the dust settles and Bastien gives the green light. Nick
Re: [O] table spreadsheet problem
On Mon, Mar 19, 2012 at 02:01:02PM -0400, Nick Dokos wrote: Be careful - you might run into problems (I don't know if you've seen Bastien's and Achim's emails about the git problems). It might be safer to wait a bit until the dust settles and Bastien gives the green light. Just out of curiosity, I decided to check out how many versions of Org I've run... I'm up to 23! One more rev can't hurt, but I appreciate the advice. I'll wait for the release. My use stabilized a while back, while I use many features above and beyond the standard TODO's and outline (agenda, capture, babel, latex html publishing, spreadsheet, column view), my workflow hasn't required any extra features recently so I'm out of touch with the latest version. I'll be paying careful attention to the readme's for this new rev. Thanks. Details for the OCD: org-4.42 org-4.45 org-4.47 org-4.49 org-4.74 org-5.08 org-5.09 org-5.10-fix org-5.10b org-5.19a org-5.22a org-6.04c org-6.05b org-6.07b org-6.21b org-6.23 org-6.24b org-6.28e org-6.31a org-6.34c org-6.36 org-6.36c org-7.01e -- Russell Adamsrlad...@adamsinfoserv.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint:1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
[O] merging habits and normal scheduled items in the agenda grid
Hi all, A lot of my todo items and habits are scheduled to specific times in a day. However, The agenda view groups the habits together, so I end up with a grid containing my normal todos and below that is my list of habits, again sorted by time. This means that at any time, I need to check 2 lists to see if I have something planned for this moment. Is there a way to prevent the grouping of habits and just mix them with regular todo items in the grid? Thanks, Mathijs
[O] Request for hacks: Project month notations
Hi all, I'm working on a project where project dates were initially defined by a relative time given in months to some fixed date (the kick-off). So I've got a lot of dates which look like M19 (month 19 after kick-off), and I would like to use this notation (or something resembling it) for deadlines and other dates. The most viable option in my view is to define an elisp function and use it as a sexp date. I guess I'll be able to figure out how to, but I thought maybe somebody else has a better idea. One drawback is that I'd have (?) to define it in/through init.el, not in the project's org-mode file, which is unfortunate as the kick-off date is project-specific. Ideas anyone? Thanks in advance, Simon
[O] how to include graphics in pdf output
I am running org mode 7.7 on Win XP. I hope to export a document to pdf,
and I'd like to include an image in it. The image is a file called
DataLoggerImage.jpg; it resides in the same directory as my org file.
These are the first three lines of my org file:
#+OPTIONS: todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}
I have tried the following code to include a figure (tried both
approaches simultaneously, and the second one alone, neither with success):
\begin{figure}\centering
\includegraphics{DataLoggerImage}
\caption{Temperature and humidity data logger}\label{datalogger}
\end{figure}
#+CAPTION: Temperature and humidity data logger
#+LABEL: datalogger
[[./DataLoggerImage.jpg]]
The figure does not appear in the resulting pdf. Any advice as to what
I am doing wrong?
Thanks.
--Chris
--
Christopher W. Ryan, MD
SUNY Upstate Medical University Clinical Campus at Binghamton
425 Robinson Street, Binghamton, NY 13904
cryanatbinghamtondotedu
Observation is a more powerful force than you could possibly reckon.
The invisible, the overlooked, and the unobserved are the most in danger
of reaching the end of the spectrum. They lose the last of their light.
From there, anything can happen . . . [God, in Joan of Arcadia,
episode entitled, The Uncertainty Principle.]
Re: [O] org-map-entries broken?
I can confirm this and add that it additionally breaks tag inheritance. I first noticed that a org-collector code block that I've been using forever was generating table that were way too long. My collector block includes =:conds ( not (string-match-p noexport ALLTAGS)= and the extra results I was getting all were from long trees tagged at the parent :no export: I also have some Agenda custom views that use tag inheritance that broke at the same time. I reverted =e0072f79137bbfabdf848da6865d8e4de776a549= and both behaviors corrected themselves. Mike On Monday, March 19, 2012, Charles Sebold cseb...@gmail.com wrote: I think this patch may have broken org-map-entries for me: e0072f79137bbfabdf848da6865d8e4de776a549 is the first bad commit commit e0072f79137bbfabdf848da6865d8e4de776a549 Author: David Maus dm...@ictsoc.de Date: Sun Mar 18 18:38:50 2012 +0100 Require one or more spaces (+) between keyword and headline * org.el (org-scan-tags): Require one or more spaces (+) between keyword and headline. Otherwise the re will match a line like: * TODO@ Foobar And assumes the @ to be part of the headline. This fixes a glitch reported by Simon Thum in 4f53def7.8080...@gmx.de. Hi all, I have found some irritating behaviour, potentially a bug. I have a block agenda which goes like: tags-todo @homeTODO=\TODO\ and it displays a certain org line that reads TODO_ state triggers Which is just a heading for dealing with TODO state triggers, and I appended the _ as I don't want it to be a TODO. For example, the global TODO list and syntax highlighting does not consider it a todo, but C-c a m TODO=TODO does. TODO=T does not, so it's not very grave. Most likely, it's simply an inconsistency arising from not having a real parser. I just wanted to report it here so it may get fixed. :04 04 8f5974f2dd7cf5f0ad10db56d223ba09a6dbca80 624cee5569de7ef8f240ad75943be215bb823ccc M lisp - Try the following before and after this patch was applied, for a test result: - * test one * test two * test three #+BEGIN_SRC emacs-lisp :results both (org-map-entries 'org-get-heading nil nil) #+END_SRC - The results ought to be the three test headings in a table output. After the patch it's blank. -- Charles Sebold Ego delendus sum
Re: [O] how to include graphics in pdf output
Christopher W. Ryan cr...@binghamton.edu wrote:
I am running org mode 7.7 on Win XP. I hope to export a document to pdf,
and I'd like to include an image in it. The image is a file called
DataLoggerImage.jpg; it resides in the same directory as my org file.
These are the first three lines of my org file:
#+OPTIONS: todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}
I have tried the following code to include a figure (tried both
approaches simultaneously, and the second one alone, neither with success):
Not sure what you mean here: did you just add the latex code into your org file
as is?
\begin{figure}\centering
\includegraphics{DataLoggerImage}
\caption{Temperature and humidity data logger}\label{datalogger}
\end{figure}
#+CAPTION: Temperature and humidity data logger
#+LABEL: datalogger
[[./DataLoggerImage.jpg]]
The figure does not appear in the resulting pdf. Any advice as to what
I am doing wrong?
Can you post your org file and the tex file that's produced on export?
Thanks,
Nick
Re: [O] [babel] [bug] org-babel-use-quick-and-dirty-noweb-expansion
Nicolas Girard girard.nico...@gmail.com writes: 2012/3/19 Eric Schulte eric.schu...@gmx.com Thanks for bringing up this bug. I'm attaching a patch to this email, once the current repositories issues are resolved I'll apply this patch to the repository. In the interim, you can apply this patch to your local copy of the git repository with. Great ! It's such a relief to be able to tangle my stuff in 8 s vs 4 to 5 minutes ! Thanks so much ! Nicolas Wow, Out of curiosity how large is this file and with how many code blocks? Is it possible to see how many times the `org-entry-get' function is called during tangling? The speed of non-quick-and-dirty style tangling is entirely dependent on the heavy use of Org-mode properties so the former will only see speed improvements if they are made in the later. Happy the quick options is now working for you. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] org-contacts quit working?
Hi -- After a git pull today, my org-contacts no longer works. (e.g. M-x org-contacts George finds no matches. So especially: tab-completion in message-mode no longer works). Has anyone else noticed this? (I'm not quite sure how to provide more useful info...) All the best, george -- ,-- | George McNinch gmcninch (at) gmail.com | http://gmcninch.math.tufts.edu `--
Re: [O] org-contacts quit working?
George McNinch gmcni...@gmail.com writes: After a git pull today, my org-contacts no longer works. (e.g. M-x org-contacts George finds no matches. So especially: tab-completion in message-mode no longer works). Has anyone else noticed this? (I'm not quite sure how to provide more useful info...) Yes, we have... Bastien is in the process of fixing the repo, meanwhile you could compile from these commits: e85080 (maint) 7e903a (master) Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
[O] Patch: Customize failure for org-agenda-custom-commands
The Customize interface for org-agenda-custom-commands fails for agenda commands with an org-agenda-entry-types command option. The reason it fails is that the org-agenda-entry-types option should be a quoted list, but the defcustom expression doesn't add the quote properly. A patch is below. To reproduce the error: 1. M-x customize-variable RET org-agenda-custom-commands 2. Click the first INS button 3. Choose a convenient access key and description (or leave them as defaults -- I used access key x) 4. Click the second Value Menu button (currently set to Tags/Property match (all agenda files)) and choose Agenda 5. Under Local settings for this command. Remember to quote values:, click INS 6. Click the new Value Menu button and choose Set daily/weekly entry types 7. C-c C-c (sets Customize variable for the current session) 8. M-x org-agenda RET x (or just C-c a x) -- you'll get an empty agenda buffer and the error message Symbol's function definition is void: :deadline. I haven't checked whether there are other quoting issues in the customization definition for org-agenda-custom-commands but thought I would submit the patch anyway. Joe V. Patch: diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 1b033e8..2e74d5d 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -306,11 +306,13 @@ you can \misuse\ it to also add other text to the header. However, (string :tag +tag or -tag (list :tag Set daily/weekly entry types (const org-agenda-entry-types) - (set :greedy t :value (:deadline :scheduled :timestamp :sexp) - (const :deadline) - (const :scheduled) - (const :timestamp) - (const :sexp))) + (list + (const :format quote) + (set :greedy t :value (:deadline :scheduled :timestamp :sexp) +(const :deadline) +(const :scheduled) +(const :timestamp) +(const :sexp (list :tag Standard skipping condition :value (org-agenda-skip-function '(org-agenda-skip-entry-if)) (const org-agenda-skip-function)
[O] Should maint branch be deprecated?
As an infrequent committer to org-mode, I wonder if the maint branch is more pain than gain. I've read through the mails arguing for its conception, and the benefits just don't appear to be resultant. Add to that - infrequent committer's who commit via the list generally know nothing about the maintenance branch (including me), which just leads to more confusion. I follow the commits to master, and the work to core developers due to the maint branch is clearly not insignificant? If the gain is greater than the pain then somebody needs to clue me up. Best, Martyn
Re: [O] org-contacts quit working?
Hi-- After a git pull today, my org-contacts no longer works. Has anyone else noticed this? (I'm not quite sure how to provide more useful info...) Achim Yes, we have... Bastien is in the process of fixing the repo, Achim meanwhile you could compile from these commits: Achim e85080 (maint) 7e903a (master) Thanks! -- ,-- | George McNinch gmcni...@gmail.com | http://gmcninch.math.tufts.edu `--
Re: [O] Should maint branch be deprecated?
Hi Martyn Martyn Jago martyn.j...@btinternet.com writes: As an infrequent committer to org-mode, I wonder if the maint branch is more pain than gain. I'm still in the process of fixing things. After I'm done, I will suggest a new workflow. Thanks, -- Bastien
Re: [O] Should maint branch be deprecated?
Martyn Jago martyn.j...@btinternet.com writes: As an infrequent committer to org-mode, I wonder if the maint branch is more pain than gain. I've read through the mails arguing for its conception, and the benefits just don't appear to be resultant. It seemed to work well until Bastien made a mistake because the release script wasn't properly adapted and digged the hole deeper while trying to fix it (too) quickly. Maint is good again, master still needs a few more touches. Add to that - infrequent committer's who commit via the list generally know nothing about the maintenance branch (including me), which just leads to more confusion. I follow the commits to master, and the work to core developers due to the maint branch is clearly not insignificant? It is actually quite easy: If it's a bugfix for something broken in a release version, commit to maint and merge maint back into master. If implementing a new feature or fixing something not yet released, commit to master. If the gain is greater than the pain then somebody needs to clue me up. The argument is the same as before: master contains changes that introduce new features and may break compatibility while maint should only contain bugfixes. This is important because org also needs to respect Emacs' release schedule (and synchronize with the bzr repo they use), which generally means that they will accept bugfixes, but no new features during certain times (like right now). The other development model is to develop new stuff in feature branches and those tend not to get tested too well before going mainline. Ultimately it's Bastiens' call. If he decides to go back to the single branch model, he'll have to do much more tedious manual work to keep org in sync with Emacs and when doing bugfix releases. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] how to include graphics in pdf output
On Mon, Mar 19, 2012 at 20:53, Nick Dokos nicholas.do...@hp.com wrote: [[./DataLoggerImage.jpg]] The figure does not appear in the resulting pdf. Any advice as to what I am doing wrong? Can you post your org file and the tex file that's produced on export? Is the above correct syntax? Shouldn't it be as shown below? [[file:./DataLoggerImage.jpg]] -- Suvayu Open source is the future. It sets us free.
Re: [O] how to include graphics in pdf output
suvayu ali fatkasuvayu+li...@gmail.com wrote: On Mon, Mar 19, 2012 at 20:53, Nick Dokos nicholas.do...@hp.com wrote: [[./DataLoggerImage.jpg]] The figure does not appear in the resulting pdf. Any advice as to what I am doing wrong? Can you post your org file and the tex file that's produced on export? Is the above correct syntax? Shouldn't it be as shown below? [[file:./DataLoggerImage.jpg]] I had the same reaction at first, but I tried it and the pdf export went through without a hitch in either case. I'm not sure whether that's intended behavior or an accident though. Nick
[O] Org release 7.8.06 (bugfix)
Dear all, I'm releasing Org 7.8.06 which replaces the two previous bugfix versions (7.8.04 and 7.8.05). Please don't use those versions. http://orgmode.org/org-mode-download.html As Achim summarised, I relied on a script that did not the right thing, got me confused, and I turned the problem into a horrible mess by trying to fix it too hastily. Thanks to everyone for your patience and to Achim for his kind directions while sorting things out. -- Bastien
[O] [DEV] New git workflow
Hi all, our current git workflow is pretty well summarised by Achim -- we have two main branches, master and maint, and we (try to) follow these rules: If it's a bugfix for something broken in a release version, commit to maint and merge maint back into master. If implementing a new feature or fixing something not yet released, commit to master. On top of that, some local development happens in dedicated branches. The role of master is clear: it contains latest mature developments, which are either (1) bugfixes merged from maint, (2) features merged from dedicated branches or (3) features developed in master directly. The role of maint is less clear: it is both a hotfix branch and a release branch for bugfix releases. The reason for this branch was first that we need to keep a production-like version of Org in sync with Emacs. The main problem I see With this workflow is that releases are made from two different branches: bugfix releases are made from maint and major releases are made from master. This doesn't look right to me. So I suggest to use three branches with these rules: - master: the main persistent branch. This is were regular development goes. This branch is merged back to the maint branch when we release a new major version. No release happens directly from this branch. - maint: the production persistent branch. This branch is dedicated to the release process: when hot fixes are hot enough, we merge the hotfix branch to the maint branch and release a bugfix release. When the master branch (where hot fixes are also merged to) is mature and well tested, we merge master into maint and release a major version. - hotfix-7.XX.XX: the transient branch for hotfixes. Severe bugs are fixed there first, then merged back to maint when this makes sense. The branch is created when we need it and deleted when we don't need it anymore. This workflow looks clearer to me. Here are the advantages I see: 1) *all releases happen on the same branch* (the maint branch): it is easier to keep this branch in sync with Emacs and we can also add git hooks to automate the release process. 2) the master branch *is* the development branch: yes, pretty unusual. At least as unusual as not having two mailing lists, one for users and one for devs. But I want to stick to what makes this list a great place: regular users are invited to live on the bleeding edge and to contribute patches on the development branch, the one they will clone first. So, what's next? I will merge 7.8.06 into Emacs. Nothing should be committed to maint anymore before the next release. Important bug fixes for 7.8.06 all go to a new branch hotfix-7.8.06. Usual development goes to master, from where we regularily merge the hotfix branch. We'll get rid of the hotfix branch when releasing 7.8.07 or 7.9. ... Finally, two positive things from the mess I put and went through: I learned more about git, and I experienced once again how patient and helpful people can be on this list. Thanks to all again! -- Bastien
Re: [O] Should maint branch be deprecated?
Hi Achim, Achim Gratz strom...@nexgo.de writes: It seemed to work well until Bastien made a mistake because the release script wasn't properly adapted and digged the hole deeper while trying to fix it (too) quickly. Maint is good again, master still needs a few more touches. This should be all right now -- thanks again! If the gain is greater than the pain then somebody needs to clue me up. The argument is the same as before: master contains changes that introduce new features and may break compatibility while maint should only contain bugfixes. This is important because org also needs to respect Emacs' release schedule (and synchronize with the bzr repo they use), which generally means that they will accept bugfixes, but no new features during certain times (like right now). See my email about the new git workflow: I want to have a branch dedicated to releases. I think it will make things way more readable and manageable. The other development model is to develop new stuff in feature branches and those tend not to get tested too well before going mainline. We already use dedicated branch for development sometimes -- see the branch for Max/Carsten new feature. But you're right in saying that I want to keep the majority of development happening in master. Ultimately it's Bastiens' call. If he decides to go back to the single branch model, he'll have to do much more tedious manual work to keep org in sync with Emacs and when doing bugfix releases. With the old model, the *only* reason for having maint was the Emacs sync issue. Now the reason is to clarify the release process. Best, -- Bastien
Re: [O] Should maint branch be deprecated?
Hi Martyn, Martyn Jago martyn.j...@btinternet.com writes: As an infrequent committer to org-mode, I wonder if the maint branch is more pain than gain. It is a pain when too many things should happen on it. IMO It is a gain when we dedicate it to releases only. No pain should come out of introducing hotfix-* branches, as they are transient branches. Now I'm off to a well-deserved bed :) -- Bastien
Re: [O] Temporary commit freeze while fixing the repo and before 7.8.06
Bastien b...@altern.org writes: Developers: please don't commit anything while we are fixing this. The freeze is over. Normal development can continue on master with bugfixes committed to the newly created hotfix-7.8.06. -- Bastien
Re: [O] org-map-entries broken?
Mike McLean mike.mcl...@pobox.com writes: I reverted =e0072f79137bbfabdf848da6865d8e4de776a549= and both behaviors corrected themselves. I reverted this commit both in maint (included in 7.8.06) and master. Thanks, -- Bastien
Re: [O] [PATCH] Adding Simplified Chinese(UTF-8) translation for org-exp
tumashu tuma...@gmail.com writes: It should be: #+begin_example html xmlns=http://www.w3.org/1999/xhtml; lang=zh-CN xml:lang=zh-CN #+end_example [[http://www.w3.org/International/articles/bcp47/]] Fixed in maint (included in 7.8.06) and master. Thanks! -- Bastien
Re: [O] Org-mode version 7.8.05 (release_7.8.05.19.gb32d.dirty) `org-agenda-filter' bug pushing to mobile
Nick Bell mail+...@nickbell.org writes: Using the above version, needed to apply the patch http://article.gmane.org/gmane.emacs.orgmode/51812 in order to make org-mobile-push work. My git-fu isn't quite up to working out what should (if anything) have happened to incorporate this fix into the release. This is fixed now in maint (included in 7.8.06) and master. Sorry for this. -- Bastien
Re: [O] [babel] [bug] org-babel-use-quick-and-dirty-noweb-expansion
Hi Eric, Eric Schulte eric.schu...@gmx.com writes: Thanks for bringing up this bug. I'm attaching a patch to this email, once the current repositories issues are resolved I'll apply this patch to the repository. In the interim, you can apply this patch to your local copy of the git repository with. Applied in hotfix-7.8.06, thanks. -- Bastien
Re: [O] [PATCH] LaTeX export: added support for sidewaystable from the rotating package
Hi Andreas, Andreas Leha andreas.l...@med.uni-goettingen.de writes: below you find a small patch that allows to use sidewaystable during latex export, i.e. this file should export as expected: Applied, thanks. -- Bastien
Re: [O] Problem with choosing mode while editing blocks with C-c '
Hi Suvayu, Suvayu Ali fatkasuvayu+li...@gmail.com writes: On Wed, Mar 14, 2012 at 09:41, suvayu ali fatkasuv...@gmail.com wrote: Yup, your analysis was spot on. :) Changing the let to let* and reevaluating the defun fixed the issue. I hadn't grasped this subtlety about let*, dependencies on preceding bindings hidden behind function calls! I am attaching the changes as a patch. Let me know if it is okay. Applied, thanks to you and Nick! -- Bastien
Re: [O] Should maint branch be deprecated?
Bastien b...@altern.org writes: Hi Bastien, Achim Hi Martyn, Martyn Jago martyn.j...@btinternet.com writes: As an infrequent committer to org-mode, I wonder if the maint branch is more pain than gain. It is a pain when too many things should happen on it. IMO It is a gain when we dedicate it to releases only. No pain should come out of introducing hotfix-* branches, as they are transient branches. Now I'm off to a well-deserved bed :) I certainly appreciate the need to stabilize releases. But I did get to wondering lately if the original purpose of maint was kind of lost in the overall high-throughput repo activity. I'm a big fan of Git, and have started using it for non-version control activities, so I appreciate things can always be fine-tuned to suit the current situation. Thanks for the considered replies. Best, Martyn
Re: [O] how to include graphics in pdf output
I've attached a small org file that reproduces my problem with getting
images to export to pdf. I've also attached the resulting .tex file.
I think my issue may have something to do with my misunderstanding of
inline tasks, since if I put my org code for inclusion of the image
elsewhere in the org file, under its own 2nd level heading (2 stars)
then it exports fine. The narrative text in the attached org file
explains my observations in more detail.
Thanks.
--Chris Ryan
Nick Dokos wrote:
suvayu alifatkasuvayu+li...@gmail.com wrote:
On Mon, Mar 19, 2012 at 20:53, Nick Dokosnicholas.do...@hp.com wrote:
[[./DataLoggerImage.jpg]]
The figure does not appear in the resulting pdf. Any advice as to what
I am doing wrong?
Can you post your org file and the tex file that's produced on export?
Is the above correct syntax? Shouldn't it be as shown below?
[[file:./DataLoggerImage.jpg]]
I had the same reaction at first, but I tried it and the pdf export went
through without a hitch in either case. I'm not sure whether that's intended
behavior or an accident though.
Nick
#+OPTIONS: todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}
* I guess I don't understand enough about Org's hierarchical trees yet
** Study design
Here's what we'll do.
As patients of home care agencies, the subjects will all be considered
homebound by definition. Subjects with cognitive impairment or psychiatric
illness sufficiently severe to make them unable to consent to the study will
not be eligible.
** TODO notice how end on next line is expandable
** END
Somehow this text is under, hierarchically-speaking, the END statement of this
inline task.
So it does not show up in the final pdf
** TODO there is text and the image file inside end
** END
Neither does this paragraph.
Neither does this image, which must also be under the END statement of the
inline task
#+CAPTION: Temperature and humidity data logger
#+LABEL: datalogger
[[./DataLoggerImage.jpg]]
** But if I start a new 2-star heading
and put the image here, it works fine.
#+CAPTION: Temperature and humidity data logger
#+LABEL: datalogger
[[./DataLoggerImage.jpg]]
% Created 2012-03-20 Tue 00:04
\documentclass[11pt]{article}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{fixltx2e}
\usepackage{graphicx}
\usepackage{longtable}
\usepackage{float}
\usepackage{wrapfig}
\usepackage{soul}
\usepackage{textcomp}
\usepackage{marvosym}
\usepackage{wasysym}
\usepackage{latexsym}
\usepackage{amssymb}
\usepackage{hyperref}
\tolerance=1000
\usepackage[margin=1in]{geometry}
\usepackage{graphicx}
\providecommand{\alert}[1]{\textbf{#1}}
\title{WhereIsImage}
\author{Chris Ryan}
\date{\today}
\begin{document}
\maketitle
\section{I guess I don't understand enough about Org's hierarchical trees yet}
\label{sec-1}
\subsection{Study design}
\label{sec-1-1}
Here's what we'll do.
As patients of home care agencies, the subjects will all be considered homebound by definition. Subjects with cognitive impairment or psychiatric illness sufficiently severe to make them unable to consent to the study will not be eligible.
\subsection{But if I start a new 2-star heading}
\label{sec-1-2}
and put the image here, it works fine.
\begin{figure}[htb]
\centering
\includegraphics[width=10em]{./DataLoggerImage.jpg}
\caption{\label{datalogger}Temperature and humidity data logger}
\end{figure}
\end{document}
Re: [O] how to include graphics in pdf output
Christopher W. Ryan cr...@binghamton.edu wrote:
I've attached a small org file that reproduces my problem with getting
images to export to pdf. I've also attached the resulting .tex file.
I think my issue may have something to do with my misunderstanding of
inline tasks, since if I put my org code for inclusion of the image
elsewhere in the org file, under its own 2nd level heading (2 stars)
then it exports fine. The narrative text in the attached org file
explains my observations in more detail.
#+OPTIONS: todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}
* I guess I don't understand enough about Org's hierarchical trees yet
** Study design
Here's what we'll do.
As patients of home care agencies, the subjects will all be considered
homebound by definition. Subjects with cognitive impairment or psychiatric
illness sufficiently severe to make them unable to consent to the study will
not be eligible.
** TODO notice how end on next line is expandable
** END
Somehow this text is under, hierarchically-speaking, the END statement of
this inline task.
So it does not show up in the final pdf
** TODO there is text and the image file inside end
** END
Neither does this paragraph.
Neither does this image, which must also be under the END statement of the
inline task
#+CAPTION: Temperature and humidity data logger
#+LABEL: datalogger
[[./DataLoggerImage.jpg]]
** But if I start a new 2-star heading
and put the image here, it works fine.
#+CAPTION: Temperature and humidity data logger
#+LABEL: datalogger
[[./DataLoggerImage.jpg]]
What is the value of org-inlinetask-min-level? If it's the default 15,
then you just haven't formatted the inline tasks correctly (not enough
stars)- did you use C-c C-x t to insert them? I used that to
insert the inline tasks and I got the following org file which exports
correctly afaict:
--8---cut here---start-8---
#+OPTIONS: todo:nil toc:nil tags:nil
#+LATEX_HEADER: \usepackage[margin=1in]{geometry}
#+LATEX_HEADER: \usepackage{graphicx}
* I guess I don't understand enough about Org's hierarchical trees yet
** Study design
Here's what we'll do.
As patients of home care agencies, the subjects will all be considered
homebound by definition. Subjects with cognitive impairment or psychiatric
illness sufficiently severe to make them unable to consent to the study will
not be eligible.
*** TODO notice how end on next line is expandable
*** END
Somehow this text is under, hierarchically-speaking, the END statement of this
inline task.
So it does not show up in the final pdf
*** TODO there is text and the image file inside end
*** END
Neither does this paragraph.
Neither does this image, which must also be under the END statement of the
inline task
#+CAPTION: foo
#+LABEL: foo
[[./DataLoggerImage.jpg]]
** But if I start a new 2-star heading
and put the image here, it works fine.
#+CAPTION: bar
#+LABEL: bar
[[./DataLoggerImage.jpg]]
--8---cut here---end---8---
Nick
Re: [O] org-map-entries broken?
At Tue, 20 Mar 2012 02:34:40 +0100, Bastien wrote: Mike McLean mike.mcl...@pobox.com writes: I reverted =e0072f79137bbfabdf848da6865d8e4de776a549= and both behaviors corrected themselves. I reverted this commit both in maint (included in 7.8.06) and master. Thanks, I'll give a fix for the problem I tried to fix with this commit a new shot. Best, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgpJsFgamohYt.pgp Description: OpenPGP Digital Signature
Re: [O] [bug] org-agenda-write does not handle date stamps without day of week
I have just pushed the new version of this regexp into master. Karl, let me know if it fixes the issues you where having with writing agendas. - Carsten On 19.3.2012, at 10:12, Carsten Dominik wrote: On 17.3.2012, at 07:45, Nick Dokos wrote: Karl Voit devn...@karl-voit.at wrote: * Nick Dokos nicholas.do...@hp.com wrote: Karl Voit devn...@karl-voit.at wrote: For me, it was a no time to work on org - stash it... OK. I just wanted to make sure that it *is* on someone's todo list :-) * Karl Voit devn...@karl-voit.at wrote: * 2012-03-05 08:00-09:00 Wrong: ends up as full day event org-agenda-write calls org-export-icalendar which calls org-print-icalendar-entries which loops over all the entries and parses them, decomposing them into timestamps. Each timestamp is then passed to org-parse-time-string. It's this one that cannot handle non-standard formats: it uses a regexp and assumes that all the matched parts are going to be in fixed places: As to how to fix it, there are several possibilities: 1. fix your scripts that produce time stamps to include day-of-week. Sorry, deriving DOW from an arbitrary timestamps from arbitrary data sources is either pretty time consuming (calendar calculations) or simply hard to calculate. Outside Org-mode, DOW is seldom part of time-stamp data :-( 2. change the callers of org-parse-time-string to make sure that DOW is included. There are roughly three dozen callers, so 2. is possible but a pain. Ack. 3. change just one caller: org-print-icalendar-entries to make sure that DOW is included. 3. is simple but ugly as sin, Ouch, ack :-) 4. change org-parse-time-string to handle a missing DOW. 4. is the best way to handle it within org. Full ack. I vote for 1. where *you* have to do all the work ;-) YMMD :-) If my brain would be compatible to ELISP, I'd send a patch. Promised. But I'll take my chance and wait for someone else (you?) implementing 4. to resolve this issue for everybody. I really appreciate every second you guys invest in maintaining Org-mode! I don't know about you, but whenever I engage in hand-to-hand combat with a complicated regexp, I come out bruised, muddied and a lot worse for wear. In any case, I'm attaching an org file with my investigations. It contains a description and a code block for testing. I hope that the attachment will come through unscathed: it contains regexps, and munging a regexp that looks like hen scratchings in the first place through uncooperative mailers is not something to be relished. BTW, I'm not advocating a change: I'll leave it to Karl to do that if he really wants to and to the maintainers to decide whether it's worth doing. But it can be done (more or less). And maybe somebody will come up with a better way than the proof-of-concept that I'm attaching here. Hi Nick and Karl, since we did make a change to Org a while ago to allow date stamps without the name of the day, I think it is only consequent to also do it for this case. Must have slipped our attention back then. The only thing we must ensure is that this regexp matches fast as it is used a lot. Nick's proposal works, except for the fact that is also matches when the time is directly attached to day name. Maybe it is cleaner to not match in this case. If we are going to make the day name optional, then it is better to include matching of the whitespace after the date into the day-name part of the regexp. I am attaching Nick's file again, with a third proposal for an updated regexp. As far as speed is concerned, this regexp will, if there is name and time, match directly and straight. If the date name is missing, it will notice on the first digit belonging to the time and switch without backtracking (well, minimal backtracking when there are multiple spaces) to the regexp section for the time of day. Rematching the spaces after the date will be the only overhead. Cheers - Carsten reproducer.org Nick PS. BTW, if you look at the attachment, it helps if you have a wide window, something like 165 characters wide. reproducer.org
