Hi Richard,
2014ko abuztuak 20an, Richard Lawrence-ek idatzi zuen:
>
> Hi everyone,
>
> I recently pulled from master and noticed that an option in the LaTeX
> export backend that I rely on had gotten lost in the shuffle. (I didn't
> check the history, but I believe it must have been removed ac
Nicolas Goaziou writes:
Hello,
> You may want to read my answer again. There is no "write this, write
> that" in it. I'm pointing out what is missing or flawed and _suggesting_
> alternative approaches.
I appreciate your comments and input, but unfortunately I gave up on the
original idea becau
Hi everyone,
I recently pulled from master and noticed that an option in the LaTeX
export backend that I rely on had gotten lost in the shuffle. (I didn't
check the history, but I believe it must have been removed accidentally,
since the code that checks this option is still there.) Here is a pa
Hi Grant,
2014ko abuztuak 20an, Grant Rettke-ek idatzi zuen:
>
> Good afternoon,
>
> While debugging one of my babel documents, I re-read [this]
> documentation on `:noweb-ref'.
>
> What I had wanted to do was to define a bunch of source blocks and then
> at the end of the heading to tangle the
Good afternoon,
While debugging one of my babel documents, I re-read [this]
documentation on `:noweb-ref'.
What I had wanted to do was to define a bunch of source blocks and then
at the end of the heading to tangle them all into a file. This was just
a natural thing to do while /in the flow/ and
Thierry Banel writes:
> You are trying to create a C++ project bigger than a few lines, in Org-mode.
> This is very close to the idea of "literate programming" from Donal Knuth.
> You may find inspiration here:
> http://orgmode.org/worg/org-contrib/babel/intro.html#literate-programming
>
> There
Nicolas Goaziou writes:
> FWIW, I think prefix conformance should go to maint.
Patch has been split and just the prefix conformance committed to maint
in b8bd2147cb.
Introduction of defcustom, some code cleanups and associated tests
committed to master in 64821bd967.
Regards,
Achim.
--
+<[Q+ M
Hi,
I have the following in a file that I export to LaTeX
#+LATEX_CLASS: mysetup
#+LATEX_HEADER: \newcommand{\RATE}{65.00}
mysetup class
(add-to-list 'org-latex-classes
'("mysetup"
"\\documentclass[11pt,letterpaper,oneside]{scrartcl}
\\usepackage{verbatim}
% \\usepackage[T1]{fonte
I've turn on Markdown exporting with (require 'ox-md). Citations aren't
being exported properly, so I'm trying to customize it. I have the
following setup:
(org-add-link-type
"textcite" (lambda (key) (org-open-file cby-references-file t nil key))
(lambda (path desc format)
(cond
((eq for
On Sun, Jul 27, 2014 at 7:27 AM, Bastien wrote:
> Hi Jacob,
>
> Jacob Gerlach writes:
>
> > Is it possible to configure the exporter to stop and throw an error
> > for a bad link?
>
> No. But what is really a "bad link"? Is it bad because it cannot be
> exported to a specific backend?
>
By ba
Thorsten Grothe writes:
> * Nick Dokos, 20.08.2014 18:34:15:
>
>> That leaves the somewhat counterintuitive case of a completely empty
>> first column which is therefore deemed special and gets stripped. This
>> could be "fixed" as a special case but instead I propose to document that
>> behaviou
* Nick Dokos, 20.08.2014 18:34:15:
That leaves the somewhat counterintuitive case of a completely empty
first column which is therefore deemed special and gets stripped. This
could be "fixed" as a special case but instead I propose to document that
behaviour in the above section, with a suggeste
when i remove recentf catch file, it's ok. thank.---Original---From: "Aaron Ecay"Date: 2014/08/13 14:19:01To: "Feng Shu";"emacs-orgmode";Subject: Re: [O] "#+begin_src R :results output drawer" doesn't work.Hi Feng,
2014ko abuztuak 9an, Feng Shu-ek idatzi zuen:
>
> #+begin_src R :results outpu
Sebastien Vauban
writes:
> Nick Dokos wrote:
>> Thorsten Jolitz writes:
>>> Thorsten Jolitz writes:
>>>
>>> As a side-remark, I did send these blocks with emptly lines between them,
>>> and when I look at my post in gmane the format looks alright, however
>>> when I open it in gnus the empty li
Nicolas Richard writes:
>> Although Org functions are of course made only for working in org-mode
>> and its a bit hard to see at first sight how this could be useful, I
>> wonder if the regexps could be made a bit more general to make
>> `org-element-at-point' work in programming modes too (most
Hi,
I would like to provide a very tiny change in the regexp matching a
beginning of table in org-table.el.
Its current value is "^\\(\\*+ \\)\\|[ \t]*|". The second part of the
regexp ("[ \t]*|") indicates that it matches any | character, following
spaces or not. This means that the "[ \t]" is u
Nick Dokos wrote:
> Thorsten Jolitz writes:
>> Thorsten Jolitz writes:
>>
>> As a side-remark, I did send these blocks with emptly lines between them,
>> and when I look at my post in gmane the format looks alright, however
>> when I open it in gnus the empty lines are gone and it looks like this
Thorsten Jolitz writes:
> Am I the only one seeing this? Bug in gnus/message mode?
I also see the problem. I suspect that it happens when Gnus fontifies
the blocks. Doing "C-u g" shows that the "source" of the message is
correct (i.e. has the newlines).
--
Nico.
> Although Org functions are of course made only for working in org-mode
> and its a bit hard to see at first sight how this could be useful, I
> wonder if the regexps could be made a bit more general to make
> `org-element-at-point' work in programming modes too (most likely this
> behaviour is ca
Thorsten Jolitz writes:
> Thorsten Jolitz writes:
>
> As a side-remark, I did send these blocks with emptly lines between them,
> and when I look at my post in gmane the format looks alright, however
> when I open it in gnus the empty lines are gone and it looks like this:
>
>> * ORG SCRATCH
>>
Thorsten Jolitz writes:
As a side-remark, I did send these blocks with emptly lines between them,
and when I look at my post in gmane the format looks alright, however
when I open it in gnus the empty lines are gone and it looks like this:
> * ORG SCRATCH
>
> #+BEGIN_QUOTE
> hallo world
> #+END_
Sharon Kimble writes:
>
> ** WAITING Anise
> CLOSED: [2014-08-20 Wed 10:29]
>
>
> And only _waiting_ shows as closed, none of these other conditions do -
>
> #+TODO: TODO DONE NEXT IN-PROGRESS NOTES FIXME WAITING
>
> ...
>
> I think that the problems all stem from my set-up, but I can't see exact
Hi List,
with point at the beginning of each of the following blocks,
`org-element-at-point' does recognize the correct type when buffer is in
org-mode and other text-modes, but not so in programming modes, e.g. the
*scratch* buffer (lisp-interaction-mode). Then only the src-block is
recognized c
Nicolas Goaziou writes:
> Hello,
>
> Nick Dokos writes:
>
>> That leaves the somewhat counterintuitive case of a completely empty
>> first column which is therefore deemed special and gets stripped. This
>> could be "fixed" as a special case but instead I propose to document that
>> behaviour in
On Wednesday, 20 Aug 2014 at 11:46, Sharon Kimble wrote:
[...]
> Hmm, if they work for you then its something in my set-up. And after
> having a play, the cookie is only changed when it is toggled [C-c C-t] to
> "Waiting" which then shows
>
> ** WAITING Anise
> CLOSED: [2014-08-20 Wed 10:29]
>
>
I have a shell function that exports my agenda to an ical file and uploads it
for Google to read; however, there seem to be a couple glaring omissions from
the ical. Here's the bash line that works over my agenda for export:
emacs --batch --user $USER --eval "(progn (org-agenda-list nil
Eric Abrahamsen writes:
> Sharon Kimble writes:
>
>> I'm trying to get cookies working with TODO items. The source document
>> is a book I'm writing and is an outline of each section and chapters so
>> that I can see what is still to be done. I'm writing it in latex but
>> doing the outline in o
Hello,
Nick Dokos writes:
> That leaves the somewhat counterintuitive case of a completely empty
> first column which is therefore deemed special and gets stripped. This
> could be "fixed" as a special case but instead I propose to document that
> behaviour in the above section, with a suggested
28 matches
Mail list logo
