I'm used to VS Code. What works the same in Furge's code editor?

Developer → Code works like the editor you know. Files open as tabs. A file you only look at gives its tab to the next one (its name is in italics); a double-click, or typing in it, keeps it. Each tab keeps its unsaved text, its place and its own undo, so you can go between files without saving first. A dot marks a tab that isn't saved, and Save all saves every one. Press F1 (or Ctrl+Shift+P) for every command, Ctrl+P to open a file from a few letters of its name (add :12 to open it at line 12), and Ctrl+G to go to a line. On a Mac, use ⌘ where this says Ctrl, except Ctrl+G. The keys you're used to work: Ctrl+D selects the next match so you can change several at once, Alt+Up and Alt+Down move a line, Shift+Alt+Down copies it, Ctrl+/ comments it, Ctrl+F finds and Ctrl+Shift+F searches every file. Alt+Z turns word wrap on and off, and the commands include Text size: bigger and Text size: smaller. Two keys differ because the browser keeps them for itself: Alt+W closes a tab, and Alt+1 to Alt+9 show a tab by its number (Ctrl and the number on a Mac). Your open tabs come back the next time you turn Developer mode on in this browser. Source control beside Files (Ctrl+Shift+G) pushes the code to GitHub and pulls back what you change there. Furge has no terminal, npm or extensions: a site that needs a build step stays in your own editor and publishes from GitHub.

Steps

  1. Turn on Developer (Shift+D) and open Code.
  2. Press Ctrl+P, type a few letters of a file's name and press Enter.
  3. Press F1 to find any command, such as Save all or Word wrap.

Also asked as

Related

Still stuck? Ask Furge Help, the round chat button at the bottom right, or contact the Furge team.

← All of Furge's docs