>
> Try this:
>
> #+BEGIN_SRC org :exports results :results replace :wrap example
> ,#+STARTUP: align
> ,* COMMENT Local Variables
> ,# Local Variables:
> ,# fill-column: 90
> ,# End:
> #+END_SRC
>
> and be sure to (require 'ob-org)
>
> HTH,
>
That definitely helped. Thanks!
--
--
Kaushal Modi
How about ":comments link" header arg?
https://org-babel.readthedocs.io/en/latest/header-args/#comments
-k.
On 2016-05-03 at 17:33, Ethan Ligon wrote:
> When one exports from org to, say, latex the resulting *.tex file
> includes a comment at the top indicating the time of creation. This is
On Tue, 3 May 2016, Kaushal Modi wrote:
Hi,
I would like to add the Local Variables comment block to my org file (for
documentation purpose) without affecting the actual local variable values
in that buffer.
Here is a minimum working example:
#+BEGIN_SRC org
,#+STARTUP: align
,* COMMENT Local
On Tue, May 3, 2016 at 3:58 PM, John Hendy wrote:
> On Tue, May 3, 2016 at 2:55 PM, William Denton wrote:
>> I updated my packages today and now Org documents with R source blocks are
>> failing when I try to use a running R session.
Submitted a github issue on this:
- https://github.com/emacs-e
When one exports from org to, say, latex the resulting *.tex file includes
a comment at the top indicating the time of creation. This is useful in
part because it lets the user know that the *.tex file isn't the original
source.
The same isn't true of tangled code from a source block, and
On Tue, May 3, 2016 at 2:55 PM, William Denton wrote:
> I updated my packages today and now Org documents with R source blocks are
> failing when I try to use a running R session.
>
> If you start R and leave that session open, then run this in an Org doc, it
> will fail (though it will success wi
Nick Dokos writes:
> The OP should try moving the #+ATTR_LATEX line to just before the table.
> I'm not sure, but I don't think it applies long distance.
>
I checked, so now I'm sure :-) - see the org-syntax document on Worg,
section "Affiliated Keywords"
(http://orgmode.org/worg/dev/org-syntax
I updated my packages today and now Org documents with R source blocks are
failing when I try to use a running R session.
If you start R and leave that session open, then run this in an Org doc, it will
fail (though it will success without the :session parameter):
#+BEGIN_SRC R :session :resu
Hi,
I would like to add the Local Variables comment block to my org file (for
documentation purpose) without affecting the actual local variable values
in that buffer.
Here is a minimum working example:
#+BEGIN_SRC org
,#+STARTUP: align
,* COMMENT Local Variables
,# Local Variables:
,# fill-colu
Hello,
Chunyang Xu writes:
> Sometimes I turn on lisp debugger with M-x toggle-debug-on-error for
> some reason, then aborting org-capture with 'q' or 'C-g' enters the
> debugger, which is annoying. I think `user-error' is better than `error'
> in this case.
>
> From 9d950e96c48b8e1a0dad779cdf34
Hello,
Rainer M Krug writes:
> attached please find a patch which adds additional output file types for
> plantuml.
Applied. Thank you.
Could you provide an entry for ORG-NEWS?
Regards,
--
Nicolas Goaziou
Thanks Michael!
That solution works great! I followed the discussion that followed in that
thread and have adopted the following solution in my config for now.
# http://thread.gmane.org/gmane.emacs.orgmode/106497/focus=106683
| / | <#> || |
| | 1n | 2y | 3y |
# Exports to ASCII as
# 2y
Eric S Fraga writes:
> On Tuesday, 3 May 2016 at 14:04, vendo.li...@libero.it wrote:
>> Hello Nick,
>>
>> Thank you for fixing the <10> character-width problem with the 2nd
>> column of the table in Org-mode problem, your solution worked. Now the
>> table is much more legible, within Emacs' redu
I have some capture templates that supply both a deadline and a
regular date. This is because I want the days-in-advance notice of
deadlines when I view in my agenda, but deadlines are not exported
to ICAL so I need a regular date as well. However, these two are
always the same value. Any sugge
On Tuesday, 3 May 2016 at 14:04, vendo.li...@libero.it wrote:
> Hello Nick,
>
> Thank you for fixing the <10> character-width problem with the 2nd
> column of the table in Org-mode problem, your solution worked. Now the
> table is much more legible, within Emacs' reduced window.
>
> Unfortunately
Hello Nick,
Thank you for fixing the <10> character-width problem with the 2nd column of
the table in Org-mode problem, your solution worked. Now the table is much more
legible, within Emacs' reduced window.
Unfortunately the ultimate pdf if still giving problems. The table is too wide
and the
Sharon Kimble writes:
> Rainer M Krug writes:
>
>> Hi
>>
>> I have a DESCRIPTION file, in which I store the version of the document,
>> which I extract with the following code:
>>
>> src_sh{sed -n '/^Version: /s///p' ./DESCRIPTION}
>>
>
> Have you looked at the latex package 'mversion'? I use it
Eric S Fraga writes:
> On Monday, 2 May 2016 at 13:41, Rainer M Krug wrote:
>
> [...]
>
>> Is there a way, that I can have this dynamically in the Title of the
>> document, or in a footer after LaTeX export (using fancyhdr)?
>
> Maybe something along these lines:
>
> @@latex:\rfoot{@@ Version
Julien Cubizolles writes:
> John Kitchin writes:
>
>> I found a (save-buffer) in the bibtex entry clean functions and took
>> that out. I think it solves this problem.
>
> It's working fine now, thanks.
Actually it seems to be broken again:
--8<---cut here---start--
19 matches
Mail list logo
