gt; And the filter can translate the cookie to the appropriate backend
> specific expansion.
Another option would be a link:
(org-add-link-type
"ruby" nil
(lambda (path desc format)
(cond
((eq format 'html)
(format " %s (%s) <\ruby>" path desc))
((memq format '(beamer latex))
(format "\\ruby{%s}{%s}" path desc)
[[ruby:東][ひがし]]
(untested)
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
cial block? (First
> guess, "#+BEGIN_figure*" causes the special block not to be
> recognized.) Or do I need to write the literal LaTeX code for that?
>
No, you don't need to write literal LaTeX code. See Section 12.7.4 of
the manual, which describes setting the :float attribute to
'multicolumn'.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
ve changed the title of this document to indicate that it was written
for the old exporter, Org Mode < 8.0.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
>> >remote: worg publish process 7241 exited at 05/05/13@07:53:51
>> >To w...@orgmode.org:worg.git
>> > a3eed5c..9531016 master -> master
>> >
>> > I assume this is an error?
>>
>> I guess, I've never published on worg before.
>>
>> > In any case, you can find the tutorial at
>> > ./org-tutorials/koma-letter-export.org
>>
>> Thanks, I'll have a look.
>>
>> Alan
>>
>
>
--
Thomas S. Dye
http://www.tsdye.com
> #+LABEL: fig:WhatWeWant
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
blah
The :: separator lets Org (and ultimately LaTeX) know that the part
before the separator is the term that is being described.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
iple invocations of export. I use BIND to change the formatting
> for active and inactive time stamps on latex export and it works
> sometimes but is ignored other times. I've not figured out a
> deterministic recipe to have this consistently repeatable yet but, if
> and when I d
Aloha Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Try:
>
> #+BIND: org-latex-title-command ""
>
> This assumes `org-export-allow-bind-keywords' is non-nil.
I couldn't find a reference to this variable in the manual. I'd suggest
replacing the word `Eventually' with the clause before the fir
Aloha James,
James Harkins writes:
> On Apr 29, 2013 8:23 PM, "Thomas S. Dye" wrote:
>>
>> James Harkins writes:
>>
>> > The problem is that the "org-latex-title-command" variable places
>> > \maketitle before the \twocolumn[...] bit.
every document I export to LaTeX.
Does an empty #+TITLE: do what you want?
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Yagnesh Raghava Yakkala,
Yagnesh Raghava Yakkala writes:
> Hello Thomas,
>
> On Apr 28 2013, t...@tsdye.com (Thomas S. Dye) wrote:
>
>> Aloha Feng Shu,
>>
>> Hmm. The links to an mobileorg FAQ here
>> http://mobileorg.ncogni.to/support/ and here
>
oes anybody knows how to configure emacs to push and pull notes
>> automatically.
>
> Please read org-mobile FAQ!
>
>>
>> Thanks
>> M
--
Thomas S. Dye
http://www.tsdye.com
s of creating and tending the language-specific code. If
:results graphics makes good sense for Python, then users should feel
free to add it to ob-python.el. With the examples you point out, it
shouldn't be too difficult.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
rom the command line, I run Emacs with --batch,
> and I don't load any of my personal configuration. That way the export
> can easily be distributed as it doesn't rely on my personal config.
This is what asynchronous export does, IIUC. Here is the relevant part
of a setup I'm using:
(setq org-export-in-background t)
(setq org-export-async-debug t)
(setq org-export-async-init-file (expand-file-name "init.el"))
I tangle the initialization file (init.el) from my document. Everything
is contained in the one Org file.
Asynchronous export works really well for me.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
gy behavior is the first one: the fact that the "code" block
> disappears, as you say.
I took a quick look at ob-latex.el. The code there sets `:exports
results' and then, IIUC, goes on its way without checking if :exports
has been set in the buffer.
IIRC, the main uses of
le
>> ambiguity, AFAICT, in Org syntax.
>>
>> Suggestions welcome.
>
> How about {}^{14}C or {^{14}}C?
The LaTeX solution, which recognizes the superscript and subscript
symbols in math mode, would only require a change in the Org
documentation. This works: \(^{14}\)C.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha all,
FYI, Org 8.0 appears to require the LaTeX amstext package to export
super/subscripts to LaTeX.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
From my point of view, the new exporter framework is a huge
step forward. Congratulations!
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Rasmus,
Rasmus writes:
> The following message is a courtesy copy of an article
> that has been posted to gmane.emacs.orgmode as well.
>
>
> Thomas,
>
>>> Tom, do tell us more about what these habits are.
>>
>> The new exporter is really your friend. Where before I might choose to
>> gene
tml
>
> Feel free to improve it, embellish it, play with it, modify it, add
> captions,...
>
> Cheers,
> Jay
Now Bastien's new unicorn looks very angry!
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Vikas,
Vikas Rawal writes:
>> I've been down it too many times myself. The habits I've developed
>> over time have helped, but I think they are less systematic than
>> what you've devised.
>
> Tom, do tell us more about what these habits are.
The new exporter is really your friend. Where
Hi Suvayu,
Suvayu Ali writes:
> Hey Tom,
>
> Actually, I am working on a workflow for large writing projects, my PhD
> thesis in this case :-p. What I have in mind is have a Makefile based
> build system that uses `emacs --batch' to export to LaTeX and html. The
> images are generated separate
well-worn, I've
been down it too many times myself. The habits I've developed over time
have helped, but I think they are less systematic than what you've
devised. I'd love to see some notes on your solution as a brief tutorial
or an expanded FAQ on Worg. I'll be happy to contribute or help if you
find time to do something like this.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
her way? I don't know, but it
seems to me that :wrap is still potentially useful and we might want to
keep it around.
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha all,
With a recent git pull and #+OPTIONS: ^:{}, `C^{14}' is interpreted
correctly but ` ^{14}C' is not, both in the Org buffer and in LaTeX
export. The space before the caret appears to be the problem.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
orse to try ;)
>
The anti-zenburn theme is the light version. It is subdued and the
faces make the distinctions well, as does zenburn.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
ository on the server? This
> is powerful enough to deserve a separate place IMO.
Perhaps the Library of Babel would be a good place?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Bastien writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> After a fresh pull from git, I get this when exporting to LaTeX:
>>
>> Debugger entered--Lisp error: (void-function copy-seq)
>> copy-seq((org-fill-paragraph-separate-nobreak-p
>> org-fil
()
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
other package that I do load.
Thanks,
Tom
Eric Schulte writes:
> Hi Tom,
>
> The `first' function is provided by the cl package. I'd either replace
> `first' with `car' in your code block, or add (require 'cl) to your
> personal Emacs configuration.
>
c "\n")
"\n\\end{flushleft}"))
#+end_src
#+name: author-table
| Author name | Department | Institution | City
| State | Country | Email | Corresponding |
|---++---+--+---+-+---+---|
| Thomas S. Dye
near the bottom.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Seb,
"Sebastien Vauban"
writes:
> Hi Thomas,
>
> Thomas S. Dye wrote:
>> In this situation I often put the arguments in a named Org table and
>> then write the Babel source code block to take a single argument--the
>> table name--and par
gt; cname="Dr. Stefan Vollmar",\ # full name for headline
> gname="Stefan",\ # given name
> photo="stefan-vollmar.jpg",\ # can be jpg or png
> ...)
>
> Maybe there already is a good solution to increase readability? Maybe
> the "line continuation marker" (3) would be a general solution for all
> cases in org where now no line breaks are possible?
>
> Many thanks for any help with this.
> Warm regards,
> Stefan
--
Thomas S. Dye
http://www.tsdye.com
Aloha John,
Nice work. I look forward to contributing.
Another part is either getting rid of, or clearly labeling, all the Worg
pages that deal with the old exporters. I can see them being a source
of real confusion when 8.0 is adopted by users.
All the best,
Tom
--
Thomas S. Dye
http
ng for detailed content
from users. There are still many languages without a guide (see
http://orgmode.org/worg/org-contrib/babel/languages.html). The template
for language guides
(http://orgmode.org/w/?p=worg.git;a=blob;f=org-contrib/babel/languages/ob-doc-template.org;hb=HEAD)
has a section for header arguments, so there is a structure in place.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Marcelo,
Marcelo de Moraes Serpa writes:
> I still don't understand why the TARGET_FILE argument is optional. I would
> expect it to create a file of the same name of the org file that is
> tangled.
Here is the docstring:
(org-babel-tangle-file FILE &optional TARGET-FILE LANG)
Extr
Aloha Marcelo,
Marcelo de Moraes Serpa writes:
> Oh, actually that wasn't the issue.
>
> org-babel-load-file seems to force tangling the file to an .el.
> org-babel-tangle-file doesn't. Is there a way to force the output to the
> .el file without using the parameter in the code block itself?
>
(provide 'peepopen-config)
>
>
> I'm trying to tangle it with (org-babel-tangle-file
> "peepopen-config.org"), but I get the following in the "Messages"
> buffer:
>
> Tangled 0 code blocks from peepopen-config.org
>
>
> I'm confused, since the file *does* contain a code block. Am I doing
> something wrong?
>
> Thanks in advance,
>
> - Marcelo.
>
>
>
--
Thomas S. Dye
http://www.tsdye.com
Hi Bastien,
Bastien writes:
> Hi Tom,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I pushed some small additions to Worg yesterday, but they aren't showing
>> on the web page.
>
> I just pushed a test change which shows fine, and I see yours is here:
>
&
Aloha all,
I pushed some small additions to Worg yesterday, but they aren't showing
on the web page.
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com
ke: [local.mk] Error 255 (ignored)
>> make -C lisp autoloads
>> rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc
>> org-install.elc
>> org-version: 8.0-pre (release_8.0-pre-150-g412d98)
>> End of file during parsing
>> make[1]: *** [org-version.el] Erro
=
> > = Created a default local.mk template. =
> > = Setting "oldorg" as the default target. =
> > = Please adapt local.mk to your local setup! =
> > ==============
> > End of file during parsing
> > make: [local.mk] Error 255 (ignored)
> > make -C lisp autoloads
> > rm -f org-version.el org-loaddefs.el org-version.elc
> org-loaddefs.elc org-install.elc
> > org-version: 8.0-pre (release_8.0-pre-150-g412d98)
> > End of file during parsing
> > make[1]: *** [org-version.el] Error 255
> > make: *** [autoloads] Error 2
> >
> > Not sure where to go from here.
> >
>
>
> This
>
>
> > Start Emacs with
> > the `--debug-init' option to view a complete error
> backtrace.
>
>
> would be a start. The "End of file during parsing" probably
> indicates
> a missing paren or some such, possibly in init.el. I presume emacs
> -q
> starts up properly?
>
> Nick
>
>
>
--
Thomas S. Dye
http://www.tsdye.com
into this. I found some time to investigate and
haven't been able to reproduce the problem. It all seems to work as
advertised (and I like it).
Sorry for the noise.
Tom
--
Thomas S. Dye
http://www.tsdye.com
) (bookmark-jump . t)))" ((:comments . "") (:shebang . "") (:cache .
"no") (:padline . "") (:noweb . "yes") (:tangle . "yes") (:exports . "code")
(:results . "replace") (:session . "none") (:padnewline . "yes") (:hlines .
"yes") (:colnames . "no") (:result-type . value) (:result-params "replace")
(:rowname-names) (:colname-names)) "" nil 0))
org-babel-execute-src-block-maybe()
org-babel-execute-maybe()
org-babel-execute-safely-maybe()
run-hook-with-args-until-success(org-babel-execute-safely-maybe)
org-ctrl-c-ctrl-c(nil)
call-interactively(org-ctrl-c-ctrl-c nil nil)
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
eel
> free to alter it!)."
>
> How can I get such "live" documentation?
You can click on the `Show Org source' button at the bottom left of the
page, then cut and paste into Emacs.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
shripad sinari writes:
> This seems to work for me:
>
> #+DATE: %Y-%m-%d
>
>
And might be a nice addition to the FAQ on Worg.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
like they're being
> exported to the PDF file.
>
> Am I doing something wrong here?
Perhaps. I don't see =source= on the list of :exports header arguments.
If you change =source= to =code= does it work?
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
;*.xls*"))
cat("\\normalsize")
#+END_SRC
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
or a clearly stated "no go".
>>
>> I tend to agree with Jay here and I prefer the minimalist syntax,
>> although values for the :results parameter are heterogeneous.
>>
>
> +1 for maintaining the existing concise syntax.
+1 for stable syntax.
Tom
--
Thomas S. Dye
http://www.tsdye.com
John Hendy writes:
> Thanks, Tom. Having an issue, though. From what I've read/heard...
> =:width= is used for all backends now? This seems to be indicated by
> this pretty recent post as well:
> - http://permalink.gmane.org/gmane.emacs.orgmode/68306
>
> #+begin_quote Aaron Ecay
>
> Eliminating s
were escaped. Now, quotes are not used and
backslashes don't need to be escaped. Multi-word options are fine
without quotes.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
finish editing the Installation instructions, then tag the
commit to indicate that it is "current" with org.texi.
Then, unless you think there is more to fix with the conversion, I'll
get down to documenting Nicolas' work according to the instructions he
gave me months ago.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Hi Bastien,
Bastien writes:
> Hi Thomas,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>>> I would mention "make config" here for a sanity check of the created
>>> configuration.
>>
>> Good idea. Done.
>
> Oh, I thought it was done i
Aloha Thorsten,
What a joy to find the following bit on Worg!
To sum it up in one sentence: Outline with Outshine outshines
Outline
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
- in LaTeX terminology -- a listing?
>
> Good point. Yes, Listing would be good. Any idea how to solve this
> reference problem as a listing?
The LaTeX minted package has a facility for "floated listings" that
might do what you want.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Achim,
Achim Gratz writes:
> Thomas S. Dye writes:
>>In most cases where you have permission to write to system locations,
>> you will probably want to install Org with the Emacs system files.
>> This is a system-specific operation that is guided by a file,
>
ystem.html).
-- Footnotes --
(1) The `local.mk' template is designed to work out of the box with
GNU systems.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
avoids
mentioning all the bad behaviors that can be found on mailing lists.
Please feel free to edit so it suits!
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
's ability to
contribute code to Org might be used to the same effect.
Because I am keen to know that my investment in Org is being suitably
protected, could someone assure me either that my concern is unfounded,
i.e., that code contributed by Jambunathan can be successfully vetted so
that it doesn't delay development or cause confusion, or that
appropriate steps have been taken to ensure that future code
contributions from Jambunathan will not become part of Org?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
explanation of Org's build system can be found at the Org
Build System page on Worg
(http://orgmode.org/worg/dev/org-build-system.html).
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
endation for the worktree location and
also provide a suitable warning about where *not* to put the worktree,
if needed.
Thanks for your help.
Tom
--
Thomas S. Dye
http://www.tsdye.com
`make install.'
It seems clear to me that `install' is being used in two different senses
here. I'd like to disambiguate--can someone suggest a concise way to do
this?
Thanks,
Tom
--
Thomas S. Dye
http://www.tsdye.com
s any way I can help.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Achim,
Achim Gratz writes:
> Thomas S. Dye writes:
>> Help?
>
> Nice riddle. But here's what I think is happening: your macro expansion
> ends with a texinfo export snippet. That export snippet is ignored by
> the the HTML backend as it should, but in doing so
:
S-TAB or C-u TAB, org-global-cycle
but not in html:
S-TABor C-u TAB, org-global-cycle
which loses the space between `TAB' and `or'.
Help?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Achim,
Achim Gratz writes:
> Thomas S. Dye writes:
>> I do have a problem here. I think I have mis-configured BTEST_POST.
>>
>> I have this:
>>
>> BTEST_POST =
>> # -L /ert # needed for Emacs23, Emacs24 has
>> ert built in
Emacs or GNU ELPA after
> a 6 month or 1 year period. My code is meant for others to use and I am
> not bothered about a 6 month or a 1 year break.
Good news. I look forward to the release of this code. It would be
great if you could announce the release on our mailing list.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Achim Gratz writes:
> Thomas S. Dye writes:
>> That works nicely. I found the error and orgmanual.pdf is now produced
>> without errors.
>
> Progress! :-)
>
> With the current version from git I cannot export to texinfo
This is fixed now.
>
> I've extend
ntial mentor?
I think the Org community might want to decide whether or not to accept
patches from Jambunathan K in the future. I don't think we are under
any obligation to accept his contributions.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha all,
>
> I'm not sure how this happened, but chapter 2 of orgmanual now has all
> the macros replaced by their expansions. You can see this here:
>
> https://github.com/tsdye/orgmanual/blob/master/orgmanual.org
Apologies for
s need
not concern you at all.
Peace,
Tom
--
Thomas S. Dye
http://www.tsdye.com
yable.
I hope you know that I admire your work and think you are a valuable
member of our community. But, like the rest of us, you have to deal with
the Org community, because it is the Org mode community, ever changing,
that will shepherd the code you, many others, and (to a much lesser
extent) I wrote. If we work well together on this magnificent idea, Org
mode might outlive us all.
Peace,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha all,
I'm not sure how this happened, but chapter 2 of orgmanual now has all
the macros replaced by their expansions. You can see this here:
https://github.com/tsdye/orgmanual/blob/master/orgmanual.org
Please don't ask for an ECM!
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologis
Achim Gratz writes:
> Thomas S. Dye writes:
>> The orgmanual now creates a pdf file, too, but one lacking the indexes
>> and with links that look like they need another run through TeX.
>
> In that case, texi2dvi and hence make should have signaled an error
> (I've j
Aaron and Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> aarone...@gmail.com writes:
>
>> I think the following patch (on top of current master) will fix the
>> problem:
>
> [...]
>
> It does. Thank you.
>
Works here now. Thanks!
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
might use. Apparently,
it's not possible to design a data table that supports all the
bibliography styles that one might want to use.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
anguages/ob-doc-template.org;hb=HEAD
I don't know the first thing about Perl, but I'll be happy to help if
there are questions about getting to ob-doc-perl from the template.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
c|
> #+attr_foo: :prop var="value" :another-prop nil
>From the user POV +1.
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha Rasmus,
Rasmus writes:
> t...@tsdye.com (Thomas S. Dye) writes:
>
>
> Indeed, but perhaps there is a better possible syntax. With Reftex
> the the link-way is OK, but I still think that we should think about
> whether there is a "Better Way"ᵀᴹ if Org was to
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I think this behavior was introduced in the last week or so.
>>
>> This in the Org file:
>>
>> #+attr_latex: :height "2in"
>> [[file:saa-fig/wet-dry.jpeg]]
&
our contributions? The line
seems somewhat dated to me.
Peace,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha all,
I think this behavior was introduced in the last week or so.
This in the Org file:
#+attr_latex: :height "2in"
[[file:saa-fig/wet-dry.jpeg]]
yields this in LaTeX output:
\begin{figure}[htb]
\centering
\includegraphics[width=.9\linewidth,height=2in]{saa-fig/wet-dry.jpeg}
\end{figure}
osed to Natbib).
Given that 1., 2., and 4. are possible with "link hacks" doesn't this
leave just 3. in need of solution? If the current link syntax would
take another function used to display the link, then wouldn't that solve
3.?
Tom
--
Thomas S. Dye
http://www.tsdye.com
Achim Gratz writes:
> Thomas S. Dye writes:
>> The orgmanual now creates a pdf file, too, but one lacking the indexes
>> and with links that look like they need another run through TeX.
>
> In that case, texi2dvi and hence make should have signaled an error
> (I've j
al', or would some other workflow better fit my needs?
Suggestions warmly welcomed.
Thanks again for your help.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
quot;l|r" :width "\\textwidth"
Note the double backslashes for the LaTeX command.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Hi Achim,
Achim Gratz writes:
> Thomas S. Dye writes:
> […]
>> I look forward to picking this project up again in a week or so, or
>> learning from my Org colleagues that the project ought to be scuttled.
>
> Hi Tom,
>
> this looks good.
Thanks for reviewing a
ted files
> like .bbl, .blg, .tex, .lof etc ?
>
> Thanks
>
>
> -
> Sanjib Sikder
> Ph.D. Fellow
> Chemical Engineering
> IIT Bombay
>
>
--
Thomas S. Dye
http://www.tsdye.com
>'org-babel-do-load-languages
>'(
> (sh . t)
> (python . t)
> ))
>
> If I load this first, then your print-example shows error like indicated in
> subject line.
>
> Something wrong with this code?
>
I think it should be 'org-babel-load
Aloha all,
An experiment to see if it is possible to convert the Org manual to Org
is now (hopefully) at the "proof of concept" stage and I would like to
determine whether or not the approach is viable. The experiment is here:
https://github.com/tsdye/orgmanual.git
The file orgmanual.org has a h
ic error that was actually
> inserting
> description at column+5)
>
I hadn't detected the logic error, but can confirm that the other fix
works.
Thanks!
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Aloha all,
IIUC, there is currently no support for @pxref{} in the texinfo
exporter. This is a texinfo @-command that does one thing in the info
output and another in the LaTeX output.
My idea is to create a custom link type, something like this:
(org-add-link-type
"pxref" nil
(lambda (
TITLE:.
>
> Tom,
>
> This will cause the menu titles to no longer export properly until you
> change the property names.
I can confirm that this works.
Thanks!
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
cognized type, otherwise it
> will simply be an unnumbered headline.
Yes, this works nicely.
>
> I've additionally added support for appendices. These will export as
> @appendix .
>
An :APPENDIX: property triggers this one, which works as advertised.
Thanks!
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Hi Jon,
Jonathan Leech-Pepin writes:
> Hi Tom,
>
> On 21 February 2013 18:44, Thomas S. Dye wrote:
>
>> Hi Jon,
>> [...]
>>
>> Based on this example from the Org manual, it looks as if the
>> descriptions should start on column 32 or the third column a
Nicolas Goaziou writes:
> Hello,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> I've learned that there are certain conditions (I don't know how many)
>> where the space after a sentence won't accept a footnote insertion.
>
> There shouldn't
Aloha all,
This footnote:
[fn:141] See the attributes ~table:template-name~,
~table:use-first-row-styles~, ~table:use-last-row-styles~,
~table:use-first-column-styles~, ~table:use-last-column-styles~,
~table:use-banding-rows-styles~, and ~table:use-banding-column-styles~
of the ~~ eleme
se are under development and the current
behavior is expected to change slightly in the weeks ahead. I believe
the goal is to have a stable texinfo exporter for version 8.0.
hth,
Tom
--
Thomas S. Dye
http://www.tsdye.com
t so that data are lost,
should org-footnote-auto-adjust be deprecated?
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
801 - 900 of 1836 matches
Mail list logo
