[Orgmode] [OT] what about asymptote ?
87eigde28n@gmail.com
87d3vw8shu.wl%ucec...@ucl.ac.uk
87631o8ebj@gmail.com
87wru4uhux.wl%ucec...@ucl.ac.uk
aanlktikoyclhdvuisb11vymrceivo9hx3n3rdrsow...@mail.gmail.com
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/23.2 Mule/6.0
(HANACHIRUSATO)
Hello,
While I'm at it, I'd like to suggest asymptote as a neat tool to draw
all those graphs.
Here are two examples illustrating it (admittedly not so well for the
surface, but I explain why in my comments) :
#+begin_src asymptote
import graph3;
size(7cm,0);
currentprojection=orthographic(-4,-2,3);
// define function f(z), where z ( z.x , z.y )
real f(pair z) { return sin(z.x) + sin(z.y); }
// Drawing meshes (pen for surface is nullpen)
draw(surface(f,(-4,-4),(4,4),nx=30),nullpen,meshpen=red,nolight);
// Dumb axis but my asymptote version is too old for something
// more complex
xaxis3();
yaxis3();
zaxis3();
#+end_src
#+begin_src asymptote :file graph-asy-polar.pdf
import graph;
size(7cm,0);
// defining function and its graph
real f(real t) {return sqrt(2)/2-cos(3t);}
path Cf=polargraph(f,0,2pi,n=1440,operator ..)--cycle;
// drawing graph
draw(Cf,.8bp+red);
// axis and units
xaxis($x$);
yaxis($y$);
draw((0,0)--(1,0),.8bp+blue,Arrow());
draw((0,0)--(0,1),.8bp+blue,Arrow());
#+end_src
--
Nicolas
___
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
Re: [Orgmode] sup-mail link
Daniel Goldin wrote: Anybody know of a way to link to a sup-mail email? Integration with sup is not (yet?) supported by Org mode. What you basically need is (a) a way to create a link from within sup and (b) a way to remotely open a message in sup. Maybe this tutorial about integrating Org mode and Mutt can be a starting point: Stefano Zacchiroli remember Mutt's mail in Org-mode and jump back to them http://upsilon.cc/~zack/blog/posts/2010/02/integrating_Mutt_with_Org-mode/ HTH -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgpXqS2SsFHyx.pgp Description: PGP signature ___ 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
Re: [Orgmode] Rescheduling an item works properly only if SCHEDULED is after the heading
Tom wrote: I sometimes move the SCHEDULED keyword after textual content of a heading, because for me the content is more important to see than the keyword which is a technical detail of org implementation. The problem is if I use org-schedule on such a heading to reschedule the task then it inserts a new SCHEDULED keyword after the heading instead of modifying the existing keyword after the text content. Isn't it a bug? Shouldn't org always modify the existing keyword like it does when the keyword is immediately after the heading? I can reproduce this and yes, this looks like a bug or at least an inconsistency. -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgpradUv0lwK0.pgp Description: PGP signature ___ 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
Re: [Orgmode] Could inline footnotes be made to work with latex commands that have arguments?
Scot Becker wrote:
If I put a LaTeX citation command inside one of org's inline
footnotes, no problem, thus:
Lorem ipsum dolor sit amet,\footnote{\cite{rowe_acts_2007} }
consectetur adipisicing elit,
But if I need an optional argument, no dice. This:
ex ea commodo consequat.[fn:: \cite[56]{fitzmyer_one_2007}] Duis aute irure
dolor
exports to LaTeX like this:
ex ea commodo consequat.[fn:: \cite[56]{fitzmyer_one_2007}] Duis aute irure
dolor
(i.e. there is no \footnote{} macro created)
For consistency in my markup, I would rather use org's inline
footnotes for citations like this (which sometimes number several
inside a footnote). If I can't, I'd just go ahead and use LaTeX
\footnote{} macros right in my org files.
Is the present behaviour likely to be fixable? Or should I just
write my footnotes as LaTeX \footnotes{}?
This does not look like easy to fix: It are the square brackets of the
\cite command that prevent Org mode from recognizing the inline
footnote.
You could try to work with a LaTeX hack, something along:
,
| \newcommand{\mycite}[2]{\cite[#1]{#2}}
`
This would provide the macro \mycite with two arguments given in
curly brackets that is expanded to the \cite sequence.
HTH
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber dmj...@jabber.org
Email. dm...@ictsoc.de
pgp1VF64aCCc9.pgp
Description: PGP signature
___
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
Re: [Orgmode] [patch] overprotective begin/end during latex export
Eric Schulte writes:
Hello,
I've run across the following bug a couple of times before, but have
finally had a chance to really distill it. When exporting the following
--8---cut here---start-8---
#+TITLE: latex environments bug
there is markup /out here/
#+LaTeX: \begin{enumerate}
but *no markup* in here
#+LaTeX: \end{enumerate}
and markup _down here_ as well
--8---cut here---end---8---
everything works as expected, except that the
but *no markup* in here
line is *not* exported to LaTeX, but is rather copied verbatim into the
final LaTeX file.
It is because org-latex.el doesn't check if \begin{enumerate} is
already protected or not. Thus, it treats it as if it was some plain
LaTeX code inside the file.
In other words,
#+LaTeX: \begin{enumerate}
*bold*
#+LaTeX: \end{enumerate}
is the same as
\begin{enumerate}
*bold*
\end{enumerate}
In this case, org-latex protects everything between \begin and \end,
making it impossible to apply modifications to the text in-between.
With the following patch, org-latex will not protect an environment
coming from a #+LaTeX: instruction.
Btw, a bug I described some day ago (about org-latex badly exporting
lists when an equation spans across two lines) is also about
over protection. I have a workaround, but I still don't understand
why protection is needed for lists.
HTH,
--
Nicolas
0001-org-latex.el-do-not-protect-environments-already-pro.patch
Description: Binary data
___
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
Re: [Orgmode] sup-mail link
Unfortunately, I'm not a programmer, just a cut-and-paster. But I love org and I love sup -- and I thought it would be nice to get the two together. d. Excerpts from David Maus's message of Sun Jun 13 06:29:49 -0700 2010: Daniel Goldin wrote: Anybody know of a way to link to a sup-mail email? Integration with sup is not (yet?) supported by Org mode. What you basically need is (a) a way to create a link from within sup and (b) a way to remotely open a message in sup. Maybe this tutorial about integrating Org mode and Mutt can be a starting point: Stefano Zacchiroli remember Mutt's mail in Org-mode and jump back to them http://upsilon.cc/~zack/blog/posts/2010/02/integrating_Mutt_with_Org-mode/ HTH -- David -- Daniel Goldin 213.926.1960 ___ 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] Org mode issue file
Hello all, The Org mode issue file located at http://orgmode.org/worg/org-issues.php was just updated with a explanations about the nomenclature of keywords and tags, how the recorded issues flow inside the file, and some remarks on operating on this file collaboratively. Most notably the issue file is supposed to supersede the old todo file[1], thus it includes a section with the open development task of the old todo file. I've attached a copy of the introduction to the issue and a preliminary version of a library to operate on the issue file from withing Gnus and Wanderlust. Please see the commentary section of org-issue.el for the functions it provides. Regards and happy hacking, -- David [1] http://orgmode.org/todo.html -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de org-issue.el Description: Binary data Open issues with Org mode = Date: 2010-06-13 18:21:25 CEST Table of Contents = Introduction Nomenclature Document structure and maintenance Using this file Introduction ~ This is a simple mailing list based tracker for issues and other things about Org mode. It is a replacement of the abandoned todo file and incorporates it's structure and parts of the nomenclature. The purpose of this document is to keep track of issues, i.e. anything that requires some kind of actions, and other things like announcements, hacks, feature ideas and the like. Nomenclature = On this page, TODO keywords are used in the following way: *Keyword* Intention -+--- *NEW* A new issue that is not yet classifed. *TODO*A task to be done. This includes but is not limited to answers to user requests, development or documentation tasks. *ASSIGNED*Someone started to take care of this task. A property *ASSIGNEE* should provide a hint on who it is. *IDEA*A new idea, I have not yet decided what if anything I will do about it. *WISH*A wish, probably voiced by someone on emacs-orgm...@gnu.org. This is less than a new idea, more a change in existing behavior. *DECLINED*A feature or idea that was declined. Still in the list so that people can see it, complain, or still try to convince Carsten to implement it. *INCONSISTENCY* Some behavior in Org-mode that is not as clean and consistent as it should be. *BUG* This needs to be fixed, as soon as possible. *DONE*Well, done is done. In addition, tags are used to provide more detailed context information. Currently these tags are used in this file: *Tag* Context -+--- *Babel* Issue concerning the library of [Babel] *Mobil* Issue concerning [MobileOrg] *Patch* A patch is available via Org mode's [Patchwork tracker] [Babel]: http://orgmode.org/worg/org-contrib/babel/index.php [MobileOrg]: http://mobileorg.ncogni.to/ [Patchwork tracker]: http://patchwork.newartisans.com/project/org-mode/list/ Document structure and maintenance === New issues hitting the Org mode [mailing list] are recorded on a (almost) daily basis using a yet to be published library that allows operating on the issue file from within Wanderlust and (partly) Gnus. They are first filed to the heading *New Issues*. In a second step issues beneath this heading are reviewed. If an issue triggers a development task it is properly classified (keywords, tag) and refiled to heading *Development Task*. If it is already closed according to the mailing list, it is immediately closed and moved to *Closed issues*. If it cannot yet be classified or closed, it stays where it is. [mailing list]: http://lists.gnu.org/mailman/listinfo/emacs-orgmode Using this file This file is hosted and published
Re: [Orgmode] [patch] overprotective begin/end during latex export
Hi Nicolas,
Your patch has been applied, many thanks.
I looked at your previous email, and it's not immediately clear to me
where the problem is either.
Thanks for the quick solution on this issue however -- Eric
Nicolas Goaziou n.goaz...@gmail.com writes:
Eric Schulte writes:
Hello,
I've run across the following bug a couple of times before, but have
finally had a chance to really distill it. When exporting the following
--8---cut here---start-8---
#+TITLE: latex environments bug
there is markup /out here/
#+LaTeX: \begin{enumerate}
but *no markup* in here
#+LaTeX: \end{enumerate}
and markup _down here_ as well
--8---cut here---end---8---
everything works as expected, except that the
but *no markup* in here
line is *not* exported to LaTeX, but is rather copied verbatim into the
final LaTeX file.
It is because org-latex.el doesn't check if \begin{enumerate} is
already protected or not. Thus, it treats it as if it was some plain
LaTeX code inside the file.
In other words,
#+LaTeX: \begin{enumerate}
*bold*
#+LaTeX: \end{enumerate}
is the same as
\begin{enumerate}
*bold*
\end{enumerate}
In this case, org-latex protects everything between \begin and \end,
making it impossible to apply modifications to the text in-between.
With the following patch, org-latex will not protect an environment
coming from a #+LaTeX: instruction.
Btw, a bug I described some day ago (about org-latex badly exporting
lists when an equation spans across two lines) is also about
over protection. I have a workaround, but I still don't understand
why protection is needed for lists.
HTH,
___
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
Re: [Orgmode] [OT] what about asymptote ?
Hi Nicolas,
I agree asymptote does generate beautiful figures (does it use the same
pgf backend as tikz)?
However my most common graphical need is to display data read in from an
external file or from the command line, which I believe is orthogonal to
the main asymptote functionality.
Best -- Eric
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
While I'm at it, I'd like to suggest asymptote as a neat tool to draw
all those graphs.
Here are two examples illustrating it (admittedly not so well for the
surface, but I explain why in my comments) :
#+begin_src asymptote
import graph3;
size(7cm,0);
currentprojection=orthographic(-4,-2,3);
// define function f(z), where z ( z.x , z.y )
real f(pair z) { return sin(z.x) + sin(z.y); }
// Drawing meshes (pen for surface is nullpen)
draw(surface(f,(-4,-4),(4,4),nx=30),nullpen,meshpen=red,nolight);
// Dumb axis but my asymptote version is too old for something
// more complex
xaxis3();
yaxis3();
zaxis3();
#+end_src
#+begin_src asymptote :file graph-asy-polar.pdf
import graph;
size(7cm,0);
// defining function and its graph
real f(real t) {return sqrt(2)/2-cos(3t);}
path Cf=polargraph(f,0,2pi,n=1440,operator ..)--cycle;
// drawing graph
draw(Cf,.8bp+red);
// axis and units
xaxis($x$);
yaxis($y$);
draw((0,0)--(1,0),.8bp+blue,Arrow());
draw((0,0)--(0,1),.8bp+blue,Arrow());
#+end_src
--
Nicolas
___
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
___
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
Re: [Orgmode] [OT] what about asymptote ?
Eric Schulte writes: I agree asymptote does generate beautiful figures (does it use the same pgf backend as tikz)? Asymptote is unrelated to pgf. IMHO, it is far more powerful (i.e. 3D functionality) but admittedly less integrated into LaTeX (that's why org-babel is god sent). However my most common graphical need is to display data read in from an external file or from the command line, which I believe is orthogonal to the main asymptote functionality. Asymptote can read and write text and XDR files. I'm not sure about the command line thing. Regards, -- Nicolas ___ 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
Re: [Orgmode] Meta-grouping properties?
Hi David David Maus dm...@ictsoc.de writes: Maybe the tutorial Org-mode tricks for team management by Juan Reyero at http://juanreyero.com/article/emacs/org-teams.html can provide a solution to the problem? At least it sounds like a similar problem that is described there. I fear there is no solution for the mentioned idea on that site. In fact, I had the idea of constructing meta-groups exactly while I was implementing org-secretary for my needs after I found the mentioned homepage by chance. Thanks, Sven ___ 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] [PATCH] recursively resolve #+INCLUDE files
What do people think of this proposed patch.
I'd like to apply it, but figured I'd run it by the list first
Best -- Eric
,[from the commit message]
| org-exp: now recursively resolve #+INCLUDE: files in a safe way
|
| * lisp/org-exp.el (org-export-preprocess-string):
| now using `org-export-handle-include-files-recurse' to resolve
| included files
|
| (org-export-handle-include-files): now returns a list of the
| included files
|
| (org-export-handle-include-files-recurse): recursively calls
| `org-export-handle-include-files' while checking to see if the
| process has entered an infinite loop.
`
From 3c3dbd683857041703109e950e0ad85e6fec8a13 Mon Sep 17 00:00:00 2001
From: Eric Schulte schulte.e...@gmail.com
Date: Sun, 13 Jun 2010 15:14:08 -0700
Subject: [PATCH] org-exp: now recursively resolve #+INCLUDE: files in a safe way
* lisp/org-exp.el (org-export-preprocess-string):
now using `org-export-handle-include-files-recurse' to resolve
included files
(org-export-handle-include-files): now returns a list of the
included files
(org-export-handle-include-files-recurse): recursively calls
`org-export-handle-include-files' while checking to see if the
process has entered an infinite loop.
---
lisp/org-exp.el | 22 +++---
1 files changed, 19 insertions(+), 3 deletions(-)
diff --git a/lisp/org-exp.el b/lisp/org-exp.el
index 915e1f5..9428439 100644
--- a/lisp/org-exp.el
+++ b/lisp/org-exp.el
@@ -1032,7 +1032,7 @@ on this string to produce the exported version.
(untabify (point-min) (point-max))
;; Handle include files, and call a hook
- (org-export-handle-include-files)
+ (org-export-handle-include-files-recurse)
(run-hooks 'org-export-preprocess-after-include-files-hook)
;; Get rid of archived trees
@@ -1969,7 +1969,7 @@ TYPE must be a string, any of:
(defun org-export-handle-include-files ()
Include the contents of include files, with proper formatting.
(let ((case-fold-search t)
- params file markup lang start end prefix prefix1 switches)
+ params file markup lang start end prefix prefix1 switches all)
(goto-char (point-min))
(while (re-search-forward ^#\\+INCLUDE:?[ \t]+\\(.*\\) nil t)
(setq params (read (concat ( (match-string 1) )))
@@ -1986,6 +1986,7 @@ TYPE must be a string, any of:
(not (file-exists-p file))
(not (file-readable-p file)))
(insert (format CANNOT INCLUDE FILE %s file))
+ (setq all (cons file all))
(when markup
(if (equal (downcase markup) src)
(setq start (format #+begin_src %s %s\n
@@ -1998,7 +1999,22 @@ TYPE must be a string, any of:
(insert (org-get-file-contents (expand-file-name file)
prefix prefix1 markup))
(or (bolp) (newline))
- (insert (or end ))
+ (insert (or end
+all))
+
+(defun org-export-handle-include-files-recurse ()
+ Recursively include files aborting on circular inclusion.
+ (let ((now (list org-current-export-file)) all)
+(while now
+ (setq all (remove-duplicates (append now all)))
+ (setq now (org-export-handle-include-files))
+ (let ((intersection
+ (delq nil
+ (mapcar
+ (lambda (el) (when (member el all) el))
+ now
+ (when (intersection now all)
+ (error recursive #+INCLUDE: %S intersection))
(defun org-get-file-contents (file optional prefix prefix1 markup)
Get the contents of FILE and return them as a string.
--
1.7.0.4
___
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
Re: [Orgmode] Could inline footnotes be made to work with latex commands that have arguments?
Thanks, David, for your response. I suspected it might not be that easy to
fix.
I hadn't thought of making a custom command which only used mandatory
arguments. I'll try it out and see if I like it.
Thanks,
Scot
On Sun, Jun 13, 2010 at 3:16 PM, David Maus dm...@ictsoc.de wrote:
Scot Becker wrote:
If I put a LaTeX citation command inside one of org's inline
footnotes, no problem, thus:
Lorem ipsum dolor sit amet,\footnote{\cite{rowe_acts_2007} }
consectetur adipisicing elit,
But if I need an optional argument, no dice. This:
ex ea commodo consequat.[fn:: \cite[56]{fitzmyer_one_2007}] Duis aute
irure dolor
exports to LaTeX like this:
ex ea commodo consequat.[fn:: \cite[56]{fitzmyer_one_2007}] Duis aute
irure dolor
(i.e. there is no \footnote{} macro created)
For consistency in my markup, I would rather use org's inline
footnotes for citations like this (which sometimes number several
inside a footnote). If I can't, I'd just go ahead and use LaTeX
\footnote{} macros right in my org files.
Is the present behaviour likely to be fixable? Or should I just
write my footnotes as LaTeX \footnotes{}?
This does not look like easy to fix: It are the square brackets of the
\cite command that prevent Org mode from recognizing the inline
footnote.
You could try to work with a LaTeX hack, something along:
,
| \newcommand{\mycite}[2]{\cite[#1]{#2}}
`
This would provide the macro \mycite with two arguments given in
curly brackets that is expanded to the \cite sequence.
HTH
-- David
--
OpenPGP... 0x99ADB83B5A4478E6
Jabber dmj...@jabber.org
Email. dm...@ictsoc.de
___
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] Orgnode - a Python module for reading Org-mode files
Last year I released a Python module for reading org-mode files and accessing their contents through a set of methods. Several people have asked me about reusing the code and the licencing of the source code. I have added an MIT licence and updated the source code on my web site. http://members.optusnet.com.au/~charles57/GTD/orgnode.html I believe there are versions of orgnode available through git but I haven't looked at these changes. I would certainly be interested to include these changes in the version I have on my web page or to include instructions on how people can find these. Suggestions welcome as always, Charles ___ 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] [PATCH] lists and exportation to latex
Hello, Here is a patch making latex exporter smarter about lists. Here is a (vicious) example of what can be exported now. -- 1. A very long line with a mathematical environment at its end \(x = 25 \) #+BEGIN_EXAMPLE 3. three 4. four #+END_EXAMPLE 2. Another line -- Exporting to html is still a problem though : it doesn't seem to use org-list-to-html (and thus org-list-parse-list) from org-list.el. -- Nicolas 0001-Fix-and-improve-list-exporting-to-latex.patch Description: Binary data ___ 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
