Clément Pit--Claudel writes:
Hi Clément,
> Adam, what do you think of my earlier suggestion (displaying the
> brackets when the pointer is on them, hiding them otherwise? (In the
> style of prettify-symbols-mode with unprettify-symbol-at-point)
Sorry, I missed that in the thread. That sounds l
On 2016-10-07 22:38, Adam Porter wrote:
> I understand the motivation for making this change, but I respectfully
> request that this be made configurable. I much prefer the "clean" links
> without visible brackets, and adding them would seem like a regression
> to me. I'm guessing that many curre
Nicolas Goaziou writes:
> I'd like to make the following change to bracket links display (i.e.,
> when `org-highlight-links' contains `bracket', which is the default).
>
> Basically, I want to leave a visible pair of brackets around the link,
Hi Nicolas,
I understand the motivation for making t
Sharon Kimble writes:
> In an org-mode document which is then converted I'm using the latex
> glossary package, which shows my glossary items as '\gls{foo}'. I'm now
> getting to the stage of having a paper copy of the latexed PDF but am
> finding that the glossary items in the main text do not s
Philip Hudson writes:
> On 7 October 2016 at 23:14, Nick Dokos wrote:
>> Philip Hudson writes:
>>
>>> Question: How do I specify how an Org element appears in the
>>> corresponding exported PDF? Specifically the typeface (font).
>>>
>>
>> E.g.
>>
>> #+LATEX_HEADER: \usepackage{palatino}
>
I sh
On 7 October 2016 at 23:14, Nick Dokos wrote:
> Philip Hudson writes:
>
>> Question: How do I specify how an Org element appears in the
>> corresponding exported PDF? Specifically the typeface (font).
>>
>
> E.g.
>
> #+LATEX_HEADER: \usepackage{palatino}
Right, that's one of the packages I found
Hello,
David Talmage writes:
> What does the parser do with a drawer? How is that different from a
> block? It seems that one can put text that looks like a headline in a
> drawer and it won't be interpreted as a headline. Why couldn't blocks be
> parsed the same way?
Drawers behave in exact
Philip Hudson writes:
> Question: How do I specify how an Org element appears in the
> corresponding exported PDF? Specifically the typeface (font).
>
E.g.
#+LATEX_HEADER: \usepackage{palatino}
> Meta-question: Where might this question be answered that I haven't
> looked? I haven't managed to
Question: How do I specify how an Org element appears in the
corresponding exported PDF? Specifically the typeface (font).
Meta-question: Where might this question be answered that I haven't
looked? I haven't managed to find it in the manual or on Worg using a
fairly exhaustive variety of search t
On 7 October 2016 at 14:31, Aaron Ecay wrote:
> Org isn’t currently set up to handle compiling Latex documents on a
> remote machine. I suppose the relevant function should detect such an
> attempt, and immediately error out. Over the longer term, remote
> compilation support could be added.
T
Nicolas Goaziou writes:
> Hello,
>
> Nick Dokos writes:
>
>> Is the "* on column 0 is a headline" convention a consequence of the
>> dependence on outline.el? Or is it just historical baggage? I cannot
>> remember the grammar rules, but I'm wondering if the parser could be
>> made to say "not a
Hello,
I'm using
Org-mode version 8.3.4 (release_8.3.4-1034-gadcaf9 @
/home/hs/.emacs.d/git/org-mode/lisp/)
on emacs 25.1/25.2.
With this version (also newer versions) I have a problem with loading files.
I normally switch all files with extensions ".org" and also ".txt" to
org-mode, even if th
On Fri, Oct 7, 2016 at 2:09 AM, Nicolas Goaziou
wrote:
> Hello,
>
> Nick Dokos writes:
>
> > Is the "* on column 0 is a headline" convention a consequence of the
> > dependence on outline.el? Or is it just historical baggage? I cannot
> > remember the grammar rules, but I'm wondering if the pars
Hi Phil,
Org isn’t currently set up to handle compiling Latex documents on a
remote machine. I suppose the relevant function should detect such an
attempt, and immediately error out. Over the longer term, remote
compilation support could be added.
--
Aaron Ecay
Dear all,
I know org-mode has an #+INCLUDE directive for header and initialization
code. I was wondering whether this works also for creating contents
below headlines. E.g.
#+BEGIN_SRC org-mode
* Chapter 1
#+INCLUDE: chapter-1-with-two-stars-headlines.org
* Chapter 2
#+INCLUDE: chapter-2-wi
Greetings.
I think I have discussed multiline Org macros here before. But I bumped
into the issue again.
One of the most useful properties of LaTeX is \newcommand, which allows
you to reuse document structures. I really, _really_ miss this feature
in Org. Org has #+MACRO, but it is limited to a
16 matches
Mail list logo
