2013ko abenudak 11an, Nicolas Goaziou-ek idatzi zuen:
>
> Aaron Ecay writes:
>
>> I have found one case where both match, but an underline is intended.
>> Are there any reverse cases, i.e. where both match but a subscript is
>> intended?
>
> I don't know. Perhaps something as convoluted as:
>
>
Hi James,
2013ko abenudak 12an, James Harkins-ek idatzi zuen:
> What's the best way to handle that? I really want the "hidelinks"
> option for hyperref to be used globally. But, customizing
> org-latex-default-packages-alist means that I will miss updates to
> that variable in future org versions
On Wed, Dec 11, 2013 at 11:22 PM, Nicolas Goaziou wrote:
> Your first "attr_latex" line applies to the "figure" special block, not
> to the source block.
I did eventually figure that out.
As far as I can see, this is the only reference to figure*
environments in the manual:
~~
multicolumn: if y
On Thu, Dec 12, 2013 at 10:40 AM, James Harkins
wrote:
> On Wednesday, December 11, 2013 10:47:42 PM HKT, Nicolas Goaziou wrote:
>>>
>>> Is "ulem" one of the LaTeX export default packages?
>>
>> Yes, it is. See `org-latex-default-packages-alist'.
>
> Ah... I must have customized that at some point
James Harkins writes:
> Incidentally, while I was trying different versions last night (for
> the LaTeX starred-figure issue), I saw the following warnings during
> "make":
>
> In toplevel form:
> ox-texinfo.el:1683:1:Warning: !! The file uses old-style backquotes !!
> This functionality has been
Achim Gratz writes:
> Eric Schulte writes:
>> I just pushed up a change which fixes this when exporting on my system,
>> if the problem persists please provide an ECM.
>
> This test is still failing:
>
> Test test-ob/noweb-expansions-in-cache condition:
> (void-variable <>)
>FAILED 149/4
On Wednesday, December 11, 2013 10:47:42 PM HKT, Nicolas Goaziou wrote:
Is "ulem" one of the LaTeX export default packages?
Yes, it is. See `org-latex-default-packages-alist'.
Ah... I must have customized that at some point.
Drifting off the topic slightly, to a related question. I have a fe
Incidentally, while I was trying different versions last night (for the
LaTeX starred-figure issue), I saw the following warnings during "make":
In toplevel form:
ox-texinfo.el:1683:1:Warning: !! The file uses old-style backquotes !!
This functionality has been obsolete for more than 10 years al
Aaron Ecay writes:
> I have found one case where both match, but an underline is intended.
> Are there any reverse cases, i.e. where both match but a subscript is
> intended?
I don't know. Perhaps something as convoluted as:
A'_{a_-1}
But that's not the real problem: whenever we change under
Hi Michael,
Trying to file a minimal init.el for bug reporting I discovered the
culprit. In my init file I had:
(setq org-agenda-files (concat org-directory "/gtd.org"))
The missing quote was causing Tramp to be ignited every time I opened a
file or tried to open the agenda view.
Thanks for
On Wed, Dec 11, 2013 at 5:12 AM, Vikas Rawal
wrote:
> What is the best solution for the following scenario?
>
> In my org file, I use an R source code to generate a table. I would like to
> additionally specify notes to this table, and use threeparttable in latex
> export to be able to specify no
Hi Nicolas,
Thanks for your comments.
2013ko abenudak 11an, Nicolas Goaziou-ek idatzi zuen:
> Actually, this is not really a parser problem but a syntax one.
> underline and subscript are ambiguous, and therefore ill-defined,
> because, in some situations, both can match at the same location.
I
On 12/11/2013 10:57 AM, Nicolas Goaziou wrote:
> Hello,
>
> Scott Randby writes:
>
>> I had a file with the following structure:
>>
>> #+OPTIONS: tags:nil
>> * Grades
>> ** Student :studenttag:
>> :PROPERTIES:
>> :EXPORT_FILE_NAME: Exported-Grades/studenttag
>> :END:
>> *** Totals :totals:
>>
On 12/11/2013 11:03 AM, Nicolas Goaziou wrote:
> Scott Randby writes:
>
>> I already have the following in my file:
>>
>> #+HTML_DOCTYPE: html5
>
> You need to upgrade Org then.
Okay, I will do that.
Scott
>
>
> Regards,
>
Scott Randby writes:
> I already have the following in my file:
>
> #+HTML_DOCTYPE: html5
You need to upgrade Org then.
Regards,
--
Nicolas Goaziou
Hello,
Scott Randby writes:
> I had a file with the following structure:
>
> #+OPTIONS: tags:nil
> * Grades
> ** Student :studenttag:
> :PROPERTIES:
> :EXPORT_FILE_NAME: Exported-Grades/studenttag
> :END:
> *** Totals :totals:
> Content
>
> Whenever I exported the entire file, no tags were e
Mark Edgington writes:
> Nicolas Goaziou gmail.com> writes:
>>
>> You can remove offending packages with `org-export-before-parsing-hook'
>> if you don't want them to be used during the export process.
>>
>
> Yes, but I need the package which is buggy. If I were to remove it, I
> couldn't pre
On 12/11/2013 10:24 AM, Nicolas Goaziou wrote:
> Hello,
>
> Scott Randby writes:
>
>> On 12/11/2013 10:04 AM, Nick Dokos wrote:
>>> Scott Randby writes:
>>>
>>>
I tried C-c C-c on the #+OPTIONS line and I tried killing the file and
opening it up again---neither works. I looked in the
I had a file with the following structure:
#+OPTIONS: tags:nil
* Grades
** Student :studenttag:
:PROPERTIES:
:EXPORT_FILE_NAME: Exported-Grades/studenttag
:END:
*** Totals :totals:
Content
Whenever I exported the entire file, no tags were exported (what I
want). However, whenever I exported t
Nicolas Goaziou gmail.com> writes:
>
> You can remove offending packages with `org-export-before-parsing-hook'
> if you don't want them to be used during the export process.
>
Yes, but I need the package which is buggy. If I were to remove it, I
couldn't preview latex fragements or export a PD
Hello,
Mark Edgington writes:
> Nonetheless, I do think that to make it easier for people to share
> org-mode files that use packages that are in some way buggy, having a
> way to specify #+LaTeX_HEADER options which only apply when generating
> preview images would be useful, so that workaround
Hello,
Scott Randby writes:
> On 12/11/2013 10:04 AM, Nick Dokos wrote:
>> Scott Randby writes:
>>
>>
>>> I tried C-c C-c on the #+OPTIONS line and I tried killing the file and
>>> opening it up again---neither works. I looked in the manual (section
>>> 12.3) and noticed that html5-fancy: is
James Harkins writes:
> On Wednesday, December 11, 2013 10:54:37 PM HKT, James Harkins wrote:
>> I have also tried
>>
>> #+ATTR_LaTeX: :float multicolumn :options [htb]
>>
>> per documentation at [1]. I still get \begin{figure}, not
> \begin{figure*}.
>
> Forgot the footnote: it's
> http://orgmo
On 12/11/2013 10:04 AM, Nick Dokos wrote:
> Scott Randby writes:
>
>
>> I tried C-c C-c on the #+OPTIONS line and I tried killing the file and
>> opening it up again---neither works. I looked in the manual (section
>> 12.3) and noticed that html5-fancy: is not on the list of arguments
>> recogni
Ok, I dug into the problem a little deeper, and it seems that it
really can be considered a bug in the circuitikz code -- in order to
remedy it for the present time, the circuitikz.code.tex file from this
package should be modified, and the line:
\ctikzset{color/.initial=black}
must be removed /
Nicolas Goaziou gmail.com> writes:
> I could be a suggested feature that didn't make it into code base.
> Anyway, you can use:
>
> #+begin_figure*
> ...
> #+end_figure*
>
> instead.
OK, relief. That did it.
Should #+begin_something* be documented under "special blocks" here?
http://org
Scott Randby writes:
> I tried C-c C-c on the #+OPTIONS line and I tried killing the file and
> opening it up again---neither works. I looked in the manual (section
> 12.3) and noticed that html5-fancy: is not on the list of arguments
> recognized by the #+OPTIONS keyword.
It's documented in se
On Wednesday, December 11, 2013 10:54:37 PM HKT, James Harkins wrote:
I have also tried
#+ATTR_LaTeX: :float multicolumn :options [htb]
per documentation at [1]. I still get \begin{figure}, not
\begin{figure*}.
Forgot the footnote: it's
http://orgmode.org/manual/LaTeX-specific-attributes.ht
Hello,
James Harkins writes:
> A few months ago, I wrote an academic paper with code examples, using the
> listings environment like so:
>
> #+ATTR_LaTeX: :starred t :options [htb]
> #+BEGIN_figure
> #+CAPTION: Simple sequencer, implementing the musical flow from Figure
> [[basicseq_graph]].
>
A few months ago, I wrote an academic paper with code examples, using the
listings environment like so:
#+ATTR_LaTeX: :starred t :options [htb]
#+BEGIN_figure
#+CAPTION: Simple sequencer, implementing the musical flow from Figure
[[basicseq_graph]].
#+NAME: basicseq
#+BEGIN_SRC {} -i
TLSequenc
Hello,
James Harkins writes:
> Is "ulem" one of the LaTeX export default packages?
Yes, it is. See `org-latex-default-packages-alist'.
Regards,
--
Nicolas Goaziou
org-latex-text-markup-alist is a variable defined in `ox-latex.el'.
Its value is ((bold . "\\textbf{%s}")
(code . verb)
(italic . "\\emph{%s}")
(strike-through . "\\sout{%s}")
(underline . "\\uline{%s}")
(verbatim . protectedtexttt))
underline . "\\uline{%s}" -- According to [1],
~~
\uline
U
On 12/11/2013 07:58 AM, Nick Dokos wrote:
> Scott Randby writes:
>
>> On 12/09/2013 02:53 PM, Nick Dokos wrote:
>>> Catonano writes:
>>>
I' m trying to follow the examples at this page
http://orgmode.org/manual/HTML-doctypes.html#HTML-doctypes
to transform
On Wed, Dec 11, 2013 at 3:46 AM, Eric S Fraga wrote:
> Mark Edgington writes:
>
> [...]
>
>> Is there any way that I can make it so that without a lot of "hacks" I
>> can make the previews appear as white-on-black, and the PDFs print
>> black on white? Would something need to change with how org
Scott Randby writes:
> On 12/09/2013 02:53 PM, Nick Dokos wrote:
>> Catonano writes:
>>
>>> I' m trying to follow the examples at this page
>>>
>>> http://orgmode.org/manual/HTML-doctypes.html#HTML-doctypes
>>>
>>> to transform
>>>
>>> #+BEGIN_ASIDE
>>> Lorem ipsum
>>> #+END_ASID
What is the best solution for the following scenario?
In my org file, I use an R source code to generate a table. I would like
to additionally specify notes to this table, and use threeparttable in
latex export to be able to specify notes below the table.
Can somebody point me to an example on h
Nick,
2013/12/9 Nick Dokos
> Catonano writes:
>
> Try
>
> --8<---cut here---start->8---
> #+HTML_DOCTYPE: html5
> #+OPTIONS: html5-fancy:t
>
> #+BEGIN_ASIDE
> Lorem Ipsum
> #+END_ASIDE
> --8<---cut here---end--->8---
>
I'
Nicolas,
thanks for your hint. I have a couple of observations.
2013/12/9 Nicolas Goaziou
> Hello,
>
> Catonano writes:
>
> > I tried to both include the directive in the "group" in the project
> > definition AND using
> >
> > #+HTML_HTML5_FANCY: t
> >
> > in level-0.org
>
> There is no such
Mark Edgington writes:
[...]
> Is there any way that I can make it so that without a lot of "hacks" I
> can make the previews appear as white-on-black, and the PDFs print
> black on white? Would something need to change with how org-mode
> handles previewing to make this possible?
I have the f
Christian Moe wrote:
> Sebastien Vauban writes:
>
>> Fixed with:
>>
>> --8<---cut here---start->8---
>> ;; accented characters on graphics
>> (setq org-babel-R-command
>> (concat org-babel-R-command " --encoding=UTF-8")))
>> --8<---c
Hello,
Aaron Ecay writes:
> I have encountered two related misbehaviors in the parser/exporter.
>
> The first manifests if you type the following line into an org-mode
> buffer and execute M-: (org-element-context) with point on the ‘f’; the
> result is a subscript object, whereas I would have e
41 matches
Mail list logo
