i greatly appreciate that! i am not sure if JulIDE can or will become as big as Juno or the VSCode extension, but that dosent mean i wont try 
i am not sure how that works, but glad to hear!
also, if you have any features you want to see in JulIDE, i am open to suggestions, and even if i dont accept them, we have a plugin registry now 
I admire how your projects spark engagement in the community. Mine haven’t found that rhythm yet, but your work is a reminder of the impact thoughtful contributions can have.
If you have reasons other than just being better than VSCode and Juno, ofc it will why not
my reasoning for building JulIDE is not to be better than Juno or VSCode, its to be a decent option for Julia developers for their IDE
not sure this is relaistic, but ill try to achieve that
Does it have a way of saving output in the REPL in a file?
i saw your projects, they are very cool! i am sure they will find their audiance sooner or later 
not currently, do you mean like for error logs or in general?
yeah, i have seen it. :), 4 more improvments:
Thanks again, i have stared your project.
Ohh nicee, pardon me for getting the reason wrong
first of all, thank you for the star! it helps a ton
about the improvements you suggested
A: that is on purpose because of how the JulIDE security model works, but i should make a toggle to enable external images
B: even with ```Julia?
C: could you explain further about this? like in the editor or in markdown?
D: ill happily add that
thank you very much for the suggestions!
I meant output in general, e.g., text output from functions. I am not interested in error logs.
A. it would be better to see images in markdown
B. in plain text mode, it has some rendering,
but in preview mode it does not.
C. latex not rendered in markdown both in editor and markdown.
I have another advice, whenever i changed a file, the title of the file should give some changing sign, like a * or ● or a lighter color 
btw, i’m using win10 OS. Thanks!
the images in markdown fix is already in github and will be released along with JulIDE 0.5.0
as for the rest, they may have to wait until 0.6.0 or even 0.7.0 since my backlog is pretty full, which is a good thing in my opinion, but at the end of the day i am a solo maintainer xD
ill try adding a backround to the logo, i hope that will fix it, but not sure since my art skills are horrible (the logo was made by a friend of mine xD)
I think the issue is really the background color that together with the font color make the ensemble difficult to see.
Update: JulIDE 0.5.0 is out! this release introduces the ability to use jupyter notebooks in plain .jl files via the Jupytext format, dev containers are now fixed to work on windows, and are now the recommended way to work with Linux tooling from windows. fatou on windows has been fixed as well
(note: i was in a bit of a rush for this release due to the fatou bug, so if you encounter anything abnormal, let me know!)
update: JulIDE is now available via flatpak!
simply add the remote via
flatpak remote-add --if-not-exists julide https://julide-rgstry.org/julide.flatpakrepo
and install via
flatpak install julide io.github.Julideorg.JulIde
a few notes:
Suggestion, don’t use characters like these
use plain ASCII !==
Personally, I find them very disturbing to read, but surely this is only one opinion (make them optional?)
in the docs or in the IDE itself? either way ill make it optional