I choose the md2pdf option, but ended up with a html file instead of a pdf file
Finally had some time to read here.
I must say that I was very disappointed. I almost didn’t want to respond, because I expected it to be misunderstood.
But in fact, I myself almost feel offended or feel offended. It is as though I’m being attacked for simply bringing arguments or words soundly and fairly. I just say it like it is, without offense.
How, Mason, could you read a tone, if there was none, as there is no sound to a written letter? Or put it like this: had my words been obviously offensive (like with the use of profanity or whatever such clear offense), then yes, but you chide me for no good reason, and seem to even get praised for it!
About that definition of that simple IDE, since someone mentioned it and it looked like critique… You could’ve known what is meant by simply reading certain posts and making necessary conclusions. Even abstractness can be clear and lead to answers.
I will write no word in this here thread anymore, because it is obviously not appreciated (except for maybe one or a few, if they’re authentic). It would get misunderstood, or twisted, or some “politician” (possibly trying to score points, I don’t know) would attack my person.
If my words now in this particular post appear mean, I assure you there’s no such thing. If anything, it would sooner be anger. Righteous, burning, flaming anger.
Could you open an issue? I think we just call Weave to create these files…
I believe, what was not appreciated is the following:
Here you are suggesting that a person should not post here unless they exceed your personal standards for arguments and debates. Perhaps, people on this thread would appreciate your comments more if you had not made this type of suggestion.
That is definitely not true for everybody. I set up everything in probably 10 ways and tracked down the issue until a node package, that somehow ist not able to download files because it uses an odd self made proxy implementation. I do not remember the name, i can look it up tomorrow. I wanted to improve the situation by submitting an issue but the package does not allow filing issues. So after 2 hours of spending time I was stuck and frustrated.
edit: fixed typos
I think that the word ‘tone’ is universally understood to be applicable to the written word. I will point you to a Wikipedia page on the subject, here, not to back up the claim, but for an explanation of what is meant.
Your posts definitely have a tone.
it looks like Jupyter Lab. is it faster than vscode?
JupyterLab is pretty responsive, despite it runs in a browser.
This is Linux only…
I just tried installing Cantor, it seems like it doesn’t support Julia v1.3
It looked very neat though though I guess its not so simple to install.
So, I finally did make the switch from Atom to VS Code and boy is it better for me. There may have been something going on with Atom in the last few months but despite several attempts to re-install and start all over, I was still bothered by the time lag to get things started. Moreover, the editor would crash a lot (sometimes when I wanted to do something simple like change the font size) and at some point my Ctrl-C on Atom stopped working which was a pain while programming (if I am not wrong, this has been a known issue with the Atom-Julia plugin for a few weeks).
I still like Atom because that’s how I started but it’s unlikely I’ll be going back to it anytime soon given my recent experience with VS Code.
Phew, what a long thread. So two cents of input:
- If someone is keeping a running count: Atom + Juno is the nicest solution we have but suffers from being slow, is prone to crashing in my hands, and doesn’t do remote dev nearly as nicely as VS Code. None of those things are in the control of Julia community devs, so I guess it is what it is.
- To those wringing hands about what you can do with vim…I recently heard about (via Julia Slack no less) the neovim plugin “iron” https://github.com/Vigemus/iron.nvim
The documentation is a little sparse, but once I sorted it out its verrrryyyy slick. It will launch a Julia REPL in a separate window pane of neovim and then pushing code is just a combination of vim motions in combination with
ctr For example:
0ctr$ to send the current line over for execution.
Now, this is out of the box. Apparently it’s straightforward to throw in custom language-specific behavior for REPL interaction too… combine with Deoplete, NERDTree, LanguageServer and junegunn/fzf and you have a solid minimalistic IDE. Not aware of replacements for the way Juno handles error messages/results inline etc though
That’s a compelling argument for me.
But regarding the theme war, I guess people pick their editor based on performance, functionality and plugin availability. Then, once they found their editor, they customize it, including themes, keybindings and scripts. Thus, I guess, which browser is used in the long run will primary depend upon the former three points. Especially for performance, VS code seems to win. For functionality and plugins my perception is, that both are on par. At least for what I need from other languages.
That’s a definite point aswell!
I doubt the performance is much better than
vim, which is the king of remote dev and performance
Ah, well, I was referring to the theme war, aka, I was only comparing Atom and VS Code
But sure, effective productivity is highest with (neo)vim. EDIT: … CAN become highest with (neo)vim.
I just saw your error message on github issue…
“Spawning child process: Invalid argument” looks like problem you could have with spaces in the path definition (or in environment variables or somewhere else? ).
For example: if you have julia in
c:\Program Files\julia directory maybe you could try to change it in emacs config (if there you have something like that) to
c:/Progra~1/julia/ (see Filename mangling).
I think that the future looks very bad for Atom when compared to VS Code. Although not official, it seems clear which project has Microsoft full support. Just a glance at the pace of contributions and decreased development in Atom is very telling.
Although powerusers can overcome tooling shortcomings, the wider adoption of julia is influenced by the tooling around it and the officially supported IDE is like the official portrait of the language. I love how julia flows through Atom right now but maybe is time to shift the official focus and adapt to the trends?
Ive been using the VSCode extension with Julia and I think it works really well!
It will take a bit of time to mature like how to get the debuggers to work (they don’t yet) but Ive really enjoyed using it as it just feels faster and slowly I have strong believe that it will match Juno soon.
There’s a recent release that now works with Julia 1.3, so I encourage everyone to try if they haven’t. Finding an IDE that works well with Julia has been one of the things I always felt was lacking, and I think VSCode might be it.
(A quick work of warning to those trying. The first run through, Julia Language Server takes a while, a long while if you have a lot of libraries.)
It’s definitely not impossible that we’ll have a Juno built on VSCode at some point.