Nuno Salgado writes:
> My question was to figure out what's the point to tangle the code
> without substituition!
Your imagination is the limit. E.g. this could be useful to document
the ":noweb eval" behavior opposed to ":noweb yes".
My approach to this is to create three blocks that are tangled and a
separate block (or more than one if you have different tests you want to
perform) for evaluation that references those three blocks (via noweb)
but is not tangled.
--
Eric S Fraga via Emacs 28.0.50, Org release_9.3.1-94-g0ac6a9
Thanks Kyle! I've slightly updated the patch, because I had neglected to
handle Python exceptions. If you haven't started yet, please consider
the updated patch instead (it only differs by a few lines within
org-babel-python--eval-tmpfile).
>From c2fff65f36141b78d91af9d6264d0f936ee5a3a1 Mon Sep
Jack Kamm writes:
> This patch fixes several related issues with python blocks with
> parameters ":session :results value", including:
>
> - Broken if-else and try-except statements.
> - Correctly parsing blank lines in indented blocks.
> - Returning the correct value when the underscore "_"
Still not working for me :(
On Jan 22, 2020, at 8:30 PM, John Kitchin
mailto:jkitc...@andrew.cmu.edu>> wrote:
that is strange. I was able to reproduce it a few times, but now it works fine.
all within a few minutes of trying to debug it.
This makes me think something was not right in the
That is indeed very interesting.
Thanks for looking into this.
Cheers,
M
On Jan 22, 2020, at 8:30 PM, John Kitchin
mailto:jkitc...@andrew.cmu.edu>> wrote:
that is strange. I was able to reproduce it a few times, but now it works fine.
all within a few minutes of trying to debug it.
This makes
that is strange. I was able to reproduce it a few times, but now it works
fine. all within a few minutes of trying to debug it.
This makes me think something was not right in the request or reply.
json-read-from-string("\n\015\n400 The plain HTTP
request was sent to HTTPS
port\015\n\015\n400 Bad
-Hi Everybody,
For some reason, I keep getting an error (JSON readable error: 60) whenever I
try to add a BibTex entry to a BibTex file using
doi-utils-add-bibtex-entry-from-doi. I would appreciate if someone could tell
me how to resolve this problem.
Best Wishes,
M
Here is the backtrace
Marco,
Thank you for your help. I read it again and didn't find. But no
problem.
My question was to figure out what's the point to tangle the code without
substituition!
NS
Marco Wahl writes:
> Nuno Salgado writes:
>
>> Vars definition:
>> #+NAME:DEFVARS
>>
>> #+BEGIN_SRC shell
Diego,
Thank you for your help.
Yes, I want the scripts to be all in one file in order to execute them
all. But it's nice do execute then individualy (C-c C-c) to test and debug.
I think I have to have 2 blocks of code for each script: one for tangle,
with no <> and another to test, with <> and
Somebody seems to be playing with stuff on code.orgmode.org: every
once in a while when I look at the repo (e.g by visiting
https://code.orgmode.org/bzg/org-mode), I get a literal HTML page,
instead of a rendered one. That seems to be caused by some extra text
at the beginning:
,
| 2020/01/22
Hi Nuno,
":noweb eval" means that noweb references are only expanded during
evaluation of the code, but not during export. This is why you get the
literal <> references in exported output. Here are the possible
values of :noweb and what they mean: https://orgmode.org/manual/noweb.html
Also note
Nuno Salgado writes:
> Vars definition:
> #+NAME:DEFVARS
>
> #+BEGIN_SRC shell :tangle yes
> v1=1;
> v2=2;
> #+END_SRC
>
> Script1:
>
> #+BEGIN_SRC shell :tangle yes :noweb eval
> <>
> echo $v1;
> #+END_SRC
>
> This works great when I do C-c C-c in each script.
>
>
Hi,
I'm writing an installation script in org-mode.
I'm doing something like this:
Vars definition:
#+NAME:DEFVARS
#+BEGIN_SRC shell :tangle yes
v1=1;
v2=2;
#+END_SRC
Script1:
#+BEGIN_SRC shell :tangle yes :noweb eval
<>
echo $v1;
#+END_SRC
Script2:
Nicolas Goaziou writes:
> Hello,
>
> stardiviner writes:
>
>> In an *empty* Org file buffer, I press =[C-c C-x p]= to add properties
>> drawer. It
>> works fine. But when the Org buffer has nodes already like this:
>>
>> #+begin_src org
>> |
>>
>> ,* node 1
>>
>> context
>> #+end_src
>>
>>
Nicolas Goaziou writes:
> Hello,
>
> Jack Kamm writes:
>
>> Apologies for the delay on this. I've now got a more complete patch for
>> displaying remote images inline. Since downloading many remote images
>> could potentially hang Emacs on a slow connection, I've added an option
>> to control
16 matches
Mail list logo
