Hi Eric,
Eric S Fraga writes:
> On Wednesday, 28 Nov 2018 at 16:09, Loris Bennett wrote:
>> Hi,
>>
>> I want to specify the size of a graphic in an Beamer presentation
>> generated from my org file. The following
>>
>> #+ATTR_LATEX: :height 0.75\textheight
>>
>> works, but
>>
>>
TL;DR : your fix works, but I disagree with the absence od
documentation and default. See below :
Le mercredi 28 novembre 2018 à 15:06 +0100, Nicolas Goaziou a écrit :
> Hello,
>
> Emmanuel Charpentier writes:
>
> > Close, but no cigar :
> >
> > I used the `customize' interface to add it to
On Wednesday, 28 Nov 2018 at 15:35, Samuel Wales wrote:
> fyi only: i don't understand the examples or the relevance to pipes.
The output (or more generally the results) of one src block is passed directly
as input to another using the :post argument.
See, for instance:
#+begin_src org
Nicolas Goaziou writes:
> David Masterson writes:
>
>> * Header 1
>>
>> * Header 2
>>
>> Position the cursor on '1' and M-return will create a new header with a
>> blank line before and after it, but C-return will create a new header
>> with a blank line before, but not after it.
> I see. I
As a possible fix I implemented this
font-lock-extend-after-change-region-function:
(defun my-org-extend-region (beg end old-len)
(let ((begin-re "[\t ]*\\(#\\+BEGIN\\|begin{\\)")
(end-re "[\t ]*\\(#\\+END\\|end{\\)"))
(save-excursion
(goto-char beg)
fyi only: i don't understand the examples or the relevance to pipes.
On 11/28/18, Eric S Fraga wrote:
> On Tuesday, 27 Nov 2018 at 19:33, Samuel Wales wrote:
>> this might be the most ridiculous idea you have ever heard, but does
>> babel have a concept similar to stdio pipes? i've often wanted
Exactly what Ken said. Look at the documentation for org-latex-classes to
see the full description. You can see an example in my Emacs config:
https://github.com/zzamboni/dot-emacs/blob/master/init.org#various-exporters
(look
for the paragraph that starts with "Some customizations for the LaTeX
Hi Bill,
On 2018-11-28 at 20:42 +0100, William Denton wrote:
> Is there a way, exporting as a book, to make Org skip "part" and make
> a top-level Org headline turn into a chapter? Is there a built-in way,
> or do I need to make my own class in org-latex-classes that has the
> structure I want?
By default the LaTeX export uses the article class, and headline levels are
mapped to headings this way: top level becomes section, second level becomes
subsection, third level becomes subsubsection. That's simple and works very
well.
If the book class is used, then the top level becomes
Well, now I do have found a bug ;). It's related to the limit issue I
mentioned before. Indeed the problem with rehighlighting broken
environments and highlighting new environments also happens for basic
latex fontification when org-highlight-latex-and-related is set to
'(latex), it has nothing to
On Wed, Nov 28, 2018 at 1:08 AM Eric S Fraga wrote:
> Check out the :post option for src blocks. May be exactly what you
> want.
Thanks for sharing that!
> (lambda (start end args)
> (org-src-font-lock-fontify-block "latex" start end
Or a safer version:
(lambda (start end prop face)
(when (eq face 'org-latex-and-related)
(org-src-font-lock-fontify-block "latex" start end)
Also note that
Hi Nicolas,
I know nothing about lisp, but I think I understand enough of the structure
to propose the following changes:
In my testfile, this preserves the current behavior if no #+CAPTION is
present. However, if the #+CAPTION is not empty, the table will be
exported as float with the proper
> all fontification is lost for the entire environment and never reapplied
The problem is with the limit argument passed by the font locking
framework to org-do-latex-and-related .
Once you natively fontified the environment this limit arg became non
nil and it's in general not enough to match
On Wednesday, 28 Nov 2018 at 16:09, Loris Bennett wrote:
> Hi,
>
> I want to specify the size of a graphic in an Beamer presentation
> generated from my org file. The following
>
> #+ATTR_LATEX: :height 0.75\textheight
>
> works, but
>
> #+ATTR_LATEX: :height 0.75\beamer@frametextheight
>
> I
On Tuesday, 27 Nov 2018 at 23:08, Alan E. Davis wrote:
> Eric:
>
> I was able to access the API docs (requiring, with my Firefox, to
> accept a security exception.)
>
> https://aa.usno.navy.mil/data/docs/api.php
Very useful. Thanks. With wget, I had to add --no-check-certificate to get
Hi,
I want to specify the size of a graphic in an Beamer presentation
generated from my org file. The following
#+ATTR_LATEX: :height 0.75\textheight
works, but
#+ATTR_LATEX: :height 0.75\beamer@frametextheight
I get the error
! Undefined control sequence.
\Gin@@eheight ->0.5\beamer
Hi Nicolas, thank you for your detailed answer!
To be honest I was wrapping my head around this until late tonight when it
all suddenly made sense and I more or less concluded the same you explained
about the role of each block and was going to say that you could indeed
dismiss this request.
Hello,
Emmanuel Charpentier writes:
> Close, but no cigar :
>
> I used the `customize' interface to add it to `org-latex-default-
> packages-alist' (because the package to load is compiler-dependent),
This has nothing to do with compiler. You can add it to
`org-latex-packages-alist'.
> which
Le mercredi 28 novembre 2018 à 00:40 +0100, Nicolas Goaziou a écrit :
> emanuel.charpent...@gmail.com writes:
>
> > Le mardi 27 novembre 2018 à 21:26 +0100, Nicolas Goaziou a écrit :
> >
> > [ Snip... ]
> >
> > > What happens if you remove "org-ref.el" reference?
> >
> > Same thing.
> >
> >
Hello,
Carlos Pita writes:
> The behavior of
>
>(P) previews,
>(E) C-c ' editing and
>(F) native fontification
>
> is very inconsistent for latex:
>
> 1. $xxx$ and $$xxx$$ no (F) no (E) but (P)
I guess (E) could be added, we already do this for inline source code,
but no one
> Decoupling is not a good idea. Because it will let user define too much
> keybindings. And User can define keybinding in Emacs easily. Emacs is
> powerful for customization.
I disagree. It is against emacs philosophy.
It is one of the key features of emacs that users can redefine
keybindings if
Check out my previous email. (Because I lost the screenshot image file...)
--
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG:
Decoupling is not a good idea. Because it will let user define too much
keybindings. And User can define keybinding in Emacs easily. Emacs is
powerful for customization.
And user need convention for Org default keybindings so that when Org
users communications can know what he did. For example,
24 matches
Mail list logo
