Re: [O] Support Freemind/Freeplane export
Bastien writes: Also, the change in ox-html.el is not good IMHO: it will populate everyone's HTML code with unfamiliar strings (like #xa0; instead of nbsp;) just for the sake of keeping ox-freemind.el users happy. It also requires that the HTML is output in UTF-8. I would (reluctantly, I don't really know much about how this would work) suggest that the export should always be done with symbolic entities and a post-export filter should then replace them with whatever the particular backend prefers. Does that work? 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] List admin: Plain text attachments appearing in the digest
Bastien writes: What maximum size is it now? What maximum size would you like? Only the list admin can see that setting. But the standard configuration is to send the digest at fixed intervals with no size cap, IIRC. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] List admin: Plain text attachments appearing in the digest
Achim Gratz strom...@nexgo.de writes: Bastien writes: What maximum size is it now? What maximum size would you like? Only the list admin can see that setting. Yes -- I'm asking what James wants to ask the list admins if they think it would be a sensible default and if they can implement it. -- Bastien
Re: [O] Support Freemind/Freeplane export
Achim Gratz strom...@nexgo.de writes: It also requires that the HTML is output in UTF-8. I would (reluctantly, I don't really know much about how this would work) suggest that the export should always be done with symbolic entities and a post-export filter should then replace them with whatever the particular backend prefers. Does that work? This seems a good idea to me. Nicolas, do you think so? -- Bastien
Re: [O] Beamer presentation using new exporter
Vikas Rawal vikasli...@agrarianresearch.org writes:
I have been trying to figure out how to do this. I saw Suvayu's config
files which he has kindly kept on github
(https://github.com/suvayu/.emacs.d).
I tried to evaluate the following lines
(add-to-list 'org-latex-classes
'(beamer
\\documentclass\[presentation\]\{beamer\}
(\\section\{%s\} . \\section*\{%s\})
(\\subsection\{%s\} . \\subsection*\{%s\})
(\\subsubsection\{%s\} . \\subsubsection*\{%s\})))
But I get the following error:
Symbol's value as variable is void: org-latex-classes
Why should that be?
You may be using an outdated version (maint branch?). Otherwise, latex
back-end may not be loaded, but it is by default (see
`org-export-backends').
I shifted from the elpa version to the version downloaded using git
repository. But I still get this error. org-version says:
Org-mode version 7.9.3f (release_7.9.3f-1360-g2d3add @
/home/vikas/lisp/org-mode/lisp/)
Without configuration, export framework and default back-ends are not
loaded along with Org, but the first you need them (by calling an
autoloaded function).
You may be trying to modify `org-latex-classes' before having `ox-latex'
loaded.
You can either explicitly (require 'ox-latex) before that, which will
load all export framework along with Org, or use the following
construct:
(eval-after-load 'ox-latex
'(add-to-list ...))
In the latter case, you still get framework loaded only when you need it
the first time.
Regards,
--
Nicolas Goaziou
Re: [O] Support Freemind/Freeplane export
Bastien b...@altern.org writes: Achim Gratz strom...@nexgo.de writes: It also requires that the HTML is output in UTF-8. I would (reluctantly, I don't really know much about how this would work) suggest that the export should always be done with symbolic entities and a post-export filter should then replace them with whatever the particular backend prefers. Does that work? This seems a good idea to me. Nicolas, do you think so? Yes. We can add a defconst associating each HTML entity to its utf-8 counterpart, and add a filter to :filter-final-output in freemind back-end definition (not to `org-export-filter-final-output-functions', which is user-oriented). Any taker? Jambunathan? Regards, -- Nicolas Goaziou
Re: [O] How to markup verbatim code including = and ~?
Hello, Nathaniel Cunningham nathaniel.cunning...@gmail.com writes: Alright, I solved my own problem. I was able to get verbatim working with a unicode symbol (√) as delimeter, by editing both org-emphasis-alist and org-export-latex-emphasis-alist. Cheers! FYI, modifying `org-emphasis-alist' will not be compatible with export in Org 8.0 (the parser assumes there's a fixed set of emphasis markers). Regards, -- Nicolas Goaziou
Re: [O] org-meta-return
Hi John On Sun, Mar 3, 2013 at 12:59 AM, 42 147 aeus...@gmail.com wrote: That said, were you a QWERTY user before you transitioned into Colemak? Yes. Michael
Re: [O] org-exp-bibtex missing in git?
Le dimanche 3 mars 2013 à 08h06, Vikas Rawal a écrit: org-exp-bibtex seems to have gone missing from git repository. Can somebody confirm pleae. Vikas Dear Vikas, I do confirm. org-exp-bibtex, because of its dependency on the old exporter, was first moved from contrib/lisp to contrib/oldexp during the process of migration towards org new exporter. And yesterday, the directory contrib/oldexp was eventually removed[1]. It is still possible to checkout before this commit to rescue it, and try to update it for the new exporter (which I would do, if I was technically able to do so). In the meanwhile, checking, building, and exporting with the old exporter is still a possible option. Best, François [1] http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=ee3b3eb421e74339119d730a5bf896a070b2ed60
Re: [O] org-meta-return
Michael Brand michael.ch.br...@gmail.com writes: Hi John On Feb 21, 2013 10:16 PM, 42 147 aeus...@gmail.com wrote: [continues off-topic] Have you tried a Dvorak keyboard? A friend of mine ridicules me for being a QWERTY typist, but I have found no empirical evidence that it is actually superior. At best, it has been proven, in /some/ studies, to be /slightly/ superior; and from a cost-benefit standpoint, /slight/ superiority according to /some/ studies (and I should add, only at extreme speeds), is not worth relearning how to type. Colemak is a much better keyboard layout than Dvorak. I have been using Colemak for many years now with great pleasure. Whoa, that's what I was looking for! Keyboard layout taped to the wall, typing this in Colemak now. Thanks for the tip. E
Re: [O] org-caldav can't find org-prepare-agenda-buffers
Hi Bastien, I didn't follow this thread in detail. But shouldn't it be enough to symlink e.g. org-icalendar against ox-icalendar. As far as I understood emacs would prioritize those local symlinks over the system wide installation. This would be a temporary solution until a new emacs release. Actually, under Linux, this is a pretty common way to bend dependencies towards the newest version of a lib. Not sure for windows users. Instead of a simple symlink, the current dev head could have wrappers for those old files which bend the calls to the new files and issue a warning. That would help to identify 3 party code which needs some rework. Torsten Bastien b...@altern.org wrote: Hi David, David Engster d...@randomsample.de writes: Did you actually try that? How should Emacs possibly know that the file ox-icalendar provides the feature org-icalendar? This will only work if ox-icalendar is already loaded. Of course, you're right. I reverted the commit. So the problems stay. For third-party libraries developers, we cannot do anything else now than to ask them to update their code. For the problem of Emacs autoloaded functions, org.el provides (load org-loaddefs.el t t t) which should load the correct autoloads from the correct files... but that's unstable. It seems the ox- prefix is a bad idea, you're right. I'll think about it again. Thanks, -- Bastien
Re: [O] [ANN] Merge of new export framework on Wednesday
On Sat, Mar 2, 2013 at 6:14 PM, Bastien b...@altern.org wrote: Hi Sean, Sean O'Halpin sean.ohal...@gmail.com writes: One small point: as we're going to have to change the meta directive #+STYLE to #+HTML_STYLE, can we change the name to reflect what it really does in the HTML backend, i.e. insert text verbatim into the head element? I suggest we rename it to #+HTML_HEAD. Done. You can now use HTML_HEAD instead of HTML_STYLE. Some variables were also renamed, check the details here: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=2752ef Best, -- Bastien Thanks! It will now feel less hacky to use it for other head elements :) Also, it's just struck me - wouldn't it be more consistent if ATTR_HTML were HTML_ATTR, ATTR_LATEX were LATEX_ATTR, etc.? But I suppose if you go down that route of everything export backend related being prefixed with the export type, you'd really have to change BEGIN_HTML to HTML_BEGIN, etc. Perhaps going too far... Regards, Sean
[O] build fails
I am using OSX 10.8.2 and Emacs 2.24.1 I am trying to build org-mode from the current version in git, and I get the following errors: Ran 423 tests, 419 results as expected, 4 unexpected (2013-03-03 13:23:56+0100) 5 expected failures 4 unexpected results: FAILED test-org-table/references/format-specifier-E FAILED test-org-table/references/format-specifier-EL FAILED test-org-table/references/format-specifier-L FAILED test-org-table/references/format-specifier-none make[1]: *** [test-dirty] Error 1
[O] [BABEL] the julia language
Hello, Maybe you've heard about the relatively new language, julia [1]? The ESS team added support for it some months back [2] and they've been working on it more recently even [3]. It seemed natural to investigate Babel support for julia and after quite a bit of fiddling with ob-R.el I believe I've sorted out the major pieces: git://github.com/gjkerns/ob-julia.git There's an ob-julia.el file which is the meat, then ob-julia-doc.org and ob-julia-beamer.org files for testing, plus an intro-julia.org file in case you're new to julia and would like to learn more. For testing you'd need a recent installation of julia [2] and you'd need an almost bleeding-edge version of ESS [4]. By the way, it was written under the development branch of Org so if you haven't updated recently you might need that too. LaTeX/HTML/Beamer export is working, C-c C-c evaluation of code chunks, plotting figures (need the Winston package), etc. Session evaluation is required at least for the time being. If you see ways to improve it I'd appreciate any feedback. Cheers, Jay [1] http://julialang.org/ [2] https://stat.ethz.ch/pipermail/ess-help/2012-September/008212.html [3] https://stat.ethz.ch/pipermail/ess-help/2013-February/008640.html [4] https://github.com/emacs-ess/ESS -- G. Jay Kerns, Ph.D. Youngstown State University http://people.ysu.edu/~gkerns/
[O] [PATCH] orgcontacts.el: Fix `date' being broken in `org-contacts-anniversaries'.
* contrib/lisp/org-contacts.el: Add defvar for date. Similar to org.el. (org-contacts-anniversaries): Setting date to nil breaks the function. Bug was introduced in e4cebbe40. Signed-off-by: Rüdiger Sonderfeld ruedi...@c-plusplus.de --- contrib/lisp/org-contacts.el | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/lisp/org-contacts.el b/contrib/lisp/org-contacts.el index 4ffe360..d849e7f 100644 --- a/contrib/lisp/org-contacts.el +++ b/contrib/lisp/org-contacts.el @@ -499,6 +499,7 @@ A group FOO is composed of contacts with the tag FOO. ;; show the next heading (org-flag-heading nil))) +(org-no-warnings (defvar date)) ;; unprefixed, from calendar.el (defun org-contacts-anniversaries (optional field format) Compute FIELD anniversary for each contact, returning FORMAT. Default FIELD value is \BIRTHDAY\. @@ -512,8 +513,7 @@ Format is a string matching the following format specification: (let ((calendar-date-style 'american) (entry )) (unless format (setq format org-contacts-birthday-format)) -(loop with date = nil ; FIXME: prevent a warning - for contact in (org-contacts-filter) +(loop for contact in (org-contacts-filter) for anniv = (let ((anniv (cdr (assoc-string (or field org-contacts-birthday-property) (caddr contact) -- 1.8.1.1
Re: [O] Bug? Agenda problems after update
Hi Bastien, I tried to reproduce using -q and had another error occurring in customizing the agenda (hard to reproduce agenda problem with a blank list): apropos-parse-pattern: Wrong type argument: stringp occurs when using the search button. This is emacs org, from GNU Emacs 24.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.12) due to -q. The below refers to git emacs, of course. On 03/03/2013 07:34 AM, Bastien wrote: Hi Simon, thanks for reporting those problems. Simon Thum simon.t...@gmx.de writes: Press key for agenda command (unrestricted): Update Org Contacts Database Bad sexp at line 350 in /home/simon/org/privat.org: (org-contacts-anniversaries BIRTHDAY %y. Geburtstag %l) [7 times] Invalid face reference: nil [619 times] 1: Altough org-contacts is invoked, birthdays fail. I tried both sexp syntaxes (%%() and %%()). I'm cc'ing Grégory, maybe this is related to recent changes in org-contact.el. Grégory, can you have a look ? Don't look in the wrong end - I checked out an out org-contacts.el (127bffa9e9cfe525fad0d8c) but the issue persisted. Also see below. 2: Hovering the mouse over the agenda produces these nil face warnings. I have no idea how to diagnose this, but it does not hurt much it seems. On every mouse motion event that hovers over agenda lines below today (except for the first line below today's date line, misteriously, and only if a certain line with a past-due deadline with [#C] priority cookie is visible), one such warning is produced. Mhh... I can't reproduce this. Can you give a recipe? What emacs version is it with? I tried a lot of stuff and this is triggering it for me: (setq org-highest-priority ?B) (setq org-lowest-priority ?D) (setq org-default-priority ?D) However, this seems just a factor. Removing it works but is undesirable for me, and re-adding it in an otherwise minimal config is fine too. I'm dropping this for now, let's see how my windows box responds. 3: The agenda dropped back to 10 sec and more. I used to have agenda generation times of 2-3 sec after I switched to SSDs. I hope this is the issue from the org-agenda-write taking very long thread currently going on. I don't think it is the same issue. Here again, can you give a hint on what your configuration and agenda file/command look like? Well, even the default agenda was pretty lousy. But guess what? I executed one of my not-so-daily review (block-) agendas, and whatever it did, it fixed the issue. Could that be? I'm at a loss to explain things, but the slowdown is gone now. Some cache/temp file issue? Is there some kind of make clean for the operational org-mode? What's even better, since that the org-contacts integration is working fine again! Maybe that was the culprit, or my whole setup is somehow botched. 4: When jumping to a file from the agenda, it is completely visible, including ARCHIVE tags (which otherwise work as expected). Just opening them is fine; it only affects the case the agenda file was not loaded before. Thus it seems to be a bug. (setq org-agenda-inhibit-startup nil) The new default is supposed to make the agenda generation faster, actually. Tassilo reported it was not speeding up things and I need to check this again. Apparently, it did not slowdown mine but fixed the issue. Thanks! So the nil face is the only issue left, and it depends a lot on config. I will see if I can find out more. Cheers, Simon
Re: [O] Support Freemind/Freeplane export
Nicolas Goaziou n.goaz...@gmail.com writes: Bastien b...@altern.org writes: Achim Gratz strom...@nexgo.de writes: It also requires that the HTML is output in UTF-8. I would (reluctantly, I don't really know much about how this would work) suggest that the export should always be done with symbolic entities and a post-export filter should then replace them with whatever the particular backend prefers. Does that work? This seems a good idea to me. Nicolas, do you think so? Yes. We can add a defconst associating each HTML entity to its utf-8 counterpart, and add a filter to :filter-final-output in freemind back-end definition (not to `org-export-filter-final-output-functions', which is user-oriented). Any taker? Jambunathan? Please merge , http://repo.or.cz/w/org-mode/org-kjn.git | | URL git://repo.or.cz/org-mode/org-kjn.git | http://repo.or.cz/r/org-mode/org-kjn.git | ` I will submit more changes to ox-html.el and ox-odt.el. It's going to some time though. ps: I have a feeling that `org-html-display-buffer-mode' is superfluous. A simple `set-auto-mode' will do the trick. , | kjambunathan@debian-6:~/src/org-mode$ git log upstream/master.. | commit b8d0b1ae89bd769a898aba90f6c85c680963e0ed | Author: Jambunathan K kjambunat...@gmail.com | Date: Sun Mar 3 20:21:07 2013 +0530 | | doc/org.texi: Replace org-export-odt with org-odt | | commit c5d46d21b5a3f902cfd7b9d709660b493f67bd94 | Author: Jambunathan K kjambunat...@gmail.com | Date: Sun Mar 3 20:15:10 2013 +0530 | | Always use utf-8 encoding for HTML export | | * ox-html.el (org-html-coding-system): Removed. Always use | utf-8 for HTML export. | (org-html--build-meta-info, org-html-template) | (org-html-entity, org-html-export-to-html): Propagate above | change. | (org-html-table--table.el-table): Replace nbsp; with it's | utf-8 equivalent. | (org-html-special-string-regexps, org-html--tags) | (org-html-format-headline, org-html--format-toc-headline) | (org-html-checkbox, org-html-table-cell, org-html-timestamp) | (org-html-verse-block): Replace numeric entities with their | utf-8 equivalent. | | Mark ox-html.el as utf-8 encoded. | | commit 75708cf644944d301e57bc343db8749b8fa3c242 | Author: Jambunathan K kjambunat...@gmail.com | Date: Sun Mar 3 13:51:32 2013 +0530 | | ox-html.el (org-html-code, org-html-verbatim): Transcode value | | * lisp/ox-html.el (org-html-code, org-html-verbatim): | Transcode value. ` Regards, --
Re: [O] Bug? Agenda problems after update
Ahh, crap. Sorry to have spread confusion. The issues persit - except for the last one (4). I probably defected to the emacs org which miraculousy had 2 secs agenda generation time, not 16. I removed the built-in one to avoid future confusion, but cannot dig deeper now. Cheers, Simon On 03/03/2013 03:36 PM, Simon Thum wrote: Hi Bastien, I tried to reproduce using -q and had another error occurring in customizing the agenda (hard to reproduce agenda problem with a blank list): apropos-parse-pattern: Wrong type argument: stringp occurs when using the search button. This is emacs org, from GNU Emacs 24.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.12) due to -q. The below refers to git emacs, of course. On 03/03/2013 07:34 AM, Bastien wrote: Hi Simon, thanks for reporting those problems. Simon Thum simon.t...@gmx.de writes: Press key for agenda command (unrestricted): Update Org Contacts Database Bad sexp at line 350 in /home/simon/org/privat.org: (org-contacts-anniversaries BIRTHDAY %y. Geburtstag %l) [7 times] Invalid face reference: nil [619 times] 1: Altough org-contacts is invoked, birthdays fail. I tried both sexp syntaxes (%%() and %%()). I'm cc'ing Grégory, maybe this is related to recent changes in org-contact.el. Grégory, can you have a look ? Don't look in the wrong end - I checked out an out org-contacts.el (127bffa9e9cfe525fad0d8c) but the issue persisted. Also see below. 2: Hovering the mouse over the agenda produces these nil face warnings. I have no idea how to diagnose this, but it does not hurt much it seems. On every mouse motion event that hovers over agenda lines below today (except for the first line below today's date line, misteriously, and only if a certain line with a past-due deadline with [#C] priority cookie is visible), one such warning is produced. Mhh... I can't reproduce this. Can you give a recipe? What emacs version is it with? I tried a lot of stuff and this is triggering it for me: (setq org-highest-priority ?B) (setq org-lowest-priority ?D) (setq org-default-priority ?D) However, this seems just a factor. Removing it works but is undesirable for me, and re-adding it in an otherwise minimal config is fine too. I'm dropping this for now, let's see how my windows box responds. 3: The agenda dropped back to 10 sec and more. I used to have agenda generation times of 2-3 sec after I switched to SSDs. I hope this is the issue from the org-agenda-write taking very long thread currently going on. I don't think it is the same issue. Here again, can you give a hint on what your configuration and agenda file/command look like? Well, even the default agenda was pretty lousy. But guess what? I executed one of my not-so-daily review (block-) agendas, and whatever it did, it fixed the issue. Could that be? I'm at a loss to explain things, but the slowdown is gone now. Some cache/temp file issue? Is there some kind of make clean for the operational org-mode? What's even better, since that the org-contacts integration is working fine again! Maybe that was the culprit, or my whole setup is somehow botched. 4: When jumping to a file from the agenda, it is completely visible, including ARCHIVE tags (which otherwise work as expected). Just opening them is fine; it only affects the case the agenda file was not loaded before. Thus it seems to be a bug. (setq org-agenda-inhibit-startup nil) The new default is supposed to make the agenda generation faster, actually. Tassilo reported it was not speeding up things and I need to check this again. Apparently, it did not slowdown mine but fixed the issue. Thanks! So the nil face is the only issue left, and it depends a lot on config. I will see if I can find out more. Cheers, Simon
Re: [O] [patch] ox-koma-letter
Rasmus writes:
Export the following to LaTeX:
#+BEGIN_SRC Org
#+TITLE:test
#+LATEX_HEADER:\newcommand{test}{\textsc{ps}:this is a test}
#+LATEX_HEADER:\newcommand{ttest}{\textsc{ps}\:this is a test}
#+LATEX_HEADER:\newcommand{tttest}{\textsc{ps}\\:this is a test}
#+LATEX_HEADER:\newcommand{est}{\textsc{ps}$\colon$this is a test}
this is a test
#+END_SRC
I see, and this is quite a serious issue. It also means we cannot put a
':' in any other field, like the opening or closing of the letter. And
multiline ps are going to be tricky.
Maybe we could have a way to set the closing at the spot where we want
it to happen, then write the ps and encl manually. I don't really know
how to tweak the exporter for this to happen, though.
Alan
Re: [O] How can I stop org-agenda-write from overwriting existing files.
Dear Bastien, On 03/01/2013 03:07 PM, Bastien wrote: Hi Rainer, Rainer Stengele rainer.steng...@online.de writes: How can I stop org-agenda-write from overwriting existing files? Should we consider to introduce an option instead of advising the function? You are now asked before overwriting the file, thanks for suggesting this. this breaks my setup. I export to mobileOrg on my server whenever I sync. Now I am being asked Overwrite existing file /home/org-mobile/mobileOrg/agendas.org? (y or n) y but the script does not answer. I am invoking: emacs -batch -l ~/.emacs.d/init.el -f org-mobile-push --kill but even though I use -batch the question is asked! How can I fix this? Cheers, Simon
Re: [O] Support Freemind/Freeplane export
Jambunathan K kjambunat...@gmail.com writes: Nicolas Goaziou n.goaz...@gmail.com writes: Bastien b...@altern.org writes: Achim Gratz strom...@nexgo.de writes: It also requires that the HTML is output in UTF-8. I would (reluctantly, I don't really know much about how this would work) suggest that the export should always be done with symbolic entities and a post-export filter should then replace them with whatever the particular backend prefers. Does that work? This seems a good idea to me. Nicolas, do you think so? Yes. We can add a defconst associating each HTML entity to its utf-8 counterpart, and add a filter to :filter-final-output in freemind back-end definition (not to `org-export-filter-final-output-functions', which is user-oriented). Any taker? Jambunathan? Please merge , http://repo.or.cz/w/org-mode/org-kjn.git | | URL git://repo.or.cz/org-mode/org-kjn.git | http://repo.or.cz/r/org-mode/org-kjn.git | ` Sorry for the double post. Here comes the patch file(s). From 75708cf644944d301e57bc343db8749b8fa3c242 Mon Sep 17 00:00:00 2001 From: Jambunathan K kjambunat...@gmail.com Date: Sun, 3 Mar 2013 13:51:32 +0530 Subject: [PATCH 1/3] ox-html.el (org-html-code, org-html-verbatim): Transcode value * lisp/ox-html.el (org-html-code, org-html-verbatim): Transcode value. --- lisp/ox-html.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lisp/ox-html.el b/lisp/ox-html.el index a0f3f4f..3a4c0e7 100644 --- a/lisp/ox-html.el +++ b/lisp/ox-html.el @@ -1899,7 +1899,7 @@ channel. CONTENTS is nil. INFO is a plist holding contextual information. (format (or (cdr (assq 'code org-html-text-markup-alist)) %s) - (org-element-property :value code))) + (org-html-plain-text (org-element-property :value code) info))) Drawer @@ -3029,7 +3029,7 @@ holding contextual information. CONTENTS is nil. INFO is a plist holding contextual information. (format (or (cdr (assq 'verbatim org-html-text-markup-alist)) %s) - (org-element-property :value verbatim))) + (org-html-plain-text (org-element-property :value verbatim) info))) Verse Block -- 1.7.2.5 From c5d46d21b5a3f902cfd7b9d709660b493f67bd94 Mon Sep 17 00:00:00 2001 From: Jambunathan K kjambunat...@gmail.com Date: Sun, 3 Mar 2013 20:15:10 +0530 Subject: [PATCH 2/3] Always use utf-8 encoding for HTML export * ox-html.el (org-html-coding-system): Removed. Always use utf-8 for HTML export. (org-html--build-meta-info, org-html-template) (org-html-entity, org-html-export-to-html): Propagate above change. (org-html-table--table.el-table): Replace nbsp; with it's utf-8 equivalent. (org-html-special-string-regexps, org-html--tags) (org-html-format-headline, org-html--format-toc-headline) (org-html-checkbox, org-html-table-cell, org-html-timestamp) (org-html-verse-block): Replace numeric entities with their utf-8 equivalent. Mark ox-html.el as utf-8 encoded. --- lisp/ox-html.el | 55 +-- 1 files changed, 21 insertions(+), 34 deletions(-) diff --git a/lisp/ox-html.el b/lisp/ox-html.el index 3a4c0e7..efd9b2f 100644 --- a/lisp/ox-html.el +++ b/lisp/ox-html.el @@ -136,10 +136,10 @@ (defvar htmlize-buffer-places) ; from htmlize.el (defconst org-html-special-string-regexps - '((- . #x00ad;) ; shy -(---\\([^-]\\) . #x2014;\\1) ; mdash -(--\\([^-]\\) . #x2013;\\1) ; ndash -(\\.\\.\\. . #x2026;)) ; hellip + '((- . ) ; shy +(---\\([^-]\\) . —\\1) ; mdash +(--\\([^-]\\) . –\\1) ; ndash +(\\.\\.\\. . …)) ; hellip Regular expressions for special string conversion.) (defconst org-html-scripts @@ -821,12 +821,6 @@ and corresponding declarations. (cons (string :tag Extension) (string :tag Declaration) -(defcustom org-html-coding-system 'utf-8 - Coding system for HTML export. -Use utf-8 as the default value. - :group 'org-export-html - :type 'coding-system) - (defcustom org-html-divs '(preamble content postamble) The name of the main divs for HTML export. This is a list of three strings, the first one for the preamble @@ -1337,12 +1331,7 @@ INFO is a plist used as a communication channel. (keywords (plist-get info :keywords))) (concat (format title%s/title\n title) - (format - meta http-equiv=\Content-Type\ content=\text/html;charset=%s\/\n - (or (and org-html-coding-system - (fboundp 'coding-system-get) - (coding-system-get org-html-coding-system 'mime-charset)) - iso-8859-1)) + meta http-equiv=\Content-Type\ content=\text/html;charset=utf-8\/\n (format meta name=\title\ content=\%s\/\n title) (format meta name=\generator\ content=\Org-mode\/\n) (and date (format meta name=\generated\ content=\%s\/\n date)) @@ -1515,10 +1504,7 @@ holding export options. (cdr (assoc html org-html-xml-declaration)) ) -(or (and org-html-coding-system - (fboundp 'coding-system-get) -
Re: [O] Bug? Agenda problems after update
Hi Simon, Simon Thum simon.t...@gmx.de writes: I tried a lot of stuff and this is triggering it for me: (setq org-highest-priority ?B) (setq org-lowest-priority ?D) (setq org-default-priority ?D) However, this seems just a factor. Removing it works but is undesirable for me, and re-adding it in an otherwise minimal config is fine too. I'm dropping this for now, let's see how my windows box responds. What are the values of `org-agenda-fontify-priorities' and `org-priority-faces'? -- Bastien
Re: [O] [PATCH] orgcontacts.el: Fix `date' being broken in `org-contacts-anniversaries'.
Hi Rüdiger, Rüdiger Sonderfeld ruedi...@c-plusplus.de writes: * contrib/lisp/org-contacts.el: Add defvar for date. Similar to org.el. (org-contacts-anniversaries): Setting date to nil breaks the function. Bug was introduced in e4cebbe40. Applied, thanks a lot. -- Bastien
Re: [O] How can I stop org-agenda-write from overwriting existing files.
Hi Simon, Simon Thum simon.t...@gmx.de writes: this breaks my setup. I've removed the check when org-agenda-write is called non-interactively. Please let me know if this fixes your setup. Thanks, -- Bastien
[O] New exporter: minor issue
Hi Nicolas, I have scripted an ical export that invokes: org-icalendar-combine-agenda-files but the thing fails on my server and home boxes. I investigated and found that a misguided babel block I added in a hurry and forgot about was causing trouble: #+BEGIN_SRC xml #+END_SRC It seems this was the culprit, so I'm reporting this so maybe the failure can be made more graceful. One thing I noted that while I was informed of the temp .ics files I had no idea which file it was failing on - I assumed it would be when combining. Anyway, ascii export had the same trouble on this file so it's generic, and may actually be a bug, or that's what it looks to me. The failure is: Debugger entered--Lisp error: (wrong-number-of-arguments max 0) max() apply(max nil) (+ (apply (quote max) (mapcar (quote length) code-lines)) (if (not num-start) 0 (length (format num-fmt num-start (let* ((code-info (org-export-unravel-code element)) (code (car code-info)) (code-lines (org-split-string code \n)) (refs (and (org-element-property :retain-labels element) (cdr code-info))) (num-start (case (org-element-property :number-lines element) (continued (org-export-get-loc element info)) (new 0))) (num-fmt (and num-start (format %%%ds (length (number-to-string (+ ... num-start)) (max-width (+ (apply (quote max) (mapcar (quote length) code-lines)) (if (not num-start) 0 (length (format num-fmt num-start)) (org-export-format-code code (lambda (loc line-num ref) (let ((number-str (and num-fmt (format num-fmt line-num (concat number-str loc (and ref (concat (make-string ... 32) (format (%s) ref)) num-start refs)) org-export-format-code-default((src-block (:language xml ...
Re: [O] Bug in behavior of M-RET with latest Org-mode
Hi Nick and John, Nick Dokos nicholas.do...@hp.com writes: So the heuristic might not be perfect, but it seems to work for all but the first headline. I fixed this and the heuristic should not insert undue blank lines anymore. Thanks for confirming, -- Bastien
Re: [O] how can I insert a new heading after all at this level?
Hi David, David Naumann naum...@cs.stevens.edu writes: What I would like to be able to do is insert a new heading at the same level as current, _following_ all the others. For example, with the cursor on the A in this tree: * top - ** A ** B ** C * next I would like to insert a last sibling and move to it: * top ** A ** B ** C - ** * next From current git repo (master branch), you can now use C-u C-u M-RET to insert a headline after all siblings. Thanks for suggesting this, -- Bastien
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Sean, Sean O'Halpin sean.ohal...@gmail.com writes: Also, it's just struck me - wouldn't it be more consistent if ATTR_HTML were HTML_ATTR, ATTR_LATEX were LATEX_ATTR, etc.? I don't really think so -- ATTR_HTML is more like BEGIN_HTML than #+HTML_HEAD, which is a global option, not a local setting or an environment... and we can't break all .org files like this :) -- Bastien
Re: [O] org-exp-bibtex missing in git?
Hi Vikas, François Allisson franc...@allisson.co writes: org-exp-bibtex, because of its dependency on the old exporter, was first moved from contrib/lisp to contrib/oldexp during the process of migration towards org new exporter. And yesterday, the directory contrib/oldexp was eventually removed[1]. Yes. What features of org-exp-bibtex.el would you need that you don't have with the current version of Org (from the master branch)? It will help knowing what to implement. Thanks in advance, -- Bastien
Re: [O] org-exp-bibtex missing in git?
Bastien b...@altern.org writes:
Hi Vikas,
François Allisson franc...@allisson.co writes:
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from contrib/lisp to contrib/oldexp during the process of
migration towards org new exporter. And yesterday, the directory
contrib/oldexp was eventually removed[1].
Yes. What features of org-exp-bibtex.el would you need that you don't
have with the current version of Org (from the master branch)? It will
help knowing what to implement.
It would be good to integrate citations in export framework, so we do
not rely on an external tool and \cite{...} constructs.
We already got rid of \ref{...}.
Maybe something like [cite:]. org-element could parse this, and
ox.el provide some tools to access data. Then each back-end could deal
with them.
But it requires first to think about proper specifications.
Regards,
--
Nicolas Goaziou
Re: [O] New beamer exporter: top-aligned columns
Hello, James Harkins jamshar...@gmail.com writes: According to beameruserguide.pdf, I can give an option t to a columns environment to align the columns by the top line of text. It's not clear to me how to put this into org. So far, I have: *** Columns :B_columns: :PROPERTIES: :BEAMER_env: columns :END: Where should the t go? Some :options string, I suppose. Try :BEAMER_opt: t property. Adding options to columns is the only case where you explictly need a columns environment. Otherwise it can be omitted, and will be created along with the first headline with a BEAMER_col property (see comments at the beginning of ox-beamer.el). Regards, -- Nicolas Goaziou
Re: [O] How can I stop org-agenda-write from overwriting existing files.
On 03/03/2013 05:54 PM, Bastien wrote: Hi Simon, Simon Thum simon.t...@gmx.de writes: this breaks my setup. I've removed the check when org-agenda-write is called non-interactively. Please let me know if this fixes your setup. Thanks, Works like a charm! Thank you very much!
Re: [O] [patch] ox-koma-letter
Hello,
Alan Schmitt alan.schm...@polytechnique.org writes:
Rasmus writes:
Export the following to LaTeX:
#+BEGIN_SRC Org
#+TITLE:test
#+LATEX_HEADER:\newcommand{test}{\textsc{ps}:this is a test}
#+LATEX_HEADER:\newcommand{ttest}{\textsc{ps}\:this is a test}
#+LATEX_HEADER:\newcommand{tttest}{\textsc{ps}\\:this is a test}
#+LATEX_HEADER:\newcommand{est}{\textsc{ps}$\colon$this is a test}
this is a test
#+END_SRC
I didn't read the thread carefully, but there should be a space after
#+LATEX_HEADER:.
Regards,
--
Nicolas Goaziou
Re: [O] Bug? Agenda problems after update
Hi, I'm pleased to announce that with commit b06735aa85506e04f9b2e agneda performance is back to lighting-fast and the agenda works with birthdays. Thanks a lot! On 03/03/2013 05:50 PM, Bastien wrote: Hi Simon, Simon Thum simon.t...@gmx.de writes: I tried a lot of stuff and this is triggering it for me: (setq org-highest-priority ?B) (setq org-lowest-priority ?D) (setq org-default-priority ?D) However, this seems just a factor. Removing it works but is undesirable for me, and re-adding it in an otherwise minimal config is fine too. I'm dropping this for now, let's see how my windows box responds. What are the values of `org-agenda-fontify-priorities' and `org-priority-faces'? org-agenda-fontify-priorities cookies org-priority-faces nil I don't knowingly change these. HTH, Simon
Re: [O] Support Freemind/Freeplane export
Jambunathan K kjambunat...@gmail.com writes: ps: I have a feeling that `org-html-display-buffer-mode' is superfluous. A simple `set-auto-mode' will do the trick. Indeed, I applied a patch using `set-auto-mode'. Thanks for the suggestion! -- Bastien
Re: [O] Support Freemind/Freeplane export
Bastien b...@altern.org writes: Also, the change in ox-html.el is not good IMHO: it will populate everyone's HTML code with unfamiliar strings (like #xa0; instead of nbsp;) just for the sake of keeping ox-freemind.el users happy. How many people are going to read HTML code? There is correctness and there is readability. Those who actually read HTML code better know what they are looking at. Remember the character in question are occurring here and there and not everywhere. Adding a filter function will only add a moving part. It could be a robust moving part, but it is a moving part nevertheless. In short, the concern you have raised is more cosmetic than functional. --
[O] Bug: org-agenda-undo does not work on repeated tasks [7.9.3d (7.9.3d-dist @ /home/wlin/.emacs-lisp/org/lisp/)]
Emacs : GNU Emacs 23.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.5) of 2011-08-14 on allspice, modified by Debian Package: Org-mode version 7.9.3d (7.9.3d-dist @ /home/myth/.emacs-lisp/org/lisp/) To reproduce: In an org agenda buffer, mark a task as done. Then, run org-agenda-undo. If the task is a repeated task like this: * TODO A weekly repeated task SCHEDULED: 2013-03-03 Sun +1w After mark a task as done from the agenda buffer, it becomes: * TODO A weekly repeated task SCHEDULED: 2013-03-10 Sun +1w :LOGBOOK: - State DONE from TODO [2013-03-03 Sun 12:43] :END: :PROPERTIES: :LAST_REPEAT: [2013-03-03 Sun 12:43] :END: Then, if I run org-agenda-undo (with C-z) in agenda buffer, * TODO A weekly repeated task SCHEDULED: 2013-03-10 Sun +1w :LOGBOOK: :END: :PROPERTIES: :LAST_REPEAT: [2013-03-03 Sun 12:43] :END: As you can see, the LOGBOOK changed, but the SCHEDULED time did not go back to the original. Thanks for looking into it.
[O] Always use utf-8 for HTML export (No support for other coding systems)
Always use utf-8 for HTML export (No support for other coding systems). For or against. Please register your views. --
[O] org-capture with org-contacts template causing problems
Good day! So, I tried giving org-contacts another go. For capturing new contacts, I have this template configured (based on the example on org-contacts.el): #+begin_src elisp (add-to-list 'org-capture-templates '(c Contacts entry (file ~/org/contacts.org) ** %(org-contacts-template-name) :PROPERTIES: :EMAIL: %(org-contacts-template-email) :END:)) #+end_src When using `org-capture' (and then selecting c in the menu window), I get the following error message in the CAPTURE-contacts.org buffer: * %![Error: (invalid-function gnus-with-article-headers)] :PROPERTIES: :EMAIL: %![Error: (invalid-function gnus-with-article-headers)] :END: The following however works from the `*scratch*' buffer: #+begin_src elisp (gnus-with-article-headers (mail-fetch-field From)) #+end_src This is with an emacs snapshot, M-x version: GNU Emacs 24.3.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.2) of 2013-03-01 on jim, modified by Debian M-x org-version: Org-mode version 7.9.3e (7.9.3e-3-gb07a9b @ /usr/share/emacs/24.3.50/lisp/org/) This is with `org-contacts.el' from org-mode's git HEAD. I'm unsure about how to debug this. Any pointers welcome. Regards, Frank -- In protocol design, perfection has been reached not when there is nothing left to add, but when there is nothing left to take away. -- RFC 1925
Re: [O] New exporter: minor issue
Hello, Simon Thum simon.t...@gmx.de writes: I have scripted an ical export that invokes: org-icalendar-combine-agenda-files but the thing fails on my server and home boxes. I investigated and found that a misguided babel block I added in a hurry and forgot about was causing trouble: #+BEGIN_SRC xml #+END_SRC It seems this was the culprit, so I'm reporting this so maybe the failure can be made more graceful. One thing I noted that while I was informed of the temp .ics files I had no idea which file it was failing on - I assumed it would be when combining. Anyway, ascii export had the same trouble on this file so it's generic, and may actually be a bug, or that's what it looks to me. The failure is: Debugger entered--Lisp error: (wrong-number-of-arguments max 0) This should be fixed in master. Thank you for reporting this. Regards, -- Nicolas Goaziou
Re: [O] Support Freemind/Freeplane export
Jambunathan K kjambunat...@gmail.com writes: In short, the concern you have raised is more cosmetic than functional. I trust you. The thing is, I have this small incertainty in my mind on whether there is something functional involved here or not. Also, IIUC the change is triggered only because ox-freemind.el needs it, so the little incertainty + why it's needed makes me think twice. Is it fine to assume that all users want utf8 for their HTML files? If so, I'm fine with the patch. I'm just asking confirmation from (other) HTML/coding system experts. Achim, what do you think? (The local variable coding: utf-8 should be coding: utf-8-emacs I think.) -- Bastien
Re: [O] Always use utf-8 for HTML export (No support for other coding systems)
Jambunathan K writes: Always use utf-8 for HTML export (No support for other coding systems). For or against. Please register your views. It is becoming more rare these days, but still possible that the document encoding cannot be UTF-8 for whatever reason. So if it's not unduly complicating things, I'd suggest to avoid prescribing the UTF-8 encoding for any and all exports. Character entities and character entity references are what SGML/XML/HTML are using to get around that problem (the markup languages are all defined as operating on UCS), however the set of entitiy references defined by default is different, which makes the numeric character entities the most portable (unfortunately they are less readable). Remark: IIUC, this is what derails the (HTML, but not XML) symbolic entities in Freemind. It might be possible to simply declare the DTD defining these for XML in the freemind preamble. http://www.w3.org/TR/xml-entity-names/ 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] Always use utf-8 for HTML export (No support for other coding systems)
On Sun, Mar 3, 2013 at 11:58 PM, Achim Gratz strom...@nexgo.de wrote: Jambunathan K writes: Always use utf-8 for HTML export (No support for other coding systems). For or against. Please register your views. I am not sure if it effects our project. We use org and Emacs for post-processing our wiki pages to produce html pages. Currently we are getting proper exports since we get the output in utf-8. As far as I know, using utf-8 will support other coding systems as well. Am I wrong? -- GN
Re: [O] [BABEL] the julia language
Hi Jay, Having read through intro-julia.org and scanned ob-julia.el I have to say this looks great. Thanks for sharing! Would you be willing to contribute ob-julia.el to the Org-mode repository? I don't see you listed as an Org-mode contributor (see [1]), so to do so you would likely have to complete the FSF copyright attribution. Please let me (and more importantly Bastien) know if this is something you'd like to do, so we can help get julia support into Org-mode. Additionally, it would be nice for your excellent introduction to be added to worg, and for julia to be listed as a supported babel language (see [2]). Cheers, Jay Kerns gjkerns...@gmail.com writes: Hello, Maybe you've heard about the relatively new language, julia [1]? The ESS team added support for it some months back [2] and they've been working on it more recently even [3]. It seemed natural to investigate Babel support for julia and after quite a bit of fiddling with ob-R.el I believe I've sorted out the major pieces: git://github.com/gjkerns/ob-julia.git There's an ob-julia.el file which is the meat, then ob-julia-doc.org and ob-julia-beamer.org files for testing, plus an intro-julia.org file in case you're new to julia and would like to learn more. For testing you'd need a recent installation of julia [2] and you'd need an almost bleeding-edge version of ESS [4]. By the way, it was written under the development branch of Org so if you haven't updated recently you might need that too. LaTeX/HTML/Beamer export is working, C-c C-c evaluation of code chunks, plotting figures (need the Winston package), etc. Session evaluation is required at least for the time being. If you see ways to improve it I'd appreciate any feedback. Cheers, Jay [1] http://julialang.org/ [2] https://stat.ethz.ch/pipermail/ess-help/2012-September/008212.html [3] https://stat.ethz.ch/pipermail/ess-help/2013-February/008640.html [4] https://github.com/emacs-ess/ESS Footnotes: [1] http://orgmode.org/worg/org-contribute.html [2] http://orgmode.org/worg/org-contrib/babel/languages.html -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] build fails
Neuwirth Erich writes: 4 unexpected results: FAILED test-org-table/references/format-specifier-E FAILED test-org-table/references/format-specifier-EL FAILED test-org-table/references/format-specifier-L FAILED test-org-table/references/format-specifier-none I've reported these yesterday in another thread. Fixed in e541a1d. 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] Always use utf-8 for HTML export (No support for other coding systems)
Nagarjuna G writes: I am not sure if it effects our project. We use org and Emacs for post-processing our wiki pages to produce html pages. Currently we are getting proper exports since we get the output in utf-8. As far as I know, using utf-8 will support other coding systems as well. Am I wrong? If you already use UTF-8 encoding for your HTML files, you can safely ignore this discussion. 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] org-exp-bibtex missing in git?
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@altern.org writes:
Hi Vikas,
François Allisson franc...@allisson.co writes:
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from contrib/lisp to contrib/oldexp during the process of
migration towards org new exporter. And yesterday, the directory
contrib/oldexp was eventually removed[1].
Yes. What features of org-exp-bibtex.el would you need that you don't
have with the current version of Org (from the master branch)? It will
help knowing what to implement.
It would be good to integrate citations in export framework, so we do
not rely on an external tool and \cite{...} constructs.
We already got rid of \ref{...}.
Maybe something like [cite:]. org-element could parse this, and
ox.el provide some tools to access data. Then each back-end could deal
with them.
This would be truly *awesome*. This is the major barrier blocking truly
cross-backend export.
The data would be still from bibtex files?
Regards,
Andreas
Re: [O] org-exp-bibtex missing in git?
Hello,
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Bastien b...@altern.org writes:
Hi Vikas,
François Allisson franc...@allisson.co writes:
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from contrib/lisp to contrib/oldexp during the process of
migration towards org new exporter. And yesterday, the directory
contrib/oldexp was eventually removed[1].
Yes. What features of org-exp-bibtex.el would you need that you don't
have with the current version of Org (from the master branch)? It will
help knowing what to implement.
It would be good to integrate citations in export framework, so we do
not rely on an external tool and \cite{...} constructs.
We already got rid of \ref{...}.
Maybe something like [cite:]. org-element could parse this, and
ox.el provide some tools to access data. Then each back-end could deal
with them.
This would be truly *awesome*. This is the major barrier blocking truly
cross-backend export.
The data would be still from bibtex files?
No idea.
That's why specifications must be discussed first. What [cite:...]
entries (if we agree on that syntax) should provide?
Regards,
--
Nicolas Goaziou
Re: [O] Support Freemind/Freeplane export
Jambunathan K kjambunat...@gmail.com writes: Jambunathan K kjambunat...@gmail.com writes: Nicolas Goaziou n.goaz...@gmail.com writes: Bastien b...@altern.org writes: Achim Gratz strom...@nexgo.de writes: It also requires that the HTML is output in UTF-8. I would (reluctantly, I don't really know much about how this would work) suggest that the export should always be done with symbolic entities and a post-export filter should then replace them with whatever the particular backend prefers. Does that work? This seems a good idea to me. Nicolas, do you think so? Yes. We can add a defconst associating each HTML entity to its utf-8 counterpart, and add a filter to :filter-final-output in freemind back-end definition (not to `org-export-filter-final-output-functions', which is user-oriented). Any taker? Jambunathan? Please merge , http://repo.or.cz/w/org-mode/org-kjn.git | | URLgit://repo.or.cz/org-mode/org-kjn.git |http://repo.or.cz/r/org-mode/org-kjn.git | ` Sorry for the double post. Here comes the patch file(s). I have applied the first patch (about verbatim and code markup), the other one still being debated. Thank you. Regards, -- Nicolas Goaziou
Re: [O] build fails
Achim Gratz strom...@nexgo.de writes: Neuwirth Erich writes: 4 unexpected results: FAILED test-org-table/references/format-specifier-E FAILED test-org-table/references/format-specifier-EL FAILED test-org-table/references/format-specifier-L FAILED test-org-table/references/format-specifier-none I've reported these yesterday in another thread. Fixed in e541a1d. Well spotted! Thanks for fixing this, -- Bastien
Re: [O] [BABEL] the julia language
Dear Eric, On Sun, Mar 3, 2013 at 2:05 PM, Eric Schulte schulte.e...@gmail.com wrote: Hi Jay, Having read through intro-julia.org and scanned ob-julia.el I have to say this looks great. Thanks for sharing! I should be saying Thanks to you! Org Babel is truly great work; I use it almost every day of my life. Would you be willing to contribute ob-julia.el to the Org-mode repository? Yes, of course, it would be an honor to give back to the Org community. And I'm not just saying that. I don't see you listed as an Org-mode contributor (see [1]), so to do so you would likely have to complete the FSF copyright attribution. Please let me (and more importantly Bastien) know if this is something you'd like to do, so we can help get julia support into Org-mode. OK, I'll get started on that right away. Additionally, it would be nice for your excellent introduction to be added to worg, and for julia to be listed as a supported babel language (see [2]). Thanks for the kind words, and I would be happy to contribute to worg. I've been sitting on my hands about worg so far because I'm scared I'm going to break it with something that isn't compatible with the old exporter. In an earlier message Bastien indicated that Org 8.0 might be coming out in a few weeks (thanks, Bastien!) and I've been trying to wait for it patiently. In the meantime, maybe I'll check out the maintenance branch and dig up those old configurations to get the ball rolling on my side. -- Jay
Re: [O] Always use utf-8 for HTML export (No support for other coding systems)
Achim Gratz writes: Jambunathan K writes: Always use utf-8 for HTML export (No support for other coding systems). For or against. Please register your views. It is becoming more rare these days, but still possible that the document encoding cannot be UTF-8 for whatever reason. So if it's not unduly complicating things, I'd suggest to avoid prescribing the UTF-8 encoding for any and all exports. Chinese law mandates use of GB-18030, not UTF-8. The two are losslessly and unambiguously convertable, but their bit encodings are different. They are accustomed to dealing with UTF-8 from other parts of the world, but might prefer to generate local pages in compliance with the law. R Horn rjh...@alum.mit.edu
Re: [O] [PATCH] org-protocol: Pass optional value using query in url to capture from protocol.
* lisp/org-protocol.el: (org-protocol-convert-query-to-plist): New function. (org-protocol-do-capture): Use new function. (org-protocol-data-separator): Change default separator. When org-protocol's url has query, org-capture get query using plist-get from store-link. For example: Url is org-protocol:/capture:/URL/TITLE/BODY?key=value org-capture can get (:key value) with (plist-get org-store-link-plist :query). --- Hello, Bastien I fixed and resend a patch. Thanks, Ryo lisp/org-protocol.el | 18 +++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/lisp/org-protocol.el b/lisp/org-protocol.el index 2a804ad..d676c39 100644 --- a/lisp/org-protocol.el +++ b/lisp/org-protocol.el @@ -267,10 +267,12 @@ string with two characters. :group 'org-protocol :type 'string) -(defcustom org-protocol-data-separator /+ +(defcustom org-protocol-data-separator /+\\|\\? The default data separator to use. This should be a single regexp string. :group 'org-protocol + :version 24.4 + :package-version '(Org . 8.0) :type 'string) ;;; Helper functions: @@ -291,7 +293,7 @@ nil, assume \/+\. The results of that splitting are returned as a list. If UNHEXIFY is non-nil, hex-decode each split part. If UNHEXIFY is a function, use that function to decode each split part. - (let* ((sep (or separator /+)) + (let* ((sep (or separator /+\\|\\?)) (split-parts (split-string data sep))) (if unhexify (if (fboundp unhexify) @@ -411,6 +413,14 @@ Now template ?b will be used. (message Item captured.)) nil) +(defun org-protocol-convert-query-to-plist (query) + Convert query string that is part of url to property list. + (if query + (apply 'append (mapcar (lambda (x) + (let ((c (split-string x =))) +(list (intern (concat : (car c))) (cadr c +(split-string query ) + (defun org-protocol-do-capture (info) Support `org-capture'. (let* ((parts (org-protocol-split-data info t org-protocol-data-separator)) @@ -423,6 +433,7 @@ Now template ?b will be used. (region (or (caddr parts) )) (orglink (org-make-link-string url (if (string-match [^[:space:]] title) title url))) +(query (or (org-protocol-convert-query-to-plist (cadddr parts)) )) (org-capture-link-is-already-stored t)) ;; avoid call to org-store-link (setq org-stored-links (cons (list url title) org-stored-links)) @@ -431,7 +442,8 @@ Now template ?b will be used. :link url :description title :annotation orglink - :initial region) + :initial region + :query query) (raise-frame) (funcall 'org-capture nil template))) -- 1.7.9.6 (Apple Git-31.1)
Re: [O] [PATCH] org-protocol: Pass optional value using query in url to capture from protocol.
Hi Ryo, Ryo TAKAISHI ryo.takaish...@gmail.com writes: * lisp/org-protocol.el: (org-protocol-convert-query-to-plist): New function. (org-protocol-do-capture): Use new function. (org-protocol-data-separator): Change default separator. Applied, thanks a lot! -- Bastien
Re: [O] Support Freemind/Freeplane export
Jambunathan K kjambunat...@gmail.com writes: How many people are going to read HTML code? [...] In short, the concern you have raised is more cosmetic than functional. Replying to the org-mode mailing list. I did not closely followed the discussion, so maybe I'm missing the point. A lot of people are not going to read HTML, but it does not mean that nobody does. Many people still read HTML code, for a variety of reasons. I find HTML code should stay as legible as possible. As long as legibility is at stake, character entities are a pain in the neck (or anywhere else of your choice along the spine!). So, if the charset of the HTML can be ascertained, usually within the headers, the remainder of the HTML file should take full advantage of it, and limit character entities as much as possible. Character set entities are meaningful when the HTML file does not declare a charset. They should be avoided otherwise, in my opinion. François
Re: [O] [ANN] Merge of new export framework on Wednesday
Bastien-
On Sat, Mar 02, 2013 at 07:14:07PM +0100, Bastien wrote:
Done. You can now use HTML_HEAD instead of HTML_STYLE.
Some variables were also renamed, check the details here:
http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=2752ef
In trying to migrate these changes to the slide exporters, i noticed
some confusion w/ the migration of html-style vs. html-style-extra:
- (:html-style nil nil org-html-style)
- (:html-style-extra HTML_STYLE nil org-html-style-extra newline)
- (:html-style-include-default nil nil org-html-style-include-default)
- (:html-style-include-scripts nil nil org-html-style-include-scripts)
+ (:html-head HTML_HEAD nil org-html-head newline)
+ (:html-style-include-default nil nil org-html-head-include-default-style)
+ (:html-head-include-scripts nil nil org-html-head-include-scripts)
...
- exp-plist :html-style-extra
- (concat (or (plist-get exp-plist :html-style-extra) )
+ exp-plist :html-head-extra
+ (concat (or (plist-get exp-plist :html-head-extra) )
\n
style)
Specifically,
- :html-style was renamed to :html-head (ok), but the
in-buffer property HTML_HEAD was added to this export
property.
- :html-style-extra was (which was associated w/t the
in-buffer property HTML_STYLE) was removed from the export
prop list (but is referenced later in the code.
- `org-html-head-extra' is mentioned in a doc string but never
defined.
I think this is a bug/typo. Wouldn't the following be closer to a
straight renaming:
(:html-head nil nil org-html-head newline)
(:html-head-extra HTML_HEAD nil org-html-head-extra newline)
or should {org-,:}html-head-extra be dropped entirely?
Also, shouldn't :html-style-include-default be
:html-head-include-default?
rick
[O] [PATCH] Don't generate links for empty theme or transition.
* ox-deck.el (org-deck--get-packages): Check for non-blank deck-theme and deck-transition. --- contrib/lisp/ox-deck.el | 16 +--- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/contrib/lisp/ox-deck.el b/contrib/lisp/ox-deck.el index 5d25369..23cc3ab 100644 --- a/contrib/lisp/ox-deck.el +++ b/contrib/lisp/ox-deck.el @@ -308,13 +308,15 @@ Note that the wrapper div must include the class \slide\. (when (file-exists-p (concat dir base html)) (add-to-list 'snippets (concat dir base html)) (org-deck--find-extensions)) -(add-to-list 'sheets - (if (file-name-directory theme) theme - (format %sthemes/style/%s prefix theme))) -(add-to-list - 'sheets - (if (file-name-directory transition) transition - (format %sthemes/transition/%s prefix transition))) +(if (not (string-match-p ^[[:space:]]*$ theme)) + (add-to-list 'sheets +(if (file-name-directory theme) theme + (format %sthemes/style/%s prefix theme +(if (not (string-match-p ^[[:space:]]*$ transition)) + (add-to-list +'sheets +(if (file-name-directory transition) transition + (format %sthemes/transition/%s prefix transition (list :scripts (nreverse scripts) :sheets (nreverse sheets) :snippets snippets))) -- 1.8.1.2
Re: [O] [BABEL] the julia language
Just +1 on incorporating Julia. @Eric, babel is amazing. I am developing on it and I can't wait to use it with my students. Thanks to both of you. On Sun, Mar 3, 2013 at 5:27 PM, Jay Kerns gjkerns...@gmail.com wrote: Dear Eric, On Sun, Mar 3, 2013 at 2:05 PM, Eric Schulte schulte.e...@gmail.com wrote: Hi Jay, Having read through intro-julia.org and scanned ob-julia.el I have to say this looks great. Thanks for sharing! I should be saying Thanks to you! Org Babel is truly great work; I use it almost every day of my life. Would you be willing to contribute ob-julia.el to the Org-mode repository? Yes, of course, it would be an honor to give back to the Org community. And I'm not just saying that. I don't see you listed as an Org-mode contributor (see [1]), so to do so you would likely have to complete the FSF copyright attribution. Please let me (and more importantly Bastien) know if this is something you'd like to do, so we can help get julia support into Org-mode. OK, I'll get started on that right away. Additionally, it would be nice for your excellent introduction to be added to worg, and for julia to be listed as a supported babel language (see [2]). Thanks for the kind words, and I would be happy to contribute to worg. I've been sitting on my hands about worg so far because I'm scared I'm going to break it with something that isn't compatible with the old exporter. In an earlier message Bastien indicated that Org 8.0 might be coming out in a few weeks (thanks, Bastien!) and I've been trying to wait for it patiently. In the meantime, maybe I'll check out the maintenance branch and dig up those old configurations to get the ball rolling on my side. -- Jay -- Evan Misshula Doctoral Student (Criminal Justice) CUNY John Jay Let us reform our schools, and we shall find little reform needed in our prisons. John Ruskin, Unto This Last, essay 2 (1862) English critic, essayist, reformer (1819 - 1900) Instruction does much, but encouragement does everything. Johann Wolfgang Von Goethe www.snrg-nyc.org
[O] Export: definition lists; ordered lists
G'day Orgers, Problem 1: definition lists when exported to HTML, ODT or ASCII look just like they do in the ort-mode file. Shouldn't they be fixed up somehow? Problem 2: I need to export footnotes that are not Org footnotes. They look like this: 1. This is footnote one 2. This is footnote two Of course, the exporter thinks that I am dealing with ordered lists. According to the manual (*if* I understand it correctly), I should be able to get what I want with: [@1]. This is footnote 1. [@2]. This is footnote 2. But I don't. The exported text looks exactly like the two lines above. Am I doing something wrong? (I cheated on the problem by leaving off the full stop in the originals, but I would like it there). Cheers, and thanks for any comments, Alan -- Alan L Tyree http://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
Re: [O] Always use utf-8 for HTML export (No support for other coding systems)
Robert Horn rjh...@alum.mit.edu writes: Achim Gratz writes: Jambunathan K writes: Always use utf-8 for HTML export (No support for other coding systems). For or against. Please register your views. It is becoming more rare these days, but still possible that the document encoding cannot be UTF-8 for whatever reason. So if it's not unduly complicating things, I'd suggest to avoid prescribing the UTF-8 encoding for any and all exports. Chinese law mandates use of GB-18030, not UTF-8. The two are losslessly and unambiguously convertable, but their bit encodings are different. They are accustomed to dealing with UTF-8 from other parts of the world, but might prefer to generate local pages in compliance with the law. My proposal and patch to always use utf-8 stands annulled then. R Horn rjh...@alum.mit.edu --
Re: [O] New beamer exporter: top-aligned columns
On Mar 4, 2013 1:24 AM, Nicolas Goaziou n.goaz...@gmail.com wrote: Try :BEAMER_opt: t property. Worked perfectly, thanks! Eventually I'll be able to generalize these little tidbits on my own. hjh
Re: [O] org-exp-bibtex missing in git?
I do confirm. Thank you. I have been trying to migrate to the new-exporter. I have not had much success so far but I hope to be able to figure it all out soon. Since we do not yet have a documentation, it is difficult. Nicolas has been very kind with help. I have a website that is built using old exporter. It used org-exp-bibtex. I will move it to the new exporter, and if there is a problem, get back to the mailing list. Till then, thank you for your responses. Best, Vikas
[O] colorg report
Hi, Org people. Here is my (short) weekly status on the colorg project! This weekend either, I did not have much time to push on colorg. Yet, I got the inner guts of a test generator, using a fresh colorg server for each test. Starting and stopping colorg servers in quick succession showed latency problems, now solved. On my next visit (likely in one week), and following my plan, the generator will acquire test patterns. François
Re: [O] Agenda buffer: 't' key moves current item to window's top line
Hi James, James Harkins jamshar...@gmail.com writes: After a recent update, I noticed that the agenda buffer now moves the displayed text when you change an item's TODO state using 't'. Fixed, thanks! -- Bastien
Re: [O] [PATCH] Don't generate links for empty theme or transition.
Hi Rick, Rick Frankel r...@rickster.com writes: * ox-deck.el (org-deck--get-packages): Check for non-blank deck-theme and deck-transition. Applied, thanks. Do you want direct commit access? If so, please send me your public key and I'll add you! Thanks for your help, -- Bastien
[O] Bug: can't enforce numbering of ordered list inside unordered list when exporting to PDF
Hi, Although I enforced a staring value of the ordered list inside unordered list, the list in exported PDF starts from 1. I attached an example file. When it is exported to PDF, numbering of the ordered list would be incorrect. Here is my output of org-submit-bug-report. Emacs : GNU Emacs 24.2.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4) of 2013-01-20 on eric Package: Org-mode version 7.9.3f (7.9.3f-dist @ /usr/share/emacs/site-lisp/org/) 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-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-show-empty-lines org-optimize-window-after-visibility-change) org-export-latex-format-toc-function 'org-export-latex-format-toc-default org-export-blocks '((src org-babel-exp-src-block nil) (export-comment org-export-blocks-format-comment t) (ditaa org-export-blocks-format-ditaa nil) (dot org-export-blocks-format-dot nil)) org-export-first-hook '(org-beamer-initialize-open-trackers) org-export-interblocks '((src org-babel-exp-non-block-elements)) 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) ) Sincerely, -- Hiroshi Saito test.org Description: Binary data
[O] Bug: org-publishing error [7.9.3e (7.9.3e-7-g1056fc-elpa @ c:/home/.emacs.d/elpa/org-20130211/)]
To: emacs-orgmode@gnu.org Subject: Bug: org-publishing error [7.9.3e (7.9.3e-7-g1056fc-elpa @ c:/home/.emacs.d/elpa/org-20130211/)] --text follows this line-- Each time I try to org-publish-project RET the debugger produces this error Can you help? Thanks Dexter Emacs : GNU Emacs 24.2.1 (i386-mingw-nt5.1.2600) of 2012-08-28 on MARVIN Package: Org-mode version 7.9.3e (7.9.3e-7-g1056fc-elpa @ c:/home/.emacs.d/elpa/org-20130211/) current state: == (setq org-export-blocks '((src org-babel-exp-src-block nil) (export-comment org-export-blocks-format-comment t) (ditaa org-export-blocks-format-ditaa nil) (dot org-export-blocks-format-dot nil)) org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe) 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-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-agenda-custom-commands '((c Calendar agenda ((org-agenda-ndays 7) (org-agenda-start-on-weekday 0) (org-agenda-time-grid nil) (org-agenda-repeating-timestamp-show-all t) (org-agenda-entry-types (quote (:timestamp :sexp ) ) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook) org-babel-pre-tangle-hook '(save-buffer) org-occur-hook '(org-first-headline-recenter) org-export-interblocks '((src org-babel-exp-non-block-elements)) org-metaup-hook '(org-babel-load-in-session-maybe) org-confirm-elisp-link-function 'yes-or-no-p org-export-latex-format-toc-function 'org-export-latex-format-toc-default org-export-preprocess-before-normalizing-links-hook '(org-remove-file-link-modifiers) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) org-publish-project-alist '((orgfiles :base-directory /tmp/org/ :base-extension org :publishing-directory /tmp/html/notebook/ :publishing-function org-publish-org-to-html :headline-levels 3 :section-numbers nil :table-of-contents nil :style link rel=\stylesheet\\n href=\../other/zenburn-code.css\ type=\text/css\/ :html-preamble t) (images :base-directory /tmp/images/ :base-extension jpg\\|gif\\|png :publishing-directory /tmp/html/images/ :publishing-function org-publish-attachment) (other :base-directory /tmp/other/ :base-extension css\\|el :publishing-directory /tmp/html/other/ :publishing-function org-publish-attachment) (website :components (orgfiles images other))) org-agenda-include-diary t org-export-first-hook '(org-beamer-initialize-open-trackers) org-from-is-user-regexp nil 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-metadown-hook '(org-babel-pop-to-session-maybe) org-agenda-files '(~/org) org-src-mode-hook '(org-src-babel-configure-edit-buffer org-src-mode-configure-edit-buffer) org-after-todo-state-change-hook '(org-clock-out-if-current) org-babel-load-languages '((emacs-lisp . t) (sh . t)) org-confirm-shell-link-function 'yes-or-no-p ) --- here is test file #+STARTUP: showall * General Test Project ** MUST DO GENERAL TODO 1. first thing 2. second thing ** TABLE #+CONSTANTS: c=299792458. pi=3.14 eps=2.4e-6 | lab1 | lab2 | lab3 | | a |1 | 0.5 | | b |5 | 2.5 | | 299792460. | 3.14 | 1.57 | #+TBLFM: $3=$2/2::@4$1=$c::@4$2=$pi file:remember.org --- remember.org contents * remember This a the first line in the remember file --- here is the traceback Debugger entered--Lisp error: (wrong-type-argument stringp nil) string-match(\\([^]\\)\\([_^]\\) nil) org-export-protect-sub-super(nil) org-export-normalize-links() org-export-preprocess-string(#(#+STARTUP: showall\n\n* General Test Project\n\n\n\n \n** MUST DO GENERAL TODO\n1. first thing \n2. second thing\n\n\n** TABLE\n#+CONSTANTS: c=299792458. pi=3.14 eps=2.4e-6\n| lab1 | lab2 | lab3 |\n| a |1 | 0.5 |\n| b |5 | 2.5 |\n| 299792460. | 3.14 | 1.57 |\n#+TBLFM: $3=$2/2::@4$1=$c::@4 $2=$pi\n\n\nfile:remember.org\n\n 0 18 (fontified t font-lock-fontified t face org-meta-line) 18 19 (fontified t) 19 20 (fontified t) 20 22 (fontified t face org-level-1) 22 42 (fontified t face org-level-1) 42 49 (fontified t) 49 50 (fontified t face org-hide) 50 52 (fontified t face org-level-2) 52 72 (fontified t face org-level-2) 72 73 (fontified t) 73 90 (fontified t) 90 106 (fontified t) 106 108 (fontified t) 108 109 (fontified t face org-hide) 109 111 (fontified t face
Re: [O] Bug: org-publishing error [7.9.3e (7.9.3e-7-g1056fc-elpa @ c:/home/.emacs.d/elpa/org-20130211/)]
Hi Dexter, Dexter Rodriguez odta...@gmail.com writes: Each time I try to org-publish-project RET the debugger produces this error Can you help? Please update to the latest release, it has been fixed there. Thanks, -- Bastien
Re: [O] [patch] ox-koma-letter
Hi Nicolas,
Nicolas Goaziou writes:
Hello,
Alan Schmitt alan.schm...@polytechnique.org writes:
Rasmus writes:
Export the following to LaTeX:
#+BEGIN_SRC Org
#+TITLE:test
#+LATEX_HEADER:\newcommand{test}{\textsc{ps}:this is a test}
#+LATEX_HEADER:\newcommand{ttest}{\textsc{ps}\:this is a test}
#+LATEX_HEADER:\newcommand{tttest}{\textsc{ps}\\:this is a test}
#+LATEX_HEADER:\newcommand{est}{\textsc{ps}$\colon$this is a test}
this is a test
#+END_SRC
I didn't read the thread carefully, but there should be a space after
#+LATEX_HEADER:.
Yes, this changes everything, thanks for spotting it.
So I guess the only part of the letter design I'm worried about is
having a 'ps' with several paragraphs. (I guess it's related to the footnote
with multiple paragraphs questions, but I guess the two blank lines
approach is only for footnotes.)
Alan
Re: [O] Always use utf-8 for HTML export (No support for other coding systems)
Jambunathan K kjambunat...@gmail.com writes: My proposal and patch to always use utf-8 stands annulled then. Okay. I guess we shall go with the workaround solution for ox-freemind.el, then. Can you provide a patch for this? Thanks! -- Bastien
