/s/indention/indentation/
And sorry for the earlier top-posting and generally awful formatting. For
some odd reason I subscribed using Gmail, and that is giving me some grieve.
On Sat, Jan 14, 2017 at 11:11 PM, Jonas Bernoulli
wrote:
> On Sat, Jan 14, 2017 at 6:52 PM,
On Sat, Jan 14, 2017 at 6:52 PM, Nicolas Goaziou
wrote:
>
>
> Could you show an ECM?
>
I was going to, but:
Turns out:
1. Whether -i is used doesn't matter here.
2. The reason these blocks are not intended the same way is that
SRC => @example or @lisp
EXAMPLE =>
On Sat, Dec 31, 2016 at 3:40 PM, Nicolas Goaziou
wrote:
Besides, using `org-export-filter-final-output-functions' seems easier
> than your set up.
>
This approach works too. The following code produces exactly the same
result as what I posted earlier:
(defun
I'll get back to you in a few days.
On Sat, Jan 14, 2017 at 6:52 PM, Nicolas Goaziou
wrote:
> Jonas Bernoulli writes:
>
> > I did notice myself that the two-space indentation for blocks that are
> part
> > of a list element are reserved and
Jonas Bernoulli writes:
> I did notice myself that the two-space indentation for blocks that are part
> of a list element are reserved and also that one can do what you are
> suggesting here to keep the code-block as part of the list item while at
> the same time not
I did notice myself that the two-space indentation for blocks that are part
of a list element are reserved and also that one can do what you are
suggesting here to keep the code-block as part of the list item while at
the same time not get those two extra spaces. (By the way, I don't like
that
Hello,
Jonas Bernoulli writes:
> This seemed promising at first but let to all kinds of strange behavior.
> Code-blocks that are part of a list item turned out to particularly
> painful, as here "Finally, you can use ā-iā to preserve the indentation of
> a specific
Thanks for the tip and sorry for the late response.
This seemed promising at first but let to all kinds of strange behavior.
Code-blocks that are part of a list item turned out to particularly
painful, as here "Finally, you can use ā-iā to preserve the indentation of
a specific code block" means
On Tue, 3 Jan 2017, Jonas Bernoulli wrote:
So here's the ECM:
* Node
#+BEGIN_SRC emacs-lisp
(progn (progn foo
bar))
#+END_SRC
(info "(org) Literal examples") suggests this
#+BEGIN_SRC emacs-lisp -i
(progn (progn foo
bar))
#+END_SRC
(16 spaces before bar)
which gives
So here's the ECM:
* Node
#+BEGIN_SRC emacs-lisp
(progn (progn foo
bar))
#+END_SRC
It doesn't matter whether `bar))` is preceded, in the org file, by two tabs
or 16 spaces. In both cases it will be preceded by one tab followed by 7
spaces in the texi file; and by 5 spaces followed by one tab
Aloha Kaushal Modi,
Kaushal Modi writes:
> On Tue, Jan 3, 2017 at 8:53 AM Jonas Bernoulli
> wrote:
>
>> On Sat, Dec 31, 2016 at 3:40 PM, Nicolas Goaziou
>> wrote:
>>
>>
>> Could you provide an ECM?
>>
>>
>> What's an ECM?
>>
>
> I also do not
Kaushal Modi writes:
> On Tue, Jan 3, 2017 at 8:53 AM Jonas Bernoulli
> wrote:
>
> On Sat, Dec 31, 2016 at 3:40 PM, Nicolas Goaziou
> wrote:
>
> Could you provide an ECM?
>
> What's an ECM?
>
> I also
On Tue, Jan 3, 2017 at 8:53 AM Jonas Bernoulli
wrote:
> On Sat, Dec 31, 2016 at 3:40 PM, Nicolas Goaziou
> wrote:
>
>
> Could you provide an ECM?
>
>
> What's an ECM?
>
I also do not know what ECM means though it has been mentioned in this
Hi
So Gmail decided that your reply was spam...
On Sat, Dec 31, 2016 at 3:40 PM, Nicolas Goaziou
wrote:
>
> Could you provide an ECM?
>
What's an ECM?
>
> Besides, using `org-export-filter-final-output-functions' seems easier
> than your set up.
>
I'll try that,
Hello,
Jonas Bernoulli writes:
> I need to ensure that the texinfo exporter generates texi files that use
> space for indentation even when the global value of indent-tabs-mode is t.
> If tabs are used, then code blocks end up being intended wrong in the final
> info
15 matches
Mail list logo