[O] Org mode build failure
Hi, I am encountering the following build failure when I do `make compile': make[1]: Entering directory `/path/build/org-mode/lisp' rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc install -m 644 -p . install: missing destination file operand after ‘.’ Try 'install --help' for more information. make[1]: *** [addcontrib] Error 1 make[1]: Leaving directory `/path/build/org-mode/lisp' make: *** [compile] Error 2 Any ideas what changed? -- Suvayu Open source is the future. It sets us free.
Re: [O] Confused about inline html images
Hi John, John Hendy jw.he...@gmail.com writes: #+attr_html: width=200px [[http://i.imgur.com/tladtBz.jpg][http://i.imgur.com/tladtBz.jpg]] This is not (and has never been) converted to a link, but to an image. Maybe a limitation that we can work on later on. The fix I pushed is about #+attr_html: width=200px [[http://i.imgur.com/tladtBz.jpg][tladtBz.jpg]] where width=200px was attributed to the a href ... instead of the image. HTH, -- Bastien
Re: [O] About range references in the spreadsheet
t...@tsdye.com (Thomas S. Dye) writes: a range of three fields in the row before the current row, starting two columns before the current column and ending in the current column. Yes, it's very explicit, but a bit long -- I try to have the explanation fit in one line. I updated again to this: 3 fields in the row above, starting from 2 columns on the left -- Bastien
Re: [O] editing The compact Org-Mode Guide
Evan Misshula evanmissh...@gmail.com writes: Thanks for the instructions on how to play nice in the sandbox. We noobs are always afraid we are going to cause more work than we fix. We are all n00bs! Somehow. -- Bastien
Re: [O] [PATCH] Tiny change in ob-lilypond.el
Hi Thorsten, Thorsten Jolitz tjol...@gmail.com writes: A tiny change to make ob-lilypond export the results in the format specified for the ':file' in the source-block header. Uh, silly me. Applied, thanks! -- Bastien
Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?
Hi Martin and Bernt, the master branch now have new sorting strategies: timestamp-up Sort by any timestamp, early first timestamp-down Sort by any timestamp, late first scheduled-up Sort by scheduled timestamp, early first scheduled-down Sort by scheduled timestamp, late first deadline-upSort by deadline timestamp, early first deadline-down Sort by deadline timestamp, late first ts-up Sort by active timestamp, early first ts-downSort by active timestamp, late first tsia-upSort by inactive timestamp, early first tsia-down Sort by inactive timestamp, late first Please have a try and let me know if this works as expected. Thanks both for your input on this, -- Bastien
Re: [O] subscribing to this mailing list with gnus
Hi John, 42 147 aeus...@gmail.com writes: I don't know the correct port / address within the context of this code: (setq gnus-select-method '(nntp gmane.emacs.orgmode (nntp-port-number 119))) Please ask this to the Gnus mailing list. Thanks, -- Bastien
Re: [O] copy file from link into agenda
Hi Subhan, Subhan Tindall subhan.tind...@rentrakmail.com writes: What I'm looking for is a way to load the contents of /home/stindall/.emacs into the agenda, ideally producing something similar to this: LOG datestamp /home/stindall/.emacs contents of .emacs file LOG datestamp some other file contents of some other file I better understand now, thanks for the explanations. my elisp-fu is not strong, so I'm hoping that a workable approximation of what I need already exists. Mhh.. no, it does not exist. -- Bastien
Re: [O] Sending BibTeX entries from Zotero to Org-mode via Fireforg
Hi Marko, ma...@dimjasevic.net (Marko Dimjašević) writes: Fireforg could not be installed because it is not compatible with Abrowser 18.0.1. I'm not sure if simply changing the max version parameter in install.rdf in fireforg.xpi is the best idea. Maybe -- can you try and tell? According to the git log, the last commit dates back to 2010. I guess it's not in active development anymore. Indeed. Also, I guess it needs org-protocol, but I can't figure out where to download it from. At: http://orgmode.org/worg/org-contrib/org-protocol.html it doesn't say anything about how to obtain it. org-protocol.el is part of Org's core. Any suggestions on how to get org-protocol and fireforg working so that I can export BibTeX entries from Zotero to org-mode? If it's of any help, I have GNU Emacs 23.3.1 and Org-mode 7.6. Please update to a more recent version of Org: http://orgmode.org Hopefully this will help in making FireOrg usable to you. Best, -- Bastien
Re: [O] Prefix arguments, checklists, and lists
Hi Robert and Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: What about lists? Just replace table with list and row with item. This is a global design, and lists are but a part of it. Agreed. And Org commands are so much about context that users could benefit from a command helper: a library that would display what function C-c C-c will call depending on the context. My understanding is that Robert's concern is more about discoverability than global design inconsistency. So perhaps such a library would lower his concern. 2 cts, -- Bastien
Re: [O] Worg publishing issue
Hi Bastien, On Thu, Feb 07, 2013 at 09:42:15AM +0100, Bastien wrote: But I see that it is not being published. I just published it: http://orgmode.org/worg/org-tutorials/org-beamer/org-e-beamer.html Thanks! I got the following publishing error after pushing my commit. remote: Publishing file /home/emacs/git/worg/org-tutorials/org-beamer/org-e-beamer.org using `org-publish-org-to-html' remote: Exporting... remote: Wrong type argument: stringp, nil remote: worg publish process 16964 exited at 02/05/13@07:01:27 Any ideas? 2 problems, a trivial one and a let's-prepare-for-headache one: 1. `org-publish-org-to-html' does not exist in the new export/publish libraries -- Nicolas, would that be enough to have aliases here (from org-publish-org-to-html to org-html-publish-to-html)? I guess many people rely on thse org-publish-org-to* functions. 2. Worg is published using the maint branch of org-mode.git. Which means that neither the new exporter nor the new way of escaping Org syntax in src code blocks are available... My guess is that your file org-e-beamer.org uses the new syntax for src code blocks -- I had to use the org-mode.git *master* branch to publish it correctly. We will need to update each begin_src block in Worg in order to use a recent org-mode.git for publishing. In my file there are no begin_src blocks, however I do have begin_example blocks like the following: #+begin_example ,#+LaTeX_CLASS: beamer ,#+LaTeX_CLASS_OPTIONS: [smaller,presentation] ,#+BEAMER_THEME: default #+end_example I have not been following the list very closely for the last 5-6 months (too many deadlines in real life :(), has the above escaping syntax been changed? Thanks, -- Suvayu Open source is the future. It sets us free.
Re: [O] org-html-link problem
Hi Chuck, cbe...@tajo.ucsd.edu writes: lisp/ox-html.el around line 2172: (unless (and desc (string-match (regexp-quote (car att)) desc)) att is nil maybe (unless (and att desc (string-match (regexp-quote (car att)) desc))?? Indeed, fixed, thanks. -- Bastien
Re: [O] Still Wishing for Snooze
Hi Andrew, Andrew M. Nuxoll nux...@up.edu writes: If you do that, I may have to send you a cheesecake. Time for a cheesecake! You can now use a delay cookie like this: SCHEDULED: 2013-02-07 jeu. -2d The item will not be shown today, but in three days. See the new options `org-scheduled-delay-days' and `org-agenda-skip-scheduled-delay-if-deadline' which are quite symmetric to `org-deadline-warning-days' and `org-agenda-skip-deadline-prewarning-if-scheduled'. Thanks for this idea, and thanks to Michael for the implementation example -- I implemented it a bit differently, but I think it makes sense (1) to use -2d to tell the scheduled item is postponed, and (2) to use the same - for prewarning and delays. -- Bastien
Re: [O] Bug: org-id-get-with-outline-path-completion docstring [7.9.3d (release_7.9.3d-929-ga2febd @ /home/flo/.emacs.d/org-mode/lisp/)]
Hi Florian, Florian Beck f...@fbeck.net writes: The docstring claims when the optional argument is omitted all headlines in all agenda files are eligible. In fact, only the headlines in the current file are used (which is reasonable). Fixed, thanks. -- Bastien
Re: [O] Sending BibTeX entries from Zotero to Org-mode via Fireforg
Hello, FWIW, I am using zotelo¹ with org, which works pretty well. (and installation should be easy.) For eg, my setup includes placing local variables in my org document as following, --8---cut here---start-8--- # Local Variables: # eval: (zotelo-minor-mode 1) # zotero-collection: #(0 0 1 (name *MyPaper*)) # End: --8---cut here---end---8--- where MyPaper is a directory in zotero database (or ALL if you want all the references). Now in emacs I just call zotelo-update-database, to get my bibliography updated in the specified bib file. Thanks., ¹ https://github.com/vitoshka/zotelo -- ఎందరో మహానుభావులు అందరికి వందనములు. YYR
Re: [O] Has anybody noticed ellipses instead of the top line of the window?
Hi William, thanks for digging this further. William william.leche...@ens-lyon.org writes: On Wed, 30 Jan 2013 18:36:16 +0100, Bastien spake thus: Org's visibility code then inserts the ... at the top line of the window for unknown reasons. Can you help me reproduce it? I also have visibility problems when performing undo-es. I can reproduce such an ellipsis by : - Cutting part of the buffer containing an ellipsis - Undoing the cut On the attached example, all being visible, fold the first second level headline, kill its line (C-k with cursor at the beginning of line), and undo the kill. The buffer then looks like I think you forgot to attach the example, and I was not able to reproduce the problem by following the directions... Thanks, -- Bastien
Re: [O] org export Taskjuggler
Nicolas Goaziou n.goaz...@gmail.com writes: If nothing has been started once the new export framework is installed and the early bugs are fixed, I will do the port. I don't quite understand why we need to port anything. The taskjuggler exporter is different than the other exporters in that it doesn't really export the content of an org file. Instead it just goes through the headlines (using the mapping API), takes some to be tasks and reads the properties of these headlines to build the taskjuggler file. It pretty much ignores any text that is between the headlines (see also the commentary in org-taskjuggler.el). In essence it treats the org file as a tree of nodes with properties that define the tasks, resources and reports. It doesn't use any of the common (old) exporting infrastructure. So woudn't a ported org-taskjuggler.el look exactly like to one that we have today? Thanks Christian -- Christian Egli Swiss Library for the Blind, Visually Impaired and Print Disabled Grubenstrasse 12, CH-8045 Zürich, Switzerland
[O] new exporter - LaTeX export setting org-export-latex-packages-alist and BUG empty source block export
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
I had the following in my emacs.org:
#+begin_src emacs-lisp
(require 'org-latex)
(setq org-export-latex-listings t)
(add-to-list 'org-export-latex-packages-alist '( listings))
(add-to-list 'org-export-latex-packages-alist '( color))
#+end_src
After upgrade of org this morning using git, the new exporter is there and I
get the following
error message:
(void-variable org-export-latex-packages-alist)
I just commented them out and added
#+LATEX_HEADER: \usepackage{listings}
#+LATEX_HEADER: \usepackage{color}
to the files concerned
In addition, there seems to be a BUG:
when exporting an empty source block to LaTeX, I get the following error
message:
org-babel-exp processing... [69 times]
apply: Wrong number of arguments: max, 0
I can easily replicate this with a document only containing:
* org-mode
#+begin_src emacs-lisp
#+end_src
which exports fine to html, but not LaTeX.
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 Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJRE36oAAoJENvXNx4PUvmCqx0IAMaDyq0GHlIrV6GEAXFAaAGz
nHzlLOsBEhubciZByeyP8f/6clr4rpyNVKz4PSpqAY8dR7mi3jcPxUT7EP449ddr
pQlbXJ+51SCoKDYMszD9jsaxxELq9nShFS09l/HsVsk9tuzTmIa8cft6RiNI5V9v
e5RkFaxlndOZsrR5eRqh9ITvoLlL6OkrCSlP/SPG+ua1J9tSKqi26s0MBAtCHjhx
vg1uHvUOVVLr0eVAcwiJfUyCvBkj7yFdNi8gQmbN+gVDvbyZCcjyZjmvSGiTqfc8
5j+4A4lAzEimAn57WxiKp6IK4qeytny9BKo23iBxhN8COBqyzolehSPOJpIFAjk=
=z3pP
-END PGP SIGNATURE-
Re: [O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1
Hi Kyle, Kyle Machulis k...@nonpolynomial.com writes: As of commit 8517be79b5c1fe165d23ea65ad70a282e9c595bb (bisected to find this), agenda compilation died with the following backtrace for me: Debugger entered--Lisp error: (error Bad timestamp `' Error was: (Not a standard Org-mode time string: )) signal(error (Bad timestamp `'\nError was: (Not a standard Org-mode time string: ))) error(Bad timestamp `%s'%s\nError was: %s (Not a standard Org-mode time string: )) byte-code(...) org-time-string-to-absolute() byte-code(...) org-agenda-get-timestamps(nil) org-agenda-get-day-entries(~/emacs_org/mozilla/mozilla.org (2 6 2013) :deadline :scheduled :timestamp :sexp) apply(org-agenda-get-day-entries ~/emacs_org/mozilla/mozilla.org (2 6 2013) (:deadline :scheduled :timestamp :sexp)) byte-code(...) byte-code(...) org-agenda-list(nil) call-interactively(org-agenda-list) byte-code(...) org-agenda(nil) call-interactively(org-agenda nil nil) It's dying when it hits a headline as follows: * Meeting 13:30 , %%(memq (calendar-day-of-week date) '(3)) I'm guessing this has something to do with the agenda sorting updates in the commit not liking the fact that the sexp evaluates to true. If the sexp evaluates nil for the day the agenda is trying to parse, nothing happens. If it evaluates to something other than nil (t if I use (= 3 (calendar-day-of-week date)), 3 if I use memq on a wednesday, etc...), I get the above error. Thanks for reporting this. Yes, diary sexp are special and can't really be handled here. I fixed this in master, please confirm this is okay. -- Bastien
Re: [O] Worg publishing issue
Hi Suvayu, Suvayu Ali fatkasuvayu+li...@gmail.com writes: Amidsts all the commotion about documentation for the new exporter, I committed a very early incomplete draft article documenting the new beamer exporter. http://orgmode.org/cgit.cgi/worg.git/commit/?id=d7dfb6133bcea0127d0c386334a833e8ac64323e Thanks for this! But I see that it is not being published. I just published it: http://orgmode.org/worg/org-tutorials/org-beamer/org-e-beamer.html I got the following publishing error after pushing my commit. remote: Publishing file /home/emacs/git/worg/org-tutorials/org-beamer/org-e-beamer.org using `org-publish-org-to-html' remote: Exporting... remote: Wrong type argument: stringp, nil remote: worg publish process 16964 exited at 02/05/13@07:01:27 Any ideas? 2 problems, a trivial one and a let's-prepare-for-headache one: 1. `org-publish-org-to-html' does not exist in the new export/publish libraries -- Nicolas, would that be enough to have aliases here (from org-publish-org-to-html to org-html-publish-to-html)? I guess many people rely on thse org-publish-org-to* functions. 2. Worg is published using the maint branch of org-mode.git. Which means that neither the new exporter nor the new way of escaping Org syntax in src code blocks are available... My guess is that your file org-e-beamer.org uses the new syntax for src code blocks -- I had to use the org-mode.git *master* branch to publish it correctly. We will need to update each begin_src block in Worg in order to use a recent org-mode.git for publishing. Here you go, -- Bastien
Re: [O] Bug when exporting as html with (org-narrow-to-subtree)
HI David, David Bjergaard dbjerga...@gmail.com writes: When exporting to html with (org-narrow-to-subtree) headlines deeper than 2 levels won't get exported. Expected behavior: All subheadings should be exported to a level set by headline-levels in my org init, or H: in the #+OPTIONS: line. Can you test again with the latest version of Org? Thanks in advance! -- Bastien
Re: [O] special strings
Hi Samuel, Samuel Wales samolog...@gmail.com writes: org-html.el:2468: (let ((all org-export-html-special-string-regexps) Where is this defined? It was defined in org.el but got squeezed out during the move to the new exporter. I reintroduced it in contrib/lisp/org-html.el. Thanks, -- Bastien
Re: [O] Feature: Group and limit items in agenda
Hi Muchenxuan, Muchenxuan Tong demon...@gmail.com writes: * Motivation - Sacha Chua proposed a solution for viewing top three tasks by context (http://sachachua.com/blog/2012/12/emacs-org-display-subset-tasks-context/) - In the Next view in Things (http://culturedcode.com/), one is able to setting to see only a limited numbers of top tasks of each project. Thanks for the pointers. From latest Org (master branch), you can now use `org-agenda-max-entries' either as a global option, or locally in each agenda view. See the docstring on how to use this option and its friends: org-agenda-max-effort org-agenda-max-tags org-agenda-max-todos org-agenda-max-effort might be particularily useful in TODO views. Let me know if this works for you. As for grouping, I think this is more about setting agenda views, sorting options and agenda filters properly -- but I'm open to any idea on how to improve this (or to make it easier to set.) Thanks! -- Bastien
Re: [O] Scheduling makes link disappear
Hi Thomas, Thomas Morgan t...@ziiuu.com writes: In an Org TODO list, scheduling an item that contains a link can cause the link to disappear. Thanks very for the report. Please try the attached patch and let me know if it fixes it (it should) but more importantly: if it breaks other agenda views. Best, diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 9b6dcae..59be594 100644 --- a/lisp/org-agenda.el +++ b/lisp/org-agenda.el @@ -8686,9 +8686,8 @@ Called with a universal prefix arg, show the priority instead of setting it. (defun org-agenda-show-new-time (marker stamp optional prefix) Show new date stamp via text properties. ;; We use text properties to make this undoable - (let ((inhibit-read-only t) - (buffer-invisibility-spec)) -(setq stamp (concat prefix = stamp)) + (let ((inhibit-read-only t)) +(setq stamp (concat prefix = stamp )) (save-excursion (goto-char (point-max)) (while (not (bobp)) @@ -8750,7 +8749,7 @@ ARG is passed through to `org-schedule'. (widen) (goto-char pos) (setq ts (org-schedule arg time))) - (org-agenda-show-new-time marker ts S)) + (org-agenda-show-new-time marker ts S)) (message %s ts))) (defun org-agenda-deadline (arg optional time) @@ -8770,7 +8769,7 @@ ARG is passed through to `org-deadline'. (widen) (goto-char pos) (setq ts (org-deadline arg time))) - (org-agenda-show-new-time marker ts D)) + (org-agenda-show-new-time marker ts D)) (message %s ts))) (defun org-agenda-clock-in (optional arg) -- Bastien
Re: [O] org export Taskjuggler
Christian Egli christian.e...@sbs.ch writes: Nicolas Goaziou n.goaz...@gmail.com writes: If nothing has been started once the new export framework is installed and the early bugs are fixed, I will do the port. I don't quite understand why we need to port anything. The taskjuggler exporter is different than the other exporters in that it doesn't really export the content of an org file. Instead it just goes through the headlines (using the mapping API), takes some to be tasks and reads the properties of these headlines to build the taskjuggler file. It pretty much ignores any text that is between the headlines (see also the commentary in org-taskjuggler.el). In essence it treats the org file as a tree of nodes with properties that define the tasks, resources and reports. It doesn't use any of the common (old) exporting infrastructure. So woudn't a ported org-taskjuggler.el look exactly like to one that we have today? I am not working on Taskjuggler exporter. I do have a FreeMind exporter in the works. That said, moving the TaskJuggler exporter to new org-export-* APIs - Nicolas calls them tools - is a good thing. Each new exporter, exercises or emphasizes different aspects of the export infrastructure. I am sure porting TaskJuggler will further solidify the org-export framework in terms of exposing existing bugs or adding new utilties or APIs. http://orgmode.org/worg/dev/org-export-reference.html If TaskJuggler exporter just works, then it is good. The porting task can be done in an un-hurried manner. Thanks Christian --
Re: [O] Org mode build failure
Suvayu Ali fatkasuvayu+linux at gmail.com writes: I am encountering the following build failure when I do `make compile': make[1]: Entering directory `/path/build/org-mode/lisp' rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc install -m 644 -p . install: missing destination file operand after ‘.’ Try 'install --help' for more information. make[1]: *** [addcontrib] Error 1 make[1]: Leaving directory `/path/build/org-mode/lisp' make: *** [compile] Error 2 Any ideas what changed? The new exporter moved into core and the files you specified in ORG_ADD_CONTRIB are no longer existing there. Remove that definition and all is well. Regards, Achim.
[O] Yasnippet/Org issue: messing up properties
Hi!
I do face strange behavior when using yasnippet with Org-mode:
,[ Snippet «test» ]
| # name : Testing yasnippet/org issue
| # --
|
| ** Test ${1:test}
| :PROPERTIES:
| :ID: $1
| :END:
`
... results in ...
,[ test.txt with entering «foo bar» as $1 ]
| ** Test foo bar
| :PROPERTIES:
| :ID: foo bar
| :END:
`
... which is correct, when Org is not the major mode. However, when
executed with Org-mode as major mode, it results in:
,[ test.org ]
| ** Test foo bar
| :PROPERTIES:
| foo bar
| :END:
`
Therefore I guess that this is an Org-mode issue. Is somebody able
to help debug/fix this issue?
A slightly different example:
,[ snippet ]
| ** Test ${1:test}
| :PROPERTIES:
| :ID: $1-myid
| :END:
`
,[ test.org ]
| ** Test foo bar
| :PROPERTIES:
| foo bar:ID: test-myid
| :END:
`
- so the default text «test» does not get replaced by the «foo bar»
I enter as $1 and this time, the :ID: does not get removed.
Placing $1 outside of the PROPERTIES drawer, there does not seem to
be any problem.
My setup:
Org-mode version 7.9.3c (release_7.9.3c-816-g409ee8)
yasnippet (version 0.6.1b)
--
Karl Voit
[O] Agenda items with date ranges
I remember that previously in Agenda view, entries such as: , | * A few days | 2013-02-07 Thu--2013-02-14 Thu ` would appear with a (1/8), (2/8), etc. preceding the entry. I added a similar entry today in org-mode version 7.9.2, and it appeared in the agenda without the (1/8), etc. I have searched here, asked on IRC and looked for a variable to control this feature, but have not been successful. Any help would be appreciated. Thanks.
Re: [O] Org mode build failure
Hi Achim, On Thu, Feb 07, 2013 at 11:15:14AM +, Achim Gratz wrote: Suvayu Ali fatkasuvayu+linux at gmail.com writes: I am encountering the following build failure when I do `make compile': make[1]: Entering directory `/path/build/org-mode/lisp' rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc install -m 644 -p . install: missing destination file operand after ‘.’ Try 'install --help' for more information. make[1]: *** [addcontrib] Error 1 make[1]: Leaving directory `/path/build/org-mode/lisp' make: *** [compile] Error 2 Any ideas what changed? The new exporter moved into core and the files you specified in ORG_ADD_CONTRIB are no longer existing there. Remove that definition and all is well. Thanks a lot, this works. I don't know how I missed that! -- Suvayu Open source is the future. It sets us free.
Re: [O] New exporter, beamer confusion
Should there be a check in the exporter, for latex based backends, if the document class expected is not defined? This would have made things a lot quicker to resolve in this case! What is an expected document class? Beamer export can happen with a beamer or an article (and probably others) document class. There's no real way to know if the class used is correct. Regards, -- Nicolas Goaziou
Re: [O] bug in ascii export
Hello, Samuel Wales samolog...@gmail.com writes: exporting this subtree results in this bt. Old export framework doesn't work anymore in master. Related files are kept for now in contrib/ for archiving purpose. Regards, -- Nicolas Goaziou
Re: [O] Worg publishing issue
Hello, Bastien b...@altern.org writes: 2 problems, a trivial one and a let's-prepare-for-headache one: 1. `org-publish-org-to-html' does not exist in the new export/publish libraries -- Nicolas, would that be enough to have aliases here (from org-publish-org-to-html to org-html-publish-to-html)? I guess many people rely on thse org-publish-org-to* functions. Publishing functions have been moved into their respective back-end. That way, ox-publish.el doesn't have to know about every back-end defined. It's not very clean, but you can probably define aliases in ox-publish.el, since real publishing functions should be autoloaded anyway. If you do so, I suggest to, at least, provide a deprecation notice. Regards, -- Nicolas Goaziou
Re: [O] org export Taskjuggler
Hello, Christian Egli christian.e...@sbs.ch writes: Nicolas Goaziou n.goaz...@gmail.com writes: If nothing has been started once the new export framework is installed and the early bugs are fixed, I will do the port. I don't quite understand why we need to port anything. The taskjuggler exporter is different than the other exporters in that it doesn't really export the content of an org file. Instead it just goes through the headlines (using the mapping API), takes some to be tasks and reads the properties of these headlines to build the taskjuggler file. It pretty much ignores any text that is between the headlines (see also the commentary in org-taskjuggler.el). In essence it treats the org file as a tree of nodes with properties that define the tasks, resources and reports. What it really exports isn't important. ox.el is a framework to export any part of an Org buffer (including non-contiguous parts like headlines only) to another format that can be, at least during an intermediary step, written as a string. In a export back-end, you basically specify an export action for each type of syntax. If nothing is provided, that the syntax will be ignored. In this case, the taskjuggler back-end would only provide a function for headlines. It doesn't use any of the common (old) exporting infrastructure. To be honest, I only gave it a cursory look, but it requires org-exp and uses a few functions from from it, like, e.g. `org-default-export-plist', `org-infile-export-plist', `org-install-letbind'. Some work needs to be done at this level. So woudn't a ported org-taskjuggler.el look exactly like to one that we have today? Externally, it would, hopefully. Internally, some changes are required. I also think it would much benefit from it, but I'm biased, obviously. Regards, -- Nicolas Goaziou
Re: [O] accessibility bug: export menu unusable
Hello, Samuel Wales samolog...@gmail.com writes: The new export window is unusable. It shows the second half of the menu. Out of curiosity, how did you make the previous export window usable under these conditions? It was 28-line high with no scrolling mechanism either. If you can't reproduce, please try on a frame with 20 lines and 67 columns. If that does not reproduce, then increase font size to make it so that a *full screen* frame is 20 lines total and 67 columns total. Adding scrollability would make it work. Indeed. Jambunathan has made some progress on this functionality. I don't know in what state his patch is. Until then, you may want to set `org-export-dispatch-use-expert-ui' to a non-nil value, assuming you know which kind of export you want. You can also remove back-ends you don't need from `org-export-backends', or hide them from the menu with `org-export-invisible-backends'. Regards, -- Nicolas Goaziou
Re: [O] new exporter - LaTeX export setting org-export-latex-packages-alist and BUG empty source block export
Hello, Rainer M Krug r.m.k...@gmail.com writes: Hi I had the following in my emacs.org: #+begin_src emacs-lisp (require 'org-latex) (setq org-export-latex-listings t) (add-to-list 'org-export-latex-packages-alist '( listings)) (add-to-list 'org-export-latex-packages-alist '( color)) #+end_src After upgrade of org this morning using git, the new exporter is there and I get the following error message: (void-variable org-export-latex-packages-alist) It should be `org-latex-packages-alist', `org-latex-listings'. You also don't need (and shouldn't) require 'org-latex. Please see: http://permalink.gmane.org/gmane.emacs.orgmode/65574 In addition, there seems to be a BUG: when exporting an empty source block to LaTeX, I get the following error message: org-babel-exp processing... [69 times] apply: Wrong number of arguments: max, 0 I can easily replicate this with a document only containing: * org-mode #+begin_src emacs-lisp #+end_src which exports fine to html, but not LaTeX. Indeed. It should be fixed now. Thank you for reporting it. Regards, -- Nicolas Goaziou
Re: [O] Has anybody noticed ellipses instead of the top line of the window?
On Thu, 07 Feb 2013 11:11:21 +0100, Bastien spake thus: I can reproduce such an ellipsis by : - Cutting part of the buffer containing an ellipsis - Undoing the cut On the attached example, all being visible, fold the first second level headline, kill its line (C-k with cursor at the beginning of line), and undo the kill. The buffer then looks like I think you forgot to attach the example, and I was not able to reproduce the problem by following the directions... My bad… here: MRE.org Description: Binary data -- William
Re: [O] new exporter - LaTeX export setting org-export-latex-packages-alist and BUG empty source block export
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/13 14:37, Nicolas Goaziou wrote: Hello, Rainer M Krug r.m.k...@gmail.com writes: Hi I had the following in my emacs.org: #+begin_src emacs-lisp (require 'org-latex) (setq org-export-latex-listings t) (add-to-list 'org-export-latex-packages-alist '( listings)) (add-to-list 'org-export-latex-packages-alist '( color)) #+end_src After upgrade of org this morning using git, the new exporter is there and I get the following error message: (void-variable org-export-latex-packages-alist) It should be `org-latex-packages-alist', `org-latex-listings'. You also don't need (and shouldn't) require 'org-latex. Please see: http://permalink.gmane.org/gmane.emacs.orgmode/65574 Ups - must hae overread that, as I have seen the anouncement... Sorry In addition, there seems to be a BUG: when exporting an empty source block to LaTeX, I get the following error message: org-babel-exp processing... [69 times] apply: Wrong number of arguments: max, 0 I can easily replicate this with a document only containing: * org-mode #+begin_src emacs-lisp #+end_src which exports fine to html, but not LaTeX. Indeed. It should be fixed now. Thank you for reporting it. Thanks - working now. One observation though: I updated and compiled org while emacs was running, then reloaded it and tried the export of the empty souce block, and the error was still there although emacs told me that I had successfully loaded the new version. I restarted emacs, and the export worked. Cheers, Rainer Regards, - -- 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 Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRE7PHAAoJENvXNx4PUvmCUhoH/RaZw/+g6NSCAnj0x5FCOETT hpo3bgom203xcmuTxxRMutuj4C7OwOU44P9zvr4KlJ6F4w3HNfYB+OX36P6MtNVO dk0//X5x5xrBrxI1UDZAOjGv52Y7kUZCw6nuuwuRhUvIUaJan9tbOHnKXp/cJS3K YP4EgrQvJ8gGIj2tnK+o9HyVc5pfW3A++GfCFhImUUJ2xT3YIMXoRcziiMhQBDOn dM6rGegjHXlvVqGiJ0WVuYmtbaZPF6LDxaK3l5j9R4eJLU/pJnJte5uafT7bUJ83 m3lMI+WCU/x78Y8VwxSXBqTt5IWvm/wGvC/rfhr16b9z25lZGxQN5CrixMM6luc= =NXrO -END PGP SIGNATURE-
[O] old to new converter transition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Some remarks and questions about transition to new exporter: 1) org-export-latex-listings -becomes- org-latex-listings 2) I have org-export-kill-product-buffer-when-displayed but can't find org-kill-product-buffer-when-displayed - is it still needed? I have the impression not? Is this true? Thanks, 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 Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRE7mCAAoJENvXNx4PUvmCDBUIAO5nwFSmabC6JGtfWs2u2Mnw qU4ihcta9jfdlhl+UE0GmVMTfZv3wJDmnpLWlDcL1MAi8IyKaQjpgUArIahNvpMD cZWvLCeCHxzPJlqhlPyWdx3cuz2MGVZTn6vrbR5TC9BfBLoGjAYE+sFbJjiuUjIE UWFK47t5Ov1XCuCcvA0hHMK6lTFJuiZ+XhZnqJ134Cfvl+ga8feWFlghxqx8UuzQ WrDO2zQZZGGfUVhGp2Ba0kQjfkPM6Jt0zt6Du3HeRpcWLY6OjWevf1HkT0IzB7zx zlNgLony2Mz6wTt4Zif3lkprXK6+qL6OjxoRhN0o8TDYu/jokOzyGn5BGO90O8g= =79KA -END PGP SIGNATURE-
Re: [O] new exporter - LaTeX export setting org-export-latex-packages-alist and BUG empty source block export
Rainer M Krug r.m.k...@gmail.com writes: One observation though: I updated and compiled org while emacs was running, then reloaded it and tried the export of the empty souce block, and the error was still there although emacs told me that I had successfully loaded the new version. I restarted emacs, and the export worked. I have updated `org-reload'. It should also reload back-ends. Thank you. Regards, -- Nicolas Goaziou
Re: [O] old to new converter transition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/13 15:29, Nicolas Goaziou wrote: Hello, Rainer M Krug r.m.k...@gmail.com writes: Some remarks and questions about transition to new exporter: 1) org-export-latex-listings -becomes- org-latex-listings Correct. 2) I have org-export-kill-product-buffer-when-displayed but can't find org-kill-product-buffer-when-displayed - is it still needed? I have the impression not? Is this true? Not needed anymore. At its core, the new export engine produces a string whereas the other one filled a buffer. So there's no buffer to kill once the export is over. Thanks a lot, and so far I really like the new exporter (much cleaner to use), Rainer Regards, - -- 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 Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRE7q4AAoJENvXNx4PUvmCB64IAK2KCV+WjXxXEKwnfRnmEvIl D/r2D+WHvyYzpj6lwok7SvhZC8UtOMjTcnCAoBvAujadM9VaGfG/3OzHUobR5Htm lF4Jm6arYsN1g/cVwiAPOsTPtYGOk4V/udt2rqaAkiUxBJA7bgZu4mDADh5d14EK I55lQ0GUi8Iq2mgsUyEDZK0f589wO0c55cNitZCkqrBGnnme3fXL6EoUcIttOUy9 AtZjpQ+jmWEsSHLZmSb24XRK3/mFDUh8BBqC9qvtsw28aUt4bCLEhcVMZtM5K4qQ H/MicOJKfjKcqLqNpqei761dL3xJzezpt0hTHAaSrK3yKFVDTzEP4Aoo1Dk447M= =vd2E -END PGP SIGNATURE-
[O] edit-src on read-only files
hi. i use RCS on my .org files. it's happened to me more than once (1 == shame on me) that i've entered C-c ' on a read-only .org file, spent some time editing the source code fragment, then done C-c ', only to lose my edits, as the original buffer was read-only. it seems like org-mode should prevent that. but, in the meantime, i've put the following in my .emacs, which seems to prevent this. note that this *also* prevents C-c ' in cases where it isn't harmful: looking at included files, following links, etc. (i.e., functions that don't -- as far as i know -- modify the file whence they were invoked.) i tried putting the advice around the main culprits (org-table-edit-formulas, org-edit-src-code, and org-edit-fixed-width-region), but 1) i don't know how to loop in elisp 'special' mode (so i didn't have to repeat the same lines three times); 2) for some reason (wasn't loaded?), org-table-edit-formulas wasn't taking the advice; 3) i don't use those other functions. anyway, fwiw, here's this: ;; in org-mode, make sure we don't edit-special a read-only file... (defadvice org-edit-special (around make-sure-writable) make sure the source buffer is writable before allowing src-edit (if buffer-read-only (display-warning :error attempting to src-edit a read-only file...) ad-do-it)) (ad-activate 'org-edit-special)
Re: [O] New exporter, beamer confusion
Hi,
LaTeX class is never unspecified because `beamer' back-end is
a derivative of `latex', and, as such, `org-latex-default-class' will be
used. `beamer' could specify its own default class, but that class would
still need to be defined in `org-latex-classes'.
Sure, it should be in the default list. What is the drawback?
'(beamer
\\documentclass[presentation]{beamer}
\[DEFAULT-PACKAGES]
\[PACKAGES]
\[EXTRA]
(\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s}))
Looks reasonable.
Plain latex export is more problematic because several options are
reasonable, but I can't see beamer export with an article class ...
But it exists, and is documented in the Beamer User Guide. See section
21.2. Creating Handouts Using the Article Mode.
Yes, I know that, but the thing is, from a given org-file, I would expect
beamer export to make the slides and 'plain' latex export to create the
handout. Maybe it is difficult to achieve but it feels like the most useable
setup. Is it at all doable?
/v
Re: [O] New exporter, beamer confusion
Vincent Beffara vbeffara...@gmail.com writes: Sure, it should be in the default list. What is the drawback? The default list is defined in ox-latex.el, which doesn't know anything about ox-beamer.el. The drawback is that it doesn't seem clean to me. I think it's better to make it a fallback value hardcoded (or in a defconst) in ox-beamer.el instead. Yes, I know that, but the thing is, from a given org-file, I would expect beamer export to make the slides and 'plain' latex export to create the handout. Maybe it is difficult to achieve but it feels like the most useable setup. Is it at all doable? If the author is cautious about keywords used (i.e. #+BEAMER: or #+LATEX:), it should be possible to export the same document with either `beamer' or `latex' back-end. Though, I don't know how much difference there would be between the output from `latex' and a Beamer handout produced with article class. Regards, -- Nicolas Goaziou
Re: [O] org-agenda-show-log, org-timeline bugs
Can someone please verify these bugs? Thanks. Derek Derek Upham writes: I tried running org-timeline on an Org file with lots of timestamped TODO - DONE state changes, and didn't see the matches I was expecting. While poking around, I found two problems. 1. `org-timeline' isn't setting the text properties necessary to refresh the timeline buffer. This means that none of the special keys to update the display actually work. Here's the `org-timeline' version: (add-text-properties (point-min) (point-max) '(org-agenda-type timeline)) Here's the same chunk in `org-agenda-list' for comparison: (add-text-properties (point-min) (point-max) `(org-agenda-type agenda org-last-args (,arg ,start-day ,span) org-redo-cmd ,org-agenda-redo-command org-series-cmd ,org-cmd)) 2. Even when the `org-timeline' function has refresh set up properly, `org-agenda-log-mode' (via the `l' hotkey) doesn't work. It looks like the function changes the buffer-local copy of the `org-agenda-show-log' variable, but the refresh code looks at the global version of the variable (possibly because the refresh is happening through eval?). In order to see the log entries, you need to set `org-agenda-show-log' outside of the timeline buffer (using `setq'). Can someone take a look at these? This is all with the latest sources from the repo. Thanks. Derek
Re: [O] Still Wishing for Snooze
On Fri, Jan 25, 2013 at 12:10 PM, Michael Brand michael.ch.br...@gmail.com wrote: Let me only suggest an idea to deal with this, item-based: When the DEADLINE “warning period” would be generalized to allow positive numbers then it would extend to a “warning and delay period”. Starting with: * TODO [#B] Verify login to the virtual machines DEADLINE: 2013-01-22 Tue +1w -0d It could be delayed to 2013-01-24 Thu which means two days later by changing the “warning and delay period” to 2d: * TODO [#B] Verify login to the virtual machines DEADLINE: 2013-01-22 Tue +1w 2d This would not show up in the agenda until 2013-01-24 Thu. At that date it would be shown with the desirable “In -2 d.:” for overdue to get the higher priority. When set to done it would become: * TODO [#B] Verify login to the virtual machines DEADLINE: 2013-01-29 Tue +1w -0d Note the change from 2d to -0d: It is important that when the date repeats and has a positive warning period aka delay period then it must be reset to -0d. Otherwise undesirable surprises are guaranteed. Resetting to just -0d would only be enough for this example, not for the common case where we don’t know which DEADLINE warning period was in use before the DEADLINE has been delayed. Thus it looks like a DEADLINE delay would have to be _additional_ to the DEADLINE warning period. Some applications would require that the DEADLINE delay would affect only the warning date but not the due date of the DEADLINE. Other applications would require both to be delayed. Maybe even others only the due date. It simply means that this suggestion is still incomplete. I don’t expect it to be refined. Michael
Re: [O] Still Wishing for Snooze
Hi Bastien On Thu, Feb 7, 2013 at 10:44 AM, Bastien b...@altern.org wrote: You can now use a delay cookie like this: SCHEDULED: 2013-02-07 jeu. -2d The item will not be shown today, but in three days. For this case I would use: SCHEDULED: 2013-02-09 Sat It seems I don’t get the point because when a TODO with repeater SCHEDULED: 2013-02-01 Fri +1w -3d is set to DONE the delay remains and this way also here I would not use a delay but: SCHEDULED: 2013-02-04 Mon +1w The usefulness of a SCHEDULED delay I see together with a TODO and repeater to implement an _exception_ (to simplify: exception just for the first date, before the repetitions). For example SCHEDULED: 2013-02-01 Fri +1w -3d would mean: Usually start working on the entry earliest on the first day of the month except [2013-02-01 Fri] when work can not start before [2013-02-04 Mon]. It would start to show in the agenda on [2013-02-04 Mon], [2013-03-01 Fri], [2013-04-01 Mon], [2013-05-01 Wed], [2013-06-01 Sat] etc. On let’s say [2013-02-05 Tue] it would be set to DONE and would change to: SCHEDULED: 2013-03-01 Fri +1w Note the automatically removed delay. Am I missing something? Michael
Re: [O] [New exporter] Error: (wrong-type-argument stringp nil)
Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: Trying to convert some more files (to HTML) with the new exporter, I did a test with the following one: Fixed, thanks. -- Bastien
Re: [O] Problem with org-html-format-latex
Hi again, A bug occurs with org-html-format-latex (in ox-html.el) when called from a non-file buffer. In the context of o-blog, it gets called as (org-html-format-latex $x$ 'mathjax) but still tries to bind some ltxpng related support. This ends up calling file-name-sans-extension to the output of (file-name-nondirectory (buffer-file-name)) which is nil ... Cleaner patch uses ignore-errors, that's simpler... /v 0001-Fix-the-non-file-buffer-bug.patch Description: Binary data
Re: [O] [PATCH] Stop with an error if the LaTeX class is not known to the new exporter
Hello, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: I've lost (a bit of) time looking at why my documents were wrong with the new exporter. The fact is I've customized: (setq org-e-latex-default-class myarticle) but hadn't added yet that private class to the list `org-e-latex-classes'. The result: a PDF, but completely undreadable, as it's missing the `documentclass' directive. Here a patch to throw an error to the user, signaling he's forgotten some pieces of the puzzle, in case he played with such vars. Better stop early, and giving hints to the user how to correct the problem, no? Feel free to adapt it to your wishes. Thank you. I have applied it on the soon to be merged back-end. Regards, -- Nicolas Goaziou
Re: [O] python :session issues
Am 06.02.2013 16:17, schrieb John Kitchin: Thanks for the -Q reminder. I get the same output if I run with emacs -Q (although I do have to add :results output to each block. I had that set as a default in my init files). I had the problem described in the footnote you listed, and that is why I am using python-mode 5.2, which doesn't have that issue. John Should be fixed in current trunk. bzr branch lp:python-mode Andreas
[O] [New exporter] Key bindings and typographical error
Hello Nicolas, First of all, let me thank for your the work you've done with the exporters. I don't have yet a full 100%-compliant config, but I'm clearly on that road. And this is really great to get a very nice dispatcher, with bugless exports. While using the new dispatcher, I'd like to propose some adaptations -- before it's too late (before everybody gets accustomed to your new bindings). Here are the changes I would personally make: --8---cut here---start-8--- [h] Export to HTML [H] To temporary buffer- [b] As HTML buffer [h] To file- As HTML file [o] To file and open - As HTML file and open [l] Export to LaTeX [L] As TEX buffer - [b] As LaTeX buffer [l] As TEX file- [l] As LaTeX file [p] As PDF fileOK [o] As PDF file and open OK [B] As TEX buffer (Beamer) - [B] As LaTeX buffer (Beamer) [b] As TEX file (Beamer) - [L] As LaTeX file (Beamer) [P] As PDF file (Beamer) OK [O] As PDF file and open (Beamer) OK --8---cut here---end---8--- In summary: - Use As ... buffer/file writing - Use key `b' for buffer result (for both HTML and LaTeX exports) - Use LaTeX (or TeX) instead of TEX - Use only *small* letters for plain LaTeX export - Use only *capital* letters for Beamer LaTeX export - Use equivalent capital letters for plain - Beamer Best regards, Seb -- Sebastien Vauban
Re: [O] New exporter, beamer confusion
Nicolas Goaziou n.goaz...@gmail.com writes: If the author is cautious about keywords used (i.e. #+BEAMER: or #+LATEX:), it should be possible to export the same document with either `beamer' or `latex' back-end. Though, I don't know how much difference there would be between the output from `latex' and a Beamer handout produced with article class. There is an auxiliary package called beamerarticle. It's neat. It's described in 21.2.1 in the beamer guide v.3.26. And there's an example in the file conference-ornate-20min.en.tex which is shipped with beamer. Cool with the #+BEAMER. I didn't know about this, but it's super nice. The other day I was lookking for a replacement to #+BEAMER_HEADER (I think that was what it was called), which existed with the 'old' exporter. Does this variable exist in Beamer yet? Thanks a lot for your work Nicolas. It's super cool! –Rasmus -- In theory, practice and theory are the same. In practice they are not
[O] Agenda doesn't find agenda-files after update
Hi, I updated Org-mode yesterday (pull from git repo, make and make autoloads): , | Org-mode version 7.9.3e (7.9.3e-897-g787a07 @ /home/tj/gitclone/org-mode/lisp/) ` and now the agenda apparently doesn't find my agenda-files anymore, i.e. the agenda is produced without errors, but is empty, although , | org-agenda-files is a variable defined in `org.el'. | Its value is (~/git/org) | Original value was nil ` just like before. Anybody else experiencing this? PS , | GNU Emacs 24.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4) | of 2013-01-20 on eric ` -- cheers, Thorsten
Re: [O] Agenda doesn't find agenda-files after update
Thorsten Jolitz tjol...@gmail.com writes: After restarting Emacs it worked again - sorry for the noise. I updated Org-mode yesterday (pull from git repo, make and make autoloads): , | Org-mode version 7.9.3e (7.9.3e-897-g787a07 @ /home/tj/gitclone/org-mode/lisp/) ` and now the agenda apparently doesn't find my agenda-files anymore, i.e. -- cheers, Thorsten
Re: [O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1
Updated to 25a481d8, still getting the same error and backtrace when generating agendas where the memq block evaluates non-nil. :/ On Thu, Feb 7, 2013 at 1:33 AM, Bastien b...@altern.org wrote: Hi Kyle, Kyle Machulis k...@nonpolynomial.com writes: As of commit 8517be79b5c1fe165d23ea65ad70a282e9c595bb (bisected to find this), agenda compilation died with the following backtrace for me: Debugger entered--Lisp error: (error Bad timestamp `' Error was: (Not a standard Org-mode time string: )) signal(error (Bad timestamp `'\nError was: (Not a standard Org-mode time string: ))) error(Bad timestamp `%s'%s\nError was: %s (Not a standard Org-mode time string: )) byte-code(...) org-time-string-to-absolute() byte-code(...) org-agenda-get-timestamps(nil) org-agenda-get-day-entries(~/emacs_org/mozilla/mozilla.org (2 6 2013) :deadline :scheduled :timestamp :sexp) apply(org-agenda-get-day-entries ~/emacs_org/mozilla/mozilla.org (2 6 2013) (:deadline :scheduled :timestamp :sexp)) byte-code(...) byte-code(...) org-agenda-list(nil) call-interactively(org-agenda-list) byte-code(...) org-agenda(nil) call-interactively(org-agenda nil nil) It's dying when it hits a headline as follows: * Meeting 13:30 , %%(memq (calendar-day-of-week date) '(3)) I'm guessing this has something to do with the agenda sorting updates in the commit not liking the fact that the sexp evaluates to true. If the sexp evaluates nil for the day the agenda is trying to parse, nothing happens. If it evaluates to something other than nil (t if I use (= 3 (calendar-day-of-week date)), 3 if I use memq on a wednesday, etc...), I get the above error. Thanks for reporting this. Yes, diary sexp are special and can't really be handled here. I fixed this in master, please confirm this is okay. -- Bastien
Re: [O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1
Kyle Machulis k...@nonpolynomial.com writes: Updated to 25a481d8, still getting the same error and backtrace when generating agendas where the memq block evaluates non-nil. :/ Please pull again, it should be fixed now. Thanks! -- Bastien
Re: [O] Agenda items with date ranges
SabreWolfy sabrewo...@gmail.com writes: I remember that previously in Agenda view, entries such as: , | * A few days | 2013-02-07 Thu--2013-02-14 Thu ` would appear with a (1/8), (2/8), etc. preceding the entry. I added a similar entry today in org-mode version 7.9.2, and it appeared in the agenda without the (1/8), etc. I have searched here, asked on IRC and looked for a variable to control this feature, but have not been successful. Any help would be appreciated. Thanks. I can't reproduce this problem. Can you reproduce it with latest Org? Thanks, -- Bastien
[O] Structure editing
Hi, Is it possible to have a line between two tress which should not hide when folded, like the following example ? Unfolded state: === * Heading 1 ** Heading 1-1 ** Heading 1-2 AT THIS POINT, A LINE WHICH SHOULD NOT BE FOLDED * Heading 2 ** Heading 2-1 ** Heading 2-2 Folded state = * Heading 1 AT THIS POINT, A LINE WHICH SHOULD NOT BE FOLDED * Heading 2 Thanks. - *Sanjib Sikder *Ph.D. Fellow Chemical Engineering IIT Bombay* *
Re: [O] subscribing to this mailing list with gnus
How do I subscribe? I haven't been able to find a working address. Thanks. 2013/2/7 Bastien b...@altern.org Hi John, 42 147 aeus...@gmail.com writes: I don't know the correct port / address within the context of this code: (setq gnus-select-method '(nntp gmane.emacs.orgmode (nntp-port-number 119))) Please ask this to the Gnus mailing list. Thanks, -- Bastien
Re: [O] Structure editing
On Fri, Feb 08, 2013 at 01:27:05AM +0530, Sanjib Sikder wrote: Is it possible to have a line between two tress which should not hide when folded, like the following example ? No this is not possible. Any text following a headline is by definition a part of the tree and will be folded with it. Maybe if you tell us what you are trying to achieve, we can suggest an alternative? -- Suvayu Open source is the future. It sets us free.
Re: [O] sexp timestamp causing agenda compilation issues as of 8517be79b5c1
All fixed, thanks! On Thu, Feb 7, 2013 at 10:41 AM, Bastien b...@altern.org wrote: Kyle Machulis k...@nonpolynomial.com writes: Updated to 25a481d8, still getting the same error and backtrace when generating agendas where the memq block evaluates non-nil. :/ Please pull again, it should be fixed now. Thanks! -- Bastien
Re: [O] subscribing to this mailing list with gnus
42 147 aeus...@gmail.com writes: How do I subscribe? I haven't been able to find a working address. http://www.gnus.org/resources.html To subscribe, send a message to ding-requ...@gnus.org to subscribe. http://dir.gmane.org/gmane.emacs.gnus.general There is also a user mailing list: https://lists.gnu.org/mailman/listinfo/info-gnus-english http://dir.gmane.org/gmane.emacs.gnus.user HTH, -- Bastien
Re: [O] python :session issues
Hi Andreas, Andreas Röhler writes: Am 06.02.2013 16:17, schrieb John Kitchin: Thanks for the -Q reminder. I get the same output if I run with emacs -Q (although I do have to add :results output to each block. I had that set as a default in my init files). I had the problem described in the footnote you listed, and that is why I am using python-mode 5.2, which doesn't have that issue. John Should be fixed in current trunk. bzr branch lp:python-mode Thanks for looking at this Andreas, I have tried the bzr trunk and still have problems. John, I hope I am not hijacking your thread but I am not sure what problem is meant to be have been fixed above so I am just jumping in and assuming that we would both like to fix the same thing. Using org-mode from git, commit b810431 from Jan 22. If I start emacs like this: $ emacs -Q testPy.org -l init.el then executing the src blocks in order, *restarting Emacs between attempts*, shows the problems. -/ init.el /-- ;; use the git trunk for org mode (add-to-list 'load-path ~/.emacs.d/plugins/org-mode/lisp) (add-to-list 'load-path ~/.emacs.d/plugins/org-mode/contrib/lisp t) (require 'org) ;; use the bzr trunk for python-mode (setq py-install-directory /home/myles/.emacs.d/plugins/python-mode) (add-to-list 'load-path py-install-directory) (require 'python-mode) (org-babel-do-load-languages 'org-babel-load-languages '((python . t))) ---/ end init.el /--- -/ testPy.org /-- * First attempt :doesnotwork: #+begin_src python :results output :session a import sys #+end_src Message: inferior-python-mode: Wrong type argument: keymapp, py-down-exception * Second attempt: set org-babel-python-mode first :doesnotwork: #+begin_src elisp (setq org-babel-python-mode 'python-mode) (setq org-babel-python-command python2 py-python-command python2) #+end_src I would expect this to open a Python 2 session, however it opens a Python 3 session: #+begin_src python :results output :session a import sys print(sys.path) #+end_src * Third attempt: try python3 :works: #+begin_src elisp (setq org-babel-python-mode 'python-mode) (setq org-babel-python-command python3 py-python-command python3) #+end_src #+begin_src python :results output :session a import sys print(sys.path) #+end_src Works ok. ---/ end testPy.org /--- Perhaps I am not using it correctly? Thanks, Myles
Re: [O] New exporter, beamer confusion
Hello, Rasmus ras...@gmx.us writes: Nicolas Goaziou n.goaz...@gmail.com writes: If the author is cautious about keywords used (i.e. #+BEAMER: or #+LATEX:), it should be possible to export the same document with either `beamer' or `latex' back-end. Though, I don't know how much difference there would be between the output from `latex' and a Beamer handout produced with article class. There is an auxiliary package called beamerarticle. It's neat. It's described in 21.2.1 in the beamer guide v.3.26. And there's an example in the file conference-ornate-20min.en.tex which is shipped with beamer. Cool with the #+BEAMER. I didn't know about this, but it's super nice. The other day I was lookking for a replacement to #+BEAMER_HEADER (I think that was what it was called), which existed with the 'old' exporter. Does this variable exist in Beamer yet? There is the #+LATEX_HEADER:. Is a keyword specific to Beamer required? It would by symmetric with #+BEAMER: but I have never needed it before. Regards, -- Nicolas Goaziou
[O] [agenda] Lisp error: (args-out-of-range 0 0)
Hello, With a recent pull (of today, 15:45), I now have the following error when generating the agenda views: --8---cut here---start-8--- Debugger entered--Lisp error: (args-out-of-range 0 0) get-text-property(0 extra-space nil) (concat effort (get-text-property 0 (quote extra-space) effort)) (if (equal effort ) (concat effort (get-text-property 0 (quote extra-space) effort))) (format %7s (if (equal effort ) (concat effort (get-text-property 0 (quote extra-space) effort (format %s%s %s%s%s (format %-11s (if (equal extra ) (concat extra (get-text-property 0 (quote extra-space) extra (format %s (if (equal category-icon ) (concat category-icon (get-text-property 0 (quote extra-space) category-icon (format %-12s (if (equal category ) (concat category : (get-text-property 0 (quote extra-space) category (if (equal time) (format %-12s (if (equal time) (concat time (format %7s (if (equal effort ) (concat effort (get-text-property 0 (quote extra-space) effort) eval((format %s%s %s%s%s (format %-11s (if (equal extra ) (concat extra (get-text-property 0 (quote extra-space) extra (format %s (if (equal category-icon ) (concat category-icon (get-text-property 0 (quote extra-space) category-icon (format %-12s (if (equal category ) (concat category : (get-text-property 0 (quote extra-space) category (if (equal time) (format %-12s (if (equal time) (concat time (format %7s (if (equal effort ) (concat effort (get-text-property 0 (quote extra-space) effort)) (concat (eval formatter) txt) (setq rtn (concat (eval formatter) txt)) (let* ((category (or category (if (stringp org-category) org-category (and org-category (symbol-name org-category))) (if buffer-file-name (file-name-sans-extension (file-name-nondirectory buffer-file-name)) ))) (category-icon (org-agenda-get-category-icon category)) (category-icon (if category-icon (propertize (quote display) category-icon) )) (tag (if tags (nth (1- (length tags)) tags) )) time effort neffort (ts (if dotime (concat (if (stringp dotime) dotime ) (and org-agenda-search-headline-for-time txt (time-of-day (and dotime (org-get-time-of-day ts))) stamp plain s0 s1 s2 rtn srp l duration thecategory) (and (derived-mode-p (quote org-mode)) buffer-file-name (add-to-list (quote org-agenda-contributing-files) buffer-file-name)) (if (and dotime time-of-day) (progn (if (or (setq stamp (string-match org-stamp-time-of-day-regexp ts)) (setq plain (string-match org-plain-time-of-day-regexp ts))) (progn (setq s0 (match-string 0 ts) srp (and stamp (match-end 3)) s1 (match-string (if plain 1 2) ts) s2 (match-string (if plain 8 ...) ts)) (if (and org-prefix-has-time org-agenda-remove-times-when-in-prefix (or stamp plain) (string-match ... txt) (not ...) (if ... ... t)) (setq txt (replace-match nil nil txt) (if s1 (setq s1 (org-get-time-of-day s1 (quote string) t))) (if s2 (setq s2 (org-get-time-of-day s2 (quote string) t))) (let (org-time-clocksum-use-effort-durations) (if (and s1 (not s2) org-agenda-default-appointment-duration) (progn (setq s2 (org-minutes-to-clocksum-string ...) (if s2 (progn (setq duration (- (org-hh:mm-string-to-minutes s2) (org-hh:mm-string-to-minutes s1))) (if (string-match \\([ ]+\\)\\(:[[:alnum:]_@#%:]+:\\)[ ]*$ txt) (progn (if (or (eq org-agenda-remove-tags t) (and org-agenda-remove-tags org-prefix-has-tag)) (setq txt (replace-match t t txt)) (setq txt (replace-match (concat (make-string ... 32) (match-string 2 txt)) t t txt) (if (derived-mode-p (quote org-mode)) (progn (setq effort (condition-case nil (progn (get-text-property 0 (quote org-effort) txt)) (error nil))) (if effort (setq neffort (org-duration-string-to-minutes effort) effort (setq effort (concat [ effort ]))) (setq effort (if remove-re (progn (while (string-match remove-re txt) (setq txt (replace-match t t txt) (add-text-properties 0 (length txt) (quote (org-heading t)) txt) (setq time (cond (s2 (concat (org-agenda-time-of-day-to-ampm-maybe s1) - (org-agenda-time-of-day-to-ampm-maybe s2) (if org-agenda-timegrid-use-ampm ))) (s1 (concat (org-agenda-time-of-day-to-ampm-maybe s1) (if org-agenda-timegrid-use-ampm ..))) (t )) extra (or (and (not habitp) extra) ) category (if (symbolp category) (symbol-name category) category) thecategory (copy-sequence category) level (or level )) (if (string-match org-bracket-link-regexp category) (progn (setq l (if (match-end 3) (- (match-end 3) (match-beginning 3)) (- (match-end 1) (match-beginning 1 (if ( l (or org-prefix-category-length 0)) (progn (setq category (copy-sequence category)) (org-add-props category nil (quote extra-space) (make-string (- org-prefix-category-length l 1) 32) (if (and org-prefix-category-max-length (= (length category) org-prefix-category-max-length)) (setq category (substring category 0 (1-
Re: [O] [agenda] Lisp error: (args-out-of-range 0 0)
Hello, Sebastien Vauban wrote: With a recent pull (of today, 15:45), I now have the following error when generating the agenda views: Debugger entered--Lisp error: (args-out-of-range 0 0) get-text-property(0 extra-space nil) (concat effort (get-text-property 0 (quote extra-space) effort)) (if (equal effort ) (concat effort (get-text-property 0 (quote extra-space) effort))) (format %7s (if (equal effort ) (concat effort (get-text-property 0 (quote extra-space) effort (format %s%s %s%s%s (format %-11s (if (equal extra ) (concat extra (get-text-property 0 (quote extra-space) extra (format %s (if (equal category-icon ) (concat category-icon (get-text-property 0 (quote extra-space) category-icon (format %-12s (if (equal category ) (concat category : (get-text-property 0 (quote extra-space) category (if (equal time) (format %-12s (if (equal time) (concat time (format %7s (if (equal effort ) (concat effort (get-text-property 0 (quote extra-space) effort) [...] As I see a format %7s and the `effort' property, this could help reproducing the problem: (setq org-agenda-prefix-format '((agenda . %-11s%i %-12:c%?-12t%7e ))) BTW, I've got a question: I'd like to add different faces with the agenda line, for example to get the effort property highlighted differently (more, or less, than the task description). I've seen that there is some mechanism to compute a compiled version of the info to be displayed (see `org-prefix-format-compiled'). From what I understand, looking at the real value of that var for my agenda, I have the impression I can't stuff face info in there. Would it be still possible, I'd really appreciate a hint on what to look at in order for me to go farer in that direction... Is it? Best regards, Seb -- Sebastien Vauban
[O] [New exporter] Org LaTeX markup
Hello Nicolas,
I'm still searching which variables now host the following customizations:
--8---cut here---start-8---
;; markup for TODO keywords, as a printf format
(setq org-export-latex-todo-keyword-markup \\colorbox{yellow}{%s})
;; markup for tags, as a printf format
(setq org-export-latex-tag-markup \\hfill{}\\fbox{%s})
--8---cut here---end---8---
Can you give me a hint?
Best regards,
Seb
--
Sebastien Vauban
Re: [O] special strings
It was defined in org.el but got squeezed out during the move to the new exporter. I reintroduced it in contrib/lisp/org-html.el. Thanks. I found the new equivalent. Is (require 'ox) is the correct way to load variables before setting them? Is there a mapping of old variables to new ones? e.g.: alpha-org-export.el:45:1:Warning: Unused lexical variable `org-export-copy-to-kill-ring' alpha-org-export.el:45:1:Warning: Unused lexical variable `org-export-headline-levels' alpha-org-export.el:45:1:Warning: Unused lexical variable `org-export-html-toplevel-hlevel' In alpha-org-blog-subtree: alpha-org-export.el:195:30:Warning: reference to free variable `org-export-html-toplevel-hlevel' alpha-org-export.el:202:20:Warning: reference to free variable `org-export-headline-levels' In alpha-org-export-settings: alpha-org-export.el:631:9:Warning: reference to free variable `org-html-special-string-regexps' alpha-org-export.el:711:13:Warning: assignment to free variable `org-html-special-string-regexps' alpha-org-export.el:714:9:Warning: assignment to free variable `org-export-html-special-string-regexps' alpha-org-export.el:717:9:Warning: assignment to free variable `org-export-email-info' alpha-org-export.el:718:9:Warning: assignment to free variable `org-export-author-info' alpha-org-export.el:719:9:Warning: assignment to free variable `org-export-creator-info' alpha-org-export.el:733:9:Warning: assignment to free variable `org-export-html-preamble' alpha-org-export.el:734:9:Warning: assignment to free variable `org-export-html-postamble' alpha-org-export.el:736:9:Warning: assignment to free variable `org-export-headline-levels' alpha-org-export.el:739:9:Warning: assignment to free variable `org-inlinetask-export' alpha-org-export.el:746:9:Warning: assignment to free variable `org-export-with-toc' alpha-org-export.el:748:9:Warning: assignment to free variable `org-export-remove-timestamps-from-toc' alpha-org-export.el:760:9:Warning: assignment to free variable `org-export-with-tags' alpha-org-export.el:763:9:Warning: assignment to free variable `org-export-with-tasks' alpha-org-export.el:781:9:Warning: assignment to free variable `org-export-with-sub-superscripts' Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. ANYBODY can get it. There is no hope without action.
Re: [O] subscribing to this mailing list with gnus
42 147 aeus...@gmail.com writes: How do I subscribe? I haven't been able to find a working address. Thanks. The working address should be news.gmane.org I didn't specify a port-number. You can add a Server (^^ in the groups-buffer) with gnus-select-method nntp and server news.gmane.org: (setq gnus-select-method (quote (nntp news.gmane.org))) After opening the server Space the list of groups will downloaded (takes a few minutes) and you can subscribe with u Sure, the experts can explain this better. HTH Robert I don't know the correct port / address within the context of this code: (setq gnus-select-method '(nntp gmane.emacs.orgmode (nntp-port-number 119)))
Re: [O] New exporter, beamer confusion
Nicolas,
There is the #+LATEX_HEADER:. Is a keyword specific to Beamer
required? It would by symmetric with #+BEAMER: but I have never
needed it before.
Something like
#+LATEX_HEADER:\AtBeginSection[]{\frame{\thispagestyle{empty}\tableofcontents[currentsection]}}
is not interesting to a LaTeX article output, but perhpas in a Beamer.
Or it might want to use a more 'fun' font for my slides while sticking
with kpfonts for the article version, e.g.
#+BEAMER_HEADER:\usepackage[math]{anttor}
#+LATEX_HEADER:\usepackage[light]{kpfonts}
But perhaps (probably!) it could be sorted out on the LaTeX side,
e.g. via beamerarticle.
–Rasmus
--
Vote for proprietary math!
Re: [O] old to new converter transition
On Thu, Feb 07, 2013 at 03:26:10PM +0100, Rainer M Krug wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Some remarks and questions about transition to new exporter: 1) org-export-latex-listings -becomes- org-latex-listings Since Nicolas answered your specific question, I thought I should share some of my notes about moving to the new exporter. I assembled this by reading Nicolas' announcement, grepping through the source, and some light testing after the switch. 1. Export engine renamed: org-export → ox 2. Backend requires renamed: org-e-* → ox-* 3. All backend specific variables and functions renamed: - org-export-* → org-* (e.g. org-html-xml-declaration, ..) - org-e-* → org-* (e.g. org-latex-classes, org-ascii-bullets, ..) 4. Generic export variables retain the name org-export-* (e.g. org-export-dispatch-use-expert-ui, org-export-filter-headline-functions, ..) 5. org-latex-to-pdf-process has been renamed to org-latex-pdf-process 7. Guess, export snippets and backend symbols renamed: - e-backend → backend Hope this help others going through the switch. :) -- Suvayu Open source is the future. It sets us free.
[O] Problem with org-html-format-latex
Hi, Trying out the new exporter and hoping to have it work with o-blog ... A bug occurs with org-html-format-latex (in ox-html.el) when called from a non-file buffer. In the context of o-blog, it gets called as (org-html-format-latex $x$ 'mathjax) but still tries to bind some ltxpng related support. This ends up calling file-name-sans-extension to the output of (file-name-nondirectory (buffer-file-name)) which is nil ... Crashing in such a case makes sense for ltxpng but not for mathjax. This makes it work: diff --git a/lisp/ox-html.el b/lisp/ox-html.el index f4fc27b..03e09aa 100644 --- a/lisp/ox-html.el +++ b/lisp/ox-html.el @@ -1994,8 +1994,8 @@ CONTENTS is nil. INFO is a plist holding contextual information. (defun org-html-format-latex (latex-frag processing-type) (let* ((cache-relpath (concat ltxpng/ (file-name-sans-extension - (file-name-nondirectory (buffer-file-name) - (cache-dir (file-name-directory (buffer-file-name ))) + (file-name-nondirectory (or (buffer-file-name) ) + (cache-dir (file-name-directory (or (buffer-file-name) ))) (display-msg Creating LaTeX Image...)) (with-temp-buffer but feels like the wrong solution, probably cache-relpath and cache-dir should be set to nil in such a case ... Regards, /v -- Vincent Beffara
[O] LaTeX export: Theorem with an author
Hi,
How to generate latex code for a theorem with an author, like this:
\begin{theorem}[Newton]
Blah.
\end{theorem}
With the old exporter, you could do this:
#+BEGIN_theorem Newton
Blah.
#+END_theorem
(possibly with brackets, not sure) but now the rest of the #+BEGIN_ line is
ignored ... This works:
#+BEGIN_theorem
[Newton]
Blah.
#+END_theorem
but it is more by accident than anything else. What would be the right way?
Thanks,
/v
--
Vincent Beffara
Re: [O] subscribing to this mailing list with gnus
The working address should be news.gmane.org I didn't specify a port-number. You can add a Server (^^ in the groups-buffer) with gnus-select-method nntp and server news.gmane.org: (setq gnus-select-method (quote (nntp news.gmane.org))) After opening the server Space the list of groups will downloaded (takes a few minutes) and you can subscribe with u Sure, the experts can explain this better. Much, much, much thanks -- these simple instructions were exactly what I was looking for, in particular the code to add to my .gnus.el. I am responding right now in gnus.
[O] suggestion: M-m should move point to first word on line
Ordinarily, M-m is bound to (back-to-indentation) – move point to the first non-whitespace character on the line. It differs from C-a. Might it make sense for org-mode to override M-m? Move the point to the first user word on the line, to the first non-asterisk/whitespace/dash/TODO character on the line.
Re: [O] [New exporter] Org LaTeX markup
Sebastien Vauban wxhgmqzgwmuf@... writes:
Hello Nicolas,
I'm still searching which variables now host the following customizations:
--8---cut here---start-8---
;; markup for TODO keywords, as a printf format
(setq org-export-latex-todo-keyword-markup \\colorbox{yellow}{%s})
;; markup for tags, as a printf format
(setq org-export-latex-tag-markup \\hfill{}\\fbox{%s})
--8---cut here---end---8---
Can you give me a hint?
M-x customize-variable RET org-latex-format-headline-function RET
then copy and paste the last part of the docstring into the window - add a
closing parenthesis at the end - and then modify it to your taste.
Re: [O] subscribing to this mailing list with gnus
I am responding right now in gnus. Kudos.. that was fast. -- ఎందరో మహానుభావులు అందరికి వందనములు. YYR
Re: [O] suggestion: M-m should move point to first word on line
Hello Meng, On Feb 08 2013, Meng Weng Wong mengw...@gmail.com wrote: Ordinarily, M-m is bound to (back-to-indentation) – move point to the first non-whitespace character on the line. It differs from C-a. Might it make sense for org-mode to override M-m? Move the point to the first user word on the line, to the first non-asterisk/whitespace/dash/TODO character on the line. Alternatively, you can set `org-special-ctrl-a/e' to t and use C-a for your desired movement. Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు. YYR
Re: [O] Structure editing
Hi, What I am trying to achieve is an 'ordinary' heading, which is not in the beginning of the document but somewhere in the middle of the document, before a particular level one heading of a tree. At present the 'ordinary' heading gets hidden in the previous tree/subtree. Unfolded state: === * Heading 1 ** Heading 1-1 ** Heading 1-2 AT THIS POINT, A LINE (heading for the section below) WHICH SHOULD NOT BE FOLDED * Heading 2 ** Heading 2-1 ** Heading 2-2 Thanks. - *Sanjib Sikder *Ph.D. Fellow Chemical Engineering IIT Bombay* * On Fri, Feb 8, 2013 at 2:18 AM, Suvayu Ali fatkasuvayu+li...@gmail.comwrote: On Fri, Feb 08, 2013 at 01:27:05AM +0530, Sanjib Sikder wrote: Is it possible to have a line between two tress which should not hide when folded, like the following example ? No this is not possible. Any text following a headline is by definition a part of the tree and will be folded with it. Maybe if you tell us what you are trying to achieve, we can suggest an alternative? -- Suvayu Open source is the future. It sets us free.
Re: [O] Agenda items with date ranges
Bastien bzg at altern.org writes: I can't reproduce this problem. Can you reproduce it with latest Org? The agenda *shows* the (1/8), etc. in Org-Mode 7.8.11. It does *not* show it in version 7.9.2 (Debian sid), so that's why I have noticed it. If I get around to installing the latest version, I'll post feedback here.
Re: [O] old to new converter transition
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/13 16:04, Suvayu Ali wrote: On Thu, Feb 07, 2013 at 03:26:10PM +0100, Rainer M Krug wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Some remarks and questions about transition to new exporter: 1) org-export-latex-listings -becomes- org-latex-listings Since Nicolas answered your specific question, I thought I should share some of my notes about moving to the new exporter. I assembled this by reading Nicolas' announcement, grepping through the source, and some light testing after the switch. 1. Export engine renamed: org-export → ox 2. Backend requires renamed: org-e-* → ox-* 3. All backend specific variables and functions renamed: - org-export-* → org-* (e.g. org-html-xml-declaration, ..) - org-e-* → org-* (e.g. org-latex-classes, org-ascii-bullets, ..) 4. Generic export variables retain the name org-export-* (e.g. org-export-dispatch-use-expert-ui, org-export-filter-headline-functions, ..) 5. org-latex-to-pdf-process has been renamed to org-latex-pdf-process 7. Guess, export snippets and backend symbols renamed: - e-backend → backend Hope this help others going through the switch. I am sure. Would it be possible to collect this info on a quick and dirty worg page? At the moment, the info is in several different threads? Could be a temporarily useful. Thanks, Rainer :) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRFK8+AAoJENvXNx4PUvmCX78H/3Pfq/H5QbxiuIuIIGCankKy bFnYJaoQxBOOZO/LYv0EPKyrFGfgp6E7OxkuluQkR03WK1C59BtgmRMCzAsZY5u+ bbgW3zNgAgspPiZj6IoyYoTm6zRA0FPXrnM76voxDA8Dtf/LshWMnvrDvSh5Wm6l 1tJxmNHU7sOUGqNSpNwC5BZAhhPLH4jzoU/kpSUGomZa9Xj028dT+ejK8FoQvtsD I0PsDltL//GRWAxak0MHsnb/F5YV6GXJD/Tlgs3YZtsVLgk0agva+91xkdew8G7U GILEprBqKpFYG0Ga4F7HkuLVymOmTda1lHd+g3hCVJkCO3XDAlZv6IudBjU0Q+E= =Z+Ls -END PGP SIGNATURE-
