Re: [O] Contradiction between code and doc as regards commented lines
Hi Rafael, Rafael Laboissiere raf...@laboissiere.net writes: I just noticed that my patch have a bad side effect, since the commented lines at the beginning of the *Remember* buffer are not filtered out before inclusion into the destination org file. The patch attached below fixes this. Also, the org-remember-handler function attempts to strip comment lines at the end of the buffer. I changed the code such that only lines that really respect the definition of comment lines (as per the documentation) are actually stripped. Applied, thanks. I just added the TINYCHANGE cookie to your patch. -- Bastien
Re: [O] New exporter: no custom timestamps
Nicolas Goaziou n.goaz...@gmail.com writes: Done. I've also added :repeater-unit for good measure. Great, thanks! -- Bastien
Re: [O] Org-Mode menus not in text mode menu or lacarte
Hi Lennart, Lennart Fricke pge08...@studserv.uni-leipzig.de writes: Hello everybody, I was trying to use org-mode from console and realized that there are no Org-Mode menus when I open the text menu with f10 (tmm-menubar) or lacarte. Bug confirmed. Do you have an idea why there are not there. This is actually a bug in outline-mode, I'm now hunting this down. Thanks for reporting this, -- Bastien
Re: [O] Filter weekly/daily agenda by tag
Hi Alexander, Alexander Baier lexi.ba...@gmail.com writes: Another question: Do you know if there is any documentation on the settings i can pass to the commands in org-agenda-custom-commands? Not sure it answers your question correctly, but here is a good tutorial about this configuration area: http://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.html HTH, -- Bastien
Re: [O] Bug in org-log-into-drawer
Hi Erik and Sébastien, Erik Hetzner e...@e6h.org writes: The function org-log-into-drawer called the function org-entry-get with the inherit argument before I got there. (Maybe it needs to be added to that list?) I don't have time to look deeper in this issue. Can one of you have a closer look at the manual and see if there is any inconsistency? Thanks! -- Bastien
Re: [O] [patch] fix bug introduced in commit aba9e2b9
Le Wang l26w...@gmail.com writes: This commit broke editing any source section with blank lines. Er.. yes, indeed. Thanks for the fix! I just applied it. -- Bastien
Re: [O] Web site bug
Hi Achim, Bastien b...@altern.org writes: + (write-region (autoload-rubric org-install.el nil org-install) nil org-install.el) + (write-region (autoload-rubric org-loaddefs.el nil org-loaddefs) nil org-install.el) I don't know what autoload-rubric is. Hint? You didn't reply to this comment. What is autoload-rubric? -- Bastien
Re: [O] Web site bug
Hi Achim, let's start fresh. Can you point at an actual reproducible and simple bug with the current way Org defines autoloads? Thanks, -- Bastien
Re: [O] Announcing a script that connects org-mode and google-tasks
Hi Mark, Mark Edgington edgi...@gmail.com writes: I hacked together a python script based on some already-existing code, which allows one to push an org file to a google-tasks list, or to pull the contents of a google-tasks list into an org file. Though the code isn't beautiful at the moment, it is functional. Feel free to improve it. Get it at: https://bitbucket.org/edgimar/michel-orgmode Looks nice. Could you provide a patch against Worg so that this tool appears in http://orgmode.org/worg/org-tools/ ? Thanks, -- Bastien
Re: [O] Web site bug
Bastien writes: What is autoload-rubric? C-h f autoload-rubric autoload-rubric is a compiled Lisp function in `autoload.el'. (autoload-rubric FILE optional TYPE FEATURE) Return a string giving the appropriate autoload rubric for FILE. TYPE (default autoloads) is a string stating the type of information contained in FILE. If FEATURE is non-nil, FILE will provide a feature. FEATURE may be a string naming the feature, otherwise it will be based on FILE's name. At present, a feature is in fact always provided, but this should not be relied upon. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Web site bug
Achim Gratz strom...@nexgo.de writes: Bastien writes: What is autoload-rubric? C-h f autoload-rubric autoload-rubric is a compiled Lisp function in `autoload.el'. Thanks. The function is not autoloaded, so I had to (require 'autoload) before being able to access it. -- Bastien
Re: [O] Org-Mode menus not in text mode menu or lacarte
Hi Bastien! I don't think that it is necessary any more. It's a bug in tmm and lacarte. The keymap sturcture changed in Emacs 24. See http://debbugs.gnu.org/cgi/bugreport.cgi?bug=12744 I also posted on DrewAdams emacswiki site. Best regards Lennart Fricke
Re: [O] Web site bug
Bastien writes: Can you point at an actual reproducible and simple bug with the current way Org defines autoloads? After the introduction of org-loaddefs, the autoloads should be extracted into two files and only the first is supposed to be loaded before org is actually used and the second, org-loaddefs, is supposed to be loaded by Org itself. But when using a standalone Org, that first file doesn't exist and there's no mechanism for the generated autoloads (all in org-loaddefs) to be loaded before Org is used. You suggest that in a standalone installation the user doesn't need to do anything by way of customization: that's a bug, because the autoloads in org-loaddefs for the standalone Org are not present _at all_ in that situation. That there may be some autoloads present from another Org version (from Emacs) that by accident may point to a file that will then cause Org to be loaded anyway doesn't make this bug go away. Standalone Org needs a file separate from org-loaddefs to collect the autoload definitions into that will be loaded on startup. For Emacs, this is loaddefs; for package manager, this is org-autoloads; for Org standalone, I posit that we should keep org-install. If we keep a different system of how to handle autoloads depending on the type of installation, then it will be impossible to test that everything works correctly[1], not to mention the confusion that this discussion so amply demonstrates. [1] For instance, any first-level autoloaded function that somehow calls into these files: ob, ob-keys, ob-lob, ob-tangle, org-archive, org-ascii, org-attach, org-bbdb, org-clock, org-datetree, org-docbook, org-element, org-exp, org-feed, org-footnote, org-freemind, org-html, org-icalendar, org-id, org-indent, org-irc, org-latex, org-lparse, org-mobile, org-odt, org-plot, org-publish, org-remember, org-table, org-taskjuggler, org-timer, org-xoxo needs to make sure that org-loaddefs has been loaded, which currently only happens in org, but I have not been able to ascertain that each codepath to one of these functions will actually go through it. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Org-Mode menus not in text mode menu or lacarte
Hi Lennart, Lennart Fricke pge08...@studserv.uni-leipzig.de writes: I don't think that it is necessary any more. Good, thanks for the update! Best, PS: the emacs-devel team is great. -- Bastien
Re: [O] Web site bug
Sorry, maybe I was unclear, but I'm looking forward to reading a *recipe* to reproduce the bug. I will re-read your email when I have time to parse it in full details. Thanks, -- Bastien
Re: [O] Web site bug
Bastien writes: Sorry, maybe I was unclear, but I'm looking forward to reading a *recipe* to reproduce the bug. Build an Emacs without Org or remove all autoload forms for Org from loaddefs.el, then install a standalone Org and don't add any requires to the startup files. Try to use any Org function that should be autoloaded. 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
Re: [O] [ANN] Editable HTML export of Org-mode files
The edit option comes only for the content of the headings. We can't edit the headings and the subheadings of the headings. So the source code has to be modified to make the org-mode document editable as HTML where we can edit the Headings and subheadings. The edit button appears only for the content of the subheadings or headings of the document. So we have to modify the org-ehtml to inculcate this feature. thanks Nitin Agarwal On Sun, Oct 28, 2012 at 8:35 PM, Simon Thum simon.t...@gmx.de wrote: On 10/28/2012 04:19 PM, Eric Schulte wrote: Yes, the content of the edit boxes does come from the exported html. For each portion of the Org-mode document (as delimited by org-elements), both the raw Org-mode text and the HTML are exported side-by-side, then the raw Org-mode text is hidden and the HTML is displayed, until the [edit] button is pushed at which point JavaScript is used to hide the HTML and to expose the raw Org-mode text in an edit box. When edits are committed they are committed one portion (edit-box) at a time. Does this make sense? Why would something need to change for this to be reliable? No, that sounds correct in principle. But my whitespace got eaten nonetheless ;( I'll be investigating further. Cheers, Simon -- *Nitin Agarwal* Computer Science and Engineering Student International Institute of Information Technology Gachibowli, Hyderabad 500 032 Andhra Pradesh, India Phone : +91-9573572831 E-mail: nitinagarwal3...@gmail.com nitinagarwal1...@gmail.com *nitin.agar...@students.iiit.ac.in*
Re: [O] How to automatic list org files via Elisp and then, import them for an HTML export
Ho! I was thinking that giving the more details will eliminated doubts and misunderstanding. So to be clear enough, there was two questions in my previous message: 1/ In E-LISP, how to parse a directory containing Org files and import them with the #+INCLUDE function? I used those two functions. They parsed the directory and listed the org files. But my lake of skills in elisp programming is obvious! #+BEGIN_SRC emacs-lisp :exports results (let ((default-directory ~/path/to/the/directory/posts/)) (file-expand-wildcards ?org)) #+END_SRC #+BEGIN_SRC emacs-lisp :exports results (directory-files ~/path/to/the/directory/posts/ nil \\.org\\') #+END_SRC 2/ When I use #+INCLUDE for org files, the exporter mixed the hierarchy in the HTML generated. Each time I used :minlevel 1 as argument but the exporter seem to create a sub-level of hierarchy, which doesn't represent the true hierarchy in the imported org files? Is it a bug? I hope it's minimal enough now! Thanks Bastien for Org Mode and helps! Basile 2012/10/27 Bastien b...@altern.org Hi Flammable (!), flammable project flammable.proj...@gmail.com writes: If someone can help me to do this I will really appreciate! I think we will be able to help with a more limited example. Keep it minimal, if possible... Thanks in advance, -- Bastien
[O] [bug] Export and tangle
Hi fellows, just got the following bug report[0] from a Debian user: Typing C-c C-v t on the following file creates only bar.txt but not foo.txt as expected. Does it matter whether BEGIN_SRC and END_SRC are written in small letters or not? The .. lines are not part of foo.org File foo.org #+BEGIN_SRC text :tangle foo.txt foo #+END_SRC #+begin_src text :tangle bar.txt bar #+end_src End of foo.org From my own experience BEGIN_SRC/END_SRC do not care whether they're capitalized or not, but in this particular case it seems it's making a difference. Any idea ? Cheers, --Seb [0] http://bugs.debian.org/691505
Re: [O] Bug ? LaTeX exporter does not export subsections from included files
On 2012-10-08, Sébastien Delafond sdelaf...@gmail.com wrote: Since the update to org-mode 7.9.1-1, the LaTeX export does not work completely anymore with included files. No idea at all on this one ? :) Cheers, --Seb
Re: [O] [bug] [new-exporter] #+includes in non-exported regions do not work
Myles English mylesengl...@gmail.com writes: Hi Eric, You have: #+include: uml.org I think it should be: #+include: uml.org Indeed it should be, or at least for the new exporter. Thanks for pointing this out. There is still a bug in that the exporter should fail more gracefully? The question of structural interpretation remains: should the file be included if it is found within a not-to-be-exported headline? This is, at least for me, unexpected behaviour based on previous experience with the old exporter. Now, from C programming and so on, the behaviour in the new exporter is reasonable; however, as there is no way to optionally included material from another file, I prefer the behaviour of the old exporter. Thanks again, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.2.50.1 and Org release_7.9.2-406-g2c78ca-git
Re: [O] Web site bug
Bastien b...@altern.org writes: Sorry, maybe I was unclear, but I'm looking forward to reading a *recipe* to reproduce the bug. Bastien, I think what Achim is saying is that, for those of us that install org from git, the system of autoloading is *fragile* because it depends on non-predictable behaviour of how an older version of org may have been configured. A recipe is not necessarily possible but the problem is there nonetheless. thanks, eric -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.2.50.1 and Org release_7.9.2-406-g2c78ca-git
Re: [O] [new exporter] Date format string not handled for LaTeX export
Hello,
Michael Gauland mikely...@no8wireless.co.nz writes:
When I provide a format string to the #+DATE: option, the old LaTeX exporter
correctly uses it to format the current date; the new exporter just uses the
format string for the date.
I wasn't aware of that feature. Though, I don't like it: it is fragile
for technical reasons (it may or may not work on every exporter) and it
adds yet another special rule to remember.
On the other hand, you have a hard-coded macro to solve this problem:
#+DATE: {{{time(%c)}}}
It will work across every back-end (but you need the latest Org version,
since I recently to fixed a bug related to it).
The new HTML exporter does not have this problem.
I am going to remove this hack from new back-ends as it isn't necessary.
Regards,
--
Nicolas Goaziou
[O] [bug] Parts of code blocks are highlighted as Org comments
Hello,
If you have such a Sh code block in any Org document, you'll see that the 4th
line will be highlighted as an Org comment from the # != 2...
#+begin_src sh
# swap FILE1 FILE2
swap ()
{
if [[ $# != 2 ]]; then
return 1
fi
tmpfile=/tmp/.swapper.$$.$RANDOM
mv -f $1 $tmpfile
mv -f $2 $1
mv -f $tmpfile $2
return 0
}
#+end_src
If you edit such (via C-c '), you can check that it's NOT highlighted as a
comment in the Shell mode.
Best regards,
Seb
--
Sebastien Vauban
Re: [O] [bug] [new-exporter] #+includes in non-exported regions do not work
Hello, Eric S Fraga e.fr...@ucl.ac.uk writes: There is still a bug in that the exporter should fail more gracefully? Agreed. This syntax error should be more explicit now. Thanks. The question of structural interpretation remains: should the file be included if it is found within a not-to-be-exported headline? This is, at least for me, unexpected behaviour based on previous experience with the old exporter. There's a design choice at the roots of the export engine development: External parts (i.e. everything but org-export.el and back-ends) shouldn't have to know anything about the exporter (much like the Fight club, isn't it?). Note that this isn't the case with current exporter (org-exp.el): many files, including org-list.el, org-footnote.el... have to cope with org-exp's internals (i.e. text properties encountered only during export) so everything can run (almost) smoothly. By that design choice, Babel blocks execution should happen independently on export context, like exclude tags. And, by another principle, the one of least surprise, the same happens for include keywords expansion. Now, from C programming and so on, the behaviour in the new exporter is reasonable; however, as there is no way to optionally included material from another file, I prefer the behaviour of the old exporter. I like the current behaviour. I also fail to see why it should be a problem. Though, I'm open to discussion to implement a mid-way solution. Maybe with the COMMENT keyword which is exporter agnostic. Regards, -- Nicolas Goaziou
Re: [O] [wish] also provide documentation for contrib
On 2012-10-27, Bastien b...@altern.org wrote: I agree. Let's start by patching README_contribute with a new section containing short documentation for contributions. Hi Bastien, I unfortunately have very little time these days to take on this task :\ Hopefully this will change in the not-too-distant future... Cordialement, --SD
Re: [O] Bug ? LaTeX exporter does not export subsections from included files
Hi,
I tried with both the old exporter (emacs -Q) and the new.
The old one exports correctly on my side, here's the relevant part:
#+BEGIN_LaTeX
This is Bar.
\subsection{Bar 1}
\label{sec-2-1}
This is Bar's first part.
\subsection{Bar 2}
\label{sec-2-2}
And here is the second one.
#+END_LaTeX
I think the behaviour in the new exporter has been changed to a better:
The included trees are changed in depth according to the structure they
are imported to, so with the new exporter the included file should start
at level1 as well, e.g.
...
This is Bar
* Bar 1
...
This makes the files more usable on their own as well, which is a great
improvement!
I hope this assumption is correct.
Regards, Philipp
Sébastien Delafond sdelaf...@gmail.com writes:
On 2012-10-08, Sébastien Delafond sdelaf...@gmail.com wrote:
Since the update to org-mode 7.9.1-1, the LaTeX export does not work
completely anymore with included files.
No idea at all on this one ? :)
Cheers,
--Seb
[O] Bug: New exporter fails with void-function org-clocking-buffer [7.9.2 (release_7.9.2-532-g2e8591)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. Here is what I did: 1. Update to latest git version 2. Start emacs with emacs -Q -l ~/test.el (test.el attached) 3. Create minimal org file, e.g., #+title: test * Heading 1 * Heading 2 4. Export with M-x org-export-dispatch t a What happened: fails with void-function org-clocking-buffer. What I expected: buffer is exported to text file. Emacs : GNU Emacs 24.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.1) of 2012-10-21 on eric Package: Org-mode version 7.9.2 (release_7.9.2-532-g2e8591 @ /home/izahn/.emacs.d/izahn/org-mode/lisp/) current state: == (setq org-export-preprocess-before-selecting-backend-code-hook '(org-beamer-select-beamer-code) org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe org-babel-header-arg-expand) org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook) org-occur-hook '(org-first-headline-recenter) org-metaup-hook '(org-babel-load-in-session-maybe) org-export-preprocess-before-normalizing-links-hook '(org-remove-file-link-modifiers) org-confirm-shell-link-function 'yes-or-no-p org-export-latex-final-hook '(org-beamer-amend-header org-beamer-fix-toc org-beamer-auto-fragile-frames org-beamer-place-default-actions-for-lists) org-export-latex-after-initial-vars-hook '(org-beamer-after-initial-vars) org-after-todo-state-change-hook '(org-clock-out-if-current) org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-babel-pre-tangle-hook '(save-buffer) org-mode-hook '(#[nil \300\301\302\303\304$\207 [org-add-hook change-major-mode-hook org-show-block-all append local] 5] #[nil \300\301\302\303\304$\207 [org-add-hook change-major-mode-hook org-babel-show-result-all append local] 5] org-babel-result-hide-spec org-babel-hide-all-hashes) org-export-with-tags t org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe) org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-hide-inline-tasks org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-export-latex-format-toc-function 'org-export-latex-format-toc-default org-export-first-hook '(org-beamer-initialize-open-trackers) org-export-with-drawers t org-confirm-elisp-link-function 'yes-or-no-p org-metadown-hook '(org-babel-pop-to-session-maybe) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) ) test.el Description: Binary data
Re: [O] Bug: New exporter fails with void-function org-clocking-buffer [7.9.2 (release_7.9.2-532-g2e8591)]
Hello, Ista Zahn istaz...@gmail.com writes: Here is what I did: 1. Update to latest git version 2. Start emacs with emacs -Q -l ~/test.el (test.el attached) 3. Create minimal org file, e.g., #+title: test * Heading 1 * Heading 2 4. Export with M-x org-export-dispatch t a What happened: fails with void-function org-clocking-buffer. What I expected: buffer is exported to text file. It should be fixed in master. Thank you for the report. Regards, -- Nicolas Goaziou
Re: [O] Bug in org-log-into-drawer
At Mon, 29 Oct 2012 06:41:39 +0100, Bastien wrote: Hi Erik and Sébastien, Erik Hetzner e...@e6h.org writes: The function org-log-into-drawer called the function org-entry-get with the inherit argument before I got there. (Maybe it needs to be added to that list?) I don't have time to look deeper in this issue. Can one of you have a closer look at the manual and see if there is any inconsistency? Hi Bastien, org mode manual says: You can also overrule the setting of this variable for a subtree by setting a `LOG_INTO_DRAWER' property. This sounds to me that LOG_INTO_DRAWER inheritance is intended. Even if it is not, I would argue that LOG_INTO_DRAWER *should* apply to subtrees, because otherwise one would have to set that property on every TODO item. best, Erik Sent from my free software system http://fsf.org/.
Re: [O] Bug in org-log-into-drawer
Hello Erik and Bastien, Erik Hetzner wrote: Bastien wrote: Erik Hetzner e...@e6h.org writes: The function org-log-into-drawer called the function org-entry-get with the inherit argument before I got there. (Maybe it needs to be added to that list?) I don't have time to look deeper in this issue. Can one of you have a closer look at the manual and see if there is any inconsistency? Hi Bastien, org mode manual says: You can also overrule the setting of this variable for a subtree by setting a `LOG_INTO_DRAWER' property. This sounds to me that LOG_INTO_DRAWER inheritance is intended. Even if it is not, I would argue that LOG_INTO_DRAWER *should* apply to subtrees, because otherwise one would have to set that property on every TODO item. I share your point... But do we all agree that your original example had to fail when LOG_INTO_DRAWER is not inherited?[1] Or do I miss some point? Seb [1] If yes, is your patch still OK? -- Sebastien Vauban
[O] Logging properties, values in notes on TODO state change for column view usage?
I have been looking at trying to track training performance with org-mode. I currently just set a reoccurring schedule with note logging on state change, but wondered if there was a way to log values within this :LOGBOOK: logs? It is not a lot of effort to simply type in :abc: 5, etc in the note window. The idea being it would be nice to use column view to collect these various logged values. ** TODO Training :LOGBOOK: - State DONE [2012-10-29 Mon 16:26] \\ :abc: 5 :xyz: 9 - State DONE [2012-10-30 Tue 16:25] \\ :abc: 6 :xyz: 8 :PROPERTIES: :LAST_REPEAT: [2012-10-30 Tue 16:26] :COLUMNS: %25ITEM %10abc %10xyz :END: 2012-10-29 Mon +1d
[O] Bug: python babel does not support hlines as mentioned in docs [7.9.2 (release_7.9.2-499-ga29de0 @ /home/lennart/.emacs.d/site-lisp/org/lisp/)]
Hello, The following block exits with error: orgtbl-format-line: Wrong type argument: sequencep, None #+TBLNAME: many-cols | a | b | c | |---+---+---| | d | e | f | |---+---+---| | g | h | i | #+NAME: echo-table #+BEGIN_SRC python :var tab=many-cols :hlines yes return tab #+END_SRC I bisected it down to commit b174975eb7a828d77816a9bf8107fc1a3ae597d7 . There the special handling of None in a python list was deleted. Could that be added back? Is it desired? If not, it would be great, if you change the example in the docs of hlines header argument. Thank you and best regards Lennart Fricke Emacs : GNU Emacs 24.1.1 (i686-redhat-linux-gnu, GTK+ Version 2.24.11) of 2012-08-13 on buildvm-23.phx2.fedoraproject.org Package: Org-mode version 7.9.2 (release_7.9.2-499-ga29de0 @ /home/lennart/.emacs.d/site-lisp/org/lisp/)
Re: [O] Bug: python babel does not support hlines as mentioned in docs
This patch makes None being treated as hline again. Best regards Lennart Fricke diff --git a/lisp/ob-python.el b/lisp/ob-python.el index 71adf73..a1f834f 100644 --- a/lisp/ob-python.el +++ b/lisp/ob-python.el @@ -123,7 +123,11 @@ specifying a variable of the same value. Convert RESULTS into an appropriate elisp value. If the results look like a list or tuple, then convert them into an Emacs-lisp table, otherwise return the results as a string. - (org-babel-script-escape results)) + ((lambda (res) + (if (listp res) + (mapcar (lambda (el) (if (equal el 'None) 'hline el)) res) + res)) + (org-babel-script-escape results))) (defvar org-babel-python-buffers '((:default . nil)))
Re: [O] error in org-mark-subtree
Hello, Samuel Wales samolog...@gmail.com writes: Debugger entered--Lisp error: (void-function org-clocking-buffer) org-clocking-buffer() org-element-headline-parser(1375194 t) org-element-at-point() org-mark-element() org-mark-subtree() If it is related, then you have to load org-clock to mark the subtree. There is no clock anywhere. Git master. I (hopefully) fixed it a few hours ago. You may want to update and try again. Regards, -- Nicolas Goaziou
Re: [O] [bug] Export and tangle
Hi Sébastien, Sébastien Delafond writes: Hi fellows, just got the following bug report[0] from a Debian user: Typing C-c C-v t on the following file creates only bar.txt but not foo.txt as expected. I just tried this with the git head and get the two files. Of course, it doesn't rule out a problem with the version your user is using though. Myles
Re: [O] [bug] [new-exporter] #+includes in non-exported regions do not work
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Eric S Fraga e.fr...@ucl.ac.uk writes: There is still a bug in that the exporter should fail more gracefully? Agreed. This syntax error should be more explicit now. Thanks. Thanks! The question of structural interpretation remains: should the file be included if it is found within a not-to-be-exported headline? This is, at least for me, unexpected behaviour based on previous experience with the old exporter. There's a design choice at the roots of the export engine development: External parts (i.e. everything but org-export.el and back-ends) shouldn't have to know anything about the exporter (much like the Fight club, isn't it?). Okay. I can see that the new approach is more consistent and that is always a good thing in my books. I guess I was just perturbed at the change in behaviour, and mostly because the error message made no sense to me as the not-to-be-exported sections were all hidden in my view! [...] I like the current behaviour. I also fail to see why it should be a problem. Though, I'm open to discussion to implement a mid-way solution. Maybe with the COMMENT keyword which is exporter agnostic. It's a problem only because of the way I use the :noexport: and COMMENT tags to exclude parts of a document that are often incomplete or partially defined. However, I do realise I am being inconsistent as I use :noexport: tags to hide babel code that is referenced in the rest of my documents often. There probably is really no problem at all; I just simply need to adjust to a more logical approach to incomplete sections, e.g. commenting out =#+= directives I do not want processed. This would include =INCLUDE= and =BEGIN_SRC=. Not a big deal. So, I don't think there is anything to be done. Thanks for listening and sorry for the noise! -- : Eric S Fraga, GnuPG: 0xC89193D8FFFCF67D : in Emacs 24.2.50.1 and Org release_7.9.2-406-g2c78ca-git
Re: [O] TeX-master: TeX-master is let-bound
Nick Dokos nicholas.do...@hp.com writes: In any case, if you can get rid of the let-bind (or the need to muck with TeX-master at all within org), without introducing a regression, we are all ears. I think adding (require 'tex nil t) before the let form is a nice fix. IMO the situation ATM is pretty bad. If AUCTeX is not loaded pre export the missing variable definition breaks AUCTeX completely. Christopher
Re: [O] [new exporter] Date format string not handled for LaTeX export
Nicolas Goaziou n.goaziou at gmail.com writes:
On the other hand, you have a hard-coded macro to solve this problem:
#+DATE: {{{time(%c)}}}
It will work across every back-end (but you need the latest Org version,
since I recently to fixed a bug related to it).
Thanks--that will do nicely. Unfortunately, I can't seem to get it working. When
I export to HTML, I get a blank date; when I try to export to LaTeX, the
exporter doesn't appear to do anything. After hitting ^G, the .tex file is
unchanged.
I've grabbed the latest from git
(commit 1f3a2c42c6317a4b0e97b237f079c51f0028cc90).
Re: [O] [bug] [new-exporter] #+includes in non-exported regions do not work
Hi Nicolas and Eric, Eric S Fraga wrote: It's a problem only because of the way I use the :noexport: and COMMENT tags to exclude parts of a document that are often incomplete or partially defined. Can we assume that `:noexport:' and `COMMENT' are complete synonyms, as of today, and will stay so in the foreseen future? Best regards, Seb -- Sebastien Vauban
Re: [O] [new exporter] Date format string not handled for LaTeX export
Michael Gauland mikely...@no8wireless.co.nz writes:
Nicolas Goaziou n.goaziou at gmail.com writes:
On the other hand, you have a hard-coded macro to solve this problem:
#+DATE: {{{time(%c)}}}
It will work across every back-end (but you need the latest Org version,
since I recently to fixed a bug related to it).
Thanks--that will do nicely. Unfortunately, I can't seem to get it working.
When
I export to HTML, I get a blank date; when I try to export to LaTeX, the
exporter doesn't appear to do anything. After hitting ^G, the .tex file is
unchanged.
I just tried with a minimal init and it worked. Could you send the
example you're trying to export?
Thank you.
Regards,
--
Nicolas Goaziou
Re: [O] TeX-master: TeX-master is let-bound
Christopher Schmidt christop...@ch.ristopher.com wrote: Nick Dokos nicholas.do...@hp.com writes: In any case, if you can get rid of the let-bind (or the need to muck with TeX-master at all within org), without introducing a regression, we are all ears. I think adding (require 'tex nil t) before the let form is a nice fix. Not really: you end up pulling in auctex even if you are not going to use it. IMO the situation ATM is pretty bad. If AUCTeX is not loaded pre export the missing variable definition breaks AUCTeX completely. What missing variable definition? By the time the export is finished, the let-bind is gone. There is no definition of TeX-master anywhere, just as if you never had org loaded: why should auctex object to that? So I don't understand why it would break: all the common scenarios that I have tried work with no problem for me. I can load an org file, export to latex, open the latex file (which loads auctex) and do auctex things to it. I don't get any error. What exactly do I have to do in order to break it? Nick
[O] Texlive 2012 export?
Hi, Running Fedora 17 and org-mode 7.9.2 I have just updated texlive from the default repos to texlive-2012 and installed texlive-collection-latexextra, but have problems to export org-files to pdf. The error message received says: , | !pdfTeX error: pdflatex (file cm-super-t1.enc): cannot open encoding file for r | eading ` I did a 'find' to search for the file, without results, so I guess a package may be missing? A 'yum provides' does not return anything. Is there any known incompatibilities or procedures that I have missed? Thanks! -- Johnny
Re: [O] [new exporter] Date format string not handled for LaTeX export
Nicolas Goaziou n.goaziou at gmail.com writes:
I just tried with a minimal init and it worked. Could you send the
example you're trying to export?
The file is below. With a minimal init, I get the error Symbol's function
definition is void: org-macro-initialize-templates'. If I use my full .emacs
file, the exporter just seems to freeze up.
-- test.org -
#+DATE: {{{date(%c)}}}
This ia a test file.
Re: [O] TeX-master: TeX-master is let-bound
Nick Dokos nicholas.do...@hp.com writes: What missing variable definition? By the time the export is finished, the let-bind is gone. There is no definition of TeX-master anywhere, just as if you never had org loaded: why should auctex object to that? So I don't understand why it would break: all the common scenarios that I have tried work with no problem for me. I can load an org file, export to latex, open the latex file (which loads auctex) and do auctex things to it. I don't get any error. What exactly do I have to do in order to break it? In org-latex.el, within the binding: (if to-buffer (unless (eq major-mode 'latex-mode) (latex-mode)) (save-buffer)) Recipe: emacs -q # + AUCTeX C-x b rms RET M-x org-mode RET M-: (insert a) RET C-x h M-x org-export-region-as-latex RET # In buffer *Org LaTeX Export* C-c C-c TeX-command-master: Symbol's value as variable is void: TeX-master Christopher
Re: [O] [new exporter] Date format string not handled for LaTeX export
Michael Gauland mikely...@no8wireless.co.nz wrote:
Nicolas Goaziou n.goaziou at gmail.com writes:
I just tried with a minimal init and it worked. Could you send the
example you're trying to export?
The file is below. With a minimal init, I get the error Symbol's function
definition is void: org-macro-initialize-templates'. If I use my full .emacs
file, the exporter just seems to freeze up.
-- test.org -
#+DATE: {{{date(%c)}}}
This ia a test file.
With a minimal file, I get a cpu pegged at 100% with no end in
sight. Setting debug-on-quit and C-g gives me the following backtrace.
Org-mode version 7.9.2 (release_7.9.2-533-g07c889 @
/home/nick/elisp/org-mode/lisp/)
Nick
Debugger entered--Lisp error: (quit)
mapc((lambda (type) (let* ((successor-fun (intern (format
org-element-%s-successor (or (cdr ...) type (obj (funcall successor-fun
limit))) (and obj (setq next-candidates (cons obj next-candidates)
(inline-babel-call inline-src-block latex-or-entity link macro sub/superscript
text-markup))
(let (next-candidates types-to-search) (if (not objects) (setq
types-to-search restriction) (mapc (function (lambda (obj) (if ( (cdr obj)
(point)) (setq types-to-search (cons ... types-to-search)) (setq
next-candidates (cons obj next-candidates) objects)) (mapc (function
(lambda (type) (let* ((successor-fun (intern ...)) (obj (funcall successor-fun
limit))) (and obj (setq next-candidates (cons obj next-candidates))
types-to-search) next-candidates)
org-element--get-next-object-candidates(23 (inline-babel-call
inline-src-block latex-or-entity link macro sub/superscript text-markup) nil)
(setq candidates (org-element--get-next-object-candidates end restriction
candidates))
(while (setq candidates (org-element--get-next-object-candidates end
restriction candidates)) (let ((closest-cand (rassq (apply (quote min) (mapcar
(quote cdr) candidates)) candidates))) (if ( (cdr closest-cand) origin) (throw
(quote exit) parent) (let* ((object (progn (goto-char ...) (funcall ...)))
(cbeg (org-element-property :contents-begin object)) (cend
(org-element-property :contents-end object))) (cond (( (org-element-property
:end object) origin) (goto-char (org-element-property :end object))) ((or (not
cbeg) ( cbeg origin) ( cend origin)) (throw (quote exit)
(org-element-put-property object :parent parent))) (t (goto-char cbeg)
(org-element-put-property object :parent parent) (setq parent object
restriction (org-element-restriction object) end cend)))
(catch (quote exit) (while (setq candidates
(org-element--get-next-object-candidates end restriction candidates)) (let
((closest-cand (rassq (apply (quote min) (mapcar ... candidates)) candidates)))
(if ( (cdr closest-cand) origin) (throw (quote exit) parent) (let* ((object
(progn ... ...)) (cbeg (org-element-property :contents-begin object)) (cend
(org-element-property :contents-end object))) (cond (( ... origin) (goto-char
...)) ((or ... ... ...) (throw ... ...)) (t (goto-char cbeg)
(org-element-put-property object :parent parent) (setq parent object
restriction ... end cend))) parent)
(let ((restriction (org-element-restriction type)) (parent element)
candidates) (catch (quote exit) (while (setq candidates
(org-element--get-next-object-candidates end restriction candidates)) (let
((closest-cand (rassq (apply ... ...) candidates))) (if ( (cdr closest-cand)
origin) (throw (quote exit) parent) (let* ((object ...) (cbeg ...) (cend ...))
(cond (... ...) (... ...) (t ... ... ...)) parent))
(if (not (or (let ((post (org-element-property :post-affiliated element)))
(and post ( post origin) ( (org-element-property :begin element) origin)
(progn (beginning-of-line) (looking-at org-element--affiliated-re) (member
(upcase ...) org-element-parsed-keywords)) (setq type (quote keyword)) (if (and
(match-end 2) (= origin ...)) (progn (goto-char ...) (setq end ...))
(goto-char (match-end 0)) (setq end (line-end-position) (and (eq type
(quote item)) (let ((tag (org-element-property :tag element))) (and tag (progn
(beginning-of-line) (search-forward tag ...) (goto-char ...) (and ... ...)
(and (memq type (quote (headline inlinetask))) (progn (beginning-of-line)
(skip-chars-forward * ) (setq end (point-at-eol (and (memq type (quote
(paragraph table-row verse-block))) (let ((cbeg (org-element-property
:contents-begin element)) (cend (org-element-property :contents-end element)))
(and (= origin cbeg) (= origin cend) (progn (goto-char cbeg) (setq end
cend
) (and (eq type (quote keyword)) (let ((key (org-element-property :key
element))) (and (member key org-element-document-properties) (progn
(beginning-of-line) (search-forward key ... t) (forward-char) (setq end
...))) element (let ((restriction (org-element-restriction type)) (parent
element) candidates) (catch (quote exit) (while (setq candidates
(org-element--get-next-object-candidates end restriction candidates))
Re: [O] [bug] [new-exporter] #+includes in non-exported regions do not work
Hello, Sebastien Vauban wxhgmqzgwmuf-genee64ty+gs+fvcfc7...@public.gmane.org writes: Can we assume that `:noexport:' and `COMMENT' are complete synonyms, as of today As of today, yes. and will stay so in the foreseen future? I wouldn't bet. `:noexport' is /de facto/ limited to export. `COMMENT' keyword doesn't have to. Someone may come up with a broader use case. For example, it could prevent Babel blocks from being executed. Regards, -- Nicolas Goaziou
Re: [O] TeX-master: TeX-master is let-bound
Christopher Schmidt christop...@ch.ristopher.com wrote: Nick Dokos nicholas.do...@hp.com writes: What missing variable definition? By the time the export is finished, the let-bind is gone. There is no definition of TeX-master anywhere, just as if you never had org loaded: why should auctex object to that? So I don't understand why it would break: all the common scenarios that I have tried work with no problem for me. I can load an org file, export to latex, open the latex file (which loads auctex) and do auctex things to it. I don't get any error. What exactly do I have to do in order to break it? In org-latex.el, within the binding: (if to-buffer (unless (eq major-mode 'latex-mode) (latex-mode)) (save-buffer)) You mean that's where you get the error? Recipe: emacs -q # + AUCTeX C-x b rms RET M-x org-mode RET M-: (insert a) RET C-x h M-x org-export-region-as-latex RET # In buffer *Org LaTeX Export* C-c C-c TeX-command-master: Symbol's value as variable is void: TeX-master Christopher I get latex errors saying it cannot find none.tex but no emacs errors: , | ERROR: I can't find file `none.tex'. | | --- TeX said --- | ! I can't find file `none.tex'. | --- HELP --- | TeX can't find a file that it needs. If the name of the missing file | has the extension tex, then it is looking for an input file that you | specified---either your main file or another file inserted with an | \input or \include command. If the missing file has the extension sty | , then you have specified a nonexistent document style or style | option. ` Org-mode version 7.9.2 (release_7.9.2-533-g07c889 @ /home/nick/elisp/org-mode/lisp/) GNU Emacs 24.2.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.4) of 2012-09-21 on alphaville Nick
[O] Capture error
Aloha all, With a recent make update from Git I'm getting this error when I try to Finish (with C-c C-c) some tried and true capture templates: org-capture-bookmark-last-stored-position: Invalid function: with-demoted-errors Here is a backtrace: Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil) org-capture-bookmark-last-stored-position() org-capture-finalize(nil) call-interactively(org-capture-finalize nil nil) Org-mode version 7.9.2 (release_7.9.2-535-g8fb598 @ /Users/dk/.emacs.d/src/org-mode/lisp/) The information is captured to the file, but the capture buffer doesn't go away. All the best, Tom -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] Capture error
Thomas S. Dye t...@tsdye.com wrote: Aloha all, With a recent make update from Git I'm getting this error when I try to Finish (with C-c C-c) some tried and true capture templates: org-capture-bookmark-last-stored-position: Invalid function: with-demoted-errors Here is a backtrace: Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil) org-capture-bookmark-last-stored-position() org-capture-finalize(nil) call-interactively(org-capture-finalize nil nil) Org-mode version 7.9.2 (release_7.9.2-535-g8fb598 @ /Users/dk/.emacs.d/src/org-mode/lisp/) The information is captured to the file, but the capture buffer doesn't go away. Can't see anything wrong and I cannot reproduce it. with-demoted-errors exists in both emacs 23 and 24. It (along with other with-... constructs) is a macro, so there may be some problem with compilation (although I tried compiling org as well). Can you try with uncompiled org-capture.el? The first error message seems to indicate that o-c-b-l-s-p was compiled without knowledge of the macro, so it assumes that it is a function that will exist at runtime. Or perhaps starting with a fresh emacs might make the problem go away. Nick PS. BTW, nothing to do with this problem but make update/make test got an unexpected failure: Test test-org/end-of-line backtrace: signal(ert-test-failed (((should (org-test-with-temp-text * Headlin ert-fail(((should (org-test-with-temp-text * Headline :tag: (let ( (if (unwind-protect (setq value-3861 (let ((temp-buffer (generate-ne (let (form-description-3862) (if (unwind-protect (setq value-3861 (l (let ((value-3861 (ert--gensym ert-form-evaluation-aborted-))) (le (lambda nil (let ((value-3857 (ert--gensym ert-form-evaluation-abor byte-code(\306\307!q\210\310\216\311 \312\216\313\314\315\316\3 ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc byte-code(\306\307!\211\211r\310\311!q\210\312 d\313\223)L\210)\3 ert-run-test([cl-struct-ert-test test-org/end-of-line Test `org-end ert-run-or-rerun-test([cl-struct-ert--stats \\(org\\|ob\\) [[cl-st ert-run-tests(\\(org\\|ob\\) #[(event-type rest event-args) \306 ert-run-tests-batch(\\(org\\|ob\\)) ert-run-tests-batch-and-exit(\\(org\\|ob\\)) (let ((org-id-track-globally t) (org-id-locations-file (convert-stan org-test-run-batch-tests() call-interactively(org-test-run-batch-tests nil nil) command-execute(org-test-run-batch-tests) command-line-1((--eval (add-to-list 'load-path \./lisp\) --ev command-line() normal-top-level() Test test-org/end-of-line condition: (ert-test-failed ((should (org-test-with-temp-text * Headline :tag: (let ... ...))) :form (let ((temp-buffer ...)) (with-current-buffer temp-buffer (unwind-protect ... ...))) :value nil)) FAILED 309/326 test-org/end-of-line
Re: [O] Bug in org-log-into-drawer
At Mon, 29 Oct 2012 17:07:23 +0100, Sebastien Vauban wrote: Hello Erik and Bastien, […] I share your point... But do we all agree that your original example had to fail when LOG_INTO_DRAWER is not inherited?[1] Or do I miss some point? Seb Hi Sebastien, Yes, I had a bad example. But the function org-log-into-drawer would not work (before my patch) on the following example either: * TODO Foo :PROPERTIES: :LOG_INTO_DRAWER: nil :END: The issue was with the distinction between the value nil and string nil. org-entry-get (without an additional arg) will return the value nil in the above example, which meant that the value of org-log-into-drawer (t) was not being overidden. best, Erik Sent from my free software system http://fsf.org/.
