Aloha all,
Recently, some previously working R code (below) stopped working correctly.
It is not possible to produce a graphic without :session. I get a red
message in the pdf file "arguments imply differing numbers of rows: 86,
79".
With :session, I first get one of two error messages in red i
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Would it be possible to specify inheritance priority? So that e.g. link
>> would retain the blue coloring?
>
> One solution would be to split fontification of raw keywords and blocks
> OTOH and blocks that can contain Org data OTOH, as suggested by
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Try the attached patch.
>>
>> I have done 20 second of testing (I'm traveling) so there may be adverse
>> effects. But it looked OK.
>
> With this patch, you remove fontification from caption contents, which
> is not desirable. Caption is
operties (match-beginning 6) (+ (match-end 6) 1)
> +'(font-lock-fontified t face org-block)))
>
> Perhaps it is possible to let normal fontification rule in region six
> above?
How would I change this so descriptive links are shown in #+caption:
lines?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Rasmus,
Rasmus writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Aloha all,
>>
>> Links in #+caption: lines are shown as literal links. IIRC, they used
>> to show as descriptive links. Has this changed, or is my memory faulty?
>>
>> In any c
Aloha all,
Links in #+caption: lines are shown as literal links. IIRC, they used
to show as descriptive links. Has this changed, or is my memory faulty?
In any case, I'd like them to be descriptive links to keep the
#+caption: lines as short as possible.
All the best,
Tom
--
T.S. Dye & Colle
===
What also works is to add another word between Keyword1 and "keyword2":
=======
Keyword1 and "keyword2"
<<>>
<<>>
===
Thanks,
thomas
r argument :results table is described in the Org mode manual.
I don't think the R-specific :results table behavior is described in
ob-doc-R.org. If you'd like to remedy that, then the place to start
might be the section Header Arguments under Org Mode Features for R
Source Blocks.
ht
Nicolas,
thank you.
- thomas
On 29.05.2015 09:31, Nicolas Goaziou wrote:
Hello,
thomas writes:
I have Org-mode version 8.2.10 (8.2.10-40-gc763fa-elpa @
/home/thomas/.emacs.d/elpa/org-20150504/)
You may want to switch to development version. It should be fixed there.
Regards,
Hi Nicolas,
I have Org-mode version 8.2.10 (8.2.10-40-gc763fa-elpa @
/home/thomas/.emacs.d/elpa/org-20150504/)
org-export-with-smart-quotes is set to t.
The error goes away when org-export-with-smart-quotes is not true.
M-x org-reload (sorry, I do not know how C-u org-reload could work
n separate buffer *and* reformat the code) is poor design. At least in
> this special case. When I open the code in a separate buffer but then
> decide not to change it (C-c C-c), I'll end up with extra indentation
> and this will create unnecessary changes when I commit the file in gi
rd2
<<>>
<<>>
===
What also works is to add another word between Keyword1 and "keyword2":
=======
Keyword1 and "keyword2"
<<>>
<<>>
===
Thanks,
thomas
Titus von der Malsburg writes:
> On 2015-05-24 Sun 08:36, Thomas S. Dye wrote:
>> Titus von der Malsburg writes:
>>
>>>> You got the result of rownames(x), which is expected. The table you
>>>> expect is given by the following code:
>>>
>&
uot;One:", "Two:")
#+END_SRC
#+results:
| One: |
| Two: |
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
able :exports results :colnames yes :rownames yes
x <- data.frame(a=1:2, b=3:4)
rownames(x) <- c("One:", "Two:")
x
#+END_SRC
#+results:
| | a | b |
|--+---+---|
| One: | 1 | 3 |
| Two: | 2 | 4 |
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
perty drawers, or list
> properties to include (‘org-export-with-properties’)." I'm guessing this
> is supposed to be an #+OPTIONS thing, right?
Yes, it is an export option. The on-line version of the manual is for
the stable version, 8.2.10. This must be an option that was i
Titus von der Malsburg writes:
> While that may be a valid solution for some people, it is
> certainly not the Emacs way of doing things.
That's right. It is the Org mode way of doing things in Emacs.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
ty drawers, or list properties to include
> (‘org-export-with-properties’).
>
> in 12.3 (online manual). Tried
>
> #+OPTIONS: prop:t
>
> in my buffer and it didn't work either.
>
> On Sun, May 17, 2015 at 7:08 PM, Thomas S. Dye wrote:
>
>> Lawrence Bottorff
drawers, or list properties to
include
| (‘org-export-with-properties’).
`
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
riginal interpretation of Enter would not be
>> messed with. Messing with Alt-Enter and such is fine, but Enter, please
>> no.
>>
>> Or?
>>
>> Jarmo
>
--
Thomas S. Dye
http://www.tsdye.com
gmode.org/worg/org-contrib/babel/languages.html). There is a
template for users willing to start a first draft of the fortran or
other language documentation (see
http://orgmode.org/worg/org-contrib/babel/languages.html#develop).
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
the next item. I could use a cookie here to force start at 2,
I know.
===
- thomas
On 30.04.2015 04:59, DJ wrote:
1. blah blah\\
yatta yatta
| m | n | foo |
|---+---+-|
| x | y | z |
and this text should be part of item 1. That is the real problem -
a paragraph
Nicolas Goaziou writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Org-lint gives this warning:
>>
>> ,--
>> | 31 low Unknown value
;m still missing something :-) : what are ALT_TITLEs good for if not
> for the TOC?
I think some styles put them in the header, regardless of TOC.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
---
But, ob-core.el appears to know the value:
,
| ob-core.el: (,eval-no-export (and ,export (or (equal ,eval
"no-export")
`----
Nicolas Goaziou writes:
> I realized allowed values and combinations are already known to Babel,
> so I improved the checker.
Looks good. Org-lint raises many more warnings now.
Thanks,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> So, I decided to track wip-lint. Now, the linting stops with this
>> error:
>>
>> ,
>> | Org linting process st
e Org mode file:
,--
| #+call: r-duplicate-ids() :results replace org
`--
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Rasmus writes:
> Hi Tom,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I pulled from master this morning, refreshed Org mode, and got this
>> error message in *Messages*:
>>
>> Loading /Users/dk/.emacs.d/src/org-mode/contrib/lisp/ox-koma-letter.el
>>
best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Vikas Rawal writes:
> I am revising a long book manuscript, and would like to mark parts of
> text (not just the headlines) just to remind myself that these need to
> be dealt with.
>
> What could be an the easy way of doing it?
>
> Vikas
Bookmarks?
hth,
Tom
-
Hi Aaron,
Aaron Ecay writes:
> Hi Tom,
>
> 2015ko apirilak 23an, "Thomas S. Dye"-ek idatzi zuen:
>>
>> IIRC :results output graphics is needed for the ggplot package.
>
> Hmm. This is the case if the code is *not* evaluated in a session. In
> a sess
package.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
or=function(e){plot(x=-1:1, y=-1:1, type='n', xlab='', ylab='',
axes=FALSE); text(x=0, y=0, labels=e$message, col='red'); paste('ERROR',
e$message, sep=' : ')}); dev.off()
'org_babel_R_eoe'
+ . + null device
1
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Chuck,
"Charles C. Berry" writes:
> On Wed, 22 Apr 2015, Thomas S. Dye wrote:
>
>> Aloha all,
>>
>> Prior to eaa3a761dae, when working in a session, I was able to run this
>> R source code block without problems:
>>
>> ,
Aloha all,
Prior to eaa3a761dae, when working in a session, I was able to run this
R source code block without problems:
,-
| #+header: :file r/adze_wt_log.pdf
| #+header: :results output graphics
| #+header: :width 4 :height 3
| #+
abel{sec-1}
| This is \textsc{small caps}.
| \end{document}
`-
Did your recent Org mode upgrade lose the latex link type somehow?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
owever, in the meantime a syntax for inline latex code has been
developed:
,-
| Code within @@latex:some code@@ a paragraph.
`-
This new syntax might prove to be more robust in the long run.
hth,
Tom
--
Thom
Aloha Seb,
Sebastien Vauban
writes:
> Thomas S. Dye wrote:
>> Vikas Rawal
>> writes:
>>
>>> But a footnote at the end of a headline breaks LaTeX export. LaTeX
>>> needs an optional title as follows, to be able to include footnote in
>>>
exactly compact, and suffers from inability of the
> emancs org mode to colorize or mask the @@html: @@ constructs :-/
>
> I'm still researching a more usable solution.
Would a macro do what you want?
#+MACRO: rdfa @@html:@@$3@@html:
{{{rdfa(#me, foaf:homepage, The canonical address of my homepage is at
[[http://example.com/~bob/]])}}}
Untested.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
That was what finally worked. Thanks!
Tom
On Apr 14, 2015 9:49 AM, "Feng Shu" wrote:
>
>
> (defvar base-dir "~/Documents/org/")
> (defvar pub-dir "~/Public/notes/")
>
> (setq org-publish-project-alist
> `(("org"
> :base-directory ,base-dir
> :base-extension "org"
>
Is it possible (and I just have the wrong syntax) to do the following:
(defvar base-dir "~/Documents/org/")
(defvar pub-dir "~/Public/notes/")
(setq org-publish-project-alist '(
("org"
:base-directory base-dir
:base-extension "org"
:publishing-directory pub-dir
On 12.04.2015 10:20, thomas wrote:
Hi John,
thank you for your quick reply. I have to admit to do this at the
moment would be way over my head ...
I found an easy method to boldify inline code here:
http://orgmode.org/Changes.html
m for
LaTeX export to LaTeX classes that use section titles in page headers or
a table of contents.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> The function org-footnote--allow-reference-p seems to be restrictive.
>> Does it need to be so restrictive?
>>
>> 1) Why not allow a footnote at the beginning of a line?
>>
Aloha all,
The function org-footnote--allow-reference-p seems to be restrictive.
Does it need to be so restrictive?
1) Why not allow a footnote at the beginning of a line?
(unless (bolp) ...
2) Why not allow a footnote at the end of a headline?
((memq type org-element-all-elements)
rintf ("second example \n");
> \end{minted}
> % Emacs 24.3.1 (Org mode 8.2.4)
> \end{document}
> ===
>
> What have I done wrong ?
>
> Thank you in advance for your help.
See the variable org-latex-custom-lang-environments.
You can find an example setup for the old exporter here:
http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-12-3
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
savedInstanceState)
{
super.onCreate(savedInstanceState);
setContentView(R.layout.main); // *MAKE THIS LINE BOLD*
}
}
#+END_SRC
Is there an - easy - way to do this? My first guess: I need to write an
export filter ... what would you think?
Thanks,
thomas
CALL line, but
> then the resulting HTML doesn’t contain the figure (it outputs “nil”,
> presumably because the CALL line is trying to call it, but the code is
> refusing to run because of the no-export line)
You can set :cache yes, which can be used to avoid re-evaluating
unchanged code blocks.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Hi Richard,
Richard Lawrence writes:
> Hi Tom and all,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>>> OK, I see, that makes things clearer. Would it make sense to have two
>>> keywords, say LATEX_CITE_STYLE and CSL_FILE or similar, so that the
>>> styl
Aloha Richard,
Richard Lawrence writes:
> Hi Tom and all,
>
> Thanks for answering my questions!
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> With natbib, it is possible to give a pre-note and a post-note to the
>> citation as a whole, but not to individual cit
Richard Lawrence writes:
> Hi Tom and all,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>>> I know next to nothing about citations in general, so please bear with
>>> me: if multi-cite support means being able to condense citations (e.g.
>>> [1-3, 5, 9]), t
n't found time to experiment with the citation developments or to
read through the developing code base. Was this feature of Aaron's
experimental support subsequently dropped?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
here?
Possibly because you don't need the implicit progn?
,---
| (when test {form}+) == (and test (progn {form}+))
`---
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
>
> F -- K
> F -- G
> F -- H
> F -- I
>
>
> K -- L
> K -- M
> L -- M
> }
> #+END_SRC
>
> This is a good deal in the right direction, but a few things should be
> different:
> - E should be left of F
is due
> to the fact that I did some work on coding a dedicated, quite complex
> LaTeX class for a journal, and I know that it has taken me about 32
> hours as of now. Assuming an average pace of 2-4 hours a week, and
> assuming about 16 hours for a first version of this one – it would
| <>
| #+end_src
`--
hth,
Tom
>
> I will share my way of doing this if nothing else comes up.
>
> Thomas S. Dye writes:
>
>> Ken Mankoff writes:
>>
>>> On 2015-03-19 at 10:26, John Kitchin wrote:
>>>> Is it possible to
| Execute source code blocks in a buffer.
| Call `org-babel-execute-src-block' on every source block in
| the current buffer.
`
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
rsten's reluctance as he scaled back his Org
mode work. So, yes, I believe it has been resolved.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
On 16 March 2015 at 16:52, Subhan Michael Tindall wrote:
> You can use a custom capture template and have timestamps of various
> sorts inserted.
>
> For example, I have one datetree I use that inserts a date/time stamp
> using %T (%t gives only date, not time)
>
> See the documentation for c
On 16 March 2015 at 16:52, Subhan Michael Tindall wrote:
> You can use a custom capture template and have timestamps of various
> sorts inserted.
>
> For example, I have one datetree I use that inserts a date/time stamp
> using %T (%t gives only date, not time)
>
> See the documentation for capt
I'm using orgmode 8.2.10. When I use capture, the year/month/day headers
inserted aren't timestamps; why not? Is there a way to make them
timestamps? (I can't find anything about this in the manual.)
--
http://rrt.sc3d.org
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.
s for each
author-date CSL style, one for parenthetical citations, one for text
citations, another for genitive citations, etc. It might even be nice
down the road to have a place where these could be stored and shared.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Eric,
Eric S Fraga writes:
> On Tuesday, 10 Mar 2015 at 08:42, Thomas S. Dye wrote:
>
> [...]
>
>> Have you tried
>>
>> #+call: drawlayout[:stdin solution]() :results raw
>>
>> or,
>>
>> #+call: drawlayout[:stdin solution]() :results
raw" and ":exports results" on the src block,
> exporting that block works just fine. The call however is wrapped in an
> EXAMPLE block which does me no good!
>
> Any suggestions welcome!
Have you tried
#+call: drawlayout[:stdin solution]() :results raw
or,
#+call: drawlayout[:stdin solution]() :results latex
which should make the print "#+begin_latex" etc. lines of drawlayout redundant?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Eric S Fraga writes:
> On Monday, 9 Mar 2015 at 07:49, Thomas S. Dye wrote:
>
> [...]
>
>> Do you have a use for the shortcuts? I doubt I'd use them.
>
> Wouldn't the shortcut be the most attractive to use generally unless you
> have need for the extra
lem is limited to the shortcut citations and doesn't affect the
[cite: ...] form, which can be expected to work without modification
wherever it is placed IIUC.
Do you have a use for the shortcuts? I doubt I'd use them.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Richard Lawrence writes:
> Hi Tom and all,
>
> "Thomas S. Dye" writes:
>
>> Richard Lawrence writes:
>>
>>> But my opinion probably shouldn't count for much on this
>>> point, because I don't use a citation manager myself (I use o
Aloha Vaidheeswaran C,
Vaidheeswaran C writes:
> On Sunday 08 March 2015 11:04 PM, Thomas S. Dye wrote:
>
>> Thankfully, Richard demonstrated to his satisfaction that an
>> off-the-shelf CSL style could be made to handle this situation. If this
>> is the only potenti
Aloha Richard,
Richard Lawrence writes:
> Hi Tom and all,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> As I see it, the choice boils down to the relative benefit of citation
>> shortcuts vs. the limitation of requiring authors to configure the
>> citation manag
Aloha Vaidheeswaran C,
Vaidheeswaran C writes:
> On Sunday 08 March 2015 09:29 AM, Thomas S. Dye wrote:
>
>> Is your doubt about his eventual success founded in a general
>> skepticism about predicting the future (certainly warranted),
>> or in some particular knowledge
Aloha Rasmus,
Rasmus writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Rasmus writes:
>>
>>> Nicolas Goaziou writes:
>>>
>>>>> I'm asking because I haven't fully grasped uses for the shorthand. What
>>>>> is the
otes are
> requested at the time of insertion.
I think the OP has a valid point. After we teach org-reftex to insert
@key if no notes are requested, are we going to convince all key
generating software to prohibit keys that end in punctuation?
As I currently understand the problem, that see
Vaidheeswaran C writes:
> On Sunday 08 March 2015 03:01 AM, Thomas S. Dye wrote:
>> Aloha Vaidheeswaran C,
>>
>> (Bringing the conversation back on list.)
>>
>> Vaidheeswaran C writes:
>>
>>> Richard understood the point I was making. When y
Aloha Vaidheeswaran C,
(Bringing the conversation back on list.)
Vaidheeswaran C writes:
> Richard understood the point I was making. When you have time,
> compare how you responded with how he responded. You can learn a
> thing or two from Richard.
I've learned many things from Richard!
I'
arises (unless
someone gets there first).
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
) to insert citations?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
n my experience mostly as an observer, very many details are
worked out at the code level, rather than "in front of this forum".
Indeed, that is one of the beauties of open-source software. It is
always possible to read the code and learn from it.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
ly talented and experienced programmers. IIUC,
they are also busy with other projects (some of which hopefully make
them some money!), so I think it would help them if you could document
the problem you've identified.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Aaron,
Aaron Ecay writes:
> Hi Tom,
>
> 2015ko martxoak 2an, "Thomas S. Dye"-ek idatzi zuen:
>>
>> Aloha Aaron,
>>
>> Aaron Ecay writes:
>>
>>> By way of illustration, Biblatex (AFAICT) doesn’t provide a possessive
>>&
mat 'latex)
(format "\\citeauthor{%s}'s (\\citeyear{%s})" path path)
#+end_src
I haven't tested this, but I think it would work in Org mode.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
h) file
produced by LaTeX. Thus, it is able to take advantage of the work of
sophisticated citations managers built on bibtex. I think of it,
perhaps naively, as a program that can be configured to generate dvi
drivers for odt, html, xml, etc.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
| (author year) | (1)| (1)|
Or, is there a third-map that better captures what we're discussing?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Hi Aaron,
Aaron Ecay writes:
> Hi Thomas,
>
> 2015ko otsailak 25an, "Thomas S. Dye"-ek idatzi zuen:
>>
>> BibLaTeX has 6 standard "subtypes", which it calls "standard commands".
>>
>> A citation style can provide any number of
Vaidheeswaran C writes:
> On Tuesday 24 February 2015 11:37 AM, Thomas S. Dye wrote:
>> Aloha Vaidheeswaran C,
>>
>> Vaidheeswaran C writes:
>>
>>> On Tuesday 24 February 2015 10:31 AM, Thomas S. Dye wrote:
>>>> Vaidheeswaran C writes:
>>&
Aloha Vaidheeswaran C,
Vaidheeswaran C writes:
> On Tuesday 24 February 2015 10:31 AM, Thomas S. Dye wrote:
>> Vaidheeswaran C writes:
>>
>>> Often times there is a difference between what is possible and what is
>>> the common practice. So,
>>>
&g
>in-text or parenthetical citation could be replaced by the other
>without compromising on the overall style of the produced document.
Yes, but the author will certainly choose to use a tool that doesn't
require this.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
---
exports this valid mdframed code to LaTeX:
\begin{mdframed}[foo]
Contents of box go here.
\end{mdframed}
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha all,
The attached patch recognizes all six possible :noweb header arguments.
All the best,
Tom
>From 3106e37ba1cfd7fa8e7c1a792a7c69cf76aa5343 Mon Sep 17 00:00:00 2001
From: tsdye
Date: Sun, 22 Feb 2015 07:20:34 -1000
Subject: [PATCH] Revise noweb header argument
---
doc/org.texi | 4 ++-
ix this is to have babel run with python, not IPython,
> but then pre-load all the packages that make IPython great.
>
> To be specific, how can I executed "import numpy as np" each time I "C-c
> C-c" on a "+#BEGIN_SRC python" code block?
>
> Thanks,
>
> -k.
>
>
>
--
Thomas S. Dye
http://www.tsdye.com
eal find.
Thanks,
Tom
--
Thomas S. Dye
http://www.tsdye.com
m to scholars in the larger community.
At any rate, I'm just reacting to "desperately needs" and "rigorous,
standard".
I think Samuel's ideas on extensible syntax are compatible with
reproducible scientific writing.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Thanks for your patience as I digested your proposals. Let me know if
you think I can help in some way.
All the best,
Tom
Richard Lawrence writes:
> Hi Tom,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I want a syntax that recognizes arbitrary citation commands because I
>
ed.
Also, biber is required for some biblatex features that bibtex doesn't
support. I haven't followed this development and am not sure what they
are, though.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
pler syntax, as Stefan suggests, would it be possible
for the various ox-* files to indicate for the input helper which
commands are supported? Then, the author could specify the output
targets somewhere in the header and the input helper could serve up the
intersection of supported commands, yielding a document portable across
the indicated backends and with the richest possible set of citation
commands.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
e official
citation syntax. I'm able to achieve my goals fully in Org mode without
it.
All the best,
Tom
Richard Lawrence writes:
> Hi Tom,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> 0
>>
>> A syntax that relegates citation commands to an extension that
e adopted), 0, or -1 (meaning you'd prefer not to
> see this syntax or anything similar to it adopted).
0
A syntax that relegates citation commands to an extension that might not
export properly in future versions of Org mode isn't useful in my work.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
ichiliocosm" or
"chiliocosm."
It's eye opening to see Org mode at work so deep in the humanities.
All the best,
Tom
Vaidheeswaran C writes:
> On Thursday 12 February 2015 12:49 PM, Thomas S. Dye wrote:
>> Aloha Vaidheeswaran,
>>
>> This is an odd examp
the ODT exporter, suggests that the
> '[fn:2]' occurring in '[fn:1]' is treated as site of first
> reference. We would like to make '[fn:2]' occurring next to 'text2' be
> treated as the site of first reference. If we do that, everything
> will be just right.
>
>
>
>
>
--
Thomas S. Dye
http://www.tsdye.com
601 - 700 of 2331 matches
Mail list logo
