ne with my
limited skills. I didn't have any luck with the ELPA version when it
first came out, but the ELPA system works great and it seems like an
ideal channel to distribute Org. So, even a user like me has very little
difficulty using a non-Emacs version of Org.
I'm sure there are reasons for wanting Org to be distributed with Emacs.
Would it be OK for me to ask on the list what they are?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Achim Gratz writes:
> Thomas S. Dye writes:
>> Interesting, this Emacs distribution removed Org a few days ago. I'm not
>> certain why the distributor refers to this as "a rather drastic
>> measure." From my perspective as a user, whose interests required usin
attached
to a TODO item. It is easy for me to skip the weekly project review
that the GTD approach recommends, and attaching DEADLINE and SCHEDULE
means that fewer things fall through the cracks.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
M writes:
> Hi Thomas,
>
> thanks for your reply!
>
> Sure I know Bernt Hansen's web page and I'm already using his configuration
> for my system. (I'm still learning Emacs and org-mode, so it was easier to
> start with an existing setup).
>
> I already know and use the capture and refile feature
rned out to be easy to configure the new exporter, even in this
difficult circumstance.
The new exporter is *really* nice. It feels right, even for big complex
documents. I'm still using LaTeX at work, but I now write exclusively
in Org mode for all my projects outside work. The balance has tipped
for me.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
mple above), as assigned by #+NAME:, optionally
followed by parentheses
#+BEGIN_SRC emacs-lisp :var length=table-length()
(* 2 length)
#+END_SRC
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
La\TeX, is just plain wrong.
>
> Regards,
> Elias Assarsson
>
I agree these should be consistent, and also that \LaTeX should be
preferred. Unless someone else disagrees, could you make a patch to
this effect?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha all,
With the cursor after 'title' in the following table, pressing TAB
doesn't move me to the next cell in the table, it expands title, as
shown.
| project | title | description |
| project | #+TITLE: title
| description |
Is this expected behavior?
All the best,
Tom
--
d to refresh the local setup by C-c
C-c on the #+property: not-var 0 line, then execute the emacs-lisp
source block.
I didn't follow this thread closely, so I don't know if my experience is
useful, but when I briefly studied the accumulative property syntax I
tripped up on two things: 1) I often forgot to renew the local setup so
that changes in #+property: lines would take effect; and 2) I tried to
add more than one instance of a property in a drawer, which isn't
allowed.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha all,
I'm sometimes running into this error message when I capture:
condition-case: Capture abort: (quit pasteboard doesn't contain valid data)
Unfortunately, this doesn't mean anything to me. The problem arises
after I've been working for a while, but I haven't an idea why it
starts, or a
"Sebastien Vauban" writes:
> Hi Thomas,
>
> Thomas S. Dye wrote:
>> I'm sometimes running into this error message when I capture:
>>
>> condition-case: Capture abort: (quit pasteboard doesn't contain valid data)
>>
>> Unfortunately, thi
Thanks!
>
> Derek
>
>
I'm a fan of custom links. IIUC, you should be able to accomplish much
of what you want with the information here:
http://orgmode.org/manual/Adding-hyperlink-types.html#Adding-hyperlink-types
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
sary. For example, it will
> recognize \"{a} as ä, but will not recognize \"a or {\"a}. There are
> two ways you can solve this: either conform your .bib file to
> org-cite's requirements, or conform org-cite to your .bib file by
> customizing org-cite-latex-chars-utf8 to include \"a as well.
>
> For some reason I have not pinned down, a doubling of the bibliography
> section has been known to occur with some documents.
>
>
> * Reporting bugs:
>
> A bug report should ideally include all of the following:
> - What you expected to see, and what you got
> - The files foo.org, foo.aux and foo.bbl
> - If export failed, traceback from the debugger and the contents of
> the org-cite-temp-bbl buffer
>
--
Thomas S. Dye
http://www.tsdye.com
"Sebastien Vauban"
writes:
> Hi Thomas,
>
> Thomas S. Dye wrote:
>> I'm sometimes running into this error message when I capture:
>>
>> condition-case: Capture abort: (quit pasteboard doesn't contain valid data)
>>
>> Unfortuna
Aloha all,
The attached patch to the Org mode manual describes the current behavior
of :results wrap.
All the best,
Tom
>From bc7b5fe2cc52de4468cf847e72cb0a507ebb1626 Mon Sep 17 00:00:00 2001
From: Thomas Dye
Date: Sat, 7 Jan 2012 20:38:53 -1000
Subject: [PATCH] * doc/org.texi: :results wrap pr
Aloha all,
The attached patch defines a new header argument, :special, which wraps
the results of Org babel source block execution in a #BEGIN_ ... #+END_
block. The block name is taken from a new variable
org-babel-wrap-special, which is initialized as "results".
I use this in conjunction with
Eric Schulte writes:
> Achim Gratz writes:
>
>> t...@tsdye.com (Thomas S. Dye) writes:
>>> The attached patch defines a new header argument, :special, which wraps
>>> the results of Org babel source block execution in a #BEGIN_ ... #+END_
>>> block. The
Hi Eric,
Is there a difference between :noweb tangle and :noweb no? Based on the
documentation and some limited testing, I made the following table.
*** :noweb parameters
| param | eval | tangle | export |
|+--++|
| yes| +| + | + |
| no | -
Hi Seb,
"Sebastien Vauban" writes:
> Hi Thomas,
>
> Thomas S. Dye wrote:
>> Is there a difference between :noweb tangle and :noweb no?
>
> Yes: ":noweb no" is the default, and must *not expand* anything.
>
>> Based on the documentation and s
ll be
expanded before the block is tangled, however ``noweb'' references will not
--
1.7.5.4
--
Thomas S. Dye
http://www.tsdye.com
Hi Eric,
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Hi Seb,
>>
>> "Sebastien Vauban" writes:
>>
>>> Hi Thomas,
>>>
>>> Thomas S. Dye wrote:
>>>> Is there a difference between :noweb tang
says "tab:", while #+LABEL says "tbl:". Is that a typo?
>
> I presume, without knowing, that these prefixes are conventional, and
> they do not have a preset meaning. I could have used "zzz:" if I felt
> like it?
>
> François
>
Yes, you are correct.
Tom
--
Thomas S. Dye
http://www.tsdye.com
ink)
-#+LABEL: tbl:basic-data
+#+LABEL: tab:basic-data
| ... | ...|
|-||
@end example
--
1.7.5.4
--
Thomas S. Dye
http://www.tsdye.com
Aloha all,
Attached please find subject patch.
All the best,
Tom
>From bd3579cef735c2bb62c37a4d394597be384fe18d Mon Sep 17 00:00:00 2001
From: Thomas Dye
Date: Wed, 11 Jan 2012 08:46:27 -1000
Subject: [PATCH] * doc/org.texi: Documented :noweb no-export
---
doc/org.texi | 28
either RESULTS or NAME however any capitalization may
> | be used.
> |
> | You can customize this variable.
> |
> | [back]
> `
>
> Best,
--
Thomas S. Dye
http://www.tsdye.com
ich instead wraps the results in an Org mode drawer.
+
@node Results of evaluation, Noweb reference syntax, Header arguments, Working With Source Code
@section Results of evaluation
@cindex code block, results of evaluation
--
1.7.5.4
t...@tsdye.com (Thomas S. Dye) writes:
> Eric Schulte
Hi Eric,
It's great to find :wrap in master. Thanks for augmenting the draft.
All the best,
Tom
Eric Schulte writes:
> Hi Tom,
>
> Thanks for this patch, I've just pushed up an augmented version which
> more closely matches the current behavior.
>
> t...@tsdy
Org Compulsive Disorder) are closer in spirit to the artisan or
> craftsman than to the artist.
>
>
--
Thomas S. Dye
http://www.tsdye.com
lity that compared results
across operating systems.
Tom
>
> Perhaps the benefit would simply be a system which eases the integration
> of Org, publishing, version control, and possibly automatic Makefile
> creation with tasks like "publish", "clean" etc...
>
> Best,
>
>>
>>> http://cran.r-project.org/web/packages/roxygen/index.html
>>
>> Note that ESS has limited support for editing roxygen tags.
>>
>> Stephen
>>
>>
>
>
> Footnotes:
> [1] http://eschulte.me/org-scraps/
--
Thomas S. Dye
http://www.tsdye.com
et a "regular" tabular table.
> Any thoughts on this?Best
> regards,John-[1] http://en.wikibooks.org/wiki/LaTeX/Tables#Professional_tables
> [2] http://www.ctan.org/tex-archive/macros/latex/contrib/booktabs/
--
Thomas S. Dye
http://www.tsdye.com
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-13-2
hth,
Tom
John Hendy writes:
> On Thu, Jan 12, 2012 at 2:12 PM, Thomas S. Dye wrote:
>
>> Hi John,
>>
>> Agreed, booktabs makes good looking tables.
>>
>> Check out your Library of Babel. There
n an environment to which I
>>> can attach a caption and a label, is the LaTeX approach and might not work
>>> as well for other export targets.
>
> This new solution replaces the code block with Org-mode text before
> export. This should be the most flexible as arbitrary #+HTML and
> #+LATEX lines can be used in Org-mode.
>
> Best,
>
> Footnotes:
> [1] http://orgmode.org/worg/org-contrib/babel/uses.html
Hi Eric,
Many thanks. This works like a charm. It is deeply satisfying to find
my code block names in the book's "List of listings".
I really appreciate your attention to these details.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
S. Dye
http://www.tsdye.com
o \hyperref[sec-1.2]{Section 2}.
>
> \end{document}
>
> Any suggestion?
>
> Thanks,
>
> Alan
>
>
Aloha Alan,
Your LaTeX output indicates that this setting:
(setq org-export-latex-hyperref-format "\\ref{%s}")
hasn't taken effect for one reason or another.
What do you get with C-h v org-export-latex-hyperref-format RET?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
"Alan Schmitt" writes:
> On 20 Jan 2012, at 15:42, Thomas S. Dye wrote:
>
>> Aloha Alan,
>>
>> Your LaTeX output indicates that this setting:
>>
>> (setq org-export-latex-hyperref-format "\\ref{%s}")
>>
>> hasn't taken effe
"Alan Schmitt" writes:
> On 20 Jan 2012, at 17:42, Alan Schmitt wrote:
>
>> On 20 Jan 2012, at 17:34, Thomas S. Dye wrote:
>>
>>> Hmmm, I can't reproduce your results on my setup. What version of
>>> Org
>>> mode are you using?
>&
only
been able to get "In section First headline ..."
I really like #+toc: headlines, etc. They make organizing the front
matter easy and transparent.
My initial impression is the new exporter is extremely fast.
Thanks very much for all your work on this.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
d) output:
\caption{\label{fig:photo}[An example photograph]\{An example photograph\}.}
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> A quick question and a couple of comments on the LaTeX exporter.
>>
>> With the old exporter I set (setq org-export-latex-hyperref-format
>> "\\ref{%s}")
Aloha Nicolas,
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I think there might be a problem with the regular expression for
>> captions on line 703 or org-e-latex.el. I have a dim understanding of
>> regular expressions and the various pa
Aloha Nicolas,
The documentation string for org-e-latex-remove-logfiles might better
be:
"Non-nil means remove files with the extensions listed in
org-e-latex-extensions."
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> #+CAPTION[An example photograph]: An example photograph.
>> #+NAME: fig:photo
>>
>> for me, yields:
>>
>> \caption{\label{fig:photo}An example photograph}
>>
&g
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> The file name passed to \includegraphics is formed like this:
>> ~/path/to/graphics/file
>>
>> My LaTeX doesn't recognize this as a path.
>>
>> The old exporter passed a file na
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> A quick question and a couple of comments on the LaTeX exporter.
>>
>> With the old exporter I set (setq org-export-latex-hyperref-format
>> "\\ref{%s}") so a link t
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I think that your understanding of the new exporter architecture is
>> intimate and secure. I'm happy to follow your lead here.
>
> I know for sure my way around the new export
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> You mentioned unnumbered headlines. I wonder, would it be possible (or
>> useful) to have the num: option take an integer (like toc:)? As I
>> understand it now, its value is eith
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Nicolas Goaziou writes:
>>
>>> t...@tsdye.com (Thomas S. Dye) writes:
>
>>>> A way to set individual headings as numbered or unnumbered would be
>>>> deluxe. Perhaps this
r softwares but
> rather concepts such as GTD, which I think is tailored to the needs of people
> outside science, so I would deeply appreciate your views and experience.
>
> If this list is geared towards the proximate aspects of development and less
> towards philosophy of usage, I apologize
>
> Christoph
>
--
Thomas S. Dye
http://www.tsdye.com
s installed in core.
Yes, this is not a burning issue. In my experience, use of \section*
etc. is not frequent. It is certainly not a reason to keep the new
exporter from moving toward the Org mode core.
Thanks for making the num: option really useful for LaTeX export.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
... ...)) (76 (let ...
... ...)) (108 (org-e-latex-export-to-latex ... ... ...)) (112
(org-e-latex-export-to-pdf ... ... ...)) (100 (org-open-file ...)) (t (error
"No command associated with key %s" ...)))
(let* ((input ...) (raw-key ...) (scope ...)) (case (if ... ... raw-key) (...
...) (... ...) (76 ...) (108 ...) (112 ...) (100 ...) (t ...)))
org-export-dispatch()
call-interactively(org-export-dispatch t nil)
execute-extended-command(nil)
call-interactively(execute-extended-command nil nil)
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
s is determined by the class, because the number and
kinds of sections vary by document class. Numbering isn't something the
user thinks about--it is set by the sectioning command, according to the
class file.
The \section* form is a special case. It produces an unnumbered heading
that does not appear in the TOC.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Sent from my iPhone
On Jan 27, 2012, at 9:21 AM, Achim Gratz wrote:
> Jambunathan K writes:
>> Does numbering behavious occur uniformly for a *given* level? For
>> example, are we talking of a scenario where level 3 heading in Tree-1 is
>> numbered while level 3 heading on a Tree-2 is unnumbe
Sent from my iPhone
On Jan 27, 2012, at 8:31 AM, Jambunathan K wrote:
> Tom
>
> The aspect I am exploring is this:
>
> Does numbering behavious occur uniformly for a *given* level? For
> example, are we talking of a scenario where level 3 heading in Tree-1 is
> numbered while level 3 headin
thout the ideas and feedback of the Org-mode community, so thanks all!
>>
>> Nick Dokos writes:
>>
>>> Andreas Leha wrote:
>>>
>>>> Hi all,
>>>>
>>>> this just came into my inbox:
>>>> http://www.jstatsoft.org/v46/i03
>>>>
>>>> Great work! Big thanks to the authors.
>>>>
>>> I remember reading it with great pleasure back when Eric posted it to
>>> the list: beautiful stuff. I look forward to rereading it.
>>>
>>> Congratulations!
>>>
>>> Nick
>>>
>>>
--
Thomas S. Dye
http://www.tsdye.com
cized.
Aloha prad,
Would this work for you?
/just/ [[http://gohere.com][/go here/]] /will you?/
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
.org/v46/i03
The trick is to launch a fresh instance of Emacs and supply it with an
initialization file tailored to the content. Eric uses a Makefile for
this, and I've been able to copy and tweak his Makefile for use on other
projects.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
#+name: chunk2
>> | #+begin_src latex
>> | \begin{displaymath}
>> | x = s\cos\theta
>> | \end{displaymath}
>> | #+end_src
>> |
>> |
>> | * mini report
>> | :PROPERTIES:
>> | :EXPORT_FILE_NAME: mini.tex
>> | :EXPORT_TITLE: Minimal Report
>> | :EXPORT_AUTHOR: Mister CCB
>> | :END:
>> |
>> | #+begin_src latex :noweb yes
>> | <>
>> | <>
>> | #+end_src
>> `
>>
>> HTH,
>>
>> Chuck
>>
>>>
>>> Thanks very much.
>>>
>>> --Chris
>>
>> [snip]
>>
>> --
>> Charles C. Berry Dept of Family/Preventive
>> Medicine
>> cberry at ucsd edu UC San Diego
>> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>>
>>
>
>
--
Thomas S. Dye
http://www.tsdye.com
01-09 Mon
>
> * Formatting tags :example:
> When exporting, the default is to put tags in bold. I want a box around
> them.
>
>
> # the following is used to set some variables which affect export to latex
> #+name: export-settings
> #+begin_src emacs-lisp :exports results :results silent
> (setq org-export-latex-tag-markup "babel: \\fbox{%s}")
> #+end_src
>
>
>
> Anyway, thanks again,
> eric
--
Thomas S. Dye
http://www.tsdye.com
the org-
> manual (chapter 14 ) I read that what I need should be done using:
>
> :results output silent :exports none
>
> but despite I use this option nothing change.
>
> Do you have any suggestion??
>
> Best
> Riccardo
>
>
Aloha Riccardo,
What version of Org mode are you using?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
The current version is 7.8. Could you update and see if the problem persists?
Tom
Sent from my iPhone
On Feb 3, 2012, at 1:43 AM, Riccardo Romoli wrote:
> The version is 6.33x
>
> Best
>
> 2012/2/3 Thomas S. Dye
> Riccardo Romoli writes:
>
> > Hi, I'm
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I haven't been able to export a listing yet. The following source
>> exports with the old exporter, but fails with the experimental
>> exporter.
>
> This long standing bug
> ** R graphics output
> Note we use the object =x= generated in previous code block, thanks to
> the header option =:session *R*=. The output graphics file is
> =a.png=.
>
> #+begin_src R :file a.png
> y <- rnorm(10)
> plot(x, y)
> #+end_src
>
> Same plot with larger dimension:
>
> #+begin_src R :file b.png :width 800 :height 800
> plot(x, y)
> #+end_src
> Where do I wrong?BestRiccardo
--
Thomas S. Dye
http://www.tsdye.com
Eric S Fraga writes:
> "Thomas S. Dye" writes:
>
>
> [...]
>
>> If you (and the receiver) tangle your export-settings source code block
>> to init.el (:tangle init.el), then execute something like the following
>> source code block
>>
>&g
ot;#+toc: listings". Also, drawers[1] are exported transparently by
> default.
>
> Feedback is welcome.
>
>
> Regards,
>
> [1] properties drawers excepted: those are different elements anyway.
Hi Nicolas,
On line 427 of org-e-latex.el, reference to the variable
org-e-latex-
ot;#+toc: listings". Also, drawers[1] are exported transparently by
> default.
>
> Feedback is welcome.
>
>
> Regards,
>
> [1] properties drawers excepted: those are different elements anyway.
Hi Nicolas,
References to org-e-latex-packages-alist in org-e-latex.el docstrings
should be to org-export-latex-packages-alist.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
fficult
to answer, please do come back to the list with your queries.
All the best,
Tom
Riccardo Romoli writes:
> Hi, this is the URL:
>
> http://orgmode.org/worg/org-contrib/babel/how-to-use-Org-Babel-for-R.html
>
> Best
> R
>
> 2012/2/5 Thomas S. Dye
>
>>
l.
BTW, I have the experimental LaTeX exporter working on a real project
now. It is performing very well for me. Great work!
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
consistency with the latest syntax.
>
> Given that the Babel syntax will not be changing significantly moving
> forward now would be a good time to do such a review. Ideally this
> could be completed before the release of Emacs 24 in a couple of months.
>
> Any other ideas for upda
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> This docstring at line 186 of org-e-latex.el is incomplete
>
> Fixed.
>
>> BTW, I have the experimental LaTeX exporter working on a real project
>> now. It is performing very
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> The old exporter recognized LaTeX commands for accented characters. So,
>> \=o in the Org mode file would yield \={o} in the LaTeX file. The new
>> exporter gives $\backslash$=o for this construct.
Hi Nicolas,
I couldn't make this work.
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> The old exporter recognized LaTeX commands for accented characters. So,
>> \=o in the Org mode file would yield \={o} in the LaTeX file. The new
>> expo
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I defined a new entity in org-entities-user, but the new exporter
>> appears to ignore it. Does it look at this variable, or just
>> org-entities?
>
> I used:
supported languages
* Examples of Use
- Hello World!
- Common uses
- Links to tutorials and other resources
Eric Schulte writes:
> Hi Tom,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Hi Eric,
>>
>> Yes, this is overdue. I think your plan is a good one.
look at my
description of the ImageMagick facility. I tried to stick closely to
the sources, but might have strayed.
All the best,
Tom
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Hi Eric,
>>
>> I've attached a first draft of a template for r
tree. Speaking
>> about it, it should be a good idea to including a line about it in
>> `orgtbl-to-generic' docstring.
>>
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>
>
--
Thomas S. Dye
http://www.tsdye.com
b/babel/languages/ob-doc-R.org
>>
>> Almost. The URL containing the formatted Org source is:
>> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-R.org.html
>
+1, if this isn't too much work. It saves Worg authors having to
remember this detail, which the reader finds useful.
Tom
--
Thomas S. Dye
http://www.tsdye.com
Sorry John,
I think the important step is (require 'org-e-latex). When I checked
just now I couldn't see org-e-latex-booktables, but when I went back to
my initialization code and ran it, the variable was visible.
hth,
Tom
John Hendy writes:
> On Thu, Feb 9, 2012 at 1:57 PM,
John Hendy writes:
> On Thu, Feb 9, 2012 at 2:29 PM, Nick Dokos wrote:
>> John Hendy wrote:
>>
>>> On Thu, Feb 9, 2012 at 1:57 PM, Thomas S. Dye wrote:
>>> > Hi John,
>>> >
>>> > I had the same experience. When I restarted Em
rong? Thanks!
>
> I am running Arch linux with emacs-23.4 and org-mode 7.8.03
>
> Best,
> Peng
>
Aloha Peng,
Please try this (note the colon with :session and :exports)
#+PROPERTY: :session *R*
#+PROPERTY: :exports none
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
t
> Riccardo
>
Aloha Riccardo,
If you work in your Dropbox/PhD folder (your .org files are there), then
you should be able to do :file myFigure.pdf on both systems.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Christophe,
Has this article appeared in print? If so, can you forward publication
details?
All the best,
Tom
Christophe Pouzat writes:
> "Thomas S. Dye" a écrit :
>
>> Christophe Pouzat writes:
>>
>>> Dear all,
>>>
>>> M. Deles
he variable DC?
>
> Cheers,
>
> Rainer
>
> PS: I know that $...$ is for LaTeX math mode
Aloha Rainer,
Here is a way that works for me.
* Krug
How to have a variable show up in text.
#+name: printDC
#+BEGIN_SRC emacs-lisp :results silent raw :exports none
(print DC)
#+END
(reftex-citation t
>
> (setq org-latex-to-pdf-process
> '("pdflatex -interaction nonstopmode %b"
> "bibtex %b"
> "pdflatex -interaction nonstopmode %b"
> "pdflatex -interaction nonstopmode %b"))
>
>
> This email may be confidential and subject to legal privilege, it may
> not reflect the views of the University of Canterbury, and it is not
> guaranteed to be virus free. If you are not an intended recipient,
> please notify the sender immediately and erase all copies of the message
> and any attachments.
>
> Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more
> information.
>
>
Aloha Andreas,
Welcome to Org Mode!
You might want to define a new link type. See
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-17-2 for
one example of how this might be done.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
au!
>
> Samuel
I just ran across this article on reproducible research that some of you
might find interesting.
http://journal.r-project.org/archive/2011-2/RJournal_2011-2_Lundholm.pdf
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
r an
> +item. It is nil for keywords. It represents the footnote number
> +for footnote definitions and footnote references. If ELEMENT is
> +a target, return the same value as if ELEMENT was the closest
> +table, item or headline containing the target. In any other
> +case, return the sequence number of ELEMENT among elements or
> +objects of the same type."
> + ;; A target keyword, representing an invisible target, never has
> + ;; a sequence number.
> + (unless (eq (car element) 'keyword)
> +;; Ordinal of a target object is the ordinal of the closest table,
> +;; item, or headline containing the object.
> +(when (eq (car element) 'target)
> + (setq element
> + (loop for parent in (org-export-get-genealogy element info)
> + when
> + (memq
> +(car parent)
> +'(footnote-definition footnote-reference headline item
> table))
> + return parent)))
> +(case (car element)
> + ;; Special case 1: An headline returns its number as a list.
> + (headline (org-export-get-headline-number element info))
> + ;; Special case 2: An item returns its number as a list.
> + (item (let ((struct (org-element-get-property :structure element)))
> + (org-list-get-item-number
> +(org-element-get-property :begin element)
> +struct
> +(org-list-prevs-alist struct)
> +(org-list-parents-alist struct
> + ((footnote definition footnote-reference)
> + (org-export-get-footnote-number element info))
> + (otherwise
> + (let ((counter 0)
> + ;; Determine if search should apply to current section,
> + ;; in which case it should be retrieved first, or to full
> + ;; parse tree. As a special case, an element or object
> + ;; without a parent headline will also trigger a full
> + ;; search, notwithstanding WITHIN-SECTION value.
> + (data
> + (if (not within-section) (plist-get info :parse-tree)
> + (or (org-export-get-parent-headline element info)
> + (plist-get info :parse-tree)
> + ;; Increment counter until ELEMENT is found again.
> + (org-element-map
> + data (or types (car element))
> + (lambda (el local)
> + (cond
> + ((equal element el) (1+ counter))
> + ((not predicate) (incf counter) nil)
> + ((funcall predicate el) (incf counter) nil)))
> + info 'first-match))
>
>
> For Src-Blocks
> diff --git a/lisp/org.el b/lisp/org.el
> index a81f7fc..6708801 100644
> --- a/lisp/org.el
> +++ b/lisp/org.el
> @@ -9896,6 +9896,22 @@ visibility around point, thus ignoring
> pos (match-beginning 0
>;; There is an exact target for this
>(goto-char pos))
> + ((save-excursion
> + (goto-char (point-min))
> + (and
> + (re-search-forward
> + (format "^[ \t]*#\\+target: %s" (regexp-quote s0)) nil t)
> + (setq type 'dedicated pos (match-beginning 0
> + ;; Found an invisible target.
> + (goto-char pos))
> + ((save-excursion
> + (goto-char (point-min))
> + (and
> + (re-search-forward
> + (format "^[ \t]*#\\+name: %s" (regexp-quote s0)) nil t)
> + (setq type 'dedicated pos (match-beginning 0
> + ;; Found an element with a matching name.
> + (goto-char pos))
> ((and (string-match "^(\\(.*\\))$" s0)
> (save-excursion
>(goto-char (point-min))
--
Thomas S. Dye
http://www.tsdye.com
able on
http://orgmode.org/worg/org-contrib/babel/languages.html.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
g-contrib/babel/languages/ob-doc-R.org.html
>
>
The "Show Org source" button on Worg is a great addition. Thanks!
Tom
--
Thomas S. Dye
http://www.tsdye.com
Thorsten writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>
>> The "Show Org source" button on Worg is a great addition. Thanks!
>
> Its very convenient, and it makes the "link to this documents org source"
> section in the template for ob-doc
tions, Section
14.11 of the Org Mode manual? Or, is this a general Emacs thing
documented elsewhere?
Tom
--
Thomas S. Dye
http://www.tsdye.com
Selectively Export Some Results
:PROPERTIES:
:EXPORT_FILE_NAME: Selected_Results.pdf
:EXPORT_TITLE: Selected Results
:END:
Here are the results from block named "Ablock":
#+CALL: Ablock() :exports results
and here they are for a block named "Bblock":
#+CALL: Bblock() :exports results
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Andreas Leha writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Andreas Leha writes:
>>
>>> Hi all,
>>>
>>> attached is a patch that enhances org-babel-goto-named-src-block (bound
>>> to C-c C-v g by default). Included are two enhance
as soon as found) should be mentioned there as well.
> There will be more org- and yas-users.
>
> Regards,
> Andreas
>
>
>
Aloha Andreas,
IMO the manual should stick to describing Org Mode, and not get too
much into working around conflicts with other modes. At the same ti
+--+--+--|
| 0.02 | 0.28 | 0.49 | 0.78 | 0.98 |
#+CAPTION: Test replace results
| 0% | 25% | 50% | 75% | 100% |
|--+--+--+--+--|
| 0.01 | 0.21 | 0.44 | 0.76 | 1.00 |
I'm using Org-mode version 7.8.03 (release_7.8.03.546.gf6ea).
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
This is an interesting case. As other packages start to provide Org
Mode output this kind of problem might crop up again. Is there any
limit to the Org Mode output a third party might produce?
All the best,
Tom
> Best,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha all
Eric Schulte writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Hi Eric,
>>
>> Eric Schulte writes:
>>
>>> Would it be possible to swap the results and caption lines?
>>
>> The caption lines are part of the ascii output. I think I'd
> `
>
> ,----------title.tex
> |
> | \renewcommand\maketitle{\begin{titlepage}%
> | FOO
> | \end{titlepage}% }
> `---
>
> Myles
>
>
--
Thomas S. Dye
http://www.tsdye.com
d installation methods in the last
year or so? From what I'm able to understand, that is sometimes the
culprit.
hth,
Tom
Myles English writes:
>>> On Thu, 08 Mar 2012 09:01:01 -1000, Thomas S Dye said:
>
> > Aloha Myles, Your example works for me with emacs -q. I ha
Aloha all,
BEGIN and END are transposed with empty results, as shown in the example
below. The results shown are from two evaluations of the source code
block.
I'm using Org-mode version 7.8.03 (release_7.8.03.575.g06a1b)
All the best,
Tom
* Empty results
#+begin_src emacs-lisp :results silent
Works here. Thanks.
Tom
Eric Schulte writes:
> Fixed, Thanks for the report.
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha all,
>>
>> BEGIN and END are transposed with empty results, as shown in the example
>> below. The results shown are fro
gt; <>
>
> print entable([["One", 2, 3],["Four", 5, 6], ["Seven", 8, 9]])
> #+end_src
>
> Which gives us this result:
>
> #+results: function-demo
> : | One | 2 | 3 |
> : | Four | 5 | 6 |
> : | Seven | 8 | 9 |
>
>
Aloha!
Does the :no-expand header argument do what you want? See
http://orgmode.org/manual/no_002dexpand.html#no_002dexpand.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
701 - 800 of 1836 matches
Mail list logo
