Re: [O] [ANN] Merge of new export framework on Wednesday
On Mon, Feb 04, 2013 at 08:49:28AM -0500, David Bjergaard wrote: Detlef Steuer detlef.ste...@gmx.de writes: [...] If there are no docs at all I, as a simple user, would suggest to postpone the release till after some usage notes are available. Alternatively keep the old exporter alive , please, till the new one has documentation. (or the migration path has documentation) [...] If you rely on org-mode for some production-level things, wouldn't it be most prudent to wait until the new exporter was shipped and fully tested before migrating your work setup? You'll still have all the documentation for the older version in the mean time, and once the new documentation is written, you'll be able to migrate with fewer problems. I would echo this sentiment. Org mode from master has no business in a production environment, just like any other software project. You can still keep using the latest stable release of Org (or even the tip of the maint branch) in production. And once everything is ready (including docs) for the new exporter, it will be released and possibly shipped with Emacs. You can easily switch then. Is there any particular reason for you to use master in production? Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Eric, On Tue, Feb 05, 2013 at 11:37:35AM +1030, Eric S Fraga wrote: I have been using the new exporter for many tasks but have not completely moved over for two: generation of beamer presentations and publishing of web pages. The latter is probably not a major issue for me but the former is. I simply have no idea how to convert my old org beamer files to the new exporter as there is no documentation at all. The source code (org-e-beamer.el) is of some help but not enough for me to know how to convert, in particular, slides with blocks and columns. I have used the beamer export quite a few times with the new exporter, and I'm very pleased with it. I believe there is one backwards incompatible change, apart from that I think it's mostly feature enhancements. I have been trying to write some of the things down as a Worg article as preliminary documentation, but lately I have been incredibly busy to make any significant progress. I started from the old beamer tutorial as a template on how to structure it. Usually I also keep an eye out on the mailing list for questions related to the beamer export with the new exporter (although lately I have been much less active for the same reasons). Maybe I should put whatever I have on Worg so that others can work on it. I'll try to find some time in the coming two weeks. Hopefully this is a little reassuring. -- Suvayu Open source is the future. It sets us free.
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Eric, On Tue, Feb 05, 2013 at 07:55:46PM +1030, Eric S Fraga wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: Maybe I should put whatever I have on Worg so that others can work on it. I'll try to find some time in the coming two weeks. I think that would be great. I would be happy to work on any such document if it means getting some documentation in place. If you want to send me, offline, what you've got, I'd be happy to have a look. I have attached a somewhat cleaned up version of what I had so far. You can apply the patch on top of Worg master. If you think this is clean enough for a starting point then I will push it to Worg. Cheers, -- Suvayu Open source is the future. It sets us free. From d7dfb6133bcea0127d0c386334a833e8ac64323e Mon Sep 17 00:00:00 2001 From: Suvayu Ali fatkasuvayu+li...@gmail.com Date: Tue, 5 Feb 2013 10:21:23 +0100 Subject: [PATCH] Documentation for beamer export with new exporter Start an article to serve as initial documentation for beamer export using the new exporter. This is also the working document for a tutorial for the exporter. --- org-tutorials/org-beamer/org-e-beamer.org | 141 ++ 1 file changed, 141 insertions(+) create mode 100644 org-tutorials/org-beamer/org-e-beamer.org diff --git a/org-tutorials/org-beamer/org-e-beamer.org b/org-tutorials/org-beamer/org-e-beamer.org new file mode 100644 index 000..f857174 --- /dev/null +++ b/org-tutorials/org-beamer/org-e-beamer.org @@ -0,0 +1,141 @@ +#+TITLE: Beamer presentations using the new export engine +#+AUTHOR:Suvayu Ali +#+EMAIL: fatkasuvayu+linux at gmail dot com +#+DATE: 2013-02-05 +#+DESCRIPTION: +#+KEYWORDS: +#+LANGUAGE: en +#+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t +#+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc +#+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js +#+EXPORT_SELECT_TAGS: export +#+EXPORT_EXCLUDE_TAGS: noexport +#+LINK_UP: +#+LINK_HOME: + +#+startup: folded + +* Introduction +This tutorial covers exporting org documents to LaTeX Beamer slides +using the new export engine, =org-elements= and =org-export=, written +by Nicolas Goaziou. + +_Note:_ It will not cover any of the basic features common with the +old beamer exporter; it will only focus on the improvements, new +additions and backwards incompatibilities. It is also assumed that +the reader is already acquainted with GNU Emacs and Org mode itself. +Basic understanding of LaTeX and the Beamer package is also assumed. + +* Configuring export options +Apart from the usual export options provided by the =OPTIONS= keyword, +you can put additional beamer export options in the file header. For +a minimal beamer export, you have to specify the =LaTeX_CLASS= and the +=LaTeX_CLASS_OPTIONS= keywords in the header of a file. A preset +export template can be inserted by calling the interactive function +=org-e-beamer-insert-options-template=. This can be further modified +as per your needs. You can also do a subtree export; in that case you +can provide the keywords as =PROPERTIES=. However the keyword names +should be prepended with =EXPORT_=. A list of supported +keywords are, + +#+caption: Export option keywords and corresponding subtree properties. +| File header keywords | Subtree properties | +|---+--| +| =OPTIONS= | =EXPORT_OPTIONS= | +| =LaTeX_CLASS= | =EXPORT_LaTeX_CLASS= | +| =LaTeX_CLASS_OPTIONS= | =EXPORT_LaTeX_CLASS_OPTIONS= | +| =LaTeX_HEADER=| =EXPORT_LaTeX_HEADER=| +| =BEAMER_THEME=| =EXPORT_BEAMER_THEME=| +| =BEAMER_FONT_THEME= | =EXPORT_BEAMER_FONT_THEME= | +| =BEAMER_INNER_THEME= | =EXPORT_BEAMER_INNER_THEME= | +| =BEAMER_OUTER_THEME= | =EXPORT_BEAMER_OUTER_THEME= | + +For a subtree export, a few extra keywords are supported. For example +you can specify the exported filename with the =EXPORT_FILE_NAME= +property. + +#+caption: Properties specific to subtree export +| Subtree properties | Functionality| +|+--| +| =EXPORT_TITLE= | Export title | +| =EXPORT_AUTHOR=| Export author| +| =EXPORT_DATE= | Export date | +| =EXPORT_FILE_NAME= | Export file name | + +A simple file header might look like the example below. +#+begin_example + ,#+LaTeX_CLASS: beamer + ,#+LaTeX_CLASS_OPTIONS: [smaller,presentation] + ,#+BEAMER_THEME: default +#+end_example +A corresponding subtree export should have properties as shown below. +#+begin_example + ,* Exported title +:PROPERTIES: +:EXPORT_LaTeX_CLASS: beamer +:EXPORT_LaTeX_CLASS_OPTIONS: [presentation,smaller] +:EXPORT_BEAMER_THEME: default +:EXPORT_FILE_NAME: presentation.pdf +:END: +#+end_example + +The export class is passed on to the =\documentclass= LaTeX command, +and the options
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Eric, On Tue, Feb 05, 2013 at 11:20:18PM +1030, Eric S Fraga wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: I have attached a somewhat cleaned up version of what I had so far. You can apply the patch on top of Worg master. If you think this is clean enough for a starting point then I will push it to Worg. I think it's definitely worth pushing to Worg. There's obviously much to do but having even the basics that you present in this document is very helpful. Just knowing that there is an org-e-beamer minor mode made it worth reading. I pushed the commit, but I see the publishing failed. remote: Publishing file /home/emacs/git/worg/org-tutorials/org-beamer/org-e-beamer.org using `org-publish-org-to-html' remote: Exporting... remote: Wrong type argument: stringp, nil remote: worg publish process 16964 exited at 02/05/13@07:01:27 Not sure why though since I checked publishing to html before committing. Can someone take a look? -- Suvayu Open source is the future. It sets us free.
Re: [O] tagging text, not headlines
On Mon, Feb 04, 2013 at 07:03:01PM -0500, 42 147 wrote: It would be nice to keep things in the org-style (e.g., :favorite song: is preferable to --- favorite song, just on rudimentary aesthetic grounds. I often put in my own cookies inside floawing text. For example, I label doubts in my notes with a (?). In the example below, I have a doubt about comment 2. Some statement - Comment 1 - Comment 2 (?) Then I can easily look for it with occur or grep from the commandline. If you want fontification for cookies like above, you can try something like this (untested): ;; font-lock customisations (defface my-global-tag-face '((t (:background royalblue4 :foreground thistle :weight bold))) Face for the global tags. :group 'my-faces) (add-hook 'find-file-hook (lambda () (font-lock-add-keywords nil '((\\[ (]\\([a-zA-Z0-9]\\+\\)[) ]\\ 1 'my-global-tag-face prepend) Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] New exporter, beamer confusion
On Wed, Feb 06, 2013 at 01:32:22PM +0100, Rasmus wrote: I don't know how hard it would be to make the default block (of level 3, say) a list block, but I guess that's ultimately what you want? Such a behavior shouldn't be the default, IMO, since a headline is not a list. Nested headlines being translated to lists was always a misfeature in the old exporter. This was extensibly discussed on the list before Nicolas implemented the current beamer exporter. I do not see any reason to not fix old inconsistent behaviour for the sake of backwards compatibility. That said, I think the best way to deal with this is to follow what Nicolas suggested, mark the subtree and then do `C-c -' to convert these headlines into lists. This can be automated to a significant degree by using keyboard macros or custom lisp. A well tested keyboard macro can be easily saved and used as a command. Since the OP says his old beamer presentations number in the hundreds, the way I would approach this is to keep the macro/function handy and convert it if and when these presentations are required. Hope this helps, -- Suvayu Open source is the future. It sets us free.
[O] Worg publishing issue
Hello Worgers, Amidsts all the commotion about documentation for the new exporter, I committed a very early incomplete draft article documenting the new beamer exporter. http://orgmode.org/cgit.cgi/worg.git/commit/?id=d7dfb6133bcea0127d0c386334a833e8ac64323e But I see that it is not being published. I got the following publishing error after pushing my commit. remote: Publishing file /home/emacs/git/worg/org-tutorials/org-beamer/org-e-beamer.org using `org-publish-org-to-html' remote: Exporting... remote: Wrong type argument: stringp, nil remote: worg publish process 16964 exited at 02/05/13@07:01:27 Any ideas? -- Suvayu Open source is the future. It sets us free.
[O] Org mode build failure
Hi, I am encountering the following build failure when I do `make compile': make[1]: Entering directory `/path/build/org-mode/lisp' rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc install -m 644 -p . install: missing destination file operand after ‘.’ Try 'install --help' for more information. make[1]: *** [addcontrib] Error 1 make[1]: Leaving directory `/path/build/org-mode/lisp' make: *** [compile] Error 2 Any ideas what changed? -- Suvayu Open source is the future. It sets us free.
Re: [O] Worg publishing issue
Hi Bastien, On Thu, Feb 07, 2013 at 09:42:15AM +0100, Bastien wrote: But I see that it is not being published. I just published it: http://orgmode.org/worg/org-tutorials/org-beamer/org-e-beamer.html Thanks! I got the following publishing error after pushing my commit. remote: Publishing file /home/emacs/git/worg/org-tutorials/org-beamer/org-e-beamer.org using `org-publish-org-to-html' remote: Exporting... remote: Wrong type argument: stringp, nil remote: worg publish process 16964 exited at 02/05/13@07:01:27 Any ideas? 2 problems, a trivial one and a let's-prepare-for-headache one: 1. `org-publish-org-to-html' does not exist in the new export/publish libraries -- Nicolas, would that be enough to have aliases here (from org-publish-org-to-html to org-html-publish-to-html)? I guess many people rely on thse org-publish-org-to* functions. 2. Worg is published using the maint branch of org-mode.git. Which means that neither the new exporter nor the new way of escaping Org syntax in src code blocks are available... My guess is that your file org-e-beamer.org uses the new syntax for src code blocks -- I had to use the org-mode.git *master* branch to publish it correctly. We will need to update each begin_src block in Worg in order to use a recent org-mode.git for publishing. In my file there are no begin_src blocks, however I do have begin_example blocks like the following: #+begin_example ,#+LaTeX_CLASS: beamer ,#+LaTeX_CLASS_OPTIONS: [smaller,presentation] ,#+BEAMER_THEME: default #+end_example I have not been following the list very closely for the last 5-6 months (too many deadlines in real life :(), has the above escaping syntax been changed? Thanks, -- Suvayu Open source is the future. It sets us free.
Re: [O] Org mode build failure
Hi Achim, On Thu, Feb 07, 2013 at 11:15:14AM +, Achim Gratz wrote: Suvayu Ali fatkasuvayu+linux at gmail.com writes: I am encountering the following build failure when I do `make compile': make[1]: Entering directory `/path/build/org-mode/lisp' rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc install -m 644 -p . install: missing destination file operand after ‘.’ Try 'install --help' for more information. make[1]: *** [addcontrib] Error 1 make[1]: Leaving directory `/path/build/org-mode/lisp' make: *** [compile] Error 2 Any ideas what changed? The new exporter moved into core and the files you specified in ORG_ADD_CONTRIB are no longer existing there. Remove that definition and all is well. Thanks a lot, this works. I don't know how I missed that! -- Suvayu Open source is the future. It sets us free.
Re: [O] Structure editing
On Fri, Feb 08, 2013 at 01:27:05AM +0530, Sanjib Sikder wrote: Is it possible to have a line between two tress which should not hide when folded, like the following example ? No this is not possible. Any text following a headline is by definition a part of the tree and will be folded with it. Maybe if you tell us what you are trying to achieve, we can suggest an alternative? -- Suvayu Open source is the future. It sets us free.
Re: [O] old to new converter transition
On Thu, Feb 07, 2013 at 03:26:10PM +0100, Rainer M Krug wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Some remarks and questions about transition to new exporter: 1) org-export-latex-listings -becomes- org-latex-listings Since Nicolas answered your specific question, I thought I should share some of my notes about moving to the new exporter. I assembled this by reading Nicolas' announcement, grepping through the source, and some light testing after the switch. 1. Export engine renamed: org-export → ox 2. Backend requires renamed: org-e-* → ox-* 3. All backend specific variables and functions renamed: - org-export-* → org-* (e.g. org-html-xml-declaration, ..) - org-e-* → org-* (e.g. org-latex-classes, org-ascii-bullets, ..) 4. Generic export variables retain the name org-export-* (e.g. org-export-dispatch-use-expert-ui, org-export-filter-headline-functions, ..) 5. org-latex-to-pdf-process has been renamed to org-latex-pdf-process 7. Guess, export snippets and backend symbols renamed: - e-backend → backend Hope this help others going through the switch. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] Structure editing
Hi Sanjib, On Fri, Feb 08, 2013 at 11:06:21AM +0530, Sanjib Sikder wrote: On Fri, Feb 8, 2013 at 2:18 AM, Suvayu Ali fatkasuvayu+li...@gmail.comwrote: On Fri, Feb 08, 2013 at 01:27:05AM +0530, Sanjib Sikder wrote: Is it possible to have a line between two tress which should not hide when folded, like the following example ? No this is not possible. Any text following a headline is by definition a part of the tree and will be folded with it. Maybe if you tell us what you are trying to achieve, we can suggest an alternative? What I am trying to achieve is an 'ordinary' heading, which is not in the beginning of the document but somewhere in the middle of the document, before a particular level one heading of a tree. At present the 'ordinary' heading gets hidden in the previous tree/subtree. Unfolded state: === * Heading 1 ** Heading 1-1 ** Heading 1-2 AT THIS POINT, A LINE (heading for the section below) WHICH SHOULD NOT BE FOLDED * Heading 2 ** Heading 2-1 ** Heading 2-2 This sounds a bit superfluous. Why can't you include that text in the heading Heading 2. I understand what you are trying to do, and it is not possible with Org (at least not without some dirty hack), but you still haven't said _why_ you are attempting this. Is this document aimed for export to a specific backend, or is it just the way you want the org buffer to look? If it is about export to a backend, you should look for solutions in the backend and not Org. Hope this helps, PS: please do not top post, it becomes difficult to follow the discussion after a while. -- Suvayu Open source is the future. It sets us free.
Re: [O] [New exporter] Key bindings and typographical error
Hi Eric and Seb, On Sat, Feb 09, 2013 at 12:28:06AM +1030, Eric S Fraga wrote: Given that we have moved to a multi-key sequence for selecting exporter and then action, could these two aspects not be dealt with in the mini-buffer? I find the display of all the options confusing... I would rather have the dispatcher prompt, in the mini-buffer, something along the lines of: : Export to: (l) latex, (h) html, (o) ODT, (a) ascii with the choices obviously depending on the backends initialised. Then, depending on the key (e.g. l): : Export as: (l) file, (b) buffer, (p) PDF, ... Here one of the options (file?) could be the default, so it would be sufficient to hit RET for most cases. Just a thought which arises from my having to use small screens sometimes as I'm a sucker for punishment and insist on using Emacs on my phone and the dispatch window is too large sometimes... I agree whole-heartedly. The dispatcher menu has always bugged me. It doesn't seem to fit into rest of Emacs' minibuffer oriented interface. For me this would mean one more step towards making Org mode friendlier to text terminals. I would also suggest that beamer be a different target, separate from latex, chosen by a different first key (e.g. b). This would then allow some unification of the second key sequence (f=file, b=buffer, p=PDF, v=view...)? I am ambivalent about this suggestion. Finally, I could be more radical and suggest that the whole export dispatch should be based on keymaps... with C-h, as usual, bringing up the options. But this might be too radical ;-) Again, agree whole-heartedly. :) Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] old to new converter transition
On Fri, Feb 08, 2013 at 05:25:58PM +0100, Bastien wrote: Rainer M Krug r.m.k...@gmail.com writes: Would it be possible to collect this info on a quick and dirty worg page? At the moment, the info is in several different threads? Please guys be *bold* and don't hesitate to contribute to Worg directly... This is WikiStyle :) Thanks! http://orgmode.org/cgit.cgi/worg.git/commit/?id=e6a51c5a553d6ab4d164af7d1ce54fbc5b5028a0 :) -- Suvayu Open source is the future. It sets us free.
[O] Possible issue with the Makefile
Hi Achim, While switching to the new exporter I noticed something. In my local.mk I had `ORG_ADD_CONTRIB = org-e-*' before, but after the switch I removed it (as you had pointed it out in another thread :)). Despite that, all the org-e-* files under org-mode/lisp were not removed after I did `make cleanall'. I need to do a `git clean -f -x -e local.mk' to get rid of them. Don't you think this should be handled by the Makefile, or is this non-trivial to deal with? Thanks, -- Suvayu Open source is the future. It sets us free.
Re: [O] Possible issue with the Makefile
On Fri, Feb 08, 2013 at 11:17:28PM +0100, Achim Gratz wrote: Suvayu Ali writes: In my local.mk I had `ORG_ADD_CONTRIB = org-e-*' before, but after the switch I removed it (as you had pointed it out in another thread :)). Despite that, all the org-e-* files under org-mode/lisp were not removed after I did `make cleanall'. You would have needed to do the make clean before the update that renamed respectively moved those files if you use globbing patterns. Don't you think this should be handled by the Makefile, or is this non-trivial to deal with? See above. There is no way of knowing what the globbing pattern expanded to after the files are no longer present in contrib/ and you can't just go around in lisp/ and try the globbing there, at least not if you don't want files to vanish at random. Thanks, I understand now :). I'll put this in the FAQ. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] Worg publishing issue
On Wed, Feb 06, 2013 at 02:19:03PM +0100, Suvayu Ali wrote: [...] But I see that it is not being published. I got the following publishing error after pushing my commit. remote: Publishing file /home/emacs/git/worg/org-tutorials/org-beamer/org-e-beamer.org using `org-publish-org-to-html' remote: Exporting... remote: Wrong type argument: stringp, nil remote: worg publish process 16964 exited at 02/05/13@07:01:27 I still see issues with the publishing. My previous commit[1] to the FAQ was not published. The post-commit hook output had timed out on my end then. I had thought that was probably some network issue on my side but that doesn't seem to be the case. When I tried to push some more edits[2] to that entry, I see the following message remote: Worg publish process 11929 is still running... Can someone please take a look? Cheers, Footnotes: [1] http://orgmode.org/cgit.cgi/worg.git/commit/?id=e6a51c5a553d6ab4d164af7d1ce54fbc5b5028a0 [2] http://orgmode.org/cgit.cgi/worg.git/commit/?id=12fadc1554816ecd21fddc0af589070a99e94245 -- Suvayu Open source is the future. It sets us free.
Re: [O] Worg publishing issue
On Wed, Feb 13, 2013 at 06:32:46PM +0100, Bastien wrote: The problem was not in your file at all, it was in a bug I introduced in the maint branch, it is fixed now. Worg is wide open to new contribs! Thanks a lot Bastien! -- Suvayu Open source is the future. It sets us free.
Re: [O] Problems with latex_class
On Sat, Feb 16, 2013 at 06:51:02PM -0500, Marvin Doyley wrote: Hi there, I just updated to the latest version of org. I have a couple of classes (ie latex packages and classes, etc) that I use frequently. These are defined using the add-to-list 'org-export-latex-classes function in my .emacs file For some reason the latest version of org doesn't recognize my classes. More specifically when I evoke the org-latex exporter I get an error message 'unknown latex class blah Does anybody know how to resolve this ? The variable has been renamed to org-latex-classes for consistency. -- Suvayu Open source is the future. It sets us free.
Re: [O] Problems with latex_class
On Sun, Feb 17, 2013 at 01:51:57AM +0100, Suvayu Ali wrote: On Sat, Feb 16, 2013 at 06:51:02PM -0500, Marvin Doyley wrote: Hi there, I just updated to the latest version of org. I have a couple of classes (ie latex packages and classes, etc) that I use frequently. These are defined using the add-to-list 'org-export-latex-classes function in my .emacs file For some reason the latest version of org doesn't recognize my classes. More specifically when I evoke the org-latex exporter I get an error message 'unknown latex class blah Does anybody know how to resolve this ? The variable has been renamed to org-latex-classes for consistency. Also check this out: http://orgmode.org/worg/org-faq.html#new-exporter-switch -- Suvayu Open source is the future. It sets us free.
Re: [O] Integration of notmuch email references in notes in org-mode
Hi Rainer
On Mon, Feb 18, 2013 at 02:49:32PM +0100, Rainer M Krug wrote:
- From time to time, I have to include email references in notes in org.
There is obviously
org-notmuch.el, but I am not to happy with it as, when exporting the notes,
the link is shown but
neither clickable nor the resulting email is shown in the exported document
(both understandable).
This has also been an irritation of mine. I think I will take your
second idea (include the email on export) and see if I can come-up with
a patch for org-notmuch. Since I'm still a newbie elisp programmer,
this might take a while. :-p
I could also include a bash source block:
#+header: :results output org
#+begin_src sh
notmuch show thread:
#+end_src
the result ooks ugly formated - if I use raw, I can not fold the result, due
to strange characters
at the beginning of the header lines.
Actually what you see is supposed to be easily parsed. From the
notmuch-show man page:
--format=(text|json|sexp|mbox|raw)
text (default for messages)
The default plain-text format has all text-content MIME parts
decoded. Various components in the output, (message, header,
body, attachment, and MIME part), will be delimited by
easily-parsed markers. Each marker consists of a Control-L
character (ASCII decimal 12), the name of the marker, and then
either an opening or closing brace, ('{' or '}'), to either open
or close the component. For a multipart MIME message, these parts
will be nested.
I'm assuming what you presently see is in text format (default). Since
you are not happy with this, I would suggest you try the mbox format.
[...]
mbox
All matching messages are output in the traditional, Unix mbox
format with each message being prefixed by a line beginning with
From and a blank line separating each message. Lines in the
message content beginning with From (preceded by zero or more
'' characters) have an additional '' character added. This
reversible escaping is termed mboxrd format and described in
detail here:
http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/mail-mbox-formats.html
A quick question though, how do you plan on handling attachments, I
presume you want to strip them? In that case you will have to parse the
output anyway.
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] activate contrib packages
On Mon, Feb 18, 2013 at 04:39:35PM +0100, Rainer M Krug wrote: On 18/02/13 16:23, Suvayu Ali wrote: On Mon, Feb 18, 2013 at 04:05:26PM +0100, Rainer M Krug wrote: On 18/02/13 15:42, David Bremner wrote: Rainer M Krug r.m.krug-re5jqeeqqe8avxtiumw...@public.gmane.org writes: By the way, the library org-notmuch distributed with org-mode should make it easy to link into notmuch. Then I probably haven't loaded org-notmuch properly? What do I have to put into my .emacs file to load it properly? I put what I know at http://notmuchmail.org/emacstips/#index24h2 Thanks - got it working under Ubuntu. One thing: in my org from git, org-notmuch is in .../org-mode/contrib/lisp and not .../lisp My following comment is probably OT, but still ... If you install org-mode from git following the instructions from the Makefile, then you should be putting something like the following in your local.mk. # Define if you want to include some (or all) files from contrib/lisp # just the filename please (no path prefix, no .el suffix), maybe with # globbing ORG_ADD_CONTRIB = org-notmuch If you do that, then David's instructions are accurate. Ok - what is the advantage of doing so? I usually prefer to have all my config in one file (here emacs.org) so I don't have to remember what I have to change where? This way make knows about it and compiles the contrib libraries you use. Also you do not have unnecessary libraries in your load-path. Since Achim is the expert, he will be able to tell you more. -- Suvayu Open source is the future. It sets us free.
[O] Including linked emails during export (was Re: Integration of notmuch email references in notes in org-mode)
Hi, On Mon, Feb 18, 2013 at 04:33:45PM +0100, Rainer M Krug wrote: On 18/02/13 16:12, Suvayu Ali wrote: On Mon, Feb 18, 2013 at 02:49:32PM +0100, Rainer M Krug wrote: - From time to time, I have to include email references in notes in org. There is obviously org-notmuch.el, but I am not to happy with it as, when exporting the notes, the link is shown but neither clickable nor the resulting email is shown in the exported document (both understandable). This has also been an irritation of mine. I think I will take your second idea (include the email on export) and see if I can come-up with a patch for org-notmuch. Since I'm still a newbie elisp programmer, this might take a while. :-p If there is a solution in sight, I am happy to wait a bit - email in export, possibly in a block so that it is set apart from the rest of the document, would be brilliant. Possibly having an option which can be set to have links exported as links or expanded on export, would be really nice. The option to open the link is out of the question since different people read their emails differently. There is no way for a library to get everything right, specially since the link won't be in Emacs. It is in the exported file (e.g. html, pdf, txt). Now to include the email during the export at first I thought it should be possible to write a filter, but then I realised I need to insert an email quote block after whatever parent greater-element holds the link and then redirect the link to this new block. A filter allows you a way to modify an element, but nothing more. So I think the correct approach here would be to write a derived backend. This complicates things quite significantly since now you need to support each backend separately. I wonder if there is any easier (generic) way to do the above for all present and future backends. I have CC'd Nicolas, lets see what he has to say. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] killing all contents of a headline
On Tue, Feb 19, 2013 at 01:09:30PM +0100, Bastien wrote: When using speedy commands (setq org-use-speed-commands t) . C-w at the beginning of a headline. I'm willing to update the . speedy command and use @ instead to be consistent with the C-c @ command. Yes that would be good. To save you some work, I attached a patch. -- Suvayu Open source is the future. It sets us free. From 664f375b7c2f65269e730fdb870cf81cd01f2bf2 Mon Sep 17 00:00:00 2001 From: Suvayu Ali fatkasuvayu+li...@gmail.com Date: Tue, 19 Feb 2013 16:40:14 +0100 Subject: [PATCH] Change default org-mark-subtree speed command * org.el (org-speed-commands-default): Change default binding for org-mark-subtree from . to @ to be more consistent with C-c @. TINYCHANGE --- lisp/org.el | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lisp/org.el b/lisp/org.el index 91763d3..85a6a4a 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -18658,7 +18658,7 @@ BEG and END default to the buffer boundaries. (^ . org-sort) (w . org-refile) (a . org-archive-subtree-default-with-confirmation) -(. . org-mark-subtree) ;; FIXME Better use @ (see C-c @) here? +(@ . org-mark-subtree) (# . org-toggle-comment) (Clock Commands) (I . org-clock-in) -- 1.8.1.2
Re: [O] killing all contents of a headline
On Tue, Feb 19, 2013 at 11:40:31AM -0500, 42 147 wrote: The @ replacement is also a sensible idea -- can either of you send me the source code for this? Or how would I update my org-mode to include it? Take a look at the following FAQ and the two after: http://orgmode.org/worg/org-faq.html#updating-org -- Suvayu Open source is the future. It sets us free.
Re: [O] [new exporter] Guides on what incompatibilities to watch for?
On Tue, Feb 19, 2013 at 11:57:03AM -0600, Gunnar Wolf wrote: Hi, I'm not very specific in this mail, but am wondering… I have some nontrivial documents written in Org-mode. My main use case for Org is mostly to author texts, rather than using its time-tracking features. I fear that with the new exporter, several of my documents' features will no longer work or -worse- be interpretted differently, having a negative impact in my output. Is there a guide on what items should I mostly watch for (or even better, what syntax changes should I make) to get my results as similar as possible to what I had beforehand? I am not yet running with the new release; as I follow the Debian packaging, I'll rather wait until it lands in my system. Still, I want to prepare and not let this get me off-guard! Take a look here: http://orgmode.org/worg/org-faq.html#new-exporter-switch Apart from that I know about the following changes in syntax (to the best of my knowledge): 1. Attribute lines now take plists : #+attr_latex :width 5cm : #+attr_beamer :options width=5cm 2. Beamer backend now interprets nested headline levels as blocks instead of lists. For some preliminary guidance you can look at this: http://orgmode.org/worg/org-tutorials/org-beamer/org-e-beamer.html. Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] New exporter - variable name
On Wed, Feb 20, 2013 at 03:24:48PM +0100, itmejl wrote: Hi! Switching from old to new exporter. Using 7.9.3e and Emacs 24.2 on win7. Question about variables and name on equivalent vaiables in new exporter. Are there new equivalents variables for old variables org-odt-styles-dir, org-export-odt-styles-file and those for schema-dir? http://orgmode.org/worg/org-faq.html#new-exporter-switch -- Suvayu Open source is the future. It sets us free.
Re: [O] org-meta-return
On Wed, Feb 20, 2013 at 02:32:16PM -0500, 42 147 wrote: Invaluable command, but often I want to insert a new headline at point that is one level down; i.e.: *** topic_1 [COMMAND] subtopic M-RET M-right -- Suvayu Open source is the future. It sets us free.
Re: [O] org-meta-return
On Wed, Feb 20, 2013 at 04:17:48PM -0500, 42 147 wrote: I notice that C-M-RET is undefined. If anyone wants to add the functionality as described in my original post, and bind it to that key chord, I would be grateful; in the meantime, I'll create a macro / interactive defun to do the same. Jon's suggestion is pretty good, but you can also do (org-defkey org-mode-map (kbd C-M-RET) 'my-interactive-defun) where my-interactive-defun does what you want. -- Suvayu Open source is the future. It sets us free.
Re: [O] org-meta-return
On Wed, Feb 20, 2013 at 07:11:38PM -0500, Nick Dokos wrote: [Warning: off-topic] 42 147 aeus...@gmail.com wrote: My hands might be smaller than average, or, at least, smaller than yours. To reach right I must shift my entire arm to the right and downward. To reach RET no such movement is necessary. Maybe a slight turn of the wrist to the right. I doubt my hands are bigger than yours: I have to do exactly what you describe (at least on the bigger keyboards). It's just not as big a deal for me as it is for you. I do not see anyone mention pressing complicated key combinations with both hands. I usually press control or meta keys with my left, and character or arrow keys with my right. But maybe that is easier for me since I use a pointing device sparingly. -- Suvayu Open source is the future. It sets us free.
Re: [O] [RFC] [PATCH] conditional use of latex packages
Hello Aaron, On Wed, Feb 20, 2013 at 11:02:21PM -0500, Aaron Ecay wrote: Hello, The current way that org handles LaTeX packages for export isn’t optimal. The org-latex-(default-)packages-alist variables define a set of packages that are loaded always. If a user wants to use advanced functionality (booktabs for nicer table export, listings or minted for nicer source code), s/he has to add the packages to these variables manually. And a package like longtables is imported into every document, slowing down compilation even when it is not used. [...] I fully sympathise with your intentions and will test the patches at the earliest when I have some time (probably tomorrow). Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] C-c ^ not fully useful
On Mon, Feb 18, 2013 at 02:36:57PM -0500, François Pinard wrote: - Could org-sort, by default and for most of its current option letters, sort alphabetically (or lexicographically as they say!) over the visual aspect of the line instead of its physical contents? It might be difficult if Emacs has no function to reach the visual aspect of a line. I guess that most users would expect a visual sort. I think this is a good idea. It should be possible to just test if the first entity is a link and extract the title part using org-elements - Options might be added to sort over the physical contents of the line instead. And there always is M-x sort-lines RET !). Agreed. - Could some parameterisation be added so one could map user written functions over (free) option letters? Again, a good idea. :) Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] org-element
On Fri, Feb 22, 2013 at 11:38:16AM +, Achim Gratz wrote:
How is one supposed to write (longer) equations out on multiple lines (leaving
the operators behind on the previous line obviously works, but is ugly)?
I use LaTeX blocks. So your example would translate to:
#+begin_latex
\begin{equation}
r = a
+ b
- c
\end{equation}
#+begin_latex
With easy templates, entering blocks is trivial (l for LaTeX blocks).
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
[O] [PATCH] Fix typo in org.texi that broke compilation
Attached
--
Suvayu
Open source is the future. It sets us free.
From 3dc825a44e37dd2b8e9ca51428b309ee26326746 Mon Sep 17 00:00:00 2001
From: Suvayu Ali fatkasuvayu+li...@gmail.com
Date: Fri, 22 Feb 2013 14:29:24 +0100
Subject: [PATCH] Fix typo in org.texi that broke compilation
---
doc/org.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/org.texi b/doc/org.texi
index 268cf67..50bb211 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6562,7 +6562,7 @@ used a special setup for @file{remember.el}, then
replaced it with
@file{org-remember.el}. As of version 8.0, @file{org-remember.el} has
been completely replaced by @file{org-capture.el}.
-If your configuration depends on @fite{org-remember.el}, you need to update
+If your configuration depends on @file{org-remember.el}, you need to update
it and use the setup described below. To convert your
@code{org-remember-templates}, run the command
@example
--
1.8.1.2
Re: [O] org-element
On Fri, Feb 22, 2013 at 02:25:13PM +0100, Nicolas Goaziou wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Fri, Feb 22, 2013 at 11:38:16AM +, Achim Gratz wrote:
How is one supposed to write (longer) equations out on multiple lines
(leaving
the operators behind on the previous line obviously works, but is ugly)?
I use LaTeX blocks. So your example would translate to:
#+begin_latex
\begin{equation}
r = a
+ b
- c
\end{equation}
#+begin_latex
This is a bit different from what the OP is asking for. A LaTeX block
will only be exported by a latex (or derived) back-end. On the other
hand, \[1+1\] may be exported by any back-end (for example using mathjax
in html).
Ah! I did not realise that \[..\] was also interpreted by mathjax.
Thanks for pointing it out.
Anyway, the equivalent would be a LaTeX environment:
\begin{equation*}
r = a
+ b
- c
\end{equation*}
Typo on my part. :-p
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] bug-tracker
On Fri, Feb 22, 2013 at 08:56:54PM +0100, Andreas Röhler wrote: With exception of the noise, M-x report-emacs-bugs tends to send. Herewith is a slim version, adapted to org-mode AFAIU [...] Org already uses one of its own: org-submit-bug-report -- Suvayu Open source is the future. It sets us free.
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] {New exporter] What happened to the export template
Hey Seb, On Mon, Feb 25, 2013 at 02:15:05PM +0100, Sebastien Vauban wrote: PS- By the way, there is already such a sort of template for Beamer... I believe Nicolas' argument was, for the new exporter such a template depends on the backend hence a default one for beamer makes sense but not a backend agnostic template. I'm not completely sure I follow the argument though, since keywords like TITLE, DATE, AUTHOR, or even an OPTIONS line seem generic enough for most backends. But then I have not thought long enough to spot any inconsistencies. :-p Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] org-meta-return
On Tue, Feb 26, 2013 at 12:10:13PM +0100, Sebastien Vauban wrote: Quite a bit OT, but is it true that, for example, to type `C-whatever', we should use both hands, one for `C' and the other for `whatever'? I determine that depending on the key combination. e.g. C-x or C-s I do with my left hand with the left control key, but I do C-l, C-k, C-y, M-y with two hands with the left control key. Somehow I have a preference towards using control or meta keys with my left hand eventhough I find the two handed version much more comfortable. Maybe it's time to consciously switch to two handed key presses for everything. -- Suvayu Open source is the future. It sets us free.
Re: [O] Exporter interface question
On Wed, Feb 27, 2013 at 01:00:30PM +0100, Carsten Dominik wrote: On 27.2.2013, at 09:52, Nicolas Goaziou n.goaz...@gmail.com wrote: Carsten Dominik carsten.domi...@gmail.com writes: When exporting a subtree, lets drop a mark at the headline and then go to this mark when C-c C-e is called with a prefix arguments. This would allow to keep the cursor somewhere deep in the subtree while working on it, and still be able to quickly repeat the export command. It would be nice indeed. Though, it may be useful to put some additional limitations to this feature. For example, it would trigger only when on the same buffer as before, perhaps even within the same subtree. Yes, this is possible. I'll look into it. I love the idea, including Nicolas' proposed restrictions. Until now I was defining keyboard macros for this. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] Including linked emails during export (was Re: Integration of notmuch email references in notes in org-mode)
Hey Nicolas,
On Wed, Feb 27, 2013 at 02:35:04PM +0100, Nicolas Goaziou wrote:
Hello,
Rainer M Krug r.m.k...@gmail.com writes:
But what about defining notmuch as a new language for babel, so that
one could do the following:
#+begin_src notmuch :exports raw
search id:x
#+end_src
Would not be much different then
#+begin_src sh :exports raw
notmuch search id:x
#+end_src
but possibly open more possibilities for customizations?
x
Or inline it could be src_notmuch{search id:x}
The general advantage would be that one can use the existing
infrastructure for code blocks and
FWIW, I think the approach suggested by Rainer is good, i.e. writing
a new language for Babel, with specific headers. Such blocks would
then be expanded into appropriate Org syntax the exporter can
understand.
Thanks for your feedback. I haven't had any time to look at this yet.
I'll keep this in mind.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] bug with timestamp fontification (bisected to b6b509b)
On Wed, Feb 27, 2013 at 04:54:54PM +0100, Nicolas Richard wrote: Reproduce by doing: emacs -q -L /home/youngfrog/sources/org-mode/lisp/ -f org-mode --eval '(insert 2012-02-27 Wed.)' ^ Are you sure your timestamp has the correct syntax? As far as I know there should be no periods at the end of the day name. BTW, how do you enter timestamps? You can use C-c C-x . and C-c C-x ! for active and inactive timestamps. This way you can avoid sysntax errors conveniently. Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] Frustrated user of orgmode
On Mon, Mar 04, 2013 at 07:10:47PM +0530, Vikas Rawal wrote: Do we have even a sketchy documentation of what a user is supposed to http://orgmode.org/worg/org-faq.html#new-exporter-switch -- Suvayu Open source is the future. It sets us free.
Re: [O] org-exp-bibtex missing in git?
On Mon, Mar 04, 2013 at 10:10:37AM +0530, Vikas Rawal wrote: 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. I think people should be using maint instead of master for production use. -- Suvayu Open source is the future. It sets us free.
Re: [O] [ANN] Merge of new export framework on Wednesday
On Tue, Feb 05, 2013 at 02:07:50PM +0100, Suvayu Ali wrote: Hi Eric, On Tue, Feb 05, 2013 at 11:20:18PM +1030, Eric S Fraga wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: I have attached a somewhat cleaned up version of what I had so far. You can apply the patch on top of Worg master. If you think this is clean enough for a starting point then I will push it to Worg. I think it's definitely worth pushing to Worg. There's obviously much to do but having even the basics that you present in this document is very helpful. Just knowing that there is an org-e-beamer minor mode made it worth reading. I pushed the commit, but I see the publishing failed. I updated the article considerably. Comments welcome. http://orgmode.org/cgit.cgi/worg.git/commit/?id=0b98d52bee82c856d46df7ce49bc7738fb9d2b4d Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] [ANN] Merge of new export framework on Wednesday
Hi Bastien, On Sat, Mar 02, 2013 at 07:14:07PM +0100, Bastien 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 It seems to me a few files in contrib needs to be updated, and also the manual of course. $ git grep -i html_style contrib/lisp/ox-deck.el: (:html-style-extra HTML_STYLE nil org-html-style-extra newline) contrib/lisp/ox-s5.el: (:html-style-extra HTML_STYLE nil org-html-style-extra newline) doc/org.texi:@cindex #+HTML_STYLE doc/org.texi:#+HTML_STYLE: link rel=stylesheet type=text/css href=stylesheet.css / doc/org.texi:@itemx #+LaTeX_HEADER:, #+HTML_STYLE:, #+HTML_LINK_UP:, #+HTML_LINK_HOME:, I updated the FAQ entry on Worg for new exporter switch. http://orgmode.org/cgit.cgi/worg.git/commit/?id=b137e931edd6cddfdcf4df40d29e93f01ad59242 Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] Frustrated user of orgmode
On Mon, Mar 04, 2013 at 11:42:24AM -0700, T.F. Torrey wrote: I'm not making myself sound smart here, but the point is that I will be happy when we get the documentation migrated over. FWIW, Worg (and Org) is a volunteer effort. That particular FAQ entry started with me putting up a rather sparse 5 or so item list sometime back. Later it was brought to the current level of detail by Bastien and others. My point is, the easiest way to improve documentation is to add it yourself[1] when you hit on something new. If you do not know how to add to Worg take a look here: http://orgmode.org/worg/#sec-4 If getting that to work is a problem, post on the list with the text and someone else will add it. Cheers, PS: I updated the index for that entry. Let me know if this is better. Footnotes: [1] Here by you I do not mean specifically you Terry, just a place holder for any Org user. -- Suvayu Open source is the future. It sets us free.
Re: [O] Predictive for Latex in org-mode
Hi Bastien and Sanjib, On Tue, Mar 05, 2013 at 10:44:55AM +0100, Bastien wrote: Hi Sanjib, Sanjib Sikder sanjibju2...@gmail.com writes: I have installed Predictive package. It is working fine for normal English words while working in org-mode. When I am writing few latex codes in org-mode, it is not suggesting latex keywords it seems. I have added the following in .emacs. I'm not sure I understand the problem: isn't the purpose of the predictive package to suggest keywords depending on the context? If so, why is it a problem that predictive suggests LaTeX keywords? Do you mean: once I write some LaTeX keywords in an org-mode buffer, it only suggests LaTeX keywords (and no english words) for the rest of the session? I think what he means is that predictive _does not_ suggest LaTeX keywords inside an org-mode buffer. I do not know how predictive works, but if it is dependent on the major mode to offer suggestions, then it will fail suggesting LaTeX keywords in Org mode. This particular feature of Org mode, allowing LaTeX commands natively is somewhat of a quirk. Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] [new exporter] ignoring a headline on export to PDF via latex
On Tue, Mar 05, 2013 at 02:43:30PM +, Eric S Fraga wrote: Hello, I used to use the following to ignore a headline when exporting to PDF: #+begin_src emacs-lisp (defun my-e-latex-headline (headline contents info) (if (member ignoreheading (org-element-property :tags headline)) contents (org-latex-headline headline contents info))) (add-to-list 'org-latex-translate-alist '(headline . my-e-latex-headline)) #+end_src With the new exporter, this no longer works. Try using your function with a filter. This filter might work: org-export-filter-headline-functions. Of course it goes without saying you will have to update your function. A very simple test tells me this is probably going to be backend specific. I have had this query about filters for a while now, how to write filters that are backend agnostic. I think I'll start a new thread once I have formulated my question more clearly. Hope this helps, -- Suvayu Open source is the future. It sets us free.
Re: [O] URGENT Need help fixing beamer exporting, can someone jump on IRC?
Hi James, On Tue, Mar 05, 2013 at 11:28:35PM +0800, James Harkins wrote: I had been using C-c C-x ! to reload org after doing a make but this turned out to mess things up pretty badly. I could get reasonable behavior only by quitting emacs and restarting it. I don't know if that should be considered a bug or not. Perhaps I don't understand what C-c C-x ! is supposed to do? Tonight at least, it was totally unreliable. org-reload is there for convenience, quite often a proper emacs restart is indeed required to get a consistent Org instance. That said, I have noticed something odd about the new exporter and org-reload. I think with the new exporter after doing org-reload, org related config is not reloaded properly. This borks the Org instance. This is more visible when using the Beamer backend since it requires customisation of org-latex-classes by the user. One of these days, I'll try to come up with a proper recipe to reproduce this. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] [new exporter] ignoring a headline on export to PDF via latex
On Tue, Mar 05, 2013 at 01:25:03PM -0500, Nick Dokos wrote: Eric S Fraga e.fr...@ucl.ac.uk wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: [...] Try using your function with a filter. This filter might work: org-export-filter-headline-functions. Of course it goes without saying you will have to update your function. Thanks Suvayu. It is this update that I need help with! The documentation of that variable is close to impenetrable to me (e.g. what is a /communication channel/?). Reading the commentary in ox.el might help, at least to shed light on some terminology. As far as know, it is a property list returned by the parser. Look in lisp/ox.el:1094. Beyond that my understanding is also a bit hazy. I think I have gone through that bit of the comments at least once, but it is a little difficult to follow for me (my lack of understanding of lisp is probably to blame :-p). Good Luck, -- Suvayu Open source is the future. It sets us free.
[O] [Bug] beamer backend and org-reload
Hi Achim,
On Tue, Mar 05, 2013 at 07:26:54PM +0100, Achim Gratz wrote:
Suvayu Ali writes:
That said, I have noticed something odd about the new exporter and
org-reload. I think with the new exporter after doing org-reload, org
related config is not reloaded properly.
Config is not reloaded at all (and never has been), any configuration
variables that are already existing are not touched when the file gets
reloaded.
This borks the Org instance. This is more visible when using the
Beamer backend since it requires customisation of org-latex-classes by
the user. One of these days, I'll try to come up with a proper recipe
to reproduce this.
Please do, this should not happen.
Here is the recipe:
1. emacs -nw -Q -l ~/minimal-org.el
;;; minimal-org.el: Minimal setup to load latest `org-mode'
;;; Code:
(setq debug-on-error t
debug-on-signal nil
debug-on-quit nil)
(add-to-list 'load-path (expand-file-name ~/build/org-mode/lisp))
(require 'ox-beamer)
(add-to-list 'org-latex-classes
'(beamer
\\documentclass\[presentation\]\{beamer\}
(\\section\{%s\} . \\section*\{%s\})
(\\subsection\{%s\} . \\subsection*\{%s\})
(\\subsubsection\{%s\} . \\subsubsection*\{%s\})))
2. C-x C-f some-file.org RET
3. Now try to export: C-c C-e. You can see menu options for beamer export.
4. Now reload Org: C-c C-x !. Try step 3 again. You will notice the
entries for beamer is missing.
This might actually be a problem with ox-beamer and not org-reload
because I noticed my other Org customisations do stay intact (which is
of course in line with your comment about settings not being touched).
Instead of step (3), you could also try M-x org-beamer-export-as-latex.
After step (4), repeating this alternate step (3) should give you the
following backtrace.
Debugger entered--Lisp error: (error Unknown \beamer\ back-end: Aborting
export)
signal(error (Unknown \beamer\ back-end: Aborting export))
error(Unknown \%s\ back-end: Aborting export beamer)
org-export-barf-if-invalid-backend(beamer)
org-export-as(beamer nil nil nil nil)
org-export-to-buffer(beamer *Org BEAMER Export* nil nil nil nil)
org-beamer-export-as-latex()
call-interactively(org-beamer-export-as-latex record nil)
command-execute(org-beamer-export-as-latex record)
execute-extended-command(nil org-beamer-export-as-latex)
call-interactively(execute-extended-command nil nil)
command-execute(execute-extended-command)
Hopefully my recipe is complete to fix this issue.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] [new exporter] ignoring a headline on export to PDF via?latex
On Tue, Mar 05, 2013 at 08:58:28PM +, Charles Berry wrote: [...] FWIW, I defun'ed filters like the above for all of the filter functions that can take (text backend info) as arguments. Then using a derived backend like the above `latex3', I can see where the filterable elements are. It is trivial to do, but if anyone is interested, I can post or upload somewhere. That would be wonderful! You could put them up on Worg. This section on org-hacks would be appropriate: http://orgmode.org/worg/org-hacks.html#sec-1-10. If you do not have access to Worg, you can post the content in Org format on the list and I can add it. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] [Bug] beamer backend and org-reload
Hi Achim,
On Tue, Mar 05, 2013 at 09:50:29PM +0100, Achim Gratz wrote:
Suvayu Ali writes:
(add-to-list 'org-latex-classes
'(beamer
\\documentclass\[presentation\]\{beamer\}
(\\section\{%s\} . \\section*\{%s\})
(\\subsection\{%s\} . \\subsection*\{%s\})
(\\subsubsection\{%s\} . \\subsubsection*\{%s\})))
Pilot error, I'd say: org-latex-classes is a defcustom, I don't think it
is a good idea to muck with the data directly (it doesn't have
getter/setter methods IIRC, but still). So what happens when you add
the beamer classes properly, via customize — and then do an org-reload?
I see the same problem when I put the following in my minimal-org.el
(custom-set-variables
'(org-latex-classes (quote ((beamer \\documentclass[presentation]{beamer}
(\\section{%s} . \\section*{%s}) (\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})) (chapter
\\documentclass[11pt]{report} (\\chapter{%s} . \\chapter*{%s})
(\\section{%s} . \\section*{%s}) (\\subsection{%s} . \\subsection*{%s})
(\\subsubsection{%s} . \\subsubsection*{%s})) (article
\\documentclass[11pt]{article} (\\section{%s} . \\section*{%s})
(\\subsection{%s} . \\subsection*{%s}) (\\subsubsection{%s} .
\\subsubsection*{%s}) (\\paragraph{%s} . \\paragraph*{%s})
(\\subparagraph{%s} . \\subparagraph*{%s})) (report
\\documentclass[11pt]{report} (\\part{%s} . \\part*{%s}) (\\chapter{%s}
. \\chapter*{%s}) (\\section{%s} . \\section*{%s}) (\\subsection{%s} .
\\subsection*{%s}) (\\subsubsection{%s} . \\subsubsection*{%s})) (book
\\documentclass[11pt]{book} (\\part{%s} . \\part*{%s}) (\\chapter{%s} .
\\chapter*{%s}) (\\section{%s} . \\section*{%s}) (\\subsection{%s} .
\\subsection*{%s}) (\\subsubsection{%s} . \\subsubsection*{%s})
)
I did encounter another curious problem though. When in the customise
buffer I try to add a new class, I get a customize interface similar to
what is shown below.
[INS] [DEL] List:
LaTeX class: beamer
LaTeX header: \documentclass[presentation]{article}
Choice: [Value Menu] Heading:
numbered: \section{%s}
unnumbered: \section*{%s}
[INS] [DEL] List:
LaTeX class: article
LaTeX header: \documentclass[11pt]{article}
Levels:
[INS] [DEL] Choice: [Value Menu] Heading:
numbered: \section{%s}
unnumbered: \section*{%s}
[INS] [DEL] Choice: [Value Menu] Heading:
numbered: \subsection{%s}
unnumbered: \subsection*{%s}
[...]
As you can see, there is no way to add deeper sectioning entries for the
new entry (beamer). I worked around it for the moment to proceed with
my test, but I find this very curious indeed.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] [new exporter] #+TOC in beamer export
On Tue, Mar 05, 2013 at 10:53:42PM +0100, Andreas Leha wrote:
Nicolas Goaziou n.goaz...@gmail.com writes:
Andreas Leha andreas.l...@med.uni-goettingen.de writes:
from a recent thread I learned about #+TOC (there's always something new
to learn about org mode).
I'd like to use it in a beamer document. Here I find it hard to use
because it introduces its own frame.
My question basically is: How is this supposed to be used in a beamer
doc?
(And would it not be easier if it did not introduce its own frame?)
It seems useful to keep frame around TOC generated from toc:t option.
But we could remove it from TOC generated from #+TOC keywords.
Thanks for taking this further. Indeed, for the toc:t triggered TOC the
frame is absolutely useful.
I'm not sure what a \tableofcontents outside a frame would look like.
Can someone show an example?
I also had another thought; sometimes for long presentations, I use
something like this:
\AtBeginSubsection[]{
\ifthenelse{
\(\value{section}=1\)\AND\(\value{subsection}=1\)
}{}
{
\begin{frame}beamer
\frametitle{Outline}
\tableofcontents[currentsubsection]
\end{frame}
}
}
At the moment I put it in as one long LaTeX_HEADER line. But would it
be possible to leverage #+TOC: into having a similar effect? It might
then provide a greater degree of control where you want the toc frame to
appear.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] [new exporter] #+TOC in beamer export
On Wed, Mar 06, 2013 at 12:52:24AM +0100, Nicolas Goaziou wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
I'm not sure what a \tableofcontents outside a frame would look like.
Can someone show an example?
I think that the idea behind a frameless TOC is that you provide your
own frame for it.
It makes sense since #+TOC: allows to control accurately the location of
your table of contents.
That makes a lot of sense. :)
I also had another thought; sometimes for long presentations, I use
something like this:
\AtBeginSubsection[]{
[...]
}
At the moment I put it in as one long LaTeX_HEADER line. But would it
be possible to leverage #+TOC: into having a similar effect? It might
then provide a greater degree of control where you want the toc frame to
appear.
I think this kind of control should really belong to specific latex
code.
A TOC limited to current section sure sounds seducing, but I'm not sure
how to achieve this in LaTeX.
I think you are right. I'll see if can find a nice way to do this in
LaTeX, I'll share if I find something.
Cheers,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] [Bug] beamer backend and org-reload
I can confirm this is fixed now. :)
Thanks,
On Wed, Mar 06, 2013 at 12:29:10AM +0100, Nicolas Goaziou wrote:
Hello,
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Hi Achim,
On Tue, Mar 05, 2013 at 07:26:54PM +0100, Achim Gratz wrote:
Suvayu Ali writes:
That said, I have noticed something odd about the new exporter and
org-reload. I think with the new exporter after doing org-reload, org
related config is not reloaded properly.
Config is not reloaded at all (and never has been), any configuration
variables that are already existing are not touched when the file gets
reloaded.
This borks the Org instance. This is more visible when using the
Beamer backend since it requires customisation of org-latex-classes by
the user. One of these days, I'll try to come up with a proper recipe
to reproduce this.
Please do, this should not happen.
Here is the recipe:
1. emacs -nw -Q -l ~/minimal-org.el
;;; minimal-org.el: Minimal setup to load latest `org-mode'
;;; Code:
(setq debug-on-error t
debug-on-signal nil
debug-on-quit nil)
(add-to-list 'load-path (expand-file-name ~/build/org-mode/lisp))
(require 'ox-beamer)
(add-to-list 'org-latex-classes
'(beamer
\\documentclass\[presentation\]\{beamer\}
(\\section\{%s\} . \\section*\{%s\})
(\\subsection\{%s\} . \\subsection*\{%s\})
(\\subsubsection\{%s\} . \\subsubsection*\{%s\})))
2. C-x C-f some-file.org RET
3. Now try to export: C-c C-e. You can see menu options for beamer export.
4. Now reload Org: C-c C-x !. Try step 3 again. You will notice the
entries for beamer is missing.
This should be fixed in master. Thank you.
Regards,
--
Nicolas Goaziou
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Org-mode latex pdf export issue: Underlined lines not breaking properly
Hello Sanjib,
On Wed, Mar 06, 2013 at 06:55:36PM +0530, Sanjib Sikder wrote:
If you feel that the problem is not related to org-mode, then ignore this
email and thanks for your time and patience.
It is indeed a LaTeX issue! And I have an answer too :). Org mode
translates _underlined text_ to \underline{underlined text}, however if
you read the TeX.sx question referenced below you will see that it
doesn't support line breaks and the TeX community recommends \uline{..}
from the ulem package.
http://TeX.stackexchange.com/a/13382/4416
For now you can write a filter to alter the LaTeX source[1]; for the
long haul you should start a separate thread asking to change the
defaults in Org mode. However I'm not sure if that is desirable since
it introduces an extra LaTeX package dependency to handle corner cases.
Hope this helps,
Footnotes:
[1] A nice example can be found here:
http://orgmode.org/worg/exporters/beamer/ox-beamer.html#sec-2-3
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Unicode (hindi/devnagari) in beamer export
On Thu, Feb 2, 2012 at 12:47, Vikas Rawal
vikasli...@agrarianresearch.org wrote:
I need some Hindi/Devnagari text in a beamer presentation. I am able
to use scim-bridge to enter unicode text in orgmode. But have not yet
been able to export it correctly to a beamer presentation.
Any pointers would be helpful.
I don't know about scim-bridge, but you can use transliteration
provided within emacs to enter the text very fluidly. As for export,
try xelatex or lualatex. They have much better unicode support. The
following should do it:
(setq org-latex-to-pdf-process
xelatex -interaction nonstopmode -output-directory %o %f
xelatex -interaction nonstopmode -output-directory %o %f
xelatex -interaction nonstopmode -output-directory %o %f)
and
# for unicode export to pdf with xelatex
#+LATEX_HEADER: \usepackage{xltxtra}
You can choose your font with something like this:
# font for pdf export as article
#+LATEX_HEADER: \setmainfont{Linux Libertine}
Make sure you choose something which supports devanagari.
It would be nice if you report back whether it worked. I would be interested.
GL
--
Suvayu
Open source is the future. It sets us free.
Re: [O] Unicode (hindi/devnagari) in beamer export
On Fri, Feb 3, 2012 at 06:09, Vikas Rawal vikasli...@agrarianresearch.org wrote: Works with a minor change as below: (setq org-latex-to-pdf-process '(xelatex -interaction nonstopmode -output-directory %o %f xelatex -interaction nonstopmode -output-directory %o %f xelatex -interaction nonstopmode -output-directory %o %f)) Ah, extremely sorry about that typo. I am glad things worked for you. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] org-babel export latex problem
On Fri, Feb 3, 2012 at 12:43, Riccardo Romoli ric.rom...@gmail.com wrote: The version is 6.33x That is way too old, I believe org-babel is a much newer feature. At least its more mature now. Try one of the newer releases like 7.8.03. http://orgmode.org/w/?p=org-mode.git;a=commit;h=2b3534a81f6f4c925f55ed7aaec31ead6f400577 -- Suvayu Open source is the future. It sets us free.
[O] [BUG] cannot open menu when in an org buffer
Hi, In a minimal Emacs session when I open _any_ org file and try to access the GUI menu with a mouse, I get the following back trace: Debugger entered--Lisp error: (void-function org-in-clocktable-p) org-in-clocktable-p() org-context() (assq :todo-keyword (org-context)) Switching to a non-org buffer (e.g. scratch) the problem disappears. Can someone take a look? Thanks, -- Suvayu Open source is the future. It sets us free.
Re: [O] [BUG] cannot open menu when in an org buffer
On Sat, Feb 4, 2012 at 18:46, Nick Dokos nicholas.do...@hp.com wrote: suvayu ali fatkasuvayu+li...@gmail.com wrote: Hi, In a minimal Emacs session when I open _any_ org file and try to access the GUI menu with a mouse, I get the following back trace: Debugger entered--Lisp error: (void-function org-in-clocktable-p) org-in-clocktable-p() org-context() (assq :todo-keyword (org-context)) Switching to a non-org buffer (e.g. scratch) the problem disappears. Can someone take a look? Confirmed. If I add (require 'org-clock) to my minimal .emacs, it goes away. So it seems to be a missing dependency. It seems an odd dependency to have. Anyway, I noticed something; pressing F10 does bring up the menu as expected without any backtrace. After that I can select anything on the menu with a mouse without problems. The error occurs only when bringing up the menu for the first time with a mouse. Nick Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] [BUG] cannot open menu when in an org buffer
Hi Nick, On Tue, Feb 7, 2012 at 03:31, Nick Dokos nicholas.do...@hp.com wrote: suvayu ali fatkasuvayu+li...@gmail.com wrote: On Sat, Feb 4, 2012 at 18:46, Nick Dokos nicholas.do...@hp.com wrote: Confirmed. If I add (require 'org-clock) to my minimal .emacs, it goes away. So it seems to be a missing dependenc= y. It seems an odd dependency to have. True - org-in-clocktable-p does not have anything to do with clocks, but it ended up in org-clock.el. All of these where am I functions should probably be in org.el. In fact, they all are except for org-in-clocktable-p and org-at-item-p. The latter is in org-list.el and it is not giving an error a) because org-in-clocktable-p errors out first and b) because org.el contains a (require 'org-list). So having a (require 'org-clock) in org.el does have a precedent, but of course this way you end up defeating autoloads: the moment org.el is loaded, all of these things are too. There might be a better arrangement but it's like Pascal's letter[fn:1] : it would require time to find it :-) True, actually this is one of my only gripes (if you could call it that) about org. Loading my org customisation is a fair part of my emacs start time. If I could improve this, it would be perfect. :) Anyway, I noticed something; pressing F10 does bring up the menu as expected without any backtrace. After that I can select anything on the menu with a mouse without problems. That's true: org-context is only called from mouse code, so if you drop the menu without the mouse, there is no problem: selecting a menu item with the mouse, once the menu has dropped, is all widget code and does not invoke org code at all. Thanks for clearing that up. I was always hazy about the emacs interface libraries. I think I'll look into them someday when I have some time. The error occurs only when bringing up the menu for the first time with a mouse. That I find surprising though: I would expect that if you try to click on the menu again, you'd get the error again: nothing is done to define the function, so why should anything be different the second time? Ah, sorry my mistake. I did not word it correctly. I didn't mean bringing up the menu with a mouse a second time. I meant once the menu was up (lets say the File menu), going to a different one by hovering over the menu (say Edit or Options) with a mouse doesn't trigger the backtrace. Clearly it is obvious now why it would be so from your explanation above. :) [fn:1] Approximately: Forgive the length of this letter: I did not have time to make it shorter. This is a very interesting and true remark. I was not familiar with it before. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] Changing [X] by something else
Hi François, 2012/2/8 François Pinard pin...@iro.umontreal.ca: Hi, Org people. I notice in org.el that [X] is hard-wired, while I would have liked the possibility of changing it by [✓] in my things, which I find both softer and cleaner. Could these ([ ], [-] and [X]) be turned into variables? The difficulty might be to recognize them properly, I guess. While it would be nice that I could change it, it might also have a negative effect, making Org files less interoperable between people. On the other hand, the TODO keywords are already changeable, so there is a kind of precedent :-). One has to draw the line at something. Although I am just a user I feel this falls into the same category as the request from last year to make the stars in a headline configurable. This is an integral part of org syntax. Last time during the customisable headline thread this was discussed extensively and the core developers agreed that making org syntax customisable defeats interoperability and breaks external tools written to parse org files. That said, I believe you can customise how these check boxes are exported to various backends. AFAIR, there is a nice thread discussing the case for latex export from the end of last year. Hope this helps. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] Changing [X] by something else
Hi François, 2012/2/8 François Pinard pin...@iro.umontreal.ca: suvayu ali fatkasuvayu+li...@gmail.com writes: Hi François, Hi, Suvayu (or Ali?) Which ever comes natural to you, I don't mind either. :) Although I am just a user I feel this falls into the same category as the request from last year to make the stars in a headline configurable. This is an integral part of org syntax. Well, Org mode is built over Outline mode, stars are coming from there. While [?] are pure Org mode additions, so Org owns it better... True, in the discussion about stars I believe the suggestion was to use a regex for the headline marker in outline-mode. But the majority opinion was it would be too fragile. Your argument that org owns this better is probably correct, but I am no expert. Nicolas is the list expert, he will be able to say how easy/feasible/difficult it would be to make this customisable. making org syntax customisable defeats interoperability and breaks external tools written to parse org files. Exactly my objection to my own suggestion. :) That said, I believe you can customise how these check boxes are exported to various backends. AFAIR, there is a nice thread discussing the case for latex export from the end of last year. Oh, I was not at all thinking about export. Just my own pleasure while editing Org mode files within Emacs. :-) Not a big deal, of course. Ah! Lets wait for the experts to comment. François -- Suvayu Open source is the future. It sets us free.
Re: [O] [BUG] cannot open menu when in an org buffer
Hi David, On Wed, Feb 8, 2012 at 20:14, David Maus dm...@ictsoc.de wrote: I pushed a fix to master that relocates org-in-clocktable-p from org-clock.el to org.el -- the problem should be fixed now. This shouldn't break things because org-clock requires org. I can confirm the issue is fixed now. Best, -- David Thanks a lot. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] OrgMode - Export Simple Chinese text to Latex/PDF
Hi,
On Wed, Feb 8, 2012 at 10:07, Haisheng Wu fre...@gmail.com wrote:
#+LaTeX_HEADER: \usepackage{CJK}
#+LaTeX_HEADER: \begin{CJK}{UTF8}{gbsn}
Have you tried the following instead?
#+LaTeX_HEADER: \usepackage{CJK}
#LaTeX: \begin{CJK}{UTF8}{gbsn}
some text in chinese
#LaTeX: \end{CJK}{test}
GL
--
Suvayu
Open source is the future. It sets us free.
[O] [BUG] tags sparse tree broken
Hi, I believe the sparse tree search is broken. It has been broken for a while I think. Searching for tags returns no matches. I get the following backtrace with debug enabled on a minimal emacs on using `next-error' after a tag search which should return a positive result. Debugger entered--Lisp error: (error No more matches) signal(error (No more matches)) error(No more matches) byte-code(`\305\\211\2036 org-occur-next-match(1 nil) next-error(nil) call-interactively(next-error nil nil) To replicate this, open the attached org file and search for the tag Qn. C-c / m Q n RET I tried running a quick edebug on org-sparse-tree, but I am having a problem in answering the prompt and stepping forward with the edebug simultaneously. Hopefully someone else will have a better luck. Thanks, -- Suvayu Open source is the future. It sets us free. * Bsâ° decay ** Decay model :Qn: 1. Justify neglecting CP violation - in decay for the DsK channel - in Bs mixing for both DsK and DsÏ channels 2. Verify master equations ** Build PDF :Qn:
Re: [O] OrgMode - Export Simple Chinese text to Latex/PDF
On Thu, Feb 9, 2012 at 03:21, Haisheng Wu fre...@gmail.com wrote: I think it is `#+Latex` rather than `#Latex`. The former one works for me. Yes, both you and Nick are correct. :) Sorry for the typo. -- Suvayu Open source is the future. It sets us free.
Re: [O] worg access source
Hi Thomas, On Thu, Feb 9, 2012 at 11:09, Thomas Alexander Gerds tagt...@sund.ku.dk wrote: in worg it would be great if (as in emacs muse) there was a link to the underlying .org file which was used to generate the page. my naiive attempt to catch a glimpse of the source of Two ways, http://orgmode.org/worg/sources/ $ git clone git://orgmode.org/worg.git Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] OrgMode - Export Simple Chinese text to Latex/PDF
Hi, On Thu, Feb 9, 2012 at 04:12, Haisheng Wu fre...@gmail.com wrote: As you would see, the `CJK` is nested in the `document`, therefore, title which is in Chinese as well can not display correctly. Any ideas? Well, when it comes to utf8 export, I always recommend xelatex or lualatex. :) Recently there was a thread on devanagari (for Sanskrit and its derivatives like Hindi) which proved useful to the OP. http://thread.gmane.org/gmane.emacs.orgmode/51914 Hope this helps. -- Suvayu Open source is the future. It sets us free.
Re: [O] [BUG] tags sparse tree broken
Hi David, On Sun, Feb 12, 2012 at 19:41, David Maus dm...@ictsoc.de wrote: I pushed a patch to master that should fix the problem. Sparse tree search for a tag as outlined in the example works now in current master the same way it did in Org 7.7. It was not the matching that was broken, but the highlighting of the matches. Could you check if this problem is fixed for you? Your patch fixes the problem. Thanks a lot. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] multilingual presentation with org
On Wed, Feb 15, 2012 at 14:08, Nick Dokos nicholas.do...@hp.com wrote: I am now exploring the possibilities of how to make a 'presentation' putting the two together. I am not too comfortable using emacs for the final show because emacs occasionally crashes -- due to non-standard fonts, input methods or what I dont know -- and I dont want this to happen in front of 50 people! A two-column beamer presentation perhaps? If I may add, xelatex should let you export presentations with both Roman and Devanagari text. You might find the following thread useful. http://thread.gmane.org/gmane.emacs.orgmode/51914/focus=51919 GL -- Suvayu Open source is the future. It sets us free.
Re: [O] Refile: refile to any open file.
On Sun, Feb 26, 2012 at 02:16, lngn...@gmail.com wrote: I have been using the function oog in org-occur-goto.el to search any open file, so somewhere in that file is a way to find open files. What remains is to use some condition from this file to declare org-refile-targets. I understand that a function can be used as a value of this variable. Look at the function oog-check-input. I believe it checks buffer-list and the major-mode for each buffer to determine whether to include it in the search. GL -- Suvayu Open source is the future. It sets us free.
Re: [O] Git repo not cloneable?
On Fri, Mar 2, 2012 at 09:00, jeremiah.do...@gmail.com wrote: I was looking to add scala support to org-babel, but the repo linked from http://orgmode.org/worg/org-contribute.html appears to need some server-side love: $ git --version git version 1.7.9.2 $ git clone http://orgmode.org/w/org-mode.git Cloning into 'org-mode'... fatal: http://orgmode.org/w/org-mode.git/info/refs not found: did you run git update-server-info on the server? I believe the url is incorrect (http cloning is not enabled I think). http://orgmode.org/worg/worg-git.html#contribute-to-worg That said, it might be nice to have the clone and push urls mentioned on the gitweb summary page as in the repo.or.cz mirror: http://repo.or.cz/w/Worg.git. -- Suvayu Open source is the future. It sets us free.
Re: [O] Git repo not cloneable?
Hi Jonathan and Jeremiah, On Fri, Mar 2, 2012 at 14:29, Jonathan Leech-Pepin jonathan.leechpe...@gmail.com wrote: Seems that the URL listed on that page is not correct for cloning. The URL is the correct one for web access. [...] So http cloning is enabled, the URL simply isn't mentioned (And I can't remember where I found it originally) I updated the page. Please take a look and feel free to edit/comment if its still unclear. :) Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] How to include pre-existing pdf files/pages into orgmode pdf or other export output
Hey Martin, On Fri, Mar 2, 2012 at 16:57, Martin Weigele mar...@weigele.de wrote: Hi, is there an easy way to do this (rather than to fiddle around with resulting pdfs)? If you want to include the preexisting pdf as an image, just do [[file:/path/to/preexisting.pdf]] and export. I don't think there is any straight forward way to include it as text though. Thanks, Martin HTH -- Suvayu Open source is the future. It sets us free.
Re: [O] Include TOC in PDF export?
On Sat, Mar 3, 2012 at 00:44, Michael Hannon jm_han...@yahoo.com wrote:
I think the only way to get a TOC is to set num:t. You can probably
rewrite a chunk of latex code so that unnumbered sections etc end up in
the .toc file, but I think it would be a fairly major undertaking.
Thanks, Nick. I think I'll learn to love the current arrangement.
There is a slightly hacky solution. With num:nil, you can put a line
like the following line after every heading you want to see in the
TOC.
\addcontentsline{toc}{subsection}{\nameref{subsection latex label}}
Hope this helps.
--
Suvayu
Open source is the future. It sets us free.
Re: [O] ConTeXt export
On Sat, Mar 3, 2012 at 17:07, David Rogers davidandrewrog...@gmail.com wrote: Nick Dokos nicholas.do...@hp.com writes: Can ConTeXt handle a LaTeX program? No it can't, not that I'm aware of anyway. While both LaTeX and ConTeXt inherit from plain TeX, and therefore look somewhat similar cosmetically, they don't work the same. (e.g. ConTeXt does not use LaTeX packages, the .tex files differ in essentials and not just in details, etc.) However with the latest experimental org-export library by Nicolas, it should be possible to write an exporter without much trouble. :) -- Suvayu Open source is the future. It sets us free.
[O] [BUG] LATEX_CLASS_OPTIONS not working
Hi,
I think there is a regression bug in latex export. The
#+LATEX_CLASS_OPTIONS: a4paper
directive is supposed to generate the following latex code:
\documentclass{a4paper,article}
Instead it generates:
\documentclassa4paper{article}
A minimal example is attached.
Thanks,
--
Suvayu
Open source is the future. It sets us free.
#+LATEX_CLASS: article
#+LATEX_CLASS_OPTIONS: a4paper
#+LATEX_HEADER: \setmainfont{Linux Libertine}
* Top heading
** Meeting
:PROPERTIES:
:LaTeX_CLASS: article
:EXPORT_FILE_NAME: report.pdf
:EXPORT_TITLE: Report
:EXPORT_OPTIONS: H:1 num:nil toc:nil ^:{}
:END:
*** Things
+ Some item
+ Item 2
+ Last item
* Last heading
bug.tex
Description: TeX document
Re: [O] [BUG] LATEX_CLASS_OPTIONS not working
Hi Nick,
On Tue, Mar 6, 2012 at 03:42, Nick Dokos nicholas.do...@hp.com wrote:
I don't think it's a regression - at least I could only find two commits
that touched the relevant code (lines 1397-1405 in org-latex.el) and
they are from 2008 and 2009.
Also the latex syntax is
\documentclass[a4paper]{article}
Now I am embarrassed. :-| You are correct, I misread the latex
documentation and I didn't check the org manual before reporting.
That's what I get for sending emails after 3:00 AM. :-/
Extremely sorry about the mix up.
--
Suvayu
Open source is the future. It sets us free.
[O] AUCTeX conflicting with org-mode
Hi, I am having conflicts AUCTeX when I try to open plain latex files after I exporting an org file to latex. These are the exact steps. 1. Start Emacs as: emacs -q (so that the site files load and I have auctex available). 2. Open any org file and export to latex, C-c C-e l. 3. Open another plain latex file. At this point I see this backtrace: Debugger entered--Lisp error: (void-variable TeX-master) #[nil \301\302 !\203 \303=\203 \304\305\211\306#\210\307\306!\207 [TeX-master file-exists-p buffer-file-name shared TeX-master-file nil t TeX-update-style] 4]() run-hooks(find-file-hook) after-find-file(nil t) find-file-noselect-1(#buffer velo-links.tex ~/graphics/velo-links.tex nil nil ~/graphics/velo-links.tex (263573 64770)) find-file-noselect(~/graphics/velo-links.tex nil nil t) find-file(~/graphics/velo-links.tex t) call-interactively(find-file nil nil) Since removing the auctex site files out of the site-lisp directory resolves the conflict I am assuming the problem stems from my auctex installation. Can someone help me trouble shoot this? -- Suvayu Open source is the future. It sets us free.
Re: [O] AUCTeX conflicting with org-mode
On Wed, Mar 7, 2012 at 06:08, Yagnesh Raghava Yakkala yagn...@live.com wrote: I can reproduce this., I think your auctex installation is fine. Its definitely from org. Thanks a lot for taking a look and confirming. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] AUCTeX conflicting with org-mode
Hi Nick, On Wed, Mar 7, 2012 at 16:39, Nick Dokos nicholas.do...@hp.com wrote: In org-latex.el Tex-master is set to t to suppress auctex from asking for that variable while exporting with org-latex..(IIRC there was a discussion and Carsten made that change) Some how org leaving that to void at the end of org-latex export (I coundn't figure out how?). That sounds far-fetched to me: once TeX-master is bound, one has to go to some lengths to unbind it (see makunbound - but I'm pretty sure that's not used anywhere in org code - there are a few instances of the function analog, fmakunbound). It seems much more likely that in these cases, it never got bound in the first place, possibly because of dependency problems in the loading of packages. But I cannot reproduce the problem, so I'm speaking theoretically only and my imagination may be failing me. I think Yagnesh is talking about this thread: http://thread.gmane.org/gmane.emacs.orgmode/48512/focus=48526 I took a quick look at the commit (ca49e89) and the source (org-latex.el line 888), but everything looks good to me. To add more information, while exporting to latex I get the following warning when auctex site files are present. Export buffer: Exporting to LaTeX... Warning: defvar ignored because TeX-master is let-bound Making TeX-master buffer-local while let-bound! Hope this clearly explains the problem I am facing. PS: BTW, why is AUCTeX not part of Emacs? -- Suvayu Open source is the future. It sets us free.
Re: [O] AUCTeX conflicting with org-mode
Hi Nick, On Wed, Mar 7, 2012 at 21:00, Nick Dokos nicholas.do...@hp.com wrote: As a workaround-and-proof-of-concept, try (load tex) before loading org. Assuming that that works, you will probably want to arrange things that this is always done. This worked as you hypothesised. :) It might also be the case that Carsten's fix needs to be modified to check whether TeX-master is bound already - then it can let-bind it without problems; but I'm not sure what to do if that's not the case. The question I have is what exactly causes tex.el to be loaded at that point in time. If you can figure that out, then that might lead to a more permanent solution. I am not sure how I can conclusively confirm that, but I think when I export to latex, the exported latex buffer loads it. For example, I don't see this issue when say I go through these steps: 1. Open a tex file. 2. Open and export an org file to latex. 3. Open a new tex file. In this case step (1) must be loading tex.el, circumventing the issue. Cheers, -- Suvayu Open source is the future. It sets us free.
[O] [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS
Hi,
This is adds a small example to better illustrate the use of
LaTeX_CLASS_OPTIONS. Thanks to Nick for encouraging me to submit this.
Thanks,
--
Suvayu
Open source is the future. It sets us free.
From 1e8dc6e253ba72a1574dc7fb5f91028f68f01241 Mon Sep 17 00:00:00 2001
From: Suvayu Ali fatkasuvayu+li...@gmail.com
Date: Thu, 8 Mar 2012 01:31:05 +0100
Subject: [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS
* org.texi (Header and sectioning): Add example demonstrating how to use
LaTeX_CLASS_OPTIONS.
TINY CHANGE
---
doc/org.texi | 21 -
1 files changed, 16 insertions(+), 5 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 33ffe28..84d3102 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10361,11 +10361,22 @@ @subsection Header and sectioning structure
@code{org-export-latex-default-packages-alist} and
@code{org-export-latex-packages-alist} are spliced.}, and allows you to
define the sectioning structure for each class. You can also define your own
-classes there. @code{#+LaTeX_CLASS_OPTIONS} or a @code{LaTeX_CLASS_OPTIONS}
-property can specify the options for the @code{\documentclass} macro. You
-can also use @code{#+LaTeX_HEADER: \usepackage@{xyz@}} to add lines to the
-header. See the docstring of @code{org-export-latex-classes} for more
-information.
+classes there. @code{#+LaTeX_CLASS_OPTIONS} or a @code{:LaTeX_CLASS_OPTIONS:}
+property can specify the options for the @code{\documentclass} macro. The
+options to documentclass have to be provided, as expected by @LaTeX{}, within
+square brackets. You can also use @code{#+LaTeX_HEADER: \usepackage@{xyz@}}
+to add lines to the header. See the docstring of
+@code{org-export-latex-classes} for more information. An example is shown
+below.
+
+@example
+#+LaTeX_CLASS: article
+#+LaTeX_CLASS_OPTIONS: [a4paper]
+#+LaTeX_HEADER: \usepackage{xyz}
+
+* Headline 1
+ some text
+@end example
@node Quoting @LaTeX{} code, Tables in @LaTeX{} export, Header and sectioning, @LaTeX{} and PDF export
@subsection Quoting @LaTeX{} code
--
1.7.7.6
Re: [O] [BUG] LATEX_CLASS_OPTIONS not working
Hi Nick, On Wed, Mar 7, 2012 at 23:20, Nick Dokos nicholas.do...@hp.com wrote: but I think it would be better to add an example in section 12.6.2, Header and sectioning structure. I would encourage you to submit a doc patch. Comments are of course welcome. :) http://patchwork.newartisans.com/patch/1201/ Extremely sorry about the mix up. Nothing to be sorry or embarrassed about. We are all mistakes and we make humans :-) :) -- Suvayu Open source is the future. It sets us free.
Re: [O] [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS
Hi,
Sorry the previous patch was buggy. I forgot to escape a brace. This
patch supersedes the last one.
Thanks,
On Thu, Mar 8, 2012 at 01:41, suvayu ali fatkasuvayu+li...@gmail.com wrote:
Hi,
This is adds a small example to better illustrate the use of
LaTeX_CLASS_OPTIONS. Thanks to Nick for encouraging me to submit this.
Thanks,
--
Suvayu
Open source is the future. It sets us free.
--
Suvayu
Open source is the future. It sets us free.
From 6d7719bdb3d190ff0b2854bc781ddfec7b1382d1 Mon Sep 17 00:00:00 2001
From: Suvayu Ali fatkasuvayu+li...@gmail.com
Date: Thu, 8 Mar 2012 01:31:05 +0100
Subject: [PATCH] Add example demonstrating LaTeX_CLASS_OPTIONS
* org.texi (Header and sectioning): Add example demonstrating how to use
LaTeX_CLASS_OPTIONS.
TINY CHANGE
---
doc/org.texi | 21 -
1 files changed, 16 insertions(+), 5 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index 33ffe28..68836e0 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -10361,11 +10361,22 @@ @subsection Header and sectioning structure
@code{org-export-latex-default-packages-alist} and
@code{org-export-latex-packages-alist} are spliced.}, and allows you to
define the sectioning structure for each class. You can also define your own
-classes there. @code{#+LaTeX_CLASS_OPTIONS} or a @code{LaTeX_CLASS_OPTIONS}
-property can specify the options for the @code{\documentclass} macro. You
-can also use @code{#+LaTeX_HEADER: \usepackage@{xyz@}} to add lines to the
-header. See the docstring of @code{org-export-latex-classes} for more
-information.
+classes there. @code{#+LaTeX_CLASS_OPTIONS} or a @code{:LaTeX_CLASS_OPTIONS:}
+property can specify the options for the @code{\documentclass} macro. The
+options to documentclass have to be provided, as expected by @LaTeX{}, within
+square brackets. You can also use @code{#+LaTeX_HEADER: \usepackage@{xyz@}}
+to add lines to the header. See the docstring of
+@code{org-export-latex-classes} for more information. An example is shown
+below.
+
+@example
+#+LaTeX_CLASS: article
+#+LaTeX_CLASS_OPTIONS: [a4paper]
+#+LaTeX_HEADER: \usepackage@{xyz@}
+
+* Headline 1
+ some text
+@end example
@node Quoting @LaTeX{} code, Tables in @LaTeX{} export, Header and sectioning, @LaTeX{} and PDF export
@subsection Quoting @LaTeX{} code
--
1.7.7.6
Re: [O] Orgmode markups inside LaTeX fragments
On Thu, Mar 8, 2012 at 16:55, Truong Nghiem truong.ngh...@gmail.com wrote: If there is any solution or workaround for my problem, please let me know. If these custom commands are analogs of commands like section and such, you can always define your own LaTeX_CLASS. The manual has information on how to do that. GL -- Suvayu Open source is the future. It sets us free.
Re: [O] suggestion for the manual: mention the #+BEGIN_SRC org trick when describing drawers and plainlists
On Sat, Mar 10, 2012 at 16:01, Mirko Vukovic mirko.vuko...@gmail.com wrote: But using BEGIN/END_SRC is really a hack. I wonder if instead of using SRC blocks, we could define (with some amount of coding) a more suitable kind of blocks. In my case I would like to have a BEGIN/END_TODO block. This would permit a layout such as We have inline tasks for that. About supporting non-tree-like structures in org files, this has been discussed before. You can look up sometime towards the end of last year in the archives to see the arguments in favour and against the feature. -- Suvayu Open source is the future. It sets us free.
Re: [O] Unable to find contrib/
Hi Debaditya, On Sun, Mar 11, 2012 at 08:27, Debaditya Mukhopadhyay debadi...@gmail.com wrote: added to my .emacs (add-to-list 'load-path org-root-dir/contrib/lisp) (require 'org-mime) I would recommend using a full path. Unless you have org-root-dir as a subdirectory to where ever you have put this elisp snippet, it is bound to fail. PS: Its nice to see another bong org-mode user. :) -- Suvayu Open source is the future. It sets us free.
[O] Problem with choosing mode while editing blocks with C-c '
Hi, I am having problems editing blocks with C-c '. If the blocks are marked with upper case letters Emacs brings up the temporary buffer in picture-mode. #+BEGIN_SRC latex #+END_SRC However the buffer mode is chosen correctly if lower case letters are used. #+begin_src latex #+end_src Any ideas what could be wrong? -- Suvayu Open source is the future. It sets us free.
Re: [O] Problem with choosing mode while editing blocks with C-c '
Hi Nick, Apologies on not responding sooner. I was preparing my slides for a presentation tomorrow. On Wed, Mar 14, 2012 at 01:34, Nick Dokos nicholas.do...@hp.com wrote: Thorsten quintf...@googlemail.com wrote: suvayu ali fatkasuvayu+li...@gmail.com writes: Hi, I am having problems editing blocks with C-c '. If the blocks are marked with upper case letters Emacs brings up the temporary buffer in picture-mode. #+BEGIN_SRC latex #+END_SRC However the buffer mode is chosen correctly if lower case letters are used. #+begin_src latex #+end_src Any ideas what could be wrong? There was a discussion of this topic recently, I had and still have my quote source blocks in artists (picture) mode and thought this was strange behaviour. BTW, artist-mode is *not* the same as picture-mode. Actually I keep confusing between the two and I'm not sure which I was seeing. I also forgot to mention I did not see the problem with a minimal setup. I got frustrated (I had to get the talk done), so I restarted Emacs and worked with LaTeX directly. Now in my new session I cannot replicate my issue. However it still breaks in a different way. Hitting C-c ' prompts me for a filename or a url. For the OP (Suvayu): can you do C-h v org-edit-fixed-width-region-mode RET and post the result? If the value is picture-mode, then I can vaguely glimpse a (rather far-fetched) possible scenario that might get you into the problem you describe, but I'd rather try to rule it out first. This variable is set to artist-mode. I did a binary search through my setup and found the problem occurs when case-fold-search is set to nil. You can replicate this with the following contents in an org file and (setq case-fold-search nil). 8---8 * Heading #+BEGIN_SRC latex %% this is a LaTeX comment #+END_SRC #+begin_src latex %% this is a LaTeX comment #+end_src 8---8 C-c ' on the first block shold prompt you for a file or url and the second block should present a temporary buffer in latex mode. I have actually seen both these problem (the artist-mode and prompt for file or url) for quite a while from time to time. But I could never replicate them consistently. I guess today is my (somewhat) lucky day. :) Nick Hope this helps paint a clearer picture. -- Suvayu Open source is the future. It sets us free.
Re: [O] Problem with choosing mode while editing blocks with C-c '
Hey Nick, On Wed, Mar 14, 2012 at 04:11, Nick Dokos nicholas.do...@hp.com wrote: suvayu ali fatkasuv...@gmail.com wrote: There was a discussion of this topic recently, I had and still have my q= uote source blocks in artists (picture) mode and thought this was strange behaviour. BTW, artist-mode is *not* the same as picture-mode. Actually I keep confusing between the two and I'm not sure which I was seeing. Well, they *are* different, but it turns out that if artist-picture-compatibility is true (which it is by default), then artist-mode turns on picture-mode, so they are difficult to tell apart just looking at the modeline. Yup, your analysis was spot on. :) Changing the let to let* and reevaluating the defun fixed the issue. I hadn't grasped this subtlety about let*, dependencies on preceding bindings hidden behind function calls! Nick Thanks a lot. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] Problem with choosing mode while editing blocks with C-c '
Sorry the quoting was all wrong! Gmail was behaving weirdly. I wanted to quote the other message. On Wed, Mar 14, 2012 at 03:59, Nick Dokos nicholas.do...@hp.com wrote: The case-fold-search problem is in org-src.el:org-edit-src-code. case-fold-search is let-bound to t, but the let form evaluates all the VARLIST forms before evaluating the body, so the very next varlist (case-fold-search t) (info (org-edit-src-find-region-and-lang)) ... fails because in its evaluation, case-fold-search is still nil. The solution is to use a let* form instead: just change the let on line 216 to a let*. On Wed, Mar 14, 2012 at 09:41, suvayu ali fatkasuv...@gmail.com wrote: Yup, your analysis was spot on. :) Changing the let to let* and reevaluating the defun fixed the issue. I hadn't grasped this subtlety about let*, dependencies on preceding bindings hidden behind function calls! I am attaching the changes as a patch. Let me know if it is okay. Thanks, -- Suvayu Open source is the future. It sets us free. From 48eb85df419c38a57d35808ca3a3bc9d86e05c33 Mon Sep 17 00:00:00 2001 From: Suvayu Ali fatkasuvayu+li...@gmail.com Date: Wed, 14 Mar 2012 09:49:40 +0100 Subject: [PATCH] Change let bind to a let* in org-edit-src-code * org-src.el (org-edit-src-code): Change let bind to let*, e.g. if case-fold-search is bound to nil globally, the (case-fold-search t) doesn't work until we get to the body. The fix and analysis was provided by Nick Dokos on this email message thread: http://thread.gmane.org/gmane.emacs.orgmode/53335/focus=53342 TINY CHANGE --- lisp/org-src.el | 20 ++-- 1 files changed, 10 insertions(+), 10 deletions(-) diff --git a/lisp/org-src.el b/lisp/org-src.el index 9cd56d2..dfaa72d 100644 --- a/lisp/org-src.el +++ b/lisp/org-src.el @@ -213,16 +213,16 @@ (defun org-edit-src-code (optional context code edit-buffer-name) (interactive) (unless (eq context 'save) (setq org-edit-src-saved-temp-window-config (current-window-configuration))) - (let ((mark (and (org-region-active-p) (mark))) - (case-fold-search t) - (info (org-edit-src-find-region-and-lang)) - (full-info (org-babel-get-src-block-info 'light)) - (org-mode-p (derived-mode-p 'org-mode)) ;; derived-mode-p is reflexive - (beg (make-marker)) - (end (make-marker)) - (allow-write-back-p (null code)) - block-nindent total-nindent ovl lang lang-f single lfmt buffer msg - begline markline markcol line col transmitted-variables) + (let* ((mark (and (org-region-active-p) (mark))) + (case-fold-search t) + (info (org-edit-src-find-region-and-lang)) + (full-info (org-babel-get-src-block-info 'light)) + (org-mode-p (derived-mode-p 'org-mode)) ;; derived-mode-p is reflexive + (beg (make-marker)) + (end (make-marker)) + (allow-write-back-p (null code)) + block-nindent total-nindent ovl lang lang-f single lfmt buffer msg + begline markline markcol line col transmitted-variables) (if (not info) nil (setq beg (move-marker beg (nth 0 info)) -- 1.7.7.6
Re: [O] How to sort table in blocks.
Hi Debaditya, On Thu, Mar 15, 2012 at 01:47, Debaditya Mukhopadhyay debadi...@gmail.com wrote: 2. I would like to sort the table based on date, but instead of sorting each line is it possible to sort by block (defined by the horizontal lines.)? What you are asking about is a table.el table. You can use those with org, but the support is spotty at best. You will loose the ability use table formulae, sorting or even nice export to multiple backends. In short, the answer is no you can't. That said, I believe you can put the multiple lines in one long line and specify how wide the column can be so it appears to be small and neatly folded in buffer. While editing you can call org-edit-special and edit the long line conveniently. You also retain all the other awesome org table features. Hope this helps. -- Suvayu Open source is the future. It sets us free.
Re: [O] Org-mode and icicles - tags
Hi Nick, On Wed, Mar 14, 2012 at 20:12, Nick Bell m...@nickbell.org wrote: Does anyone else use Icicles and Org-mode, and if so have they found a way around this? I would suggest you either include the icicles author (Drew Adams) in the CC: or add the Emacs general mailing list help-gnu-em...@gnu.org. -- Suvayu Open source is the future. It sets us free.
Re: [O] Org-mode and icicles - tags
On Thu, Mar 15, 2012 at 11:01, Nick Bell m...@nickbell.org wrote: I would suggest you either include the icicles author (Drew Adams) in the CC: or add the Emacs general mailing list help-gnu-em...@gnu.org. Thanks Suvayu, in the end I just switched back to Ido-mode which feels less crazily complicated anyway. Okay, my suggestion was simply because I think Drew doesn't use org-mode, but e is very helpful and active on the general Emacs mailing list. -- Suvayu Open source is the future. It sets us free.
