Apparently I found the sequence that lead to the problem: I opened a
#+begin_src on a line and then pressed TAB on such line. This folded
the following text until a new #+end_src is found, masking whole
sections. The problem is that this is no more able to be expanded.
However, editing the text fil
Jambunathan K writes:
> For the sake of record, I haven't authorized Bastien to move the
> ox-html.el and ox-odt.el out of the ./contrib/lisp directory in to the
> main ./lisp/ directory. He didn't seek my permissions to move the file
> away from contrib/lisp in to lisp/.
1. Nicolas announced t
On 2.4.2013, at 23:54, Eric Schulte wrote:
> Gary Oberbrunner writes:
>
>> Aha -- you have to use the :var syntax on the begin_src line, not the
>> params-in-parens syntax on the name line. Your version works:
>>
>> #+name: example-block
>> #+begin_src sh :var input=""
>> echo "input is $in
Carsten
> When this code first entered the Org-mode repository, it was not in
> contrib/. The code entered in EXPERIMENTAL/. Both files where marked
> "Copyright (C) 2011-2012 FSF" and "Copyright (C) 2010-2012 FSF" from
> the first moment they entered into the repository, in agreement with
> Ja
Am 02.04.2013 23:54, schrieb Eric Schulte:
Gary Oberbrunner writes:
Aha -- you have to use the :var syntax on the begin_src line, not the
params-in-parens syntax on the name line. Your version works:
#+name: example-block
#+begin_src sh :var input=""
echo "input is $input"
#+end_src
but
Am 03.04.2013 00:25, schrieb John Hendy:
On Tue, Apr 2, 2013 at 5:16 PM, Christian Moe wrote:
Jambunathan,
If you're leaving the Org-mode community, I'd prefer to remember you
with gratitude for leaving us the excellent ODT exporter. Please stop
diminishing your legacy with this quasi-legal w
Hi,
For the record created by this mailing list thread, I would like to correct two
mistakes:
On 2.4.2013, at 10:42, Jambunathan K wrote:
>
> I have terminated my copyright assignment to Emacs (or atleast notified
> the copyright desk).
>
> For the sake of record, I haven't authorized Bastie
On Tue, Apr 2, 2013 at 5:16 PM, Christian Moe wrote:
>
> Jambunathan,
>
> If you're leaving the Org-mode community, I'd prefer to remember you
> with gratitude for leaving us the excellent ODT exporter. Please stop
> diminishing your legacy with this quasi-legal wrangling.
>
> As a user, I have gr
I'm happy to apply this patch, however please also supply a patch which
updates the corresponding documentation.
Thanks!
Aaron Ecay writes:
> * lisp/ob-exp.el (org-export-babel-evaluate): Update defcustom to
> provide 'inline-only option
> (org-babel-exp-results): Implement 'inline-only for
Aaron Ecay writes:
> Here are several patches to fix things in and around org-babel.
> They're each independent of the others (and hopefully all apply
> cleanly, without depending on other members of the series). Here's a
> little summary of each:
>
Thanks for these patches, many look like obvi
Aaron Ecay writes:
> Hi Eric,
>
> 2013ko martxoak 23an, Eric Schulte-ek idatzi zuen:
>
>> Unless you actually try :var and find it lacking in some way, I'd prefer
>> to stick with simply using :var to identify dependencies between code
>> blocks. We've seen in other places how providing multiple
Gary Oberbrunner writes:
> Aha -- you have to use the :var syntax on the begin_src line, not the
> params-in-parens syntax on the name line. Your version works:
>
> #+name: example-block
> #+begin_src sh :var input=""
> echo "input is $input"
> #+end_src
>
> but this doesn't:
>
> #+name: examp
Jambunathan,
If you're leaving the Org-mode community, I'd prefer to remember you
with gratitude for leaving us the excellent ODT exporter. Please stop
diminishing your legacy with this quasi-legal wrangling.
As a user, I have greatly appreciated both your code contributions and
your patient hel
> In my Emacs I have the following. Would that work?
> "C-c C-x C-w runs the command org-cut-special, which is an interactive
> compiled Lisp function in `org.el'.
I incidentally figured out the problem: I had rebound yank to "C-.", and
did not realize that org-yank was bound to the original yan
Aaron Ecay writes:
> * lisp/ob-core.el (org-babel-check-confirm-evaluate): remove
> (org-babel-check-evaluate),
> (org-babel-confirm-evaluate): move logic here
>
> This macro is used in only two places, and has two almost-independent
> complex logics coded into it. So, suppress the macro and m
Aaron Ecay writes:
> * lisp/ob-core.el (org-babel-execute-src-block): Simplify control flow
>
> Avoid potential duplication of org-babel-process-params call. Also
> makes the code simpler.
You may be changing semantics here. I'm not entirely certain if the
current way of dealing with the the unm
Aaron Ecay writes:
> * lisp/ob-core.el (org-babel-if-in-src-block): New macro
[…]
> +(defmacro org-babel-when-in-src-block (&rest body)
> + `(if (or (org-babel-where-is-src-block-head)
> + (org-babel-get-inline-src-block-matches))
> + (progn
> + ,@body
> + t)
> + nil)
42 147 writes:
> Hello mailing list,
>
> A source of slight irritation is killing a whole headline with C-k
> (usually to move it to another buffer), and seeing it unfold every
> single sub-headline after I yank it to its new position. This causes
> tremendous chaos sometimes, especially if there
On Tue, Apr 2, 2013 at 10:46 AM, Christian Egli wrote:
> Buddy Butterfly writes:
>
>> I still feel the lack of the support for all tj properties a
>> major drawback.
>>
>> @Christian: Did you work on something like the prefix proposal below?
>> This would be real cool as we could then just use an
Buddy Butterfly writes:
> I still feel the lack of the support for all tj properties a
> major drawback.
>
> @Christian: Did you work on something like the prefix proposal below?
> This would be real cool as we could then just use any property we would
> like.
As far as I know Yann's patches imp
Hi,
This patch enables user to applies a temporal TBLFM line where you are in.
It is useful when you switch a formula to another.
I hope you liked this.
When you have the following table,
#+TBLNAME: test2
| 1 | 2 | |
| 4 | 5 | |
| 7 | 8 | 9 |
#+TBLFM: @1$3='(+ 10 7)
Hi, Adrian,
The fine manual is not yet up to date with the new exporter, so when you're
bitten, check http://orgmode.org/worg/org-8.0.html.
The "@" html-tag quoting has been replaced with a generalized "export
snippets" syntax (currently described at
http://orgmode.org/worg/org-8.0.html#sec-8-1)
I've finally bitten the bullet and tried to get my org-mode export
working with the new export mechanisms, so far so good.
My current sticking point is with my use of #+MACRO and "@" escapes in
them -- they used to work in the old version of org-mode, in the current
one I get them quoted verbatim
Hi Christopher and Thorsten,
Thanks for your replies.
Christopher Schmidt wrote:
> Thorsten Jolitz writes:
>> maybe this is what you need (untested):
>>
>> http://www.gnu.org/software/emacs/manual/html_node/emacs/Indirect-Buffers.html
>
> No, an indirect buffer shares its parent's text propertie
Thorsten Jolitz writes:
> maybe this is what you need (untested):
>
> http://www.gnu.org/software/emacs/manual/html_node/emacs/Indirect-Buffers.html
No, an indirect buffer shares its parent's text properties.
Christopher
"Francesco Pizzolante"
writes:
> If you have 2 windows opened with the same Org buffer, when you use a
> visibility cycling command (TAB, S-TAB, etc.), it changes the visibility in
> both windows, while you would expect the visibility being changed only in the
> active windows (not in both window
Hi,
If you have 2 windows opened with the same Org buffer, when you use a
visibility cycling command (TAB, S-TAB, etc.), it changes the visibility in
both windows, while you would expect the visibility being changed only in the
active windows (not in both windows).
Is there a way to restrict the
I have terminated my copyright assignment to Emacs (or atleast notified
the copyright desk).
For the sake of record, I haven't authorized Bastien to move the
ox-html.el and ox-odt.el out of the ./contrib/lisp directory in to the
main ./lisp/ directory. He didn't seek my permissions to move the f
Adam Spiers adamspiers.org> writes:
> Sounds interesting. It would be very helpful if you could explain how it is
> different from the other synchronization possibilities out there, e.g.
>
> http://orgmode.org/worg/org-tutorials/org-google-sync.html
> https://code.google.com/p/emacs-google/
> ht
Thanks!
Yours,
Christian
Nicolas Goaziou writes:
> Christian Moe writes:
>
>>> For now, I think the patch is correct to apply. What do you think?
>>
>> Absolutely, it fixes a bug in footnote styling, and adds useful styling
>> of quotes within footnotes.
>
> Patch applied. Thank you.
>
>
> Re
30 matches
Mail list logo
