# Smart parsing .jmd files (Weave.jl)

**URL:** <https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877>\
**Category:** General Usage\
**Tags:** juno\
**Created:** [February 3, 2017, 7:32pm UTC](https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877 "2017-02-03T19:32:04Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevbonham](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kevbonham/32/216165_2.png) [@kevbonham](https://discourse.julialang.org/u/kevbonham)\
**Post date:** [February 3, 2017, 7:32pm UTC](https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877/1 "2017-02-03T19:32:04Z")

</div>

I recently discovered Weave.jl, and it’s quickly become my go-to method for incorporating code/commentary. This is important for me since I’m using julia for scientific analysis and reproducibility is essential, and is possible largely because Juno will actually evaluate the code in code blocks, which is phenomenal!

One problem I’m running into though is if I’m using the same code across multiple sessions, and I want to be able to quickly get back to where I left off - I have to manually go through and run the code in each block manually. It would be great if I could just evaluate the whole file and ignore the stuff that’s outside the

````
```julia
# codeblock
```

````

Any way to make this work?

---

<div class="post-metadata">

**Author:** ![davidanthoff](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/davidanthoff/32/223493_2.png) [@davidanthoff](https://discourse.julialang.org/u/davidanthoff)\
**Post date:** [February 3, 2017, 7:44pm UTC](https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877/2 "2017-02-03T19:44:14Z")

</div>

The next version of the julia extension for VS Code will have some Weave integration, and one thing you can do there is run a whole weave file with one command and then see the final document right within VS Code. I’m not sure when we will publish the next version, though, and I would recommend against trying to get our development version working (it is complicated). But you might keep an eye on [GitHub - julia-vscode/julia-vscode: Julia extension for Visual Studio Code](https://github.com/JuliaEditorSupport/julia-vscode) for the next release.

---

<div class="post-metadata">

**Author:** ![kevbonham](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kevbonham/32/216165_2.png) [@kevbonham](https://discourse.julialang.org/u/kevbonham)\
**Post date:** [February 4, 2017, 10:15pm UTC](https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877/3 "2017-02-04T22:15:32Z")

</div>

Neat! Not sure I’ve got the energy to shift text editors again though :-/

---

<div class="post-metadata">

**Author:** ![mkborregaard](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mkborregaard/32/556_2.png) [@mkborregaard](https://discourse.julialang.org/u/mkborregaard)\
**Post date:** [February 11, 2017, 10:55pm UTC](https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877/4 "2017-02-11T22:55:26Z")

</div>

This’d be a cool feature in Juno

---

<div class="post-metadata">

**Author:** ![pfitzseb](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/pfitzseb/32/45566_2.png) [@pfitzseb](https://discourse.julialang.org/u/pfitzseb)\
**Post date:** [February 13, 2017, 1:01am UTC](https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877/5 "2017-02-13T01:01:22Z")

</div>

Yup, this would definitely be nice to have. I won’t get around to implementing this in the foreseeable future though (next ~2 months), but feel free to open a feature request over at atom-julia-client and/or take a stab at the implementation yourself! 🙂

---

<div class="post-metadata">

**Author:** ![kevbonham](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/kevbonham/32/216165_2.png) [@kevbonham](https://discourse.julialang.org/u/kevbonham)\
**Post date:** [February 14, 2017, 3:29pm UTC](https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877/6 "2017-02-14T15:29:00Z")

</div>

[Feature request made](https://github.com/JunoLab/atom-julia-client/issues/311)!

As mentioned there - I’d be happy to take a stab at this, but I haven’t done any Atom development, so would love some guidance on where to start.

---

<div class="post-metadata">

**Author:** ![zhangliye](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/zhangliye/32/3208_2.png) [@zhangliye](https://discourse.julialang.org/u/zhangliye)\
**Post date:** [February 15, 2017, 12:51am UTC](https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877/7 "2017-02-15T00:51:22Z")

</div>

Sounds amazing. The similar function in RStudio is very useful. I like this feature.

---

<div class="post-metadata">

**Author:** ![NickNack](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/nicknack/32/1792_2.png) [@NickNack](https://discourse.julialang.org/u/NickNack)\
**Post date:** [September 13, 2017, 6:31pm UTC](https://discourse.julialang.org/t/smart-parsing-jmd-files-weave-jl/1877/8 "2017-09-13T18:31:53Z")

</div>

> [@davidanthoff](#):
>
> The next version of the julia extension for VS Code will have some Weave integration, and one thing you can do there is run a whole weave file with one command and then see the final document right within VS Code. I’m not sure when we will publish the next version, though, and I would recommend against trying to get our development version working (it is complicated). But you might keep an eye on [GitHub - julia-vscode/julia-vscode: Julia extension for Visual Studio Code · GitHub](https://github.com/JuliaEditorSupport/julia-vscode) for the next release.

(Pinging @davidanthoff…)  
Sorry for necroing this thread, but I’m curious about how far along the Weave integration in VScode has come. All I can figure out is that VScode recognizes .jmd files and you can send lines in Julia blocks to the terminal using Ctrl-Enter. But what about the dream - previews of .jmd files within VScode? And the next step after that: real-time preview while typing (is that even possible without killing performance)?