I'm not sure if this is the right place to complain about remote access issues. In general, I really appreciate that if I lost connection to remote or accidentally shut down Atom, it preserves my open tabs. However, there is this issue where if you leave remote files open on Atom when you shut it down, it opens them up from the local temporary files before you specify where you want to remote access, and then do not connect those open local files with the remote ones.

This has been a real problems for me as I have, on several occasions, thought that I was accessing remote files, when I was actually saving to local files, which made debugging programs that frequently crash and require restarting more confusing for me than usual. I also once lost a month of work when I opened a remote file and it overrode the temporary local file I didn't realize I was actually saving to.

I understand that this could be an issue if users modified the remote files through a different remote access in-between remote Atom sessions. However, is there any way to make temporary files sync with identical remote versions, and prevent temporary files from being overridden by remote files if their content differs?

@MikeInnes mentioned that there's a whole new CI thing, so it would be nice to detail that. I made a blank page for it, just add the Markdown to /docs/src/devdocs/juno_ci.md

Hi,

When I try to use Juno on a remote server I am only able to use a remote REPL and edit the remote files. My Juno won't display the variables in the workspace or evaluate expressions using ctrl+enter, I have to type include("filename") to run the codes. Does anyone know what might be happening?

Thanks!

For convenience, it would be nice if the repo description (which has a field for a URL) and the README contained a link to the actual docs --> http://docs.junolab.org

Should there be a warning on the docs or website that says there's a new IDE folks should be using?

http://docs.junolab.org/latest/man/installation.html doesn't exist.

The current documentation is three short paragraphs and a gif. An example of how to set a breakpoint (including how to import/use/include the code where the breakpoint will go) would be great in avoiding false starts.

We should probably add a version of this to the Juno Docs:

https://github.com/JunoLab/atom-julia-client/blob/master/manual/workflow.md

@dpsanders

Right now it's listed as "Super secret stuff".

The keyboard tag doesn't render right in Documenter.jl. An issue has been opened there:

JuliaDocs/Documenter.jl#299

I came here to propose a change from Ctrl+, to Ctrl+, or Ctrl + , in installation.md, because the comma is easy to miss next to the plus sign, but I wasn't able to figure out what branch one is supposed to edit from the instructions in the README. Both master and gh-pages seem to have been edited recently, so it isn't clear which one should be edited.

In any case, it's always nicer to be explicit :)

I am trying to update my Juno installation on Windows 10 following the instructions here:

http://docs.junolab.org/latest/man/update/

Unfortunately, apm does not appear on my path, and I can't seem to find the correct path containing the script. I think it'd be helpful to add something like a link to the Atom docs that describe how to add it to path.

I have followed the http://docs.junolab.org/latest/man/faq.html#Connecting-to-an-external-julia-session-on-a-remote-machine-1 and got the confirmation (on both Atom and system notificator), that I have successfully connected with the remote Julia session.

Yet when I try to start REPL I get an atom warning "Can't boot Julia with a Julia client running. Stop the current client with Packages → Julia → Stop Julia.". When I do this and open Julia again, I get the local Julia session in the REPL pane.

If it is not a bug but a feature, please update the manual (or I can do this, once you explain it) with the information about what functionality is supported when working on the remote Julia session, and how to use it.

By chance, I found that Shift+Enter was a shortcut that let me execute a line or a code block and move the curser to the next line/block. I was looking for this short-cut long ago and could not find it in the Juno documentation. Would you mind putting it there? Are there other "hidden" shortcuts?