4 ms·

This is neat, but search seems to be broken. I loaded one of my repositories and ran global searches for strings I know exist and they came up with no results.

This is neat, but search seems to be broken. I loaded one of my repositories and ran global searches for strings I know exist and they came up with no results. After I opened the file in the web editor, the results would appear in subsequent searches.

ibraheemdev 6y ago
It looks like search only works for files that are currently open.
- gbraad 6y ago
  It likely does not pull all the code into localstorage, but only those opened are retrieved as raw? An actual checkout would exceed 1s ;-)
  - chrisco255 6y ago
    Yeah, but you'd think you could pull down the directory without pulling down the files? I mean, I love the project either way, and it's already impressive as-is.
    - gbraad 6y ago
      If you want more, use gitpod.io
dstaley 6y ago
The #1 reason I end up cloning a repo and opening it in VS Code is to perform search, so it's a bummer search doesn't work. I'd even give up on the "1s" bit if I could open a full-text searchable version of the repo.
- renerthr 6y ago
  What do you guys think of vim with fzf? You can also use the `tree` command. And it consumes less RAM, probably. Why is it that VS Code seems to be so popular?
  - dmlittle 6y ago
    It's not that you _can't_ do these things in vim/emacs it's that the experience is different. I'd argue that VS Code is closer to an IDE than just an editor. For example, I can Cmd+Click on a function usage and it takes me to its definition. If I hover my mouse over it it displays information about the variables/function/data structure/etc. If I'm running docker containers I can attach a shell, view its logs, start/stop/restart it with the click of a button. There are thousands of extensions that allow me to augment the user experience – a Terraform extension that allows me to open resource documentation with the click of a button, running diffs on code, running code formatters, etc. Yes, all of this is possible with vim/emacs plugins but its not out of the box and the UX is not the same (and you're lying to yourself if you claim this isn't true). Installing and managing all of these plugins (in vim at least) is a lot more painful. As for the RAM consumption, it's honestly minimal. Running Chrome is more of a resource hog than VS Code.
    - RMPR 6y ago
      > Yes, all of this is possible with vim/emacs plugins but its not out of the box and the UX is not the same (and you're lying to yourself if you claim this isn't true). Installing and managing all of these plugins (in vim at least) is a lot more painful. Nitpicking a bit, but neovim has LSP built-in so you don't really need a plugin to achieve such basic tasks.
      - bern4444 6y ago
        It has built in LSP, but I still need a few plugins to get additional functionality like auto complete, auto import (thanks nvim-compe!), definition preview (lsp-saga) etc. I love nvim too and the direction its going, but the parent comment is correct. Its a lot more painful to set up compared to VSCode.

ibraheemdev 6y ago

It looks like search only works for files that are currently open.

gbraad 6y ago
It likely does not pull all the code into localstorage, but only those opened are retrieved as raw? An actual checkout would exceed 1s ;-)
- chrisco255 6y ago
  Yeah, but you'd think you could pull down the directory without pulling down the files? I mean, I love the project either way, and it's already impressive as-is.
  - gbraad 6y ago
    If you want more, use gitpod.io

dstaley 6y ago

The #1 reason I end up cloning a repo and opening it in VS Code is to perform search, so it's a bummer search doesn't work. I'd even give up on the "1s" bit if I could open a full-text searchable version of the repo.

renerthr 6y ago
What do you guys think of vim with fzf? You can also use the `tree` command. And it consumes less RAM, probably. Why is it that VS Code seems to be so popular?
- dmlittle 6y ago
  It's not that you _can't_ do these things in vim/emacs it's that the experience is different. I'd argue that VS Code is closer to an IDE than just an editor. For example, I can Cmd+Click on a function usage and it takes me to its definition. If I hover my mouse over it it displays information about the variables/function/data structure/etc. If I'm running docker containers I can attach a shell, view its logs, start/stop/restart it with the click of a button. There are thousands of extensions that allow me to augment the user experience – a Terraform extension that allows me to open resource documentation with the click of a button, running diffs on code, running code formatters, etc. Yes, all of this is possible with vim/emacs plugins but its not out of the box and the UX is not the same (and you're lying to yourself if you claim this isn't true). Installing and managing all of these plugins (in vim at least) is a lot more painful. As for the RAM consumption, it's honestly minimal. Running Chrome is more of a resource hog than VS Code.
  - RMPR 6y ago
    > Yes, all of this is possible with vim/emacs plugins but its not out of the box and the UX is not the same (and you're lying to yourself if you claim this isn't true). Installing and managing all of these plugins (in vim at least) is a lot more painful. Nitpicking a bit, but neovim has LSP built-in so you don't really need a plugin to achieve such basic tasks.
    - bern4444 6y ago
      It has built in LSP, but I still need a few plugins to get additional functionality like auto complete, auto import (thanks nvim-compe!), definition preview (lsp-saga) etc. I love nvim too and the direction its going, but the parent comment is correct. Its a lot more painful to set up compared to VSCode.