Mike Gauland schrieb:
>I've been using the :wrap parameter extensively, to give me control
>over the
>formatting of results from code blocks. For files with many such
>blocks, it
>makes sense to specify the formatting at the file level. This works
>well, unless
>I want a particular block to be
Hi,
suvayu ali writes:
> Hi Puneeth,
>
> On Mon, May 21, 2012 at 10:57 AM, Puneeth Chaganti
> wrote:
>> Actually, embedding code blocks in the README does work[1][2]. You
>> need to use all upper case keywords, i.e., BEGIN_SRC or BEGIN_EXAMPLE
>> instead of begin_src or begin_example.
>>
>> [
Note: Resend to the list; I did send this mail to bastien alone, not the
list - mea culpa.
Hi,
Bastien writes:
> Hi Rainer,
>
> Rainer M Krug writes:
>
>> I would like to use a README.org file on github, and also include code
>> blocks in the README.org - is this possible?
>
> No.
It depend
Eric Schulte writes:
>>
>> But I'm often bitten by the distinction between export and tangling --
>> :padline, :shebang come to mind, where I expected org-babel to honour
>> the setting in both cases.
>>
>
> Could you describe a use case where these options would be used for
> exporting and would
Nick Dokos schrieb:
>Tom Regner wrote:
>
>> Hi,
>>
>> Panruo Wu writes:
>>
>> > Dear list,
>> >
>> >
>> > #+begin_src sh=C2=A0
>> > for np in {1..32}
>> > do
>> > =C2=A0 =C2=A0 echo $np
>&g
Hi,
Panruo Wu writes:
> Dear list,
>
>
> #+begin_src sh
> for np in {1..32}
> do
> echo $np
> done
> #+end_src
>
> when executing, the output only shows
> {1..32}
> which is clearly not I want..
>
> After some investigation, I found that orgmode
> uses "sh" that cannot understand the for lo
Hi Tassilo,
Tassilo Horn writes:
[...]
>
> But I think a global all-TODO widget is of no great use anyway (there
> are simply too many). I'd very much like to have a "Today" widget that
> shows every item of today (normal timestamps, SCHEDULED, and DEADLINE).
>
With the Calendar integration I u
Tom Regner writes:
> Hi Sven,
>
> "Sven Bretfeld" writes:
>
>>
>> Thank you very much for MobileOrg 0.8. It has improved very much since
>> the last update. Really good work.
>
> I second that - it's an awesome release.
>
>> 1. Calend
Hi Sven,
"Sven Bretfeld" writes:
>
> Thank you very much for MobileOrg 0.8. It has improved very much since
> the last update. Really good work.
I second that - it's an awesome release.
> 1. Calendar Sync doesn't seem to work on my device. I chose one of my
>GoogleCalendars to sync to. But
Wow - this is /fast/ development :-); now I'm glad my son kept me awake
this night, so that I could check my mails sooner than I normaly would have...
Eric Schulte writes:
> Tom Regner writes:
>
>> Eric Schulte writes:
>>
>>> I'd rather not change t
Eric Schulte writes:
> I'd rather not change the default silently in this way.
I understand that.
>
> Could you provide a minimal example of the difference you describe? I
> just tried viewing the expanded form of the following code block and saw
> no difference between :noweb-ref and normal #+n
Tom Regner writes:
> From aea3adc952de33aa9acad94fbd9baa717b7b1a1e Mon Sep 17 00:00:00 2001
> From: Tom Regner
> Rcpt To: emacs-orgmode@gnu.org
> Date: Mon, 23 Jan 2012 12:39:52 +0100
> Subject: [PATCH] ob.el Adhere to current :padline header during noweb
> dereferencing.
>From aea3adc952de33aa9acad94fbd9baa717b7b1a1e Mon Sep 17 00:00:00 2001
From: Tom Regner
Rcpt To: emacs-orgmode@gnu.org
Date: Mon, 23 Jan 2012 12:39:52 +0100
Subject: [PATCH] ob.el Adhere to current :padline header during noweb
dereferencing.
At the moment using the :noweb-ref: prope
13 matches
Mail list logo
