Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEAT] Vim support #52

Open
Palanikannan1437 opened this issue Apr 15, 2023 · 3 comments
Open

[FEAT] Vim support #52

Palanikannan1437 opened this issue Apr 15, 2023 · 3 comments
Assignees

Comments

@Palanikannan1437
Copy link
Collaborator

Palanikannan1437 commented Apr 15, 2023

How about some VIM support building upon @axonasif's https://github.com/axonasif/dotsh configuration steps 🚀

@axonasif
Copy link
Member

axonasif commented Apr 15, 2023

VIM sounds really interesting! I'm wondering if you could share a bit more about this feature?

@henit-chobisa
Copy link
Collaborator

henit-chobisa commented Apr 15, 2023

VIM sounds really interesting! I'm wondering if you could share a bit more about how this feature?

cc: @loujaybee, @Siddhant-K-code, @filiptronicek, @pawleen, @mads-hartmann, @gtsiolis, @akosyakov,

Current plan of thought is to aim for two things,

SSHing to the workspace

As you know with the latest beta, we are able to start the workspaces, and with the workspace url we can open it anywhere, we tried sshing method today with ssh://{workspace_url}, which was a success and opens nvim with iterm and kitty 😄 (after we setup dotsh files building upon your configuration)

Setting up user's dotfiles in Gitpod(nvim for now) by using user's local config

Our extension has access to two significant things for this task,

  1. User's GitHub
  2. User's System

So basically the task being done with your dotsh prompt, we can do it with the help of a GUI interface for folks to easily get started with (of Raycast for now) within the extension

Hence we can just automate it with the default nvim config of the user's machine or if the user just wants to get started we will use options like lvim/some popular configs building upon your dotsh system and push it and automatically add this to their Gitpod preferences.

graph TD;
  A[Setup Neovim for GItpod] --> A1(Confinue Setup)
  A-->A2(Skip Prompt)
  A2--Raycast-->A21(Select Default Nvim Configuration)
  A21--Github-->ED0(Generate Dotsh Config)
  ED0--Gitpod-->ED
  ED1--Gitpod-->ED[Add to Gitpod Preferences]
  A1--Raycast-->A11(Provide Custom DotSH)
  A1--System-->A12(Take Config from System)
  A11-->ED1[Testing DotSH]
  A12-->ED0
  ED-->GPD[Ready to Use Neovim]
Loading

@Palanikannan1437
Copy link
Collaborator Author

Palanikannan1437 commented Apr 15, 2023

And here's a quick demo of how seamless it'll be to use Vim/any terminal editor with Gitpod 🍊 by giving it as an explicit choice via Raycast(please refer to the above comment for implementation details)

Start Workspace --> Launch Gitpod in your editor (acc to dotfiles) directly in your terminal without the whole browser loop

demo.vim.gitpod2.mov

CC: @loujaybee @pawlean @axonasif

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants