News for hackers. Stuff that matters.
Re:Introducing Atom-IDE by betenoire on Tuesday September 12, 2017 @09:43PM (#15234812)
I think every editor can probably configured to do this. I've set up my VIM to do this specifically (auto reload the buffer when the file is modified). I don't think that one's on VSCode.
Re:Introducing Atom-IDE by _tulpa on Wednesday September 13, 2017 @12:19AM (#15235505)
They're not configured to do that by default, most of them ask prompt you if a file changes.

This one is on VSCode for having unsafe default behaviour which is also different to pretty much all the other editors.

Re:Introducing Atom-IDE by bpasero on Wednesday September 13, 2017 @03:05AM (#15236133)
VS Code will never close a buffer that has changes (e.g. is dirty). In this case, the buffer was closed because the editor was not dirty. You can change this by configuring "workbench.editor.closeOnFileDelete": false
Re:Introducing Atom-IDE by nerdponx on Wednesday September 13, 2017 @04:09PM (#15242114)
Having that default to "true" is really silly. VSCode is OSS right? That seems like a mulligan pull request to me. I can't imagine anyone is relying on the default behavior as-is.