learn-co / learn-ide Goto Github PK

woops

rm: cannot remove waiting: Is a directory looks like rm: cannot remove âwaitingâ: Is a directory which is weird

dagnabbit

low priority

it really really really screws stuff up

• open in existing window if it exists

similar wrapper to rails/httpserver

possibilities:

1. kill off any that are running for a user when the fs server boots up
2. just don't start a new one if one is already running when fs server boots up

Two options:

1. Package it as part of the download (desirable if fast enough)
2. Prompt user to paste token (undesirable)

shouldn't be syncing files that aren't in .atom/code

/proc/sys/fs/inotify/max_user_watches

way more cross platform and significantly simpler logic

it looks like it's broken otherwise

bah

Currently if you tab back to ILE in Terminal loses cursor focus

1. Blow away all related code
2. Notify Nitrous of termination of contract

probably just need to recursively check through dirs on create

On both OSX and Windows

• weird disconnection if clicking an open button when atom isn't closed
• need to send a ctrl+c to the server if there are no windows open (or something)

(test notifications too? why not i guess)

For directory removals

undefined function 'length' for null

In addition to Nitrous, OSX

for when using on a brand new machine

need to fix that real quick so that i can actually add people to the server

things i hope work, but am slightly concerned about:

1. utf8 stuff in new websocket handling?
2. open button

issue when atom launches two windows at once...ie, a window was left open before quitting, or when there is no line that has vm in it. need to address.

try {shell} = require 'electron' catch then shell = require 'shell'

• queue websocket responses so they don't end up getting sent at the same time, squished together
• figure out the 'invalid utf8' issue that keeps popping up (right now, just try/catching)
• what's going on with inotify just kind of skipping some things?

• fs_server
  • handle open/close state
  • handle open
  • remote file handling in atom
  • local file handling in atom
• terminal_server
  • share one connection
  • properly update new terminal views
  • handle weird double vim thing
• combine connection state (so logo will be red if either fs or term disconnects)

doh!

• last thing: weird state when you lose connection to both fs/terminal (after the second one drops, terminal lights up as if it's connected)
• other last thing: try and get an extra '\r' in there so it doesn't look stupid