Achim Gratz writes:
> Oleh writes:
>> #+RESULTS:
>> :
>> : 3
>
> Well, that would still be an empty line too many. But aside from that,
> what I'm actually getting with a recent Emacs and inf-ruby is:
>
> #+RESULTS:
> :
> : irb(main):003:0> irb(main):004:0> irb(main):005:0> 3
>
> So either comint
Hi Vikas,
Vikas Rawal writes:
> How can I use roman numerals in ordered lists in an org document? I
> need them in html and latex exports.
Try this document
#+LATEX_HEADER: \renewcommand{\theenumi}{\Roman{enumi}}
#+HTML_HEAD: ol {list-style-type: upper-roman;}
1. en
2. to
3. tre
There's also
Hi,
Rasmus writes:
> This patch allows INCLUDE to have intuitive links as resolved by
> `org-link'-search'. A couple of examples:
>
> #+INCLUDE: file.org::#custom_id :noheadline :lines "3-"
> #+INCLUDE: file.org::*headline :lines "-10"
>
> :noheading tries to get rid of the first headline, and
Hi again list.
There was a discussion many years back about a formal description of
Org files [1]. In some way that might be achieved now in org-elements,
but that still is heavily bound to elisp.
So my question is; have there been more discussions of constructing
such a formal grammar? Maybe in
Hello,
Gustav Wikström writes:
> There was a discussion many years back about a formal description of
> Org files [1]. In some way that might be achieved now in org-elements,
> but that still is heavily bound to elisp.
>
> So my question is; have there been more discussions of constructing
> suc
Hello,
Rasmus writes:
> I'm happy to finally be able to send an updated version of this patch
> that touches most backends in lisp/, but not the manual. I have been
> moving over the summer etc.
Thanks for that work. Some comments follow.
> You now specify unnumbered headlines with propertie
Wow. Thanks for your reply. I will stop googling and worg-ing for a solution. I
will rather dig into your suggestion. As I understood, there is some hackery
involved here .. :)
Thanks again.
~Alban Bernard
On Saturday, September 20, 2014 2:08 PM, Nicolas Goaziou
wrote:
Hello,
alban bernar
On Thu, Sep 11, 2014 at 5:05 PM, Adriaan Sticker
wrote:
> I was wondering if it's somehow possible to give named org src buffer the
> name they were give in their #+NAME tag? Now there are just called something
> like:
> *Org Src test.org[ R ]*
>
> But if you have multiple org-src buffers opened a
Hello,
Rasmus writes:
> Rasmus writes:
>
>> This patch allows INCLUDE to have intuitive links as resolved by
>> `org-link'-search'. A couple of examples:
Thanks for the patch. Some comments follow.
>> #+INCLUDE: file.org::#custom_id :noheadline :lines "3-"
Is it `:only-contents' or `:no-hea
On Tue, Sep 16, 2014 at 8:01 AM, Fabrice Popineau
wrote:
> Curious to hear about other reports.
My primary document has 8051 lines in it so I set max-specpdl-size to
2600 "just in case".
That was before I realized that in *my* case, all the bugs were
introduced by me into
the document itself.
I
On Wed, Sep 17, 2014 at 2:37 AM, Thorsten Jolitz wrote:
> Wasn't there even a library to support this kind of workflow?
> I would appreciate any hint that updates me on this topic.
Did your research yield any further results?
--
Grant Rettke
g...@wisdomandwonder.com | http://www.wisdomandwonder
On Thu, Sep 18, 2014 at 5:27 AM, Thorsten Jolitz wrote:
> Marcin Antczak writes:
>
>> As in topic.
>>
>> I think that if both parameters 'file' and 'target-file' are set and
>> target-file' exists, 'org-babel-tangle-file' should tangle only if
>> target-file' is older.
>
> I think the Org based E
Grant Rettke writes:
> On Wed, Sep 17, 2014 at 2:37 AM, Thorsten Jolitz wrote:
>> Wasn't there even a library to support this kind of workflow?
>> I would appreciate any hint that updates me on this topic.
>
> Did your research yield any further results?
Not really, but I vaguely remember that
Hi,
Thanks for the comments. Let's give it another try, shand't we.
Nicolas Goaziou writes:
>> I introduce a new function `org-export-get-headline-id` which returns
>> the first non-nil from the following list. There's a caveat:
>> CUSTOM_ID is ensured to be unique! Did I open the famous can
Hi,
A short comment.
Nicolas Goaziou writes:
>> + (org-export--prepare-file-contents file location
>> only-contents lines
>
> Couldn't location, only-contents and lines be merged into a single
> argument? At the moment, you are either short-circuiting or breaking
> gua
Well, I ussually just try to live with this limitation. :)
I try to C-c ' in and out src block whenever possible so my my list with
buffer names doesnt get to cluttered.
Im also thinking about investigating the usefullness of polymode (
https://github.com/vitoshka/polymode)
So I dont have to go to
On Sun, Sep 21, 2014 at 10:07 AM, Adriaan Sticker
wrote:
> Im also thinking about investigating the usefullness of polymode
> (https://github.com/vitoshka/polymode)
> So I dont have to go to a different buffer all the time. Do you have any
> experience with this?
No and it is on my TODO list beca
Hi,
Here's a simple CSS workaround that might or might not work well for
you, and won't work for non-HTML backends, but at least requires minimal
hacking:
Wrap the sentence in a DIV element and define a class for it to force
child paragraphs to display as inline instead of blocks.
You can set
I will test this workaround pronto. For other backends, that's not a problem as
I render pdf from html through phantomjs and I don't use neither latex nor odt
for the moment.
Big thanks to you both.
~Alban Bernard.
On Sunday, September 21, 2014 8:07 PM, Christian Moe
wrote:
Hi,
Here's a
Rasmus writes:
> Thanks for the comments. Let's give it another try, shand't we.
There we go.
> Okay, I returned to my first hack (which never made it to this list).
> Basically, I ID everything. Unnumbered sections get the id
> "unnumbered-sec-COUNTER" and numbered sections get the id
> "sec
Rasmus writes:
>> You cannot enforce `org-mode' as the current major mode since you can
>> include other file types.
>
> But then I can't use org-element-at-point:
>
> (with-temp-buffer
> (text-mode) (insert "* test\nmy txt") (goto-char (point-min))
> (org-element-at-point))
>
> (with-temp-buf
Hello,
Nicolas Goaziou writes:
> Brady Trainor writes:
>
>> And I did have a decent export to LaTeX resume from org, but after
>> discovering moderncv, I've switched, though I will be curious to read
>> others' methods of org-to-moderncv export.
>
> One option could be to define a specialized
Hi Nicolas,
Thanks for the comments.
Nicolas Goaziou writes:
>> Okay, I returned to my first hack (which never made it to this list).
>> Basically, I ID everything. Unnumbered sections get the id
>> "unnumbered-sec-COUNTER" and numbered sections get the id
>> "sec-COUNTER".
>>
>> Perhaps you w
To followup on this, I believe there is either a bug or an inconsistency
in the export engine with regards to getting the parameters of a
src-block. Below, I show why it appears there is a bug.
* Bug report for org-mode
Here is a named table
#+tblname: tbl-data
| x | y |
|---+---|
| 1 | 1 |
| 2 |
I did some more digging on the missing :parameters during export, and it
seems that the src block itself is different during export than in the
buffer. Below illustrates what I mean. In the buffer, if I look at the
contents of the code block using output from org-element-at-point, it
looks as I ex
I am making heavy use of latex strikeout for a report I'm preparing in org
mode. I defined a macro for the necessary latex snippet, but the argument
gets truncated on export.
MWE:
* Section
{{{stk(The argument for this macro is several lines long. It seems
that after a certain length, the mac
Aloha Jacob,
Jacob Gerlach writes:
> I am making heavy use of latex strikeout for a report I'm preparing in org
> mode. I defined a macro for the necessary latex snippet, but the argument
> gets truncated on export.
>
> MWE:
>
> * Section
> {{{stk(The argument for this macro is several line
Ah, of course. Right under my nose, but since I "knew" I only had one
argument, I didn't even think about it.
Thanks for the quick reply.
On Sun, Sep 21, 2014 at 9:40 PM, Thomas S. Dye wrote:
> Aloha Jacob,
>
> Jacob Gerlach writes:
>
> > I am making heavy use of latex strikeout for a report I
After writing a detailed report in org-mode and submitting it via
latex/pdf, I've found out that for the next version of the report, I am
required to use "track changes" in MS Word.
I thought my best way to approximate this is to submit two versions: one
with removed text in strikeout and new text
John Kitchin andrew.cmu.edu> writes:
>
> I did some more digging on the missing :parameters during export, and it
> seems that the src block itself is different during export than in the
> buffer. Below illustrates what I mean. In the buffer, if I look at the
> contents of the code block using
Hi John,
Look at the functions ‘org-babel-exp-src-block’ which calls
‘org-babel-exp-do-export’, which calls ‘org-babel-exp-code’. The tl;dr
version is that indeed the babel export machinery does change the code
block in substantial ways, including the removal of parts of it.
This plays merry hel
Aloha Jacob,
Jacob Gerlach writes:
> After writing a detailed report in org-mode and submitting it via
> latex/pdf, I've found out that for the next version of the report, I am
> required to use "track changes" in MS Word.
If this means you are required to submit a pdf file that looks like it
i
32 matches
Mail list logo
