I have a org file (paper.org) which includes inlined files (abstract.org,intro.org). Like this,
** Introduction
#+INCLUDE: intro.org
** Results
#+INCLUDE: results.org
When I export to a pdf (C-c C-e d), The subsections in the intro.org do not appear in the generated pdf. Do I need to set a variable? The included files appear when I export to html.
EDIT
As requested, here is a MWE.
== paper.org ==
Abstract
#+INCLUDE: "abs.org"
Intro
#+INCLUDE: "intro.org"
== abs.org ==
This is the abstract. This should appear.
** Abstract Subsection
This will not.
== intro.org ==
This is intro. This will appear in the pdf.
** Subsection in Intro
But this will not.
There is an example of what you want to do in the manual, at http://orgmode.org/manual/Include-files.html#Include-files.
If that does not work, provide us with a MWE and/or write to the ML -- that could be a bug, then.
This was a problem with the version of org-mode that I was using. This and another problem were solved when I upgraded. See link.
Related
in emacs org mode, I saw #+ prefix many times. I think this is like option but I don't know what it is. I have tried to know them, I have been googling, but I couldn't find any good document. anybody know these symbol? is this org macros?
It is just plain text that you write in an org mode file. It may have two different functions:
1.- If you write it at the beginning of the file, it serves as a metadata descriptor or to include options for the file [1]. For example:
#+TITLE: This is the title of this file
#+AUTHOR: Loretta
#+DATE: 2022-10-15
#+STARTUP: content <--- option for displaying the contents
#+OPTIONS: H:3 toc:nil \n:nil #:t ::t |:t <--- different export options
2.- To create a block inside the file. This block may be code meant to be executed [2], a quotation, a comment, etc:
#+begin_src emacs-lisp
(+ 1 2 3 4 5 6 7)
#+end_src
#+begin_comment
Check the following paragraph. I am not really sure if it
has taken into account all the variables.
#+end_comment
[1] See https://orgmode.org/manual/In_002dbuffer-Settings.html for buffer settings and https://orgmode.org/manual/Export-Settings.html for export settings.
[2] See https://orgmode.org/manual/Literal-Examples.html for code blocks.
I'd expect
#+begin_src plantuml :file foo.png :exports results
foo -> bar: JSON request
foo -> batz : instantiate batz\npassing resources from request
#+end_src
to only produce the resulting image in the exported document, but it exports both the plantuml code that produces it and the resulting image.
Any ideas what I can do to only export the images that are generated by the code block short of commenting out the code blocks after first generating the images?
I'm not allowed to comment so will provide an answer: this works fine for me with org 9.3.7 (i.e. only the image is exported, at least to PDF via LaTeX) so maybe it's a bug in the version of org you are using?
If posting this annoys anybody, I will delete.
To distinguish this question from Doxygen: Adding a custom link under the "Related Pages" section which has an accepted answer that is not a real answer to the question, I specifically add prewritten to the question.
What I want:
Write one document tex file (without preamble, since this file will be \input-ed into a full document)
Import the document into Doxygen's HTML output.
Using Doxygen to produce tex file will probably not work, since it does too much layout work [This holds for its HTML output too like empty table rows 2015]. If Doxygen takes some other input that can easily be transformed into LaTeX, that will do.
You can easily add an already existing Latex file to your doxygen documentation using \latexonly\input{yourfile}\endlatexonly.
I would assume you put it e.g. under a doxygen \page.
Every time I want to convert an org-file to pdf using org-mode, I need t write the following lines at the end of my file:
* References:
\bibliographystyle{plain}
\bibliography{/path/to/my/bibfile}{}
In org-mode there is the command <s TAB to insert a
#begin src
#end src.
Is there something similar for the bibliography? I would like to have these line automatically added to my files, each time
I fire some <s-command.
Two answers for the price of one:
Look at the easy templates (section 15.2 of the manual) or
Use YASnippet therefore (more generic, and usable in all Emacs parts!).
I am working with some legacy code, for which I am generating XML documentation using doxygen. I have two problems with this kind of code. First it contains invalid comments. For example:
///#struct E
enum E
{
E1, E2, E3;
};
This causes doxygen to generate output for struct with name E, which is not in the code. My second problem is with HTML links. For example, for the following input:
///#brief For info about this struct see: <a href="http://www.foo.com/bar&bar"\>
struct S
{
int i;
}
the doxygen generated output is not a valid XML because the & in the link is not properly escaped.
For the above reasons I would like doxygen to ignore some comments. Is this possible?
I don't think that doxygen has a simple switch for this, however, you can write your own INPUT_FILTER program to clean up the file (by stripping out comments, for example) before doxygen runs.
I noticed and tested that html comments within a doxygen comment will be ignored:
///#brief some comment here <--! ignored here --> also continues over.
As far as the & not being escaped, have you noticed \& would escape it? Maybe this is a solution for that part.