Re: [O] converting people to Emacs and org-mode
Please let me know if you have any problems with the ikiwiki plugin or any feature requests. I haven't been too active with it lately, but I'm still around. :) Cheers, Chris On Tue, Apr 9, 2013 at 11:33 AM, Loyall, David david.loy...@nebraska.govwrote: Subject: Re: [O] converting people to Emacs and org-mode [snip] Perhaps the web incarnations of org could help here too. I plan to bring attention to Emacs by publishing a wiki on our intranet. ikiwiki[1] is a simple perl based wiki compiler. You maintain a tree of text documents in VCS, compile them into a network of linked HTML documents on demand (or on commit via a hook) and publish them on any http server (or whatever). Ikiwiki has an exporter framework that invokes different tools to export (or compile) different file formats. For example, it is trivial to configure it to render foo.lisp and bar.c as foo.lisp.html and bar.c.html, which contain pretty renderings of the code. There is an org-mode plugin[2] for ikiwiki that I am experimenting with. It invokes an Emacs session to call the org exporter. Like most wikis, ikiwiki also allows users to create and edit content via http. (Being perl, ikiwiki uses (modern) CGI.) The interface is a simple HTML text area. I intend to allow users to alter .org files via ikiwiki's web interface and have ikiwiki run them through the org exporter after each save (which is also a VCS commit). When users start to feel limited by the textbox, I'll suggest that they use Emacs and grant them direct file access to the VCS that stores all the .org files. (git in my case.) Wish me luck. :) Incidentally, I'd find an org-mode vs. Microsoft OneNote feature comparison matrix useful. Anybody got that? Cheers, --Dave [1] http://ikiwiki.info/ [2] https://github.com/chrismgray/ikiwiki-org-plugin
Re: [O] [patch] Re: meaning of body-only in org-export-as-html
Bastien b...@gnu.org writes: By the way, I am in the Processing section in the list of people who have signed papers on Worg. However, I received confirmation that my papers went through a long time ago. Should I correct Worg on this? Let me know when this is done. I did this yesterday. It turned out that I was listed in two places: once with my full name and once with the short name that I go by. I just removed my short name from the list. Cheers, Chris
Re: [O] [patch] Re: meaning of body-only in org-export-as-html
Bastien b...@gnu.org writes: I'm ready to apply this patch, but can you add a proper Emacs ChangeLog? Updated patch attached. By the way, I am in the Processing section in the list of people who have signed papers on Worg. However, I received confirmation that my papers went through a long time ago. Should I correct Worg on this? Cheers, Chris From 3ae7de6bd5b91ce18ed38dfce46466d6dd3a64b7 Mon Sep 17 00:00:00 2001 From: Chris Gray chrismg...@gmail.com Date: Tue, 3 Apr 2012 10:32:56 -0600 Subject: [PATCH] Export: Allow for TOC generation if body-only is set * lisp/org-html.el (org-export-as-html): Remove the check for body-only in the code for generating tables of contents. The docstring for org-export-as-html states that the body-only flag removes everything outside the body/body tags (inclusive). Since the table of contents is inside these tags, it should be exported when requested even if the body-only flag is set. --- lisp/org-html.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-html.el b/lisp/org-html.el index be2124b..385d8ec 100644 --- a/lisp/org-html.el +++ b/lisp/org-html.el @@ -1414,7 +1414,7 @@ PUB-DIR is set, use this as the publishing directory. \nh1 class=\title\ title /h1\n)) ;; insert body - (if (and org-export-with-toc (not body-only)) + (if org-export-with-toc (progn (push (format h%d%s/h%d\n org-export-html-toplevel-hlevel -- 1.7.9
[O] [patch] Re: meaning of body-only in org-export-as-html
Hi Myles, Sorry I missed your email for so long. On Thu, 22 Mar 2012 14:51:29 +, Myles English mylesengl...@gmail.com wrote: Hi Chris, On Fri, 16 Mar 2012 16:33:22 -0600, Chris Gray said: Hello, I am using org-export-as-html with the body-only parameter set to t in the org plugin for ikiwiki that I'm working on. It works almost perfectly, but I recently had a user point out that it's not possible to get a table of contents, even when one is explicitly asked for in the #+OPTIONS line of the org file. Since the table of contents is part of the body (at least in the sense that it is between the body tags), I found this surprising. So would it cause problems to change the line (if (and org-export-with-toc (not body-only)) ...) to (if org-export-with-toc ...) in org-export-as-html? I see one problem in that it would be then be inconsistent with org-export-as-ascii which considers the TOC to be part of the header. I would like to be able to export just the TOC (as ascii, and I understand a new ascii exporter has been written lately). The same thing for the html exporter would presumably solve your problem too because then you could export TOC+body (as html)? The thing is, the docstring is not consistent with the code. It would make my life easier if the code was changed to match the docstring, but I would also be okay if the opposite happened. I am also looking forward to the new exporter being ready, but I guess this small issue should be fixed in the current exporter until it is. I have attached the patch that I suggested for the HTML exporter. Cheers, Chris From 9f91361e8c8cd7047acf0260bff2ae81e72fcc93 Mon Sep 17 00:00:00 2001 From: Chris Gray chrismg...@gmail.com Date: Sat, 31 Mar 2012 16:35:04 -0600 Subject: [PATCH] Bring the meaning of body-only in org-export-as-html closer to docs The docstring for org-export-as-html says When BODY-ONLY is set, don't produce the file header and footer, simply return the content of body.../body, without even the body tags themselves. However, it currently also inhibits the generation of the table of contents, regardless if one is asked for by the user in the #+OPTIONS line of the file. This patch fixes that (i.e. allows for toc generation if it is requested). --- lisp/org-html.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-html.el b/lisp/org-html.el index 2de2ea9..cb785f3 100644 --- a/lisp/org-html.el +++ b/lisp/org-html.el @@ -1402,7 +1402,7 @@ PUB-DIR is set, use this as the publishing directory. \nh1 class=\title\ title /h1\n)) ;; insert body - (if (and org-export-with-toc (not body-only)) + (if org-export-with-toc (progn (push (format h%d%s/h%d\n org-export-html-toplevel-hlevel -- 1.7.9
[O] meaning of body-only in org-export-as-html
Hello, I am using org-export-as-html with the body-only parameter set to t in the org plugin for ikiwiki that I'm working on. It works almost perfectly, but I recently had a user point out that it's not possible to get a table of contents, even when one is explicitly asked for in the #+OPTIONS line of the org file. Since the table of contents is part of the body (at least in the sense that it is between the body tags), I found this surprising. So would it cause problems to change the line (if (and org-export-with-toc (not body-only)) ...) to (if org-export-with-toc ...) in org-export-as-html? Cheers, Chris
Re: [O] Minimal overhead Org-mode blogging system
On Thu, 19 Jan 2012 23:15:16 +0100, Steinar Bang s...@dod.no wrote: Puneeth Chaganti puncha...@gmail.com: This is totally home brew stuff. Well, thank you for sharing this home brew stuff. I've been trying to use the other org based blog solutions, but they have all failed for some reason or other, and they have also seemed abandoned. Have another look at ikiwiki. Either plugin for org works (I am the author of one of them), and the nice thing is that it is a really complete system. It has plugins [1] for just about anything you could want to do with a blog or wiki, and is generally well-engineered. If you have any trouble with my plugin, please open an issue on github. I promise it's not abandoned. :) Cheers, Chris [1] http://ikiwiki.info/plugins/
Re: [O] Minimal overhead Org-mode blogging system
On Sat, 21 Jan 2012 00:53:33 -0500, Nick Dokos nicholas.do...@hp.com wrote: Scott Randby sran...@gmail.com wrote: On 01/20/2012 01:19 PM, Chris Gray wrote: On Thu, 19 Jan 2012 23:15:16 +0100, Steinar Bang s...@dod.no wrote: Puneeth Chaganti puncha...@gmail.com: This is totally home brew stuff. Well, thank you for sharing this home brew stuff. I've been trying to use the other org based blog solutions, but they have all failed for some reason or other, and they have also seemed abandoned. Have another look at ikiwiki. Either plugin for org works (I am the author of one of them), and the nice thing is that it is a really complete system. It has plugins [1] for just about anything you could want to do with a blog or wiki, and is generally well-engineered. If you have any trouble with my plugin, please open an issue on github. I promise it's not abandoned. :) Cheers, Chris [1] http://ikiwiki.info/plugins/ Unless this plugin does not have org in its name, then it cannot be found on this page. What plugin are you talking about? Scott Randby Chris's plugin is on github. You can clone it with git clone git://github.com/chrismgray/ikiwiki-org-plugin.git Thanks, I should have been more clear. Both the plugins are documented here: http://ikiwiki.info/todo/org_mode/ Cheers, Chris
Re: [O] http://libremanuals.net (ikiwiki+org) to translate the Org Guide
On Tue, 13 Dec 2011 20:48:57 +0100, Bastien b...@altern.org wrote: Dear all, another announcement about translation : David Arroyo Menéndez (who already translated David O'Toole's tutorial) is launching LibreManuals to help with translating/publishing FLOSS book. Libremanuals uses ikiwiki (http://ikiwiki.info/) a wiki compiler. It builds static HTML pages for a wiki, from source in the ikiwiki/Markdown language (or others, such as texinfo or org-mode), and writes it out to destination. Libremanuals is using org-mode files to manage the tasks to do in an integrated way with ikiwiki thanks to the org ikiwiki plugin http://www.golden-gryphon.com/software/misc/org.pm.html Hi Bastien, You might have seen this already, but I recently announced a different approach to compiling org files with ikiwiki. It isn't exactly stable yet, but you might want to keep an eye on https://github.com/chrismgray/ikiwiki-org-plugin. It currently has features that Manoj's plugin does not have, such as properly setting the title of the page, and allowing images (currently only absolute urls are tested, but that should be improved soon) and wikilinks. Anyway, I think you are probably making the right decision in using Manoj's plugin for now, but mine is being more actively developed, so it might be the better choice fairly soon. Cheers, Chris
Re: [O] new ikiwiki export plugin for org
On Sat, 3 Dec 2011 23:59:51 -0500, tycho garen ga...@tychoish.com wrote: On Fri, Dec 02, 2011 at 10:23:11PM -0700, Chris Gray wrote: I've created a new export plugin for org-mode files for the ikiwiki wiki compiler. It's in a very preliminary state at https://github.com/chrismgray/ikiwiki-org-plugin Oh very nice. I saw your questions on the topic in #ikiwiki recently, and I'm very interested to follow your progress. How are you handling page directives and other parts of the ikiwiki specific markup in org? Those generally get stripped out before the org files are htmlized. Also, I am using a mix of markdown and org -- only the posts are in org, and they don't have any ikiwiki specific markup beyond a tags directive. I'm a longtime user of ikiwiki but I'm pretty comfortable with Markdown, so I typically don't really feel like I need to make my ikiwiki's use non-markdown formats. In the past when I've tried this, my feeling is that while ikiwiki *should* be pretty agnostic with regard to markup language, it isn't really. Which is to say that ikiwiki creates links between pages by inserting raw HTML into markdown pages and then hands the page off to the markdown interpreter. Which is great, but means that the other processors have to handle inline html in the same way as markdown, or links break. You can turn off the inter-page linking, but when you do that ikiwiki ends up doing very little. I've also not found a way to selectively turn the link processing plugin on or off... Right. My current thinking is that I'll use the scan and linkify hooks to do the link processing myself, so that raw html isn't inserted. Basically, the idea is to transform links into org links and let org do the transformation to html. We'll see if it works. Cheers, Chris
[O] new ikiwiki export plugin for org
Hello, I've created a new export plugin for org-mode files for the ikiwiki wiki compiler. It's in a very preliminary state at https://github.com/chrismgray/ikiwiki-org-plugin Just to prove that it is working to some extent, I am currently using it to generate my blog at http://chrismgray.github.com When it actually works properly, it will have a few advantages over the perl plugin originally authored by Manoj Srivastiva. First, it should be faster. The perl plugin starts a new emacs process for every org file that it encounters. The new plugin talks to an emacs instance using emacsclient and xml-rpc. Having the bulk of the work being done inside emacs also means that org-mode can expose its internal structure to the plugin, so getting things like the title and other metadata is much easier than writing another org-mode parser in perl. Anyway, I don't know if there are any other users of ikiwiki on this list, but I hope someone might find it useful. Cheers, Chris
[Orgmode] Re: How to write special LaTeX symbols
Xin Shi wrote: Hello all, Thanks for your response! I can go with the UTF-8 method. The only problem for me now is I don't know how to input the ö from Emacs. I've tried the C-x 8 RET, but don't know the name or hex. Any suggestions? The key combinations are pretty intuitive once you learn a few. For example, ö is C-x 8 o, and é is C-x 8 ' e. Cheers, Chris ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bug: LaTeX export and LaTeX environment
Mark Elston wrote:
Wow! I had hoped to start looking at this over the long weekend
but had other things grabbing my attention. Now Chris has already
submitted a patch for it!
Chris, I take it that the following:
#+begin_refquote {Albert Einstein}
Make things as simple as possible, but no simpler.
#+end_refquote
would then translate into:
\begin{refquote}{Albert Einstein}
Make things as simple as possible, but no simpler.
\end{refquote}
That's the idea. If it doesn't work, let me know. :)
Cheers,
Chris
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bug: LaTeX export and LaTeX environment
Carsten Dominik wrote:
Hi Mark,
several environments already to accept parameters, and in all cases it
is
done by just listing the arguments after the begin statement,
separated by spaces.
So what you could implement is that if a user writes
#+begin_xxx {aa}[bb]{cc}
that org-special-blocks will then create
\begin{xxx}{aa}[bb]{cc}
I think we must ask for the space, to make sure that all old code will
work.
A patch to org-special-blocks for this goal would be very useful, I
think.
Hi Carsten,
I actually needed this yesterday, so I'll make a patch and try to send
it in the next couple of days.
Should anything be done for the HTML exporter if there are arguments?
Cheers,
Chris
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Bug: LaTeX export and LaTeX environment
Chris Gray wrote:
I actually needed this yesterday, so I'll make a patch and try to send
it in the next couple of days.
Here is the patch for the LaTeX exporter. I'm not much of an HTML
person, so I don't know if arguments would be useful there.
Cheers,
Chris
commit 7a34d757ffbdeb97e7818411c5fe33e6339312e1
Author: Chris Gray chrismg...@gmail.com
Date: Tue Jun 1 16:52:52 2010 +0200
Add arguments to environments in the LaTeX expansion of org-special-blocks
* contrib/lisp/org-special-blocks.el
(org-special-blocks-convert-latex-special-cookies): Implement the
change by slightly altering the regexp.
Modified contrib/lisp/org-special-blocks.el
diff --git a/contrib/lisp/org-special-blocks.el b/contrib/lisp/org-special-blocks.el
index af50b30..a6064b1 100644
--- a/contrib/lisp/org-special-blocks.el
+++ b/contrib/lisp/org-special-blocks.el
@@ -64,13 +64,14 @@ seen. This is run after a few special cases are taken care of.
(defun org-special-blocks-convert-latex-special-cookies ()
Converts the special cookies into LaTeX blocks.
(goto-char (point-min))
- (while (re-search-forward ^ORG-\\(.*\\)-\\(START\\|END\\)$ nil t)
+ (while (re-search-forward ^ORG-\\([^ \t\n]*\\)[ \t]*\\(.*\\)-\\(START\\|END\\)$ nil t)
(replace-match
- (if (equal (match-string 2) START)
- (concat \\begin{ (match-string 1) })
+ (if (equal (match-string 3) START)
+ (concat \\begin{ (match-string 1) } (match-string 2))
(concat \\end{ (match-string 1) }))
t t)))
+
(add-hook 'org-export-latex-after-blockquotes-hook
'org-special-blocks-convert-latex-special-cookies)
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] multicolumn figures in latex
Hi,
I wanted to make a figure that spanned multiple lines in LaTeX. The
way to do that is via the figure* environment. Since org-mode didn't
seem to support that, I hacked it in. The patch is attached.
Cheers,
Chris
commit 4cb1a153245189aa062db4545dad76bdf413a1e1
Author: Chris Gray chrismg...@gmail.com
Date: Thu May 6 12:58:00 2010 +0200
Add support for multicolumn figures in LaTeX.
Modified lisp/ChangeLog
diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index 7f1a507..74ee48d 100644
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,8 @@
+2010-05-06 Chris Gray chrismg...@gmail.com
+
+ * org-latex.el (org-export-latex-format-image): Add support
+ for multicolumn figures in LaTeX.
+
2010-05-02 Dan Davison davi...@stats.ox.ac.uk
* org-src.el (org-edit-src-code): allow-write-back-p had
Modified lisp/org-latex.el
diff --git a/lisp/org-latex.el b/lisp/org-latex.el
index 2051de1..22833b2 100644
--- a/lisp/org-latex.el
+++ b/lisp/org-latex.el
@@ -1881,14 +1881,17 @@ The conversion is made depending of STRING-BEFORE and
STRING-AFTER.
(defun org-export-latex-format-image (path caption label attr)
Format the image element, depending on user settings.
- (let (ind floatp wrapp placement figenv)
+ (let (ind floatp wrapp multicolumnp placement figenv)
(setq floatp (or caption label))
(setq ind (org-get-text-property-any 0 'original-indentation path))
(when (and attr (stringp attr))
(if (string-match [ \t]*\\wrap\\ attr)
(setq wrapp t floatp nil attr (replace-match t t attr)))
(if (string-match [ \t]*\\float\\ attr)
- (setq wrapp nil floatp t attr (replace-match t t attr
+ (setq wrapp nil floatp t attr (replace-match t t attr)))
+ (if (string-match [ \t]*\\multicolumn\\ attr)
+ (setq multicolumnp t attr (replace-match t t attr
+
(setq placement
(cond
@@ -1912,6 +1915,11 @@ The conversion is made depending of STRING-BEFORE and
STRING-AFTER.
\\includegraphics[%attr]{%path}
\\caption{%labelcmd%caption}
\\end{wrapfigure})
+ (multicolumnp \\begin{figure*}%placement
+\\centering
+\\includegraphics[%attr]{%path}
+\\caption{%labelcmd%caption}
+\\end{figure*})
(floatp \\begin{figure}%placement
\\centering
\\includegraphics[%attr]{%path}
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Non-breaking space
Sébastien Vauban wrote: Hi Nicolas and Rémi, Rémi Vanicat wrote: Nicolas Girard nicolas.gir...@nerim.net writes: How can I typeset, for instance, 100 €, in such a way that, once exported in LaTeX, it gives: 100~€ (with a non-breaking space) ? You can use the utf-8 non breaking space (on my keyboard it's compose space space or alt-gr shift space or C-x 8 space) Or the Non-Breaking SPaces automatically added. See http://article.gmane.org/gmane.emacs.orgmode/15116 and the code `my-insert-colon'. I don't know if it has been mentioned yet, but you can also simply use \nbsp. Cheers, Chris ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] exporting to latex with multiple authors
Hi,
When I export an org file with the line
#+AUTHOR: Me \and Another person
I get
\author{Me $\wedge$ Another person}
which isn't exactly what I had in mind. :)
I suppose I could use the following:
#+LaTeX: \author{Me \and Another person}
but obviously that won't be portable to other export formats. So I
guess the question is whether there is a good way to have multiple
authors in an org file, and if there isn't, should there be?
Cheers,
Chris
P.S. It's just a matter of taste, but I always preferred \land and \lor
when typesetting logical ands and ors.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [PATCH] followup to `org-rember-templates' docstring
Carsten Dominik wrote: Hi Stepan On Apr 16, 2010, at 12:23 AM, Štěpán Němec wrote: Hello, I'm sorry for my somewhat precocious previous mail (which I unfortunately still don't see posted, I use Gmane and am not subscribed -- any chance of making the list not moderated?). No, we like it spam free here. Please subscribe, if you don't want to receive the mails, use some throw-away web-based email address. With all mailman mailing lists, it's also possible subscribe using your normal email address and turn off delivery. It's one of the options in the settings screen. This makes it easier to remember which email address you should use to write to the list with. Cheers, Chris ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: IMPORTANT: (possibly) incompatible Change
Carsten Dominik wrote: - * =org-export-latex-classes= no longer should be customized for packages The HEADER part of this variable should now only contain the documentclass macro, nothing else - at least normally. All the package calls via usepackage should go into org-export-latex-packages-alist. I moved all the default packages that into a new variable org-export-latex-default-packages-alist. This will allow me to add more packages (as needed) in the future, withour requiring you to erase and then redo your configuration of org-export-latex-classes. So if you have customized this variable, please remove once more (hopefully for the last time) your customization, so that it can revert to its now much simpler default value. Put all your package definitions into org-export-latex-packages-alist. I hope this works, and we will not get conflicts because of the sequence in which packages are called. If there are problems, please let me know so that we can find a solution. Is it sufficient to change the variable that is being set from org-export-latex-classes to org-export-latex-default-packages-alist? Or does the format of the list change at all? Cheers, Chris ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Bug: export latex bug [6.34trans]
When exporting to LaTeX, I get the error void-variable org-on-heading-p. The following patch fixes the problem. Cheers, Chris Emacs : GNU Emacs 23.1.50.1 (i686-pc-linux-gnu, GTK+ Version 2.18.3) of 2009-11-20 on portan Package: Org-mode version 6.34trans commit 7d187462ebb90c8b45b66b50551d1adc7a4f84f9 Author: Chris Gray chrismg...@gmail.com Date: Fri Feb 26 12:27:18 2010 +0100 Removed empty if statement Modified lisp/org-latex.el diff --git a/lisp/org-latex.el b/lisp/org-latex.el index c12d178..51a96d4 100644 --- a/lisp/org-latex.el +++ b/lisp/org-latex.el @@ -2045,7 +2045,6 @@ The conversion is made depending of STRING-BEFORE and STRING-AFTER. (add-text-properties (1- (length footnote-rpl)) (length footnote-rpl) '(org-protected t) footnote-rpl) -(if org-on-heading-p) (setq footnote-rpl (concat (org-export-latex-protect-string \\protect) footnote-rpl)) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Agenda and Reloading Changed Files
Bernt Hansen wrote: Make sure you don't have any unsaved information in _any_ org files in emacs before you run this to sync your emacs buffers with the on disk files -- otherwise you'll lose information. I got burned by that a couple of times, so now I use a script that does the following: --8---cut here---start-8--- emacsclient -e (save-some-buffers t) for dir in $DIRS; do cd $dir git pull done emacsclient -e (org-revert-all-org-buffers) --8---cut here---end---8--- Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Org-mode version 6.31trans; LaTeX export fails to protect \thanks command in author designation
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
http://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org-mode mailing list.
Hi,
The following line:
#+AUTHOR: Chris Gray\thanks{This research was funded by the German Ministry for
Education and Research (BMBF) under grant number 03NAP14 ``ADVEST''.}
gets exported as
\author{Chris Gray\thanks{This research was funded by the German Ministry for
Education and Research (BMBF) under grant number 03NAP14 ``ADVEST''.\}}
Note the backslash before the next-to-last curly brace.
Cheers,
Chris
Emacs : GNU Emacs 23.0.91.1 (i486-pc-linux-gnu, GTK+ Version 2.16.0)
of 2009-04-05 on palmer, modified by Debian
Package: Org-mode version 6.31trans
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] org-babel-tangle indentation
Hi, I've been using org-babel for a couple of weeks now and I really like it for programming. One thing I've noticed, though, is that source blocks are not indented when they are output by org-babel-tangle. This makes the output source hard to read, and incorrect for languages where indentation is important. For example, the following bit of python does not compile when tangled. --8---cut here---start-8--- * Introduction This is some intro text. #+srcname: the first block #+begin_src python :tangle foo :exports none print '1 + 1' if 1 + 1 == 2: print 'oh no' else: # do the other thing #+end_src Some more text. #+srcname: do the other thing #+begin_src python :tangle no :exports none print 'oh yes' #+end_src --8---cut here---end---8--- My preference would be for source blocks to be indented to the level of the comment that caused them to be inserted. Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode version 6.31trans; Exporting src blocks to LaTeX produces .tex file that fails to compile
Eric Schulte wrote:
Hi Eric,
I tried to recreate this problem but was unable to do so on my
computer. To recreate I exported
#+srcname: determine the neighbors of the segments that the bisector hits
#+begin_src lua :tangle no :exports code
local s1, s2 = intersecting_segs[1], intersecting_segs[2]
local n1 = table_find_segment(cell.neighbors, s1)
local n2 = table_find_segment(cell.neighbors, s2)
#+end_src
with my personal Emacs configuration and I got the following in the
resulting .tex file
#+begin_example
\lstset{language=lua}
\begin{lstlisting}
local s1, s2 = intersecting_segs[1], intersecting_segs[2]
local n1 = table_find_segment(cell.neighbors, s1)
local n2 = table_find_segment(cell.neighbors, s2)
\end{lstlisting}
#+end_example
Are you exporting to LaTeX or some intermediate org-based format? I am
just using C-c C-e L to export. Should I be using an org-babel command?
note that Org-babel shouldn't have any effect here as it currently
doesn't recognize the lua language.
Sorry, I should have been more clear about that. I have added the
following to my setup.
(org-babel-add-interpreter lua)
(add-to-list 'org-babel-tangle-langs '(lua lua #!/usr/bin/env lua))
Sorry I can't be of more help. Maybe try with emacs -Q and
incrementally add your personal configuration until the problem
re-appears.
Will do.
Cheers,
Chris
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode version 6.31trans; Exporting src blocks to LaTeX produces .tex file that fails to compile
Hi,
The problem was with my org-special-blocks contrib package. The
attached patch fixes it. Sorry for the noise.
Cheers,
Chris
commit 4d327b5f1e80ea0e493aa70d09c53042216a1390
Author: Chris Gray chrismg...@gmail.com
Date: Fri Oct 2 11:31:21 2009 +0200
Added a variable to ignore some blocks.
Modified contrib/lisp/org-special-blocks.el
diff --git a/contrib/lisp/org-special-blocks.el
b/contrib/lisp/org-special-blocks.el
index b8ce4d5..af50b30 100644
--- a/contrib/lisp/org-special-blocks.el
+++ b/contrib/lisp/org-special-blocks.el
@@ -40,17 +40,23 @@
;; user to add this class to his or her stylesheet if this div is to
;; mean anything.
+(defvar org-special-blocks-ignore-regexp ^\\(LaTeX\\|HTML\\)$
+ A regexp indicating the names of blocks that should be ignored
+by org-special-blocks. These blocks will presumably be
+interpreted by other mechanisms.)
+
(defun org-special-blocks-make-special-cookies ()
Adds special cookies when #+begin_foo and #+end_foo tokens are
seen. This is run after a few special cases are taken care of.
(when (or htmlp latexp)
(goto-char (point-min))
(while (re-search-forward ^#\\+\\(begin\\|end\\)_\\(.*\\)$ nil t)
- (replace-match
- (if (equal (downcase (match-string 1)) begin)
- (concat ORG- (match-string 2) -START)
-(concat ORG- (match-string 2) -END))
- t t
+ (unless (string-match-p org-special-blocks-ignore-regexp (match-string
2))
+ (replace-match
+(if (equal (downcase (match-string 1)) begin)
+(concat ORG- (match-string 2) -START)
+ (concat ORG- (match-string 2) -END))
+t t)
(add-hook 'org-export-preprocess-after-blockquote-hook
'org-special-blocks-make-special-cookies)
Chris Gray wrote:
Eric Schulte wrote:
Hi Eric,
I tried to recreate this problem but was unable to do so on my
computer. To recreate I exported
#+srcname: determine the neighbors of the segments that the bisector hits
#+begin_src lua :tangle no :exports code
local s1, s2 = intersecting_segs[1], intersecting_segs[2]
local n1 = table_find_segment(cell.neighbors, s1)
local n2 = table_find_segment(cell.neighbors, s2)
#+end_src
with my personal Emacs configuration and I got the following in the
resulting .tex file
#+begin_example
\lstset{language=lua}
\begin{lstlisting}
local s1, s2 = intersecting_segs[1], intersecting_segs[2]
local n1 = table_find_segment(cell.neighbors, s1)
local n2 = table_find_segment(cell.neighbors, s2)
\end{lstlisting}
#+end_example
Are you exporting to LaTeX or some intermediate org-based format? I am
just using C-c C-e L to export. Should I be using an org-babel command?
note that Org-babel shouldn't have any effect here as it currently
doesn't recognize the lua language.
Sorry, I should have been more clear about that. I have added the
following to my setup.
(org-babel-add-interpreter lua)
(add-to-list 'org-babel-tangle-langs '(lua lua #!/usr/bin/env lua))
Sorry I can't be of more help. Maybe try with emacs -Q and
incrementally add your personal configuration until the problem
re-appears.
Will do.
Cheers,
Chris
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
--
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode version 6.31trans; Exporting src blocks to LaTeX produces .tex file that fails to compile
Carsten Dominik wrote: Hi Chris, the error was on my side - I did not remove the backend-specific markers after selecting the content. This is now again done correctly, so your patch should not be needed. But maybe you want it in anyway, with an empty configuration variable? Famous last words, but I don't see how it can hurt. :) Cheers, Chris - Carsten On Oct 2, 2009, at 11:36 AM, Chris Gray wrote: Hi, The problem was with my org-special-blocks contrib package. The attached patch fixes it. Sorry for the noise. Cheers, Chris commit 4d327b5f1e80ea0e493aa70d09c53042216a1390 Author: Chris Gray chrismg...@gmail.com Date: Fri Oct 2 11:31:21 2009 +0200 Added a variable to ignore some blocks. Modified contrib/lisp/org-special-blocks.el diff --git a/contrib/lisp/org-special-blocks.el b/contrib/lisp/org- special-blocks.el index b8ce4d5..af50b30 100644 --- a/contrib/lisp/org-special-blocks.el b/contrib/lisp/org-special-blocks.el @@ -40,17 +40,23 @@ ;; user to add this class to his or her stylesheet if this div is to ;; mean anything. (defvar org-special-blocks-ignore-regexp ^\\(LaTeX\\|HTML\\)$ A regexp indicating the names of blocks that should be ignored by org-special-blocks. These blocks will presumably be interpreted by other mechanisms.) (defun org-special-blocks-make-special-cookies () Adds special cookies when #+begin_foo and #+end_foo tokens are seen. This is run after a few special cases are taken care of. (when (or htmlp latexp) (goto-char (point-min)) (while (re-search-forward ^#\\+\\(begin\\|end\\)_\\(.*\\)$ nil t) - (replace-match - (if (equal (downcase (match-string 1)) begin) - (concat ORG- (match-string 2) -START) - (concat ORG- (match-string 2) -END)) - t t (unless (string-match-p org-special-blocks-ignore-regexp (match-string 2)) (replace-match (if (equal (downcase (match-string 1)) begin) (concat ORG- (match-string 2) -START) (concat ORG- (match-string 2) -END)) t t) (add-hook 'org-export-preprocess-after-blockquote-hook 'org-special-blocks-make-special-cookies) ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: memory management in orgmode (supermemo)
Detlef Steuer wrote: There is flashcard.el There is also elip.el, which I have been using for a while and find quite nice. http://www.gnuvola.org/software/elip/ Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Is there any other keywords for #+BEGIN_XXX ? Can I use lower case for keywords ?
waterloo wrote: Can I use other like begin_foo ? Only two begin_src and begin_example? See also http://orgmode.org/worg/org-contrib/org-special-blocks.php Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-special-blocks for code chunks
Hi Seb, Thanks for testing things so extensively. Look, I've done an ECM with the different ways I currently see for Org-mode: I've never seen the term ECM before. What does it mean? Conclusions? - Org-special-blocks seems to misbehave in cases A3/B3 (adding an unsound environment) and A4 (letting the underscore being converted); I would argue that it is only misbehaving in A3 and B3, since the whole point of org-special-blocks is that org-style interpretation of your text is happening inside the blocks. In this sense, it was never really meant to be used with verbatim-type environments. (I use it mainly for things like lemma and proof environments). I think that A3/B3 show a bug, though, so that should be fixed. (Either with a special case in org-special-blocks or by moving the hook around in org-exp-latex). I will try to have a look at this later. - Though, case A1 is not very friendly: nothing tells I'm inline LaTeX code (what about other exports, as HTML and the like?) I'm not sure, but I think it sends the whole thing to latex and then renders the output as an image. Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-special-blocks for code chunks
Sébastien Vauban wrote:
I have a problem exporting code chunks to LaTeX (beamer, in fact -- but that
does not change anything to the problem) that contain underscores.
[snip]
So, I can't get a properly outputted underscore in my slide.
Any idea or workaround?
Hi Seb,
Is lstlisting like a verbatim environment? I think you might be able to
just use \begin{lstlisting} and \end{lstlisting} in that case. Org does
not interpret anything inside such blocks, which is why
org-special-blocks was created in the first place.
Cheers,
Chris
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: TAB completion for org-insert-link C-c C-l
Bastien wrote: Hi all, I just pushed a small change I would like to hear feedback about. The basic idea is to allow TAB completion to suggest stored links when inserting a link with C-c C-l. Here is the log from the git repo: ,[ Also use TAB for completion with org-insert-link. ] | Before this patch the completion mechanism was this: TAB let's you | complete through link prefixes (gnus: file: bbdb: ...) then RET allows | completion if a completion mechanism is available for the chosen prefix. | Navigating through the history of stored links was a separate process, | available through the up/down M-n/M-p keys. | | Now TAB not only completes through link prefixes but also through stored | links. This behavior matches other Emacs completion mechanisms a bit | more closely. ` What do you think? I love this idea. It had always annoyed me that ido said (No matches) when I was inputting a valid link. Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] argument to org-revert-all-org-buffers
Hello, I think it would be nice if org-revert-all-org-buffers took an argument so that it worked non-interactively when the argument is non-nil. This would mirror the function save-some-buffers, so that one can do something like: emacsclient -e (save-some-buffers t) git pull emacsclient -e (org-revert-all-org-buffers t) from a script. Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: A tool for creating source code files from example and src blocks in org files
Eric H. Neilsen, Jr. wrote:
Hi,
First, thank you Carsten and others, for putting this thing together;
org-mode is the most useful tool I've run across in a long time.
I recently put together a few commands to create source code files
from SRC and EXAMPLE blocks in org-mode files. The original idea is to
be able to compile examples in my notes without needing to merge them
into a separate source file by hand. As I was writing it I realized
this is exactly the same tool one needs to turn org-mode into a
literate programming tool (see http://www.literateprogramming.com/ ),
so I adopted some of the nomenclature. (I tried literate programming a
few years ago, and gave up in frustration with the tools. I am tempted
to try again with org-mode.)
I was just thinking that literate programming and org-mode would go
great together.
The two user level commands are org-tangle and org-untangle, best
explained through example. Running org-tangle in a buffer that looks
like this:
-- begin /tmp/test.org ---
* Some file
Some text here
#+CHUNK file1.sh 1
I think using numbers to order the chunks is probably not the best
idea. When I wrote the one small program I wrote with literate
programming, I really liked being able to write pseudocode with the chunks
that get substituted. Like this (admittedly poor example):
def fib(n):
find fib_{n - 2}
find fib_{n - 1}
return the sum
find fib_{n - 2}=
f2 = fib(n - 2)
find fib_{n - 1}=
f1 = fib(n - 1)
return the sum=
return f2 + f1
Is there any interest in this? My organization's rules for releasing
code to open source projects are being revised, but I am likely to be
able to do so under a BSD-like license. If there is interest, I will
push to try and figure out how to do this, and maybe even see if I can
do the assignment of copyright stuff needed for it to get under the
main umbrella (although I am not optimistic).
If you put it in a git repo somewhere, I will put some time aside for
it.
Cheers,
Chris
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: The recurring task pattern
Ivan Nedrehagen wrote: Hi everyone, I have a pattern that repeats itself in org-mode and I am wondering if anyone have any solutions to it. I have some tasks that must be done each week, it does not matter when I complete them, but they must be done before end of the week. And when the next week comes the task should be repeated. Now I have an TODO item on it and I flip it back and forth from TODO to DONE, but it requires me to remember that I have completed the task, and requires me to put it back to TODO next week. This is not working very well. What I would like: At the beginning of each week the task sets itself to TODO. When I complete it, it logs the state change (only for this state, I do not want state change logging on all). A reminder that I did not complete it last week would be nice, but I expect that to be too much to ask for. You can add a deadline that repeats every week for the task. ** TODO Do weekly task DEADLINE: 2009-06-03 Wed +1w Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: nbsp in latex export
That works perfectly. Thanks. Cheers, Chris Carsten Dominik wrote: Please try again, thanks. - Carsten On May 26, 2009, at 4:15 PM, Chris Gray wrote: Carsten Dominik wrote: On May 26, 2009, at 3:06 PM, Chris Gray wrote: Hi, I noticed in the org manual today that `\nbsp' will become `nbsp;' in HTML and `~' in LaTeX. Trying it out, that is not quite true: \nbsp becomes $\nbsp$. I would rather have the behaviour of the documentation, but I was not implement it myself---I tried adding a special case to `org-export-latex-treat-backslash-char', but it didn't work. Fixed, thanks. The fix only seemed to let \nbsp go through without being changed. I would rather it was changed to ~, as in the docs, because \nbsp is not a LaTeX command. Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode -- ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] nbsp in latex export
Hi, I noticed in the org manual today that `\nbsp' will become `nbsp;' in HTML and `~' in LaTeX. Trying it out, that is not quite true: \nbsp becomes $\nbsp$. I would rather have the behaviour of the documentation, but I was not implement it myself---I tried adding a special case to `org-export-latex-treat-backslash-char', but it didn't work. Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: nbsp in latex export
Carsten Dominik wrote: On May 26, 2009, at 3:06 PM, Chris Gray wrote: Hi, I noticed in the org manual today that `\nbsp' will become `nbsp;' in HTML and `~' in LaTeX. Trying it out, that is not quite true: \nbsp becomes $\nbsp$. I would rather have the behaviour of the documentation, but I was not implement it myself---I tried adding a special case to `org-export-latex-treat-backslash-char', but it didn't work. Fixed, thanks. The fix only seemed to let \nbsp go through without being changed. I would rather it was changed to ~, as in the docs, because \nbsp is not a LaTeX command. Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: markup in environments in latex export
Hi Carsten, You can find the commit in the special-blocks branch of my github repository. I've tested exporting both LaTeX and HTML. Cheers, Chris Carsten Dominik wrote: On May 4, 2009, at 9:52 AM, Chris Gray wrote: Hi Carsten, That seems like a good solution. I will work on it and test it over the next couple of days and let you know when it is ready. Do you have any preference for the name of the file? Hard to find a good name org-block2env.el org-anyblock.el I don't know, your call. BTW, I also have signed and sent the copyright papers. I don't know if that's necessary for a contrib package, but now it's done... It is not necessary for a contrib package, but it will be good to have anyway. Maybe this add-on will move into the core distro eventually (turned off by default), or maybe you will contribute other patches. Thanks. - Carsten Cheers, Chris Carsten Dominik wrote: Hi Chris, I have been pondering about this idea, and I prefer to not integrate it into the Org core because I think it may lead to undesired behavior, in particular in the other backends like docbook or ASCII. However, I have just created three new hooks * org-exp.el (org-export-preprocess-after-blockquote-hook): New hook. (org-export-preprocess-string): Run the new hook. * org-latex.el (org-export-latex-after-blockquotes-hook): New hook. (org-export-latex-preprocess): Run the new hook. * org-html.el (org-export-html-after-blockquotes-hook): New hook. (org-export-as-html): Run the new hook. which would allow to easily implement your idea as an add-on package that we could include in the contrib directory. Would you like to reformulate your patch into a small add-on? The only thing I would like to ask is to keep it LaTeX/HTML-specific, and this means that the action to turn #+begin_. into the cookies should be wrapped into (when (or latexp htmlp) ... ) latexp and htmlp are a local variables available when the first of the three hooks is run. - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode -- ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: markup in environments in latex export
Hi Carsten, That seems like a good solution. I will work on it and test it over the next couple of days and let you know when it is ready. Do you have any preference for the name of the file? BTW, I also have signed and sent the copyright papers. I don't know if that's necessary for a contrib package, but now it's done... Cheers, Chris Carsten Dominik wrote: Hi Chris, I have been pondering about this idea, and I prefer to not integrate it into the Org core because I think it may lead to undesired behavior, in particular in the other backends like docbook or ASCII. However, I have just created three new hooks * org-exp.el (org-export-preprocess-after-blockquote-hook): New hook. (org-export-preprocess-string): Run the new hook. * org-latex.el (org-export-latex-after-blockquotes-hook): New hook. (org-export-latex-preprocess): Run the new hook. * org-html.el (org-export-html-after-blockquotes-hook): New hook. (org-export-as-html): Run the new hook. which would allow to easily implement your idea as an add-on package that we could include in the contrib directory. Would you like to reformulate your patch into a small add-on? The only thing I would like to ask is to keep it LaTeX/HTML-specific, and this means that the action to turn #+begin_. into the cookies should be wrapped into (when (or latexp htmlp) ... ) latexp and htmlp are a local variables available when the first of the three hooks is run. - Carsten ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: markup in environments in latex export
Hi Carsten,
I took up your challenge and made a patch that does what I want. It
does what I suggested in my previous email in that it allows one to
put #+begin_foo and #+end_foo tags in the body of an org file. These
tags allow you to change the environment of the text between them.
What that means is left up to the exporter. For example, in LaTeX,
the tags are expanded to \begin{foo} and \end{foo}, whereas in HTML, I
have the tags being expanded to div class=foo and /div. (I am
not sure if that is the right thing to do in HTML...) The text
between the tags is not protected, and thus it is interpreted for
markup just as the rest of the file.
I have left the old cases in place, so blockquote, verse, and center
should still have the same behaviour as before. The only behaviour
that changes is with #+begin_quote in HTML. This no longer generates
a blockquote, but a div class=quote. It would be easy to revert
this to the old behaviour if many people were using #+begin_quote with
HTML export.
I have put the patches up in a github repository (basically because I
wanted to play with github), so you should be able to pull them from
the general-cookies branch of git://github.com/chrismgray/org-mode.git
Cheers,
Chris
Carsten Dominik wrote:
Hi Chris,
no, this is really by design the way it is. Org-mode has its own
markup. As a bonus to people used to LaTeX, it allows certain
LaTeX constructs to be intermingled into the file. For LaTeX
export, it will export these *literally*, the entire construct.
For HTML export, you can arrange for these snippets to be
processed by LaTeX as well and then included as images,
this is useful for formulas and some other constructs.
Here is a way to fool it:
\nop{}\begin{center}
- /a/ this is a
- /b/ this is b
\begin{itemize}
\item \emph{a} this is a
\item \emph{b} this is b
\end{itemize}
\nop{}\end{center}
- /a/ this is a
- /b/ this is b
Why does it fool it? Because it recognized full environments to be
included
by \begin ... \end, wit these macros at the beginning of the line.
If I were to allow what you propose, it would quickly become hard to
know
what should be LaTeX and what not. I think.
Feel free to try to make a patch that will convince me of the opposite.
- Carsten
On Apr 16, 2009, at 3:09 PM, Chris Gray wrote:
Carsten Dominik wrote:
Hi Chris,
you can't have the cake and eat it.
if you insert a LaTeX environment, the entire environment
will be protected. After all, you rely on this quoting with your
itemize environment!
Hi Carsten,
I don't really understand this. I can see it for things like the
verbatim environment, but that might be a special case.
However, you can do this:
#+begin_center
I should have chosen a different example I suppose. What I am really
using, rather than center, are the theorem, lemma, and proof
environments. I thought it would be safer for my example to use an
environment that is included by default in LaTeX. Unfortunately,
center
is already a special case in org. But I tried #+begin_proof and that
did not work.
This works by the protection being done first, and only
then #+begin_center is turned into \begin{center}
Perhaps that could be generalized so that #+begin_foo means do the
regular org parsing and then turn on \begin{foo}? Other exporters
would be free to ignore these commands.
I really like doing my work in org mode, and I can certainly convert
my
markup commands to regular LaTeX, but doing that really seems like a
second-best solution.
Cheers,
Chris
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] markup in environments in latex export
Hello,
I have been writing a draft of a paper in org, and I would like to have
the customary org markup commands work inside of LaTeX environments. As
an example, I would like the following to have the same thing three
times instead of only twice.
--8---cut here---start-8---
#+TITLE: None
\begin{center}
- /a/ this is a
- /b/ this is b
\begin{itemize}
\item \emph{a} this is a
\item \emph{b} this is b
\end{itemize}
\end{center}
- /a/ this is a
- /b/ this is b
--8---cut here---end---8---
Cheers,
Chris
___
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: org-exp-bibtex.el - add support to citing bibtex in both html and latex exports
Carsten Dominik wrote: In fact, implementing alphabetic sorting for names that actually will work is pretty much a nightmare :-) There is a switch (-a) in bibtex2html that sorts the entries as bibtex would sort them. Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: OFF-TOPIC - posting file snippets..
Hi Sergio, Check out boxquote.el at http://www.davep.org/emacs/boxquote.el Cheers, Chris sergio_101 wrote: i realize that this is off topic, but i think it will help in the future as i continue to post.. i have seen lots of people posting file snippets to this list that are really well formatted.. something like: --[filename.txt]-- | contents of | |file | ---[end]--- well, not that ugly, but you get the idea.. my question is.. how are they doing that? thanks! ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode -- ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] latex-export bug
Hi, The text =~/a_b= is not handled correctly by org-export-as-latex. It should either be put in math mode or the tilde and underscore should be escaped. I favor the latter solution, because I often put path names in fixed-width mode. Cheers, Chris ___ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
