Earlier quoted context omitted.
I am a developer for almost 15 years now. My primary operating system is windows. I have used Linux but only sparingly. I have used many IDEs. I have never ever felt the need to use vim. Is it fair to say, because VSCode does not have a "vim mode", it is somehow inferior as an editor? I seriously don't get it. I have used VSCode almost from day one. It is a fantastic editor and quite a capable tool. I seriously love…
VSCode does little out of the box. You install plugins to get what you want. Including vim mode.
Web-based editor
191–200 of 307 posts
Re: Web-based editor
#192Earlier quoted context omitted.
VSCode does have a vim mode. See this plugin here: https://github.com/VSCodeVim/Vim It works surprisingly well.
It's pretty good, although I've found it a bit funky with copy/paste/yanking.
Re: Web-based editor
#193Earlier quoted context omitted.
I get worried that VS Code is too popular, and that some higher ups might be tempted to go for an EEE play. The flipside is that MS pouring money into VS Code has tremendously benefited the entire code editor ecosystem, including (especially) FOSS editors that can reuse their language servers.
Last I checked, most of the MS-owned language servers used proprietary licenses. An example is the Python language server https://github.com/microsoft/pylance-release They base it 90% on the open-source pyright library. Then the lock down all their own enhancements. https://github.com/microsoft/pyright This is why MIT isn't always the correct choice. GPL wouldn't hurt devs at all and would protect from this kind of g…
But would it protect against Pylance existing, or would it just be more expensive to develop but still proprietary (and possibly not free-as-in-beer), or would it be Free?
There's only one of those three where devs (as opposed to Free Software ideologues) win, and one where both lose.
(And really, it would do none of those, since pyright is also owned by MS, so they could reuse it on any terms even if the owner [them] offered it to others only under GPL terms. All GPL would do is prevent someone else from competing with Pylance by taking pyright and building similar functionality on top, possibly with a still-Free license.)
Re: Web-based editor
#194Am I alone in not jumping on the Visual Studio [Code] bandwagon? Other online editors have had "vim modes" for ages (e.g. Overleaf) and frankly I'm unlikely to write a chonking great script or project in a browser on Github -- a minor modification is much more likely. VS Code's codebase is huge . Will Github allow people to use other $EDITORs? (Yes, I'm aware this makes me sound like an old man!)
I've been using a highly-tuned emacs configuration as my IDE for a decade now. Each time I want try to switch to VS Code I find that all my weird little shortcuts are going to take a lot of time to re-learn in VS Code. I should really just take the time to switch to VS Code and rip off the bandaid since I think it would make life easier in the long run.
Emacs will be around forever, but vscode will dominate.
Re: Web-based editor
#195I've been using this for a while. Very, very, very handy for - Just exploring some code. - Quickly pull up as reference code w/ decent navigation without having to checkout locally or navigate forward/back in the source tree in GitHub. - When reviewing PRs and wanting to check out some surrounding code that is not part of the actual PR. - If you want to quickly commit something really small and trivial in master/a br…
You can also use "chromium --app $url" and you'll have these key bindings available. If you want to use github isolated from your browser history, you can use it like so:
[$] chromium --user-data-dir=$HOME/github_or_whatever --app="https://github.com/orga/repo" --new-window;
edit: If you use MacOS or Windows, my browser wrapper script from another project might give you some hints on how to use Safari or Edge this way [1].
[1] https://github.com/tholian-network/stealth/blob/X0/browser/b...
Re: Web-based editor
#196how do I start? do I need enterprise account? went to the page above and found nowhere I can try out.
Hit "." on any github repo.
just hit . and installed vim plugin and it worked well for basic needs, not sure how to get my snippets and some key binding there yet, but this does look nice.
Re: Web-based editor
#197Its scary we're heading towards a situation where everything is done in a browser. Maybe Chromeos really is the future.
I am fairly comfortable having my laptop being a conduit to better resources in the cloud. There are also strong security advantages of not having sensitive data on laptops.
Re: Web-based editor
#198Am I alone in not jumping on the Visual Studio [Code] bandwagon? Other online editors have had "vim modes" for ages (e.g. Overleaf) and frankly I'm unlikely to write a chonking great script or project in a browser on Github -- a minor modification is much more likely. VS Code's codebase is huge . Will Github allow people to use other $EDITORs? (Yes, I'm aware this makes me sound like an old man!)
1) When you alt-tab you lose dialog tooltip, I can't handle this, it should be a number one priority to fix this 2) A lot of languages just look plain ugly in VS Code, not so in Emacs for example, Vim w/e
Re: Web-based editor
#199Am I alone in not jumping on the Visual Studio [Code] bandwagon? Other online editors have had "vim modes" for ages (e.g. Overleaf) and frankly I'm unlikely to write a chonking great script or project in a browser on Github -- a minor modification is much more likely. VS Code's codebase is huge . Will Github allow people to use other $EDITORs? (Yes, I'm aware this makes me sound like an old man!)
Yes, just clone? Most people who want other editors probably don't want browser-based ones.
I'm not sure if the VSCodeVim or VSCodeNeovim extensions work on the online version yet, but I'm sure some VSCode/GitHub engineers are on the case if not.
EDIT: VSCodeVim (the main "Vim" extension) does "work" on github.dev but the escape key doesn't, so as soon as you press "i" you're stuck in insert mode forever. https://github.com/VSCodeVim/Vim/issues/7005