Paul Sexton <psex...@xnet.co.nz> writes:

> Eric Schulte <schulte.eric <at> gmail.com> writes:
>> Hi, I agree with your intuition here, but I changed the default inline
>> header argument so that others would be able to use inline code blocks
>> and have the results inserted.  To regain the behavior you describe,
>> simply adjust the value of `org-babel-default-inline-header-args' as
>> follows in your .emacs file.
>> 
>> #+begin_src emacs-lisp
>>   (setf org-babel-default-inline-header-args
>>         '((:session . "none")
>>           (:results . "silent")
>>           (:exports . "results")))
>> #+end_src
>
> Thanks Eric. The 'default' behaviour I experienced where inline blocks
> were inheriting behaviour from elsewhere seems odd however.

Hi Paul, Eric,

Paul -- I do agree with you. I've had to manually delete unwanted inline
src output a few times in the last few days.

I think we did have the behaviour we want before -- replacement during
export but no modification of the buffer in interactive use. Could we
make the default behave so that it does "replace" during export and
"silent" during normal interactive evaluation? (Or some similar change
to ob-exp.el?)

Dan


> Is it intended
> to work this way?
>
> Paul
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Reply via email to