Re: [O] bug-tracker
Am 23.02.2013 08:39, schrieb Michael Albinus: Andreas Röhler andreas.roeh...@easy-emacs.de writes: There is `reporter-submit-bug-report' of reporter.el, which you could customize to your needs. Compare, how Tramp uses it in `tramp-bug' (Ha! another advertisement!). Hmm, maybe you are fastest just to copy a version with org-mode in the slots. That may replace org-submit-bug-report, if Bastien and the others agree. I believe it is better written by org maintainers. They know much better which kind of information is needed. Andreas Best regards, Michael. Okay. Seems we should wait for some more info WRT to proceeding at debbugs. If Bastien wants to go this way at all... BTW personally I'm in favor of an own debbugs package org. Best, Andreas
Re: [O] org-export-babel-evaluate and :exports none
Achim Gratz strom...@nexgo.de writes: Nicolas Goaziou writes: I'm just starting over because that wasn't a correct solution. I'm not even sure about what bug this patch fixed. The bug was that Babel blocks were evaluated during export when org-export-babel-evaluate was explicitly set to nil (the default value is t). AFAICT, they aren't. Try the following in a buffer with `org-export-babel-evaluate' set alternatively to nil and t: #+BEGIN_SRC emacs-lisp :exports both :results value (+ 2 2) #+END_SRC Anyway, it isn't org-export-babel-evaluate's job to tell when to evaluate a source code block. The documentation says that its job is exactly that, if the context is export. That was a typo. I meant it isn't org-export-execute-babel-code's job It may be org-babel-exp-process-buffer's. You call org-export-execute-babel-code however, which doesn't check the above variable. It doesn't need to. Export = ox.el, but export + babel = ob-exp.el. So everything Babel related should happen there. So, /if there's a bug/, it should be fixed in ob-exp.el (maybe in `org-babel-exp-process-buffer's'), not in ox.el. Regards, -- Nicolas Goaziou
Re: [O] org-export-babel-evaluate and :exports none
Nicolas Goaziou writes: The bug was that Babel blocks were evaluated during export when org-export-babel-evaluate was explicitly set to nil (the default value is t). AFAICT, they aren't. So let's go back to the OP (Gregor Kappler, IIRC) and ask for a reproducible recipe. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Warning with latest git pull
Bastien writes: Fixed, thanks! Uh… no, you switched the wrong function in the second line (which incidentally indicates that this branch of the conditional never sees any testing). Fixed in master by using org-float-time. I checked in XEmacs 21.5 and it has float-time, so maybe we wouldn't need a compatibility function after all, but I don't know when XEmacs introduced float-time. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] [Bug] Export Coding System
Nicolas Goaziou writes: No it is not irrelevant, it simply gets set too late in the game: it asks for the new coding system when it is time to save the buffer, while the content of the buffer has been cobbled together while assuming a different coding system. The only way I know (from browsing the documentation) to override the coding system for a buffer that does not yet have a file association is to set that variable directly, preferrably directly after the buffer is created. Does the following patch fix the problem? It fixes the problem when the Org buffer encoding is identical to the encoding for the LaTeX file. It doesn't fix the problem when I want to export the file in a different encoding (for instance by customizing Org Export Latex Coding System), that would require a second step of re-setting the buffer-file-coding-system before using it to determine what to write into the inputenc option. Other exporters like HTML probably also have a way (or should have it) to determine the target coding system independently from the input coding system, so this is not a LaTeX only exercise. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Bug: New HTML exporter incorrect attributes
Hello, First, as always, thanks for the prompt reply. Nicolas Goaziou n.goaz...@gmail.com writes: Hello, tftor...@tftorrey.com (T.F. Torrey) writes: Where attributes have been assigned to an image in a paragraph, the new exporter applies those attributes to both the image and a following link. You don't assign attributes to an image in a paragraph, you assign attributes to the paragraph itself. It would be nice if there actually was a way to assign an attribute to a paragraph, so that the ATTR_HTML: class=XXX syntax would export as p class=XXX, but that is a different issue. For the time being, Org syntax doesn't allow to specify attributes per link object. I think what you are saying is that the current intended behavior is for whatever is specified by ATTR_HTML to apply to every image or link in the paragraph. As a consequence, attributes will be assigned to every link within the paragraph. Is this behavior helpful to anyone in any practical circumstances? Moreover, this means that, not only does the new exporter fail where the old one succeeded, the new one produces invalid HTML (anchors with invalid attributes) in the use case I described (ATTR_HTML to apply to an image beginning a paragraph which later has a link in it, which happens several times in almost all my documents). It seems to me that, whether the user is happy with the output or not, the HTML exporter ought to produce valid HTML. A hack could be implemented in ox-html.el so only image links get these attributes, but it would be the same with multiple images within the same paragraph. Again, I can't think of a practical situation where this would be helpful. If all the images and/or links had the same styling, simple CSS would suffice, and there would be no need for the ATTR_HTML. In my case, however, this would actually work. I know that it is possible to style links using ATTR_HTML, but does anyone actually do that in practice? I don't think I ever have. If no one uses it, would it be missed? A proper solution to the problem would be to slightly change link syntax. The link syntax change will be a welcome addition, though I understand that it is not a high priority. Until then, you'll have to use workarounds (like, for example, writing the other link in raw HTML syntax within an export snippet). Yes, a personal workaround would be to use the raw HTML syntax to mark the image in my example. This has the strong disadvantage, however, of meaning the image doesn't appear at all when the document is exported to other formats, and of requiring changes to all affected documents when the syntax changes again. A more general workaround that would help everyone affected would be to temporarily modify ox-html.el so that attributes from ATTR_HTML only apply to the *first* item in the paragraph. This would have the advantage of mimicking the behavior of the old exporter (thus not breaking existing content) and of keeping images for other export formats. Of course, anyone relying on the ATTR_HTML to set attributes for every image and/or link in a paragraph would have to adopt a different workaround, but ... does anyone really do this? In my case, rather than changing all my documents to use raw HTML for the images, I will write a filter function that walks through the final HTML and removes invalid and superfluous attributes from the anchor tags. This strikes me as a rather ugly hack, though. It seems unlikely to me that this issue only comes up with the HTML exporter. Surely some documents with primary output formats of LaTeX or OpenDocument have similar requirements. I wonder how those export backends handle situations like this. Thanks again for your help and hard work. Best regards, Terry -- T.F. Torrey
[O] Publishing http links inside a begin_src
Dear list, I am unable to publish as html the following minimal mybuffer.org: #+BEGIN_SRC sh :exports code orghttp = http://orgmode.org/; #+END_SRC The Messages are Export buffer: Exporting... org-babel-exp processing... Setting up indent for shell type bash setting up indent stuff Indentation variables are now local. Indentation setup for shell type bash And the program crashes. Any suggestions? Best regards Emilio Using Org-mode version 7.9.3e (7.9.3e-3-gb07a9b @ /usr/share/emacs/24.3.50/lisp/org/) -- = Emilio Torres Manzanera Fac. de Comercio - Universidad de Oviedo c/ Luis Moya 261, E-33203 Gijón (Spain) Tel. 985 182 197 email: tor...@uniovi.es =
Re: [O] Bug: New HTML exporter incorrect attributes
tftor...@tftorrey.com (T.F. Torrey) writes: You don't assign attributes to an image in a paragraph, you assign attributes to the paragraph itself. It would be nice if there actually was a way to assign an attribute to a paragraph, so that the ATTR_HTML: class=XXX syntax would export as p class=XXX, but that is a different issue. It would be ATTR_HTML: :class XXX. I try to unify syntax for attributes with syntax for Babel and AFAICT, `html' is the last back-end to have key=value syntax. For the time being, Org syntax doesn't allow to specify attributes per link object. I think what you are saying is that the current intended behavior is for whatever is specified by ATTR_HTML to apply to every image or link in the paragraph. No. I am saying that ATTR_HTML behaviour in _undefined_ when a paragraph contains more than one link, as it has always been. If you carefully look at Org manual (in application with previous exporter framework), in Images in HTML export, you will notice that HTML attributes only apply to a single link pointing to an image, not to a paragraph containing many links. As a consequence, attributes will be assigned to every link within the paragraph. Is this behavior helpful to anyone in any practical circumstances? I never said it was. It's not even a feature. I'm just explaining what is happening. Moreover, this means that, not only does the new exporter fail where the old one succeeded, I worked hard to make the new export framework compatible with defined behaviour of previous exporter, not with handy undocumented side-effects it may have. It seems to me that, whether the user is happy with the output or not, the HTML exporter ought to produce valid HTML. I agree. But, in this case, you're using undefined Org syntax (which, admittedly, used to work for you). If there's a simple patch that mimics this for html back-end, I don't mind applying it. But it still won't make up for a real solution. Unless, that is, it is decided that this behaviour is an official feature supported by Org, in which case, it should be added to the manual. A more general workaround that would help everyone affected would be to temporarily modify ox-html.el so that attributes from ATTR_HTML only apply to the *first* item in the paragraph. This would have the advantage of mimicking the behavior of the old exporter (thus not breaking existing content) and of keeping images for other export formats. Of course, anyone relying on the ATTR_HTML to set attributes for every image and/or link in a paragraph would have to adopt a different workaround, but ... does anyone really do this? It would solve your problem. But what if someone starts a paragraph with a regular link and thereafter, add an image? ATTR_HTML attributes would never reach it. Again, there's no proper solution besides modifying link syntax. Regards, -- Nicolas Goaziou
Re: [O] [Bug] Export Coding System
Achim Gratz strom...@nexgo.de writes: It doesn't fix the problem when I want to export the file in a different encoding (for instance by customizing Org Export Latex Coding System), that would require a second step of re-setting the buffer-file-coding-system before using it to determine what to write into the inputenc option. Would the following patch work? Regards, -- Nicolas Goaziou From 2f2591719cc41e7312401ce7368b4bbbdde2c8ad Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou n.goaz...@gmail.com Date: Sat, 23 Feb 2013 11:29:45 +0100 Subject: [PATCH] ox-latex: Set inputenc option according to `org-export-coding-system' * lisp/ox-latex.el (org-latex-guess-inputenc): Set inputenc option according to `org-export-coding-system'. --- lisp/ox-latex.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el index cbeaa4e..4047aa2 100644 --- a/lisp/ox-latex.el +++ b/lisp/ox-latex.el @@ -946,7 +946,7 @@ when specified inputenc option is \AUTO\. Return the new header, as a string. (let* ((cs (or (ignore-errors (latexenc-coding-system-to-inputenc - buffer-file-coding-system)) + (or org-export-coding-system buffer-file-coding-system))) utf8))) (if (not cs) header ;; First translate if that is requested. -- 1.8.1.4
Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?
Hi Martin, Martin elwood...@web.de writes: I'll try to install it, test it and then get back to you with a feedback how it works as soon as I can. Thanks in advance for testing this! If you can help with updating the manual wrt this change, please go ahead. Best, -- Bastien
Re: [O] ox-texinfo.el copyright
Hi Nick, Nick Dokos nicholas.do...@hp.com writes: The head of ox-texinfo.el says , | ;;; ox-texinfo.el --- Texinfo Back-End for Org Export Engine | | ;; Copyright (C) 2012, 2013 Jonathan Leech-Pepin | ;; Author: Jonathan Leech-Pepin jonathan.leechpepin at gmail dot com | ;; Keywords: outlines, hypermedia, calendar, wp | ;; | ;; This file is not part of GNU Emacs. ` Presumably that should be changed before too long (as in: before the next release)? There are a few more: org-colview-xemacs.el:;; This file is part of Org mode, it is not part of GNU Emacs. ox-odt.el:;; This file is not part of GNU Emacs. ox-publish.el:;; This file is not part of GNU Emacs. ox-texinfo.el:;; This file is not part of GNU Emacs. I fixed this, except for org-colview-xemacs.el, which is not part of GNU Emacs but only of Org. Thanks, -- Bastien
Re: [O] ob-doc-R-extended.org
Hi Jay, Jay Kerns gjkerns...@gmail.com writes: Alright, here goes: it looks like the maint branch does not yet include the new exporter (ox-latex.el and such). Indeed. The whole point of my working on this to begin with was to get something compatible with the new exporter, so rather than go back all over again to make something work with something that's set to be outdated in the coming months (weeks?) anyway, I'd rather sit tight on the work done so far and patiently look forward to the new exporter's merge from master to maint. This should happen before the end of March. In the meantime, the latest updated draft (little more than some tweaks of Erik Iverson's original work) is here: https://github.com/gjkerns/org-mode-R-tutorial Thanks -- another issue for Worg (on top of the maint/master issue) is that allowing evaluation of code blocks, R code blocks included, is not permitted. So the document can exhibit those R blocks, but the resulting .png should be produced outside Worg and included there as pictures. I've confirmed just now that it successfully exports to PDF/HTML under the new exporter based on a freshly pulled org from git mere minutes ago. There's still work to be done, and I welcome suggestions/corrections in the balance of time between now and when some rendition of this can safely land on Worg. I'm offline right now and can't test. I hope someone else on the list can help with this. Thanks, -- Bastien
Re: [O] [PATCH] session with python-mode.el complains of void py-toggle-shells
Hi Andreas, Andreas Röhler andreas.roeh...@easy-emacs.de writes: ob-python.el patch again I applied a more complete patch, turning `org-babel-python-command' and `org-babel-python-mode' into defcustoms. `org-babel-python-mode' will not default to 'python-mode until 'python-mode is featured, so users will typically want to set this variable, exposing it as a defcustom is useful IMO. Thanks for the patch! -- Bastien
Re: [O] Getting Blorgit working on a remote server
Hi Marko, ma...@dimjasevic.net (Marko Dimjašević) writes: I'm trying to setup Blorgit on my server, and I believe I am doing something wrong because I can't navigate pages the way I want in my web browser. I managed to setup Blorgit locally on my laptop and it is working just fine. The problem I have is when I want to deploy it to my server. On my server my main web server is nginx which forwards all requests for the /marko/research-notes/ location to port 8192, and Sinatra web server is listening on port 8192. I can see the index page load in my browser (but without CSS), and when I click on a link to another page nothing happens. I can see the http requests both in nginx's and Sinatra's log. I have Emacs running and I loaded the org-interaction.el file as instructed at: http://orgmode.org/worg/blorgit.html This is how I start the web server (when in /var/www/blorgit): ./run.ru -sthin -p8192 I'd appreciate any help. Just tell me what information you need. I'm not familiar with Blorgit to help, but my guess is that relative paths are not interpreted correctly. Please tell us what Org version you use and give a minimal example .org file, together with the .html produced, if my guess is right we will spot it quickly. Thanks, -- Bastien
Re: [O] org-bullets extension
E Sabof esa...@gmail.com writes: Jambunathan K kjambunat...@gmail.com writes: (font-lock-add-keywords 'org-mode `((\\(?:^\\(?1:\\*+\\)[[:blank:]]\\) (0 (progn (compose-region (match-beginning 1) (match-end 1) (pcase (length (match-string 1)) (1 ?\u2219) (2 ?\u2022) (3 ?\u25c9) (_ ?\u25CB))) nil) I have now added this snippet to the Worg FAQ (in the section Can I use another character than * to start a headline?) and mentioned org-bullets.el there too. -- Bastien
Re: [O] block quotes in prose?
Hi Peter,
Peter Salazar cycleofs...@gmail.com writes:
What about John Hendy's suggestion of finding a face I like, and then
adding ^ text... to the list of things org fontifies with that
style? ('In other words, add ^ text regexp to the existing hunt
for lines that start with #+ in order to get src code fontification
applied.')
Is this feasible?
Use this somewhere in your configuration:
(font-lock-add-keywords
'org-mode '((^\\(:+\\) 1 (compose-region (match-beginning 1)
(match-end 1) ? ) nil)))
M-x org-mode RET in an org-mode buffer if you evaluate this sexp after
you visited the file, otherwise the change will not be visible.
HTH,
--
Bastien
Re: [O] org-unmodified asks to revert buffer if file was modified outside emacs
Hi Nicolas, Nicolas Richard theonewiththeevill...@yahoo.fr writes: Short story is : if you call org-agenda-list and some agenda files have been modified outside emacs (e.g. by some revision control system), the command fails if the user choose to revert the file when asked, leaving a blank agenda in which 'g' does not work. Does it need a fix ? Which fix ? Good questions. I think it's acceptable to get this warning when an agenda file has been changed outside of Emacs. But having it twice is clearly wrong. The problems lies in `org-agenda-prepare-buffers' which modifies the properties of agenda files. The deeper problem comes from Emacs, as IMHO changing the properties of the buffer should be fine even when the file has been changed outside, because the text properties of the buffer are part of the buffer, not of the file. remove-text-properties, set-text-properties etc. always ask for a confirmation when the underlying file has been changed outside Emacs. So for now I don't know how to fix this in Org. I will ping Emacs developers for the rational behind the current behavior of remove-text-properties and friends. Thanks, -- Bastien
Re: [O] TeX-master: TeX-master is let-bound
Hi Christopher, Christopher Schmidt christop...@ch.ristopher.com writes: In org-latex.el, within the binding: (if to-buffer (unless (eq major-mode 'latex-mode) (latex-mode)) (save-buffer)) The problem is not in master anymore, but we still need to fix it for maint, from which 7.9.4 will be released soon, and which will be part of Emacs 24.3. 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 I still cannot reproduce this. I add AUCTeX from ELPA, then I emacs -Q and loaded autoload-auctex.el to make sure the autoloads were correct. I have this in my minimal config: (add-to-list 'auto-mode-alist '(\\.tex\\' nil TeX-LaTeX-mode)) Even in this case, with Org from maint, C-c C-c in the temporary buffer returns an error about the buffer not associated with the file (which is what I expected), not an error about TeX-master. I've closely read the thread started by Tassilo, but I don't think we are in the same boat: this thread is about defvar'ing a variable that is currently let-bound, not about let-binding a variable that is otherwise defvar'ed. Please let me know if you have another recipe to reproduce the bug, I want to get rid of this issue before 7.9.4. Thanks, -- Bastien
Re: [O] Langage export for open office
Hi Steve, Steve Prud'Homme sprud...@gmail.com writes: Can I change, like the pdf export, de langage of table of content to table des matières in french. Use #+LANGUAGE: fr #+OPTIONS: toc:t in your Org file and the table of contents should be included. There is a known issue with Org versions before commit 86499c but this issue is gone since then. If you want to replace Sommaire by something else, customize the variable `org-export-language-setup'. HTH, -- Bastien
Re: [O] org-odt: command line options for soffice bug?
Hi Vinh, Vinh Nguyen vinhdi...@gmail.com writes: After some debugging, it appears my soffice command takes a single dash (-), not double dash (--) for command line arguments. When I change to soffice -headless -convert-to %f%x -outdir %d %i in org-odt.el, things seem to work. I am running org-mode 7.9.3e on Emacs 24.1.50.1 and LibreOffice 3.3.4 on Ubuntu 11.04. Not sure if this is specific to me or not, but it should be fixed in org-mode. Thanks! Since this looks like to be an issue for Ubuntu 11.04 only and since you can customize `org-export-odt-convert-processes' (from 7.9.x) or `org-odt-convert-processes' (from master), we don't really need to change Org for this. Thanks, -- Bastien
Re: [O] [new exporter] 2 questions
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Nicolas Goaziou writes:
It creates this command in the .tex file:
\#+begin$_\mathrm{multicols}$
It works here. Difficult to say what is wrong in your buffer without
more context.
That result looks exactly like my problem with multiline \[...\],
i.e. the parser found something it considers an element inside the
multicols block and that made the block itself look like random text
that needs to be escaped.
Yes, that's a problem.
I don't think \[ .. \] constructs and arbitrary blocks should allow
comma-escaping, that would be unreadable. But their content should
not be parsed further as Org syntactic elements.
Nicolas, how hard would it be to let the parser DTRT here in both
cases?
--
Bastien
Re: [O] Has anybody noticed ellipses instead of the top line of the window?
Hi Samuel and William, I still cannot reproduce the problem consistently and it seems hard to reproduce. Let's try to reproduce it with emacs -Q first, then consider customization later on. Also, I don't think we can prevent the users from ending up with wrong ellipses in *all* circumstances. `org-catch-invisible-edits' was a step in this direction, preventing users to accidentally delete hidden regions, but it's impossible to catch all mistakes. Let's try to catch the most obvious/disturbing ones first. Thanks, -- Bastien
Re: [O] org-bullets extension
Hi Evgeni, E Sabof esa...@gmail.com writes: In any case, I've updated org-bullets to use compose-region. You can get it from here: https://github.com/sabof/org-bullets I've updated the Org's repository with a fresh version of org-bullets.el. Do you want write access to the repository so that you can do the merge yourself? If so, just send me your public key. Thanks! -- Bastien
Re: [O] Feature: Group and limit items in agenda
Hi Muchenxuan, Muchenxuan Tong demon...@gmail.com writes: There's a 'org-agenda-before-sorting-filter-function' variable. However, I'm not able to use it for grouping things, because it's used as '(mapcar org-agenda-before-sorting-filter-function list)' Would it be useful to add another function here, not used in 'mapcar', but work directly on the whole list? I don't know whether it is worthy, and I'm OK if that's not general enough to be added, because I can use defadvice anyway :) Well, I guess you don't want the grouping to take place *before* the sorting, as the sorting may destroy it, so a defadvice is the way to go here I'd say. If your defadvice can be useful for others, please consider adding it to Worg! (Just send me your public key and I'll give you write access to Worg.) Thanks, -- Bastien
Re: [O] [bug] orgstruct has suddenly become overly opinionated about legal keystrokes
Christopher Schmidt christop...@ch.ristopher.com writes: Eric Schulte schulte.e...@gmail.com writes: Yes this fixes the problem. Thank you. I committed this. 14df16d org.el: Use longest form when translating keys. Thanks! -- Bastien
Re: [O] Warning with latest git pull
Achim Gratz strom...@nexgo.de writes: Bastien writes: Fixed, thanks! Uh… no, you switched the wrong function in the second line (which incidentally indicates that this branch of the conditional never sees any testing). Fixed in master by using org-float-time. Indeed, thanks for fixing this. I checked in XEmacs 21.5 and it has float-time, so maybe we wouldn't need a compatibility function after all, but I don't know when XEmacs introduced float-time. Mhh... the less compatibility functions the better. I found this ChangeLog entry in XEmacs 21.5-b33: 2010-05-30 Aidan Kehoe keh...@parhasard.net * subr.el (float-time): Add this function, available in editfns.c in GNU. And time-to-seconds seems absent -- but it seems absent from *any* version of XEmacs I could check (21.4.1, 21.4.9, 21.5.9). So yes, I think it's safe to remove this compat function. Let me know if you find time-to-seconds in 2010 versions of XEmacs. Thanks, -- Bastien
Re: [O] [new exporter] 2 questions
Bastien b...@altern.org writes:
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Nicolas Goaziou writes:
It creates this command in the .tex file:
\#+begin$_\mathrm{multicols}$
It works here. Difficult to say what is wrong in your buffer without
more context.
That result looks exactly like my problem with multiline \[...\],
i.e. the parser found something it considers an element inside the
multicols block and that made the block itself look like random text
that needs to be escaped.
Yes, that's a problem.
I don't think \[ .. \] constructs and arbitrary blocks should allow
comma-escaping, that would be unreadable. But their content should
not be parsed further as Org syntactic elements.
Nicolas, how hard would it be to let the parser DTRT here in both
cases?
IMO the parser already DTRT. In which case do you think it doesn't?
Regards,
--
Nicolas Goaziou
Re: [O] Bug: org-mode-keys Symbol is void [7.9.3e (7.9.3e-dist @ c:/Program Files/emacs-24.1/lisp/org-7.9.3e/lisp/)]
Hi Evan, `org-mode-keys' is not an Org function, so I suspect something is wrong with your setup. Did you borrow the `org-mode-keys' function from another setup? What is the value of `org-export-preprocess-after-include-files-hook'? HTH, -- Bastien
Re: [O] [Bug] Export Coding System
Nicolas Goaziou writes: Would the following patch work? Not for LaTeX export AFAICS, ox-latex doesn't seem to use org-export-coding-system. But that'd arguably be a bug in ox-latex, then (more specifically org-latex-guess-inputenc), which is easily fixed after that patch has been applied. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] [Feature Request] Cross headings in tables
Achim Gratz strom...@nexgo.de writes: But going this route takes us even further from Your life in plain text. towards Your life in another programming language. because you will need a special viewer or editor to make sense of it for all but the most trivial cases. Point taken too -- this is even more relevant considering the fact that there are .org files parsers outside of Org. Tables are one of the Wow! features in Org, using |~~~| to separate the header would be all right I guess (especially considering that the regexp should be safe enough with no false-positive.) -- Bastien
Re: [O] Warning with latest git pull
Bastien writes: And time-to-seconds seems absent -- but it seems absent from *any* version of XEmacs I could check (21.4.1, 21.4.9, 21.5.9). No it's there, in gnus/time-date.elc — maybe your versions are all without Gnus? So yes, I think it's safe to remove this compat function. Let me know if you find time-to-seconds in 2010 versions of XEmacs. I don't know which version of XEmacs is still in use, much less together with Org (and again which version of Org). I often see 21.4 versions installed in various places, but not how much use they are getting. The 21.5b32 I have installed for rudimentary testing (I still havent managed to stop the stack explosion that prevents the test suite from running) is relatively recent, so I wouldn't put it as the benchmark of compatibility. XEmacs compatibility in master is anyway broken since your reversion 04eb4b08c3 and compatibility with Emacs 22 is on shaky grounds due to b63275350f. So I'll ask this question again: which Emacs versions should Org 8 officially support? If we stick with what we have now, we'll need to make it compatible again and at least try to get testing off the ground for XEmacs, if we drop older Emacsen we will need to remove the associated cruft from Org. It's a few days of work either way, but with a possible release date approaching a decision is necessary. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] [new exporter] 2 questions
Nicolas Goaziou writes: IMO the parser already DTRT. In which case do you think it doesn't? DTRT is what you define as DTRT, so yes it does that already. At the very least it would be nice if the parser warned when it finds stray syntax pieces that are missing their match (it took me quite a while to see what was going on). If I look at the buffer I see things differently than the parser, so some way to ask what the parser thinks I'm looking at would be nice (maybe that exists already, I don't know). And in all these cases where something inside an object or an element looks like it might be another element or greater element, we do need a way of quoting, I'd say. 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] org-capture, datetree, and tags
Bastien b...@altern.org writes: Hi Tim, Tim Burt tcb...@rochester.rr.com writes: : (defun org-datetree-find-year-create (year) :(let ((re ^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t]*\\(:[[:alnum:]_@]*\\)*:*[ \t]*$) : match) I've tested with the following headlines: - 2013 - both with and without trailing spaces - 2013 :abc: - 2013 :abc123: - 2013 :abc123:_underscore:@attaboy:: - 2013 :noexport: Any comments on the regular expression are welcome before I make patch. Thanks for working on fixing this. The more or less standard regexp for tags-till-end-of-line is this: :[[:alnum:]_@#%:]*[ \t]*$ ^ With * if you want to match headlines with no tag. I may have misapplied what you suggested, but the new regexp (see below) does not work on a year headline without tags. : (defun org-datetree-find-year-create (year) :(let ((re ^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t]*\\(:[[:alnum:]_@#%:]*[ \t]*$\\)) : match) However, the suggestion helped me find the following in org-todo-line-tags-regexp \\(.*?\\([ \t]:[[:alnum:]:_@#%]+:[ \t]*\\)?$\\) Applying this regexp worked on a tag-free headline (both with and without trailing spaces) : (defun org-datetree-find-year-create (year) :(let ((re ^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)\\(.*?\\([ \t]:[[:alnum:]:_@#%]+:[ \t]*\\)?$\\)) : match) Please have a look at this page before submitting a patch: http://orgmode.org/worg/org-contribute.html#sec-5 Will do. Thanks! -- Tim Burt www.rketburt.org It is healthful to every sane man to utter the art within him; -- GK Chesterton
Re: [O] [Feature Request] Cross headings in tables
Nicolas Goaziou writes: I think the cleanest way to implement this would be to _not_ modify Org syntax, because it is export back-end very specific. Something like: #+attr_html: :header-groups (1 3) | This | will | | be| a header | |---+---| | This | won't | |---+---| | This will | be too| |---+---| | This | won't too | You are talking about formulas, so, perhaps you have plans for the spreadsheet. Anyway, if Org syntax changes, org-element.el will have to be updated accordingly, and so will have all the back-ends. I've been thinking about this some more. We've had enough inquiries on how to import tables from R or other programs and give it headers and other decorations, maybe even formulas without having to construct the table as Org syntax in the other language. If we made such attributes _table_ attributes (i.e. extend the table model of Org and not just some decoration in the export) then this would become an easy thing to do. So if a modification in this direction is in the cards, I certainly support this proposal. Defining a more user-friendly syntax for the main features so that most of that complexity would be out of sight most of the time shouldn't be too difficult. It adds an extra step to the normalization of tables before import/export, but the added functionality should make up for that many times over. 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] [new exporter] 2 questions
Achim Gratz strom...@nexgo.de writes: Nicolas Goaziou writes: IMO the parser already DTRT. In which case do you think it doesn't? DTRT is what you define as DTRT, so yes it does that already. At the very least it would be nice if the parser warned when it finds stray syntax pieces that are missing their match (it took me quite a while to see what was going on). If I look at the buffer I see things differently than the parser, The parser parses Org syntax. If you see something else, unless there is an obvious bug, then you are expecting the Org syntax to be different from what it is. It's even the goal of the parser: to define the way to read Org syntax. Actually it is very simple to understand: elements have precedence over objects. So in the following case: --8---cut here---start-8--- x x x xxx x xx xx xx x x xx x x xx - item 1 - item 2 --8---cut here---end---8--- there's a paragraph followed by a plain list, no matter what is found within the paragraph. And it's still the case when we replace x with tricky contents like: --8---cut here---start-8--- Some paragraph, something that looks like a link start [[#eisetu][and something that looks like a math snippet \(2 + 3 - item 1 - item 2 --8---cut here---end---8--- so some way to ask what the parser thinks I'm looking at would be nice (maybe that exists already, I don't know). Usually fontification is a good indicator. Unfortunately, Org fontification doesn't rely on the parser at the moment, so there are some discrepancies. Also, you're thinking backwards here: the parser doesn't have to think about what you're looking at, as it knows it. Alas it can't know what you're thinking you're looking at. Anyway you can use (org-element-context) to know where point currently is. And in all these cases where something inside an object or an element looks like it might be another element or greater element, we do need a way of quoting, I'd say. No element can be found within an object. So far, I don't see a need for quoting. In your previous example, you know (or should know) that - as the first non-white string in a line defines an item. You keep wanting to see a mathematical operation, probably because you're focused on the LaTeX snippet you're writing, but you're wrong wrt Org syntax. Regards, -- Nicolas Goaziou
Re: [O] [Bug] Export Coding System
Achim Gratz strom...@nexgo.de writes:
Nicolas Goaziou writes:
Would the following patch work?
Not for LaTeX export AFAICS, ox-latex doesn't seem to use
org-export-coding-system. But that'd arguably be a bug in ox-latex,
then (more specifically org-latex-guess-inputenc),
I don't understand your answer.
My default coding system is utf-8 and inputenc option is AUTO. When
I eval:
(setq org-export-coding-system 'iso-latin-1)
and export some test buffer to LaTeX, with the suggested patch, I get:
\usepackage[latin1]{inputenc}
So it looks like `org-export-coding-system' variable is taken into
consideration, doesn't it?
which is easily fixed after that patch has been applied.
What fix are you talking about?
For now, I apply the previous patch.
Regards,
--
Nicolas Goaziou
Re: [O] Warning with latest git pull
Hi Achim, Achim Gratz strom...@nexgo.de writes: Bastien writes: And time-to-seconds seems absent -- but it seems absent from *any* version of XEmacs I could check (21.4.1, 21.4.9, 21.5.9). No it's there, in gnus/time-date.elc — maybe your versions are all without Gnus? Yes, my versions come without Gnus. I directly downloaded them from xemacs.org (which is completely outdated by the way.) So yes, I think it's safe to remove this compat function. Let me know if you find time-to-seconds in 2010 versions of XEmacs. I don't know which version of XEmacs is still in use, much less together with Org (and again which version of Org). I often see 21.4 versions installed in various places, but not how much use they are getting. The 21.5b32 I have installed for rudimentary testing (I still havent managed to stop the stack explosion that prevents the test suite from running) is relatively recent, so I wouldn't put it as the benchmark of compatibility. XEmacs compatibility in master is anyway broken since your reversion 04eb4b08c3 If you see a way of re-reverting this without breaking the various way to install Org in Emacs, let me know. and compatibility with Emacs 22 is on shaky grounds due to b63275350f. org-condition-case-unless-debug is not in maint or master anymore, so I guess this problem is gone. Do you confirm this? So I'll ask this question again: which Emacs versions should Org 8 officially support? If we stick with what we have now, we'll need to make it compatible again and at least try to get testing off the ground for XEmacs, if we drop older Emacsen we will need to remove the associated cruft from Org. It's a few days of work either way, but with a possible release date approaching a decision is necessary. Official support is useful to officially declare something as a bug or not. But I'm not sure it's worth officially declaring that we officially support this version and not this one. We are not Org LTS. We are just a few random hackers trying to do and share their best :) But you're right, we need to publicly set a goal, at least. I hereby declare that I want Org to be fully functional for Emacs 23 and older, and I wish Org can be reasonably functional for Emacs 23 and XEmacs. XEmacs users and Emacs-22 users, please help reporting comptability bugs, or you'll be ignored till the Dawn of Apocalypse. :) -- Bastien
Re: [O] [new exporter] 2 questions
Nicolas Goaziou writes: The parser parses Org syntax. If you see something else, unless there is an obvious bug, then you are expecting the Org syntax to be different from what it is. It's even the goal of the parser: to define the way to read Org syntax. That's what I said. You also defined The Way Things Are(TM) to make the job of parsing easier and faster. I can also understand that. But I (sometimes at least) also simply use Org and I run into things that should have a solution, other than Don't do that!. Some paragraph, something that looks like a link start [[#eisetu][and something that looks like a math snippet \(2 + 3 - item 1 - item 2 The example was slightly different and I think that matters for the discussion. Note that those terms span the better part of a line and I'm usually using at least 130 chars wide lines. --8---cut here---start-8--- Some paragraph, something that looks like a link start [[#eisetu][and something that looks like a math snippet # \[ R = term1 - term2 + term3 \] # end of the paragraph started above. --8---cut here---end---8--- Org sees that as a paragraph with some wierd ending, a list with two items and another paragraph with a wierd beginning. The user doesn't even start to think about it in this way until the exporter stops with a LaTeX error. Also, you're thinking backwards here: the parser doesn't have to think about what you're looking at, as it knows it. Alas it can't know what you're thinking you're looking at. The question is if that simplification in parsing is worth the unintuitive result. The main reason for this is that the paragraph parsing doesn't consider objects in the paragraph at all during parsing. If the objects would be parsed directly when they are encountered, it would be clear that the two extra terms are not a list. Anyway you can use (org-element-context) to know where point currently is. Thanks. And in all these cases where something inside an object or an element looks like it might be another element or greater element, we do need a way of quoting, I'd say. No element can be found within an object. A list was found inside what the user intended to be a LaTeX fragment. It also made two paragraphs out of what should have been a single one. The user found out only after trying to export the document. So far, I don't see a need for quoting. In your previous example, you know (or should know) that - as the first non-white string in a line defines an item. You keep wanting to see a mathematical operation, probably because you're focused on the LaTeX snippet you're writing, but you're wrong wrt Org syntax. Or maybe the Org syntax is wrong w.r.t. usability and robustness. The same issue is encountered often enough with blocks (you've answered quite a number of those questions): they are suggestive to the user of being self contained, but Org syntax says they aren't. I call that a trap for the unwary. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Publishing http links inside a begin_src
Hi Emilio, Emilio Torres Manzanera tor...@uniovi.es writes: I am unable to publish as html the following minimal mybuffer.org: #+BEGIN_SRC sh :exports code orghttp = http://orgmode.org/; #+END_SRC I'd try this: #+BEGIN_SRC sh :exports code orghttp=http://orgmode.org/; #+END_SRC With no whitespaces around the = sign. HTH, -- Bastien
Re: [O] Warning with latest git pull
Bastien writes: No it's there, in gnus/time-date.elc ― maybe your versions are all without Gnus? Yes, my versions come without Gnus. I directly downloaded them from xemacs.org (which is completely outdated by the way.) Which means that our compatibility function doesn't provide compatibility with XEmacs anyway. org-condition-case-unless-debug is not in maint or master anymore, so I guess this problem is gone. Do you confirm this? I haven't checked Emacs 22 ever since, so I don't know. Doing a full compatibility matrix test like I did last time takes time and I should probably script it, let me see when I can get to that. But you're right, we need to publicly set a goal, at least. I hereby declare that I want Org to be fully functional for Emacs 23 and older, and I wish Org can be reasonably functional for Emacs 23 and XEmacs. XEmacs users and Emacs-22 users, please help reporting comptability bugs, or you'll be ignored till the Dawn of Apocalypse. :) I should have seen this coming. Now, if that's how we do things these days: I hereby declare that XEmacs compatibility is broken already and he who wants to have this corrected should bring a working version of ert for XEmacs. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] [Bug] Export Coding System
Nicolas Goaziou writes:
Not for LaTeX export AFAICS, ox-latex doesn't seem to use
org-export-coding-system. But that'd arguably be a bug in ox-latex,
then (more specifically org-latex-guess-inputenc),
I don't understand your answer.
My default coding system is utf-8 and inputenc option is AUTO. When
I eval:
(setq org-export-coding-system 'iso-latin-1)
The LaTeX exporter used to have a custom variable
org-export-latex-coding-system for this. This variable is not evaluated
anymore but still visible in customize due to the fact that the new
exporter didn't override the definition from the old exporter. So it's
no wonder that nothing changes when I customize away on this variable.
The only new exporter that defines its own coding system is currently
the HTML exporter.
and export some test buffer to LaTeX, with the suggested patch, I get:
\usepackage[latin1]{inputenc}
So it looks like `org-export-coding-system' variable is taken into
consideration, doesn't it?
Yes, but I was looking at the example in the HTML exporter that would
prefer its own coding system over the general export coding system and
expected to see something similar.
What fix are you talking about?
Introducing and using a defcustom specifically for LaTeX export (if
anything at all).
For now, I apply the previous patch.
Please apply the second one, too.
Now I'll have to go and see what twisted ways it takes for the old
exporter defcustoms to show up in customize, they shouldn't have been
there at all.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] [new exporter] 2 questions
Achim Gratz strom...@nexgo.de writes: Nicolas Goaziou writes: The parser parses Org syntax. If you see something else, unless there is an obvious bug, then you are expecting the Org syntax to be different from what it is. It's even the goal of the parser: to define the way to read Org syntax. That's what I said. You also defined The Way Things Are(TM) to make the job of parsing easier and faster. I can also understand that. But I (sometimes at least) also simply use Org and I run into things that should have a solution, other than Don't do that!. I gave you a solution since the beginning of this thread: use a latex environment. Some paragraph, something that looks like a link start [[#eisetu][and something that looks like a math snippet \(2 + 3 - item 1 - item 2 The example was slightly different and I think that matters for the discussion. Note that those terms span the better part of a line and I'm usually using at least 130 chars wide lines. Some paragraph, something that looks like a link start [[#eisetu][and something that looks like a math snippet # \[ R = term1 - term2 + term3 \] # end of the paragraph started above. Org sees that as a paragraph with some wierd ending, It would be interesting to know what Org judges as weird. a list with two items and another paragraph with a wierd beginning. The user doesn't even start to think about it in this way until the exporter stops with a LaTeX error. Fontification helps (or should help) here. Anyway, this problem is unrelated to the LaTeX exporter, since it only exports what parser parses. The question is if that simplification in parsing is worth the unintuitive result. The main reason for this is that the paragraph parsing doesn't consider objects in the paragraph at all during parsing. If the objects would be parsed directly when they are encountered, it would be clear that the two extra terms are not a list. It /is/ intuitive and quite simple actually. * at column 0 starts a headline, - at the beginning of a line starts a list[fn:1]... Very often, you know what you're writing just by looking at the beginning of the line. On the other hand, if you allow the first object to start to have precedence over what comes next, you're in big trouble. In fact, you may have to look dozens of lines above only to discover you had started an object before the one you were expecting to write. --8---cut here---start-8--- ~lorem ... a dozen of lines ... \[ R = term 1 - term 2 + term 3 \] end of paragraph or so I think~ --8---cut here---end---8--- Here you didn't write a math snippet. Sure, you can add a hack and arbitrary say Objects are never longer than 3 lines. Then, in this case, you didn't write a math snippet either. Also, if there's no order in which syntactical elements are parsed, the following could as well be a math snippet instead of an headline: --8---cut here---start-8--- \( * 2 \) --8---cut here---end---8--- Sorry, but it has never been the case in Org. Org has always implied classification in syntax. And that's a quite sane behaviour. Otherwise, you can never be sure about what you're writing without memorizing the complete buffer. Again, the current syntax is very regular. It can lead to surprises, I understand that, but far less than with what you expect. A list was found inside what the user intended to be a LaTeX fragment. It also made two paragraphs out of what should have been a single one. I disagree with that part. There shouldn't have been a single paragraph, and there isn't. Not in Org syntax, at least. Or maybe the Org syntax is wrong w.r.t. usability and robustness. The same issue is encountered often enough with blocks (you've answered quite a number of those questions): they are suggestive to the user of being self contained, but Org syntax says they aren't. I call that a trap for the unwary. I just suggest to learn Org syntax. Any help to upgrade the documentation accordingly and make this task easier is welcome. Regards, [fn:1] Ok, this one has exceptions, like in src blocks, but there's also an explanation. -- Nicolas Goaziou
Re: [O] [Bug] Export Coding System
Achim Gratz strom...@nexgo.de writes: Introducing and using a defcustom specifically for LaTeX export (if anything at all). I don't think it is really important, considering you can also bind it buffer-wise. On the other hand, a back-end independent variable is much more easy to handle. Now I'll have to go and see what twisted ways it takes for the old exporter defcustoms to show up in customize, they shouldn't have been there at all. As I explained in my announcement for new export framework, this is due to customize autoloads from bundled Org (cus-load.el). As soon as you call customize, these old friends are loaded. Regards, -- Nicolas Goaziou
Re: [O] Bug: :sitemap-file-entry-format export incorrectly [7.9.3e (7.9.3e-dist @ /usr/share/emacs/site-lisp/org/)]
Hi Richard, Richard Huang richard.h.huac...@gmail.com writes: When I use `org-publish-current-project` to generate a sitemap with `:sitemap-file-entry-format %d %t` option, the sitemap.org looks like this: ``` #+TITLE: Sitemap for project blog + [[file:sample.org][2013-02-22 sample.org]] ``` then it will be exported to sitemap.html, incorrectly, looks like this: This should be fixed now, please let us know. Thanks for reporting this issue! -- Bastien
Re: [O] `org-drill' broken in recent commits git commits
York Zhao gtdplatf...@gmail.com writes: But anyways, this is no longer a big problem and it is tolerable. Thank you very much for the help. You're welcome, -- Bastien
Re: [O] tags pdfs vs. html
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: There are already two ways to configure tags in latex back-end: `org-latex-format-headline-function' (which is easy to use) and headline filters. I ended up extracting the example function that was in the docstring of `org-latex-format-headline-function' and the code now use this for `org-latex-format-headline-default-function'. That was we have both compatibility and the flexibility you introduced. Hope that's fine with you! Best, -- Bastien
Re: [O] tags pdfs vs. html
Hello, Bastien b...@altern.org writes: I ended up extracting the example function that was in the docstring of `org-latex-format-headline-function' and the code now use this for `org-latex-format-headline-default-function'. That was we have both compatibility and the flexibility you introduced. Hope that's fine with you! I don't really mind, but since `org-latex-format-headline-function' can never be nil, `org-latex-headline' should be modified accordingly (i.e. default behaviour should just be removed from the function). Also, it isn't symmetrical anymore with `org-latex-format-inlinetask-function' and `org-latex-format-drawer-function'. So I think these should be changed accordingly. Regards, -- Nicolas Goaziou
Re: [O] org-unmodified asks to revert buffer if file was modified outside emacs
Bastien b...@altern.org writes: I will ping Emacs developers for the rational behind the current behavior of remove-text-properties and friends. Got the answer: `with-silent-modifications' comes to the rescue. So the issue is now fixed in master, thanks! -- Bastien
Re: [O] TeX-master: TeX-master is let-bound
Bastien b...@altern.org writes: Hi Bastien, The problem is not in master anymore, That's great! I add AUCTeX from ELPA, then I emacs -Q and loaded autoload-auctex.el to make sure the autoloads were correct. I can reproduce this. (Current maint, GNU Emacs 24.2.93.2) Did you push AUCTeX's directory in load-path? Does the docstring of latex-mode mention AUCTeX? I have this in my minimal config: (add-to-list 'auto-mode-alist '(\\.tex\\' nil TeX-LaTeX-mode)) That is not necessary. Please let me know if you have another recipe to reproduce the bug, I want to get rid of this issue before 7.9.4. Unfortunately I see is no other easy way to reproduce this. (I am fine with wontfix in maint.) Christopher
[O] [BUG] [HTML] Export to html calls publish function
Hello, I faced a problem and I think this is a bug in new exporter, html, introduced in commit 93a70ac59805bb270d15e951a14be63b9eb1d553 ox-publish: Implement tools to resolve external fuzzy links Small test files #+BEGIN_SRC org :tangle test1.org ,#+TITLE: This is test1 file ,#+AUTHOR: Vladimir Lomov ,* Purpose of this document The purpose of this document is to show or not to show a problem with exporting Org document into html. #+END_SRC #+BEGIN_SRC org :tangle test2.org ,#+TITLE: Test document number 2 ,#+AUTHOR: Vladimir Lomov ,* What I expect from this document I expect that when exported to html this file will have correct URL, http://www.orgmode.org, as well as link to external document, like [[file:test1.org::*Purpose%20of%20this%20document][Purpose of this document]]. #+END_SRC #+BEGIN_SRC emacs-lisp :tangle debug.el (setq load-path (cons /usr/share/emacs/site-lisp/org load-path)) (setq debug-on-error t) (require 'org) (require 'ox-html) #+END_SRC Backtrace: #+BEGIN_EXAMPLE Debugger entered--Lisp error: (error `org-publish-cache-get' called, but no cache present) signal(error (`org-publish-cache-get' called, but no cache present)) error(`org-publish-cache-get' called, but no cache present) org-publish-cache-get(/home/vladimir/tmp/test1.org) org-publish-cache-get-file-property(/home/vladimir/tmp/test1.org :numbering nil t) org-publish-resolve-external-fuzzy-link(test1.org *Purpose of this document) org-html-link((link (:type file :path test1.org :raw-link file:test1.org::*Purpose%20of%20this%20document :application nil :search-option *Purpose of this document :begin 231 :end 308 :contents-begin 282 :contents-end 306 :post-blank 0 :parent (paragraph (:begin 95 :end 310 :contents-begin 95 :contents-end 310 :post-blank 0 :post-affiliated 95 :parent (section (:begin 95 :end 310 :contents-begin 95 :contents-end 310 :post-blank 0 :parent (headline (:raw-value What I expect from this document :begin 59 :end 310 :pre-blank 1 :hiddenp outline :contents-begin 95 :contents-end 310 :level 1 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 0 :footnote-section-p nil :archivedp nil :commentedp nil :quotedp nil :CATEGORY nil :title ... :parent ...) #4)) #2)) #(I expect that when exported to html this file will have correct URL,\n 0 69 (:parent #2)) (link (:type http :path //www.orgmode.org :raw-link http://www.orgmode.org; :application nil :search-option nil :begin 164 :end 186 :contents-begin nil :contents-end nil :post-blank 0 :parent #2)) #(, as well as link to external document, like\n 0 45 (:parent #2)) #0 #(.\n 0 2 (:parent #2 #(Purpose of this document 0 24 (:parent #0))) #(Purpose of this document 0 24 (:parent (link (:type file :path test1.org :raw-link file:test1.org::*Purpose%20of%20this%20document :application nil :search-option *Purpose of this document :begin 231 :end 308 :contents-begin 282 :contents-end 306 :post-blank 0 :parent (paragraph (:begin 95 :end 310 :contents-begin 95 :contents-end 310 :post-blank 0 :post-affiliated 95 :parent (section (:begin 95 :end 310 :contents-begin 95 :contents-end 310 :post-blank 0 :parent ...) #4)) #(I expect that when exported to html this file will have correct URL,\n 0 69 (:parent #4)) (link (:type http :path //www.orgmode.org :raw-link http://www.orgmode.org; :application nil :search-option nil :begin 164 :end 186 :contents-begin nil :contents-end nil :post-blank 0 :parent #4)) #(, as well as link to external document, like\n 0 45 (:parent #4)) #2 #(.\n 0 2 (:parent #4 #(Purpose of this document 0 24 (:parent #2) (:input-file /home/vladimir/tmp/test2.org :title (Test document number 2) :html-extension html :html-link-home :html-link-up :html-mathjax :html-postamble auto :html-preamble t :html-style :html-style-extra :html-style-include-default t :html-style-include-scripts t :html-table-tag table border=\2\ cellspacing=\0\ cellpadding=\6\ rules=\groups\ frame=\hsides\ :creator Generated by a href=\http://orgmode.org\;Org/a mode 7.9.3e in a href=\http://www.gnu.org/software/emacs/\;Emacs/a 24.3.50.1. :with-latex t :infojs-opt nil :author (Vladimir Lomov) :date nil :description nil :email vladi...@smoon3.smoon.org :exclude-tags (noexport) :headline-levels 3 :keywords nil :language en :preserve-breaks nil ...)) org-export-data((link (:type file :path test1.org :raw-link file:test1.org::*Purpose%20of%20this%20document :application nil :search-option *Purpose of this document :begin 231 :end 308 :contents-begin 282 :contents-end 306 :post-blank 0 :parent (paragraph (:begin 95 :end 310 :contents-begin 95 :contents-end 310 :post-blank 0 :post-affiliated 95 :parent (section (:begin 95 :end 310 :contents-begin 95 :contents-end 310 :post-blank 0 :parent (headline (:raw-value What I expect from this document :begin 59 :end 310 :pre-blank 1 :hiddenp outline :contents-begin 95 :contents-end 310 :level 1 :priority nil :tags nil
Re: [O] Publishing http links inside a begin_src
Bastien b...@altern.org writes: From: Bastien b...@altern.org To: tor...@uniovi.es Cc: emacs-orgmode@gnu.org Subject: Re: Publishing http links inside a begin_src Flags: seen Date: sáb 23 feb 2013 14:17:22 CET Maildir: /inbox Hi Emilio, Emilio Torres Manzanera tor...@uniovi.es writes: I am unable to publish as html the following minimal mybuffer.org: #+BEGIN_SRC sh :exports code orghttp = http://orgmode.org/; #+END_SRC I'd try this: #+BEGIN_SRC sh :exports code orghttp=http://orgmode.org/; #+END_SRC With no whitespaces around the = sign. HTH, Thank you for your suggestion. But I feel that this trick does not solve the problem: When I use the last version of org Org-mode version 7.9.3e (7.9.3e-3-gb07a9b @ /usr/share/emacs/24.3.50/lisp/org/) I get the error (typing no spaces around the equal sign) When I use another computer with an older Org-mode version 7.8.02, both examples run smoothly. What should I do to test this issue? Best regards -- = Emilio Torres Manzanera Fac. de Comercio - Universidad de Oviedo c/ Luis Moya 261, E-33203 Gijón (Spain) Tel. 985 182 197 email: tor...@uniovi.es =
[O] seeing ??? in Ccaa rather than file name
I'm using Org-mode version 7.9.3e (7.9.3e-1194-g43c8aa @ /home/dave/.emacs.d/org/lisp/), just got the latest pull this morning, and now when I generate an agenda, I'm getting lines like 10:04.. now - - - - - ! ???:12:00.. Scheduled: TODO [#B] Change oil 12:00.. 14:00.. 16:00.. 18:00.. 20:00.. 22:00.. 24:00.. 02-24 (Sun) 02-25 (Mon) ???:12:00.. Scheduled: TODO Taxes rather than seeing the files that contain the scheduled items. It was fine yesterday, so it has to be something in the git pull from this morning. Thought I'd throw that out there and see if anyone else sees this problem. I also noticed, and I don't think it ever did this before, when I put the cursor on a listed item in the agenda, the file name shows up in the message area. Has it always done that? Maybe the two are related. Dave
Re: [O] seeing ??? in Ccaa rather than file name
Sorry, meant to say 'agenda', not 'Ccaa' Dave
Re: [O] [new exporter] 2 questions
Nicolas Goaziou writes: I gave you a solution since the beginning of this thread: use a latex environment. It is not a solution because it does not export to HTML. If I need to write the document mostly in LaTeX I can start with LaTeX and and then use some LaTeX to HTML translation. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] [BUG] [HTML] Export to html calls publish function
Hello, Vladimir Lomov lomov...@gmail.com writes: Hello, I faced a problem and I think this is a bug in new exporter, html, introduced in commit 93a70ac59805bb270d15e951a14be63b9eb1d553 ox-publish: Implement tools to resolve external fuzzy links Small test files #+BEGIN_SRC org :tangle test1.org ,#+TITLE: This is test1 file ,#+AUTHOR: Vladimir Lomov ,* Purpose of this document The purpose of this document is to show or not to show a problem with exporting Org document into html. #+END_SRC #+BEGIN_SRC org :tangle test2.org ,#+TITLE: Test document number 2 ,#+AUTHOR: Vladimir Lomov ,* What I expect from this document I expect that when exported to html this file will have correct URL, http://www.orgmode.org, as well as link to external document, like [[file:test1.org::*Purpose%20of%20this%20document][Purpose of this document]]. #+END_SRC #+BEGIN_SRC emacs-lisp :tangle debug.el (setq load-path (cons /usr/share/emacs/site-lisp/org load-path)) (setq debug-on-error t) (require 'org) (require 'ox-html) #+END_SRC It should be fixed. Note that export will not be able to resolve the search options part when you're not publishing or files do not belong to the same project. Prefer id property in this case. Thank you for reporting the problem. Regards, -- Nicolas Goaziou
Re: [O] [new exporter] 2 questions
Achim Gratz strom...@nexgo.de writes:
I gave you a solution since the beginning of this thread: use a latex
environment.
It is not a solution because it does not export to HTML.
Of course it does. Try:
--8---cut here---start-8---
Some latex
\begin{equation*}
2 + 2
\end{equation*}
--8---cut here---end---8---
and export to HTML.
Regards,
--
Nicolas Goaziou
Re: [O] [Bug] Export Coding System
Nicolas Goaziou writes: Now I'll have to go and see what twisted ways it takes for the old exporter defcustoms to show up in customize, they shouldn't have been there at all. As I explained in my announcement for new export framework, this is due to customize autoloads from bundled Org (cus-load.el). As soon as you call customize, these old friends are loaded. Welp, and its all done with symbol properties so it would really be fun to weed these out. Great. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] seeing ??? in Ccaa rather than file name
Hi David, da...@adboyd.com (J. David Boyd) writes: I'm using Org-mode version 7.9.3e (7.9.3e-1194-g43c8aa @ /home/dave/.emacs.d/org/lisp/), just got the latest pull this morning, and now when I generate an agenda, I'm getting lines like 10:04.. now - - - - - ! ???:12:00.. Scheduled: TODO [#B] Change oil 12:00.. 14:00.. 16:00.. 18:00.. 20:00.. 22:00.. 24:00.. 02-24 (Sun) 02-25 (Mon) ???:12:00.. Scheduled: TODO Taxes I cannot reproduce this problem. Can you share a minimal example (as an .org file) that I can run with emacs -q to see the problem? I also noticed, and I don't think it ever did this before, when I put the cursor on a listed item in the agenda, the file name shows up in the message area. Has it always done that? Maybe the two are related. (setq org-agenda-show-outline-path nil) to deactivate this. HTH, -- Bastien
Re: [O] [new exporter] 2 questions
Nicolas Goaziou writes: I gave you a solution since the beginning of this thread: use a latex environment. After a bit of searching: the answer was in another thread, not in answer to my original question and I read that answer as LaTeX blocks are equivalent to LaTeX environments. I see now that they are not. There is one remaining difference to a display equation or LaTeX fragment: the LaTeX environment will apparently always end the paragraph, something that LaTeX does or does not do depending on whether you surround an environment with whitespace. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] [new exporter] 2 questions
Achim Gratz strom...@nexgo.de writes: There is one remaining difference to a display equation or LaTeX fragment: the LaTeX environment will apparently always end the paragraph, Indeed. A LaTeX environment has got the same syntactical value as a paragraph (both are elements): they cannot be nested. something that LaTeX does or does not do depending on whether you surround an environment with whitespace. True, that's why there's also inline \[...\]. But you have to accept paragraph limitations (no empty line, do not start a line with list markers...). Another difference is that LaTeX environments can be given a name and a caption, allowing them to be cross-referenced. Regards, -- Nicolas Goaziou
[O] Adventures with org-footnote-auto-adjust
Aloha all, I keep footnotes in their own section and appreciate having them out of the way, where I don't have to think about them. Recently, I set #+STARTUP: fnadjust because I thought it would be nice to have the footnotes sorted and renumbered. This was a mistake in my case that lost data. I think I know how it happened, though I wasn't really paying attention to the footnotes as I worked. In the document I'm editing, I have sentences like this: If you want a list to start with a different value (e.g., 20),[fn:17] start the text of the item with ~[@20]~. As a matter of style, I prefer the footnote (which contains qualifying text, rather than a reference) be at the end of the sentence, and that it immediately follow the period. So, I cut and paste to get this: If you want a list to start with a different value (e.g., 20), start the text of the item with ~[@20]~.[fn:17] Now, the next time I insert a footnote, with C-c C-x f, I get something like this: If you want a list to start with a different value (e.g., 20),[fn:17] start the text of the item with ~[@20]~.[fn:17] The text of the original footnote, [fn:17], is lost, though the mark remains in the text. If the new [fn:17] is some distance away, then the problem of duplicate numbers isn't readily apparent in the midst of other work. Of course, I subsequently discovered that `~.[fn:17]' wasn't working and put the space back in. Now, the footnote refers to the wrong text. I've learned that there are certain conditions (I don't know how many) where the space after a sentence won't accept a footnote insertion. The example sentence is one of these. Apparently, it is the `~.' combination that triggers the condition. Org is good enough to prohibit inserting a new footnote into one of these black holes (which is how I discovered them), but it doesn't mind if I cut and paste a footnote into one. I'm not certain how much mischief this might have caused. I discovered the problem when the text of *both* footnotes in a section of the document were incorrect. In my case, org-footnote-auto-adjust doesn't perform any crucial function--it just makes the Org mode buffer seem more orderly. Given that there are black holes in the buffer, whose presence have the ability to confuse org-footnote-auto-adjust so that data are lost, should org-footnote-auto-adjust be deprecated? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] [new exporter] 2 questions
Nicolas Goaziou writes: True, that's why there's also inline \[...\]. But you have to accept paragraph limitations (no empty line, do not start a line with list markers...). Now, given that difference and the fact that these things can span over multiple lines and thus include the beginning of line (which creates the contention between different tiers of org-element's parsing hierarchy), let me ask one more time if it would be possible to escape the beginning of line (most likely and the obvious choices given Org's history would be : or ,) in a general fashion and remove it only when the (greater) elements have been parsed already and the content is about to be used. In fact if I put one of those two characters there (or anything else really that doesn't create spurious syntax) it almost works correctly already, only the stripping of the escape characters is missing. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
[O] Org-mode Talk in German
Hello, mid last year, I held a talk about Emacs Org-mode at a small hacker conference in Germany called Gulaschprogrammiernacht (GPN12) with the title Emacs Org-mode - der hackbare Notizblock in Plaintext (engl. the hackable notepad in plain text). The organization of this event recorded my talk and uploaded it to YouTube [1]. Maybe this is a talk which can be added to the org-mode talks page. My slides are also online [2] if anyone is interested. [1] https://www.youtube.com/watch?v=mUSoo4UaKBo [2] http://florian.adamsky.it/research/talks/gpn12/GPN12-Emacs-Org-mode.pdf -- Florian Adamsky http://florian.adamsky.it/
Re: [O] Warning with latest git pull
Bastien writes: I hereby declare that I want Org to be fully functional for Emacs 23 and older, and I wish Org can be reasonably functional for Emacs 23 and XEmacs. If I may say so, XEmacs and Emacs up to 23.2 are missing with-silent-modifications, preferring to make them loudly. Compatibility macro, please (you can glean it from the magit folks, you might want to check if PJ Weisberg aka Bourgouignon has FSF copyright assigned). :-) Remarks, 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] seeing ??? in Ccaa rather than file name
Bastien b...@altern.org writes: ???:12:00.. Scheduled: TODO [#B] Change oil I cannot reproduce this problem. Can you share a minimal example (as an .org file) that I can run with emacs -q to see the problem? I see the same thing. Categories that would normally set to the file name are displayed as ???. Presumably because `org-refresh-category-properties' is called inside `with-silent-modifications', which let-binds `buffer-file-name'. -- Florian Beck
Re: [O] hlines in babel output
I have the following Org document where I would like to add some extra hlines to the output. I'm using babel. I tried the ascii package but couldn't find anything giving me extra hlines. I'd also prefer to stick to just babel. I'm still looking for a good way to insert horizontal lines into generated tables. I have been trying to use Emacs Lisp to use org-table-insert-hline using (i) babel and (ii) noweb. For (i) I need to add an hline object as the second-to-last object, but I havne't been successful so far. I'd appreciate any hints. #+NAME:budget-dta #+begin_src R :colnames yes :noweb-ref TBL :exports none tt - textConnection( account p rent110 food50) ee - read.table(tt, header = TRUE) close(tt) cc - 4 ## a complicated number generated with R ee$p - ee$p * cc ee - rbind(ee, data.frame(p=sum(ee$p),account=c(total))) ee #+end_src #+NAME:test #+RESULTS: budget-dta | account | p | |-+-| | rent| 440 | | food| 200 | | total | 640 | #+BEGIN_SRC emacs-lisp :var X=test (add-to-list 'X 'hline t) #+END_SRC -- Vote for proprietary math!
Re: [O] hlines in babel output
Rasmus ras...@gmx.us writes: I have the following Org document where I would like to add some extra hlines to the output. I'm using babel. I tried the ascii package but couldn't find anything giving me extra hlines. I'd also prefer to stick to just babel. I'm still looking for a good way to insert horizontal lines into generated tables. I have been trying to use Emacs Lisp to use org-table-insert-hline using (i) babel and (ii) noweb. For (i) I need to add an hline object as the second-to-last object, but I havne't been successful so far. I'd appreciate any hints. First be sure to read the relevant page of the manual [1]. After that, something like the following should allow for arbitrary hline insertion. #+name: test #+begin_src sh seq 10 #+end_src #+begin_src emacs-lisp :var x=test (append (subseq x 0 2) (list 'hline) (subseq x 2)) #+end_src #+RESULTS: | 1 | | 2 | || | 3 | | 4 | | 5 | | 6 | | 7 | | 8 | | 9 | | 10 | Hope this helps, Footnotes: [1] http://orgmode.org/manual/hlines.html -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [org-e-texinfo] generate menu items
Hello, Jonathan Leech-Pepin jonathan.leechpe...@gmail.com writes: Hello Tom, Nicolas, I've just pushed a change that should provide the desired results. The optional title for the menu entries (as well as associated node headings) can be set using the :TEXINFO_MENU_TITLE: property. On 18 November 2012 11:22, Thomas S. Dye t...@tsdye.com wrote: Nicolas Goaziou n.goaz...@gmail.com writes: t...@tsdye.com (Thomas S. Dye) writes: Nicolas Goaziou n.goaz...@gmail.com writes: That's a bit of work, because, so far, node-property values are not parsed. So it would require to define a new class of node-properties: those with a parsed value. But then, how to decide which properties have their value parsed are parsed and which have not? Thanks for the information and explanation. Back-end-specific properties should work nicely in this case. I'll wait to see what Jonathan thinks about the original query. Assuming :EXPORT_TITLE:, :EXPORT_AUTHOR:, :EXPORT_DATE: and this one, :EXPORT_TOC_ENTRY: (?), will be the only ones being parsed, I can give it a try. If you do include these node properties I can then adjust the texinfo exporter to use the generic TOC/Optional title property rather than a backend specific one. I eventually added :OPTIONAL_TITLE: property. Get its parsed value with `org-export-get-optional-title' function. I patched ox-ascii, ox-latex and ox-html so they use it when building a TOC. I think only ox-odt and ox-texinfo are missing. Jonathan, could you have a look at it? Thank you. Regards, -- Nicolas Goaziou
[O] org-cycle hook recenter question
Hi when I cycle using shift-TAB and I go from all-content, that is just the headlines, I often don't see the top headlines in the buffer, although there would be enough space to show them. The top is truncated and a ... is shown and I need to do a ctrl-l or scroll upward to see everything. I was wondering if it would be possible to automatically recenter when the cycle goes from all-content? I tried to change the org-cycle-hook to include a line like: ((eq state 'content) (recenter 1)) and I also tried to add a (recenter-top-bottom) in org.el where org-cycle-global-status is being set to 'contents. But couldn't get it to work... what's the correct place to do this and is there a reason not to recenter by default during this cycle operation? NB: in org-cycle-hook state is tested for 'content, should it be 'contents? org-cycle-hook and org-pre-cycle-hook list both content and contents and both show up in org.el, but org-cycle-global-state seems to be only set to 'contents Arun
Re: [O] org-cycle hook recenter question
Hi Arun, On 2/23/13, Arun Persaud apers...@lbl.gov wrote: when I cycle using shift-TAB and I go from all-content, that is just the headlines, I often don't see the top headlines in the buffer, although there would be enough space to show them. The top is truncated and a ... is shown and I need to do a ctrl-l or scroll upward to see everything. This is the infamous meaningless ellipses at the top of the buffer problem. If you can provide a way to reproduce using emacs -Q, it would really help. 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] org-cycle hook recenter question
Hi [...] This is the infamous meaningless ellipses at the top of the buffer problem. If you can provide a way to reproduce using emacs -Q, it would really help. I can reproduce this with emacs -Q tmp.org. Where tmp.org is one of my org files where I removed the headers (#+...), so it's just a bunch of headlines and sublevels, starting with a toplevel headline in the first line. I'm running: C-h C-a GNU Emacs 24.2.1 (x86_64-suse-linux-gnu, GTK+ Version 3.4.4) of 2012-10-10 on build20 org-version 7.8.11 I also have the latest git-version installed, but am not sure how to use that with -Q? Let me know if I should try anything else. Arun
Re: [O] org-cycle hook recenter question
Hi Arun, On Sat, Feb 23, 2013 at 05:19:29PM -0800, Arun Persaud wrote: This is the infamous meaningless ellipses at the top of the buffer problem. If you can provide a way to reproduce using emacs -Q, it would really help. I can reproduce this with emacs -Q tmp.org. Where tmp.org is one of my org files where I removed the headers (#+...), so it's just a bunch of headlines and sublevels, starting with a toplevel headline in the first line. It would really help the devs if you could attach this tmp.org file (after removing any private information of course). Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] org-cycle hook recenter question
Suvayu Ali fatkasuvayu+li...@gmail.com wrote: Hi Arun, On Sat, Feb 23, 2013 at 05:19:29PM -0800, Arun Persaud wrote: This is the infamous meaningless ellipses at the top of the buffer problem. If you can provide a way to reproduce using emacs -Q, it would really help. I can reproduce this with emacs -Q tmp.org. Where tmp.org is one of my org files where I removed the headers (#+...), so it's just a bunch of headlines and sublevels, starting with a toplevel headline in the first line. It would really help the devs if you could attach this tmp.org file (after removing any private information of course). ... plus the steps necessary to get to the problematic point (I assume there is no problem just after the file is visited, correct?) Nick PS. I didn't go back in the thread to see whether those steps have been described already. If they have, please accept my apologies.
Re: [O] Can I refile into a journal with file+datetree?
At Fri, 22 Feb 2013 22:42:25 +0100, Martin Stemplinger wrote: Hello Org wizards, I use org-capture with file+datetree for keeping a journal which works fine. I also use mobile-org to take notes while I'm on the go. After syncing them back I'd like to refile them into my journal with an appropriate date attached. Mobile org doesn't record the date I took the note so I'd just have all entries collected under the date I refile. Is there a way to do that? Hi Martin, Maybe this will help? http://punchagan.wordpress.com/2010/07/30/refile-to-date-tree/ best, Erik Sent from my free software system http://fsf.org/.
[O] Fwd: request of numeric arguments handling by +STARTUP: content
I want to have CONTENTS showing headlines up to particular level N when open file. I couldn't find such a thing in docs and VISIBILITY can't be used since it takes no arguments too, so having multiple VISIBILITY properties in every top-level headline is a bit stupid, not saying that it can not solve the problem fully, because it also doesn't take argument for children or content. Why not handling this somewhere in +STARTUP: content N or anywhere similar? Since org-mode handles arguments for org-global-cycle, why not handle them on startup? I managed to get this behavior simply by calling the (org-global-cycle N) in find-file-hook, but this is somewhat dirty. Regards, Vitaly // Sorry if this is duplicate. I tried to send it being not subscribed before.
[O] org-drill - properties displayed during card review
I'm experimenting with org-drill. One thing that seems odd is that when reviewing a card for scoring the properties drawer is displayed. It seems unlikely that this is intended? Is it intended? If not is there some easy way I can fix it? TIA.
[O] babel and postgresql
Hi everybody, Eric, I have been starting using Babel with postgresql, R and perl, and I am loving it. I really want to thank everybody for their work. I have found one particular issue that bothers me. Say I have the following babel section: #+name: abc #+begin_src sql :engine postgresql :cmdline mydb select * from aliases limit 1; #+end_src the output is: #+name: abc | alias | uniname | | Jon t...@xyz.org| jon | Note how the column names are not separated from the body: What I want it this: #+name: | alias | uniname | |---+--| | Jon t...@xyz.org| jon | I have tracked the problem, and it is that in ob-sql.el the code of org-babel-execute:sql thinks that postgres will return a header separator, and it does not. I am not sure what is the best way to fix it, but I have come with a patch that does it (but replaced the older code). The code in org-babel-execute:sql needs to be modified so it does this only for the postgres backend: split the list into first member and rest and insert a 'hline in between. My solution is rough, but it works (sorry, I am just an elisp beginner) diff --git a/lisp/ob-sql.el b/lisp/ob-sql.el index 3586ec9..95cac85 100644 --- a/lisp/ob-sql.el +++ b/lisp/ob-sql.el @@ -170,11 +170,12 @@ This function is called by `org-babel-execute-src-block'. ) (org-table-import out-file '(16)) (org-babel-reassemble-table -(mapcar (lambda (x) - (if (string= (car x) header-delim) - 'hline -x)) -(org-table-to-lisp)) +(funcall (lambda (x) + (cons (car-safe x) + (cons 'hline (cdr-safe x)) + ) + ) + (org-table-to-lisp)) (org-babel-pick-name (cdr (assoc :colname-names params)) (cdr (assoc :colnames params))) (org-babel-pick-name (cdr (assoc :rowname-names params)) -- --dmg --- Daniel M. German http://turingmachine.org
Re: [O] babel and postgresql
It looks like my inexperience with Lisp made me ignore the obvious.
What is needed is not my patch below, but to add posgresql to the
condition of the case:
From:
(case (intern engine)
('mysql
To:
(case (intern engine)
('(postgresql mysql)
the problem is that I can't get it to work (and I could not find good
documentation for the case macro anywhere but its definition. It says
that it takes either an atom (i.e. 'mysql)
or a list (i.e. '(postgresql mysql) ) but it just does not work me.
But the code for mysql and postgres seems to be the same.
Sorry for the confusion.
--daniel
On Sat, Feb 23, 2013 at 10:42 PM, dmg d...@uvic.ca wrote:
Hi everybody, Eric,
I have been starting using Babel with postgresql, R and perl, and I am
loving it. I really want to thank everybody for their work.
I have found one particular issue that bothers me.
Say I have the following babel section:
#+name: abc
#+begin_src sql :engine postgresql :cmdline mydb
select * from aliases limit 1;
#+end_src
the output is:
#+name: abc
| alias | uniname |
| Jon t...@xyz.org| jon |
Note how the column names are not separated from the body:
What I want it this:
#+name:
| alias | uniname |
|---+--|
| Jon t...@xyz.org| jon |
I have tracked the problem, and it is that in ob-sql.el the code of
org-babel-execute:sql thinks that postgres will return a header separator,
and it does not.
I am not sure what is the best way to fix it, but I have come with a
patch that does it (but replaced the older code). The code in
org-babel-execute:sql
needs to be modified so it does this only for the postgres backend:
split the list into first member and rest and insert a 'hline in
between. My solution is rough, but it works (sorry, I am just an elisp
beginner)
diff --git a/lisp/ob-sql.el b/lisp/ob-sql.el
index 3586ec9..95cac85 100644
--- a/lisp/ob-sql.el
+++ b/lisp/ob-sql.el
@@ -170,11 +170,12 @@ This function is called by
`org-babel-execute-src-block'.
)
(org-table-import out-file '(16))
(org-babel-reassemble-table
-(mapcar (lambda (x)
- (if (string= (car x) header-delim)
- 'hline
-x))
-(org-table-to-lisp))
+(funcall (lambda (x)
+ (cons (car-safe x)
+ (cons 'hline (cdr-safe x))
+ )
+ )
+ (org-table-to-lisp))
(org-babel-pick-name (cdr (assoc :colname-names params))
(cdr (assoc :colnames params)))
(org-babel-pick-name (cdr (assoc :rowname-names params))
--
--dmg
---
Daniel M. German
http://turingmachine.org
--
--dmg
---
Daniel M. German
http://turingmachine.org
Re: [O] Warning with latest git pull
Hi Achim, Achim Gratz strom...@nexgo.de writes: Bastien writes: I hereby declare that I want Org to be fully functional for Emacs 23 and older, and I wish Org can be reasonably functional for Emacs 23 and XEmacs. If I may say so, XEmacs and Emacs up to 23.2 are missing with-silent-modifications, preferring to make them loudly. Compatibility macro, please (you can glean it from the magit folks, you might want to check if PJ Weisberg aka Bourgouignon has FSF copyright assigned). There is already this in org-macs.el: (when (and (not (fboundp 'with-silent-modifications)) (or ( emacs-major-version 23) (and (= emacs-major-version 23) ( emacs-minor-version 2 (defmacro with-silent-modifications (rest body) `(org-unmodified ,@body)) (def-edebug-spec with-silent-modifications (body))) Remarks, Rewards, -- Bastien
Re: [O] seeing ??? in Ccaa rather than file name
Hi Florian, Florian Beck f...@miszellen.de writes: Bastien b...@altern.org writes: ???:12:00.. Scheduled: TODO [#B] Change oil I cannot reproduce this problem. Can you share a minimal example (as an .org file) that I can run with emacs -q to see the problem? I see the same thing. Categories that would normally set to the file name are displayed as ???. Presumably because `org-refresh-category-properties' is called inside `with-silent-modifications', which let-binds `buffer-file-name'. Thanks for digging this further, I've fixed this now. -- Bastien
