On Sun, Jul 27, 2014 at 10:08 PM, Ken Mankoff wrote:
> Hi Jacob,
>
> #+LATEX_HEADER: does work on export (when else would it work?)
>
> Agreed. If I said otherwise it was a mistake.
2) From Aaron Ecay, put your header in a #+BEGIN_SRC latex section, and
> then run a bit of lisp to export that se
Steven Arntson writes:
> Simple question, I think, but it has me stumped. I'm wondering what
> variable controls the org-agenda function that gives you upcoming
> events, a la:
>
> todo: In 2 d.: TODO Friend's Birthday
> todo: In 4 d.: TODO Rehearsal
> todo: In 4 d
Hi Jacob,
#+LATEX_HEADER: does work on export (when else would it work?)
I think I recall a space between the ":" and the LaTeX command is
needed. Do you have one?
For more ideas on how to have lengthy custom headers, see thread here:
https://lists.gnu.org/archive/html/emacs-orgmode/2014-06/msg0
Simple question, I think, but it has me stumped. I'm wondering what
variable controls the org-agenda function that gives you upcoming
events, a la:
todo: In 2 d.: TODO Friend's Birthday
todo: In 4 d.: TODO Rehearsal
todo: In 4 d.: TODO Happy Hour
todo: In
I have a lengthy command customization that I want to include in LaTeX
export. Since it must appear in the preamble,
#+BEGIN_LATEX
...
#+END_LATEX
didn't work. I had to prepend
#+LATEX_HEADER:
to each line in order to achieve my result.
I found C-h v org-format-latex-header RET:
"The document he
Hi orgers,
I wrote a little snippet below to open footnote link definition directly
with a single call.
I think it will be very useful when you have a lot of link footnote
definitions in you documents.
Since I am a newbie to lisp, any advice of improvement will be really
appreciate.
(defun open-f
Hi,
I'm having the exact same issue as this question on stackoverflow
http://stackoverflow.com/questions/18123972/emacs-org-mode-clear-non-repeated-scheduled-time-when-deadline-is-repeated
and I've copied it below.
The solution provided to the question modifies the source, which I'd like
to avoid
Rainer M Krug krugs.de> writes:
>
> Nicolas Goaziou nicolasgoaziou.fr> writes:
>
> > Hello,
> >
> > Rainer M Krug krugs.de> writes:
> >
[snip]
>
> Amended patches attached.
AFAICS, these patches are good to go. Can they be applied, please?
Chuck
Hello,
I've some functions in worg/code/elisp/davidam.el, that could be
interesting contribute to org-mode (I use davidam-org-src every
day). The functions are:
+ davidam-org-envolve-src(msg)
+ davidam-org-src(msg)
+ davidam-org-envolve-check-list()
+ davidam-org-envolve-numbered-list()
My doub
Hi,
I upload my agenda on a website, so I can access it from multiple
devices. This works nicely with the following in a cron job:
emacs --batch -l ~/.emacs.d/init.el -eval '(org-batch-store-agenda-views)' -kill
The only thing I'm missing is links to the body of the item. Does Org
currently supp
Hello,
Federico Beffa writes:
> In the end of the day the reason why I started looking into this is
> the fact that I do not find user friendly that org-mode, when filling
> a paragraph, interprets \[...\] as any inline snippet and does not
> keep it on a separate line (as recommended by the LaT
Hello,
Export blocks are blocks dedicated to export back-ends, e.g.,
"#+BEGIN_LATEX". The way they are currently parsed is flawed.
Export blocks are back-end dependent. At the moment, back-ends register
their own export block in a variable, `org-element-block-name-alist', so
the parser can know i
Hi Nicolas,
I understand that org-mode is not LaTeX and therefore the org-mode
internal representation of LaTeX should not matter to end users like
me. That's fair enough. In the end of the day the reason why I started
looking into this is the fact that I do not find user friendly that
org-mode, w
Thorsten Jolitz writes:
> Hi List,
>
> whats wrong with this :post header arg:
>
> #+header: :post (format "#+attr_latex :float :placement {c}{scale=.6}\n%s"
> *this*)
> #+begin_src emacs-lisp
> (+ 2 2)
> #+end_src
>
> When I understand
>
> ,
> | http://orgmode.org/manual/post.html
> `-
14 matches
Mail list logo