-
snikket test
>> Hello everyone! Is there any plan to publish gram to flathub.org? > Sort of but no idea when this will happen. I still think that the flatpak format is not a good fit for a code editor like this and I personally prefer native packages. FWIW, I've found some applications distributed as flatpak fit DE themes better (I run Pop!_OS which uses COSMIC DE) than .deb packages. nextcloud desktop client and pulsar editor come to mind. Ultimately, I'm a believer in distributing whatever is easiest to maintain which seems to be appimage or flatpak.✎ ↺ -
snikket test
>> Hello everyone! Is there any plan to publish gram to flathub.org? > Sort of but no idea when this will happen. I still think that the flatpak format is not a good fit for a code editor like this and I personally prefer native packages. FWIW, I've found some applications distributed as flatpak fit DE themes better (I run Pop!_OS which uses COSMIC DE) than .deb packages. nextcloud desktop client and pulsar editor come to mind. Ultimately, I'm a believer in distributing whatever is easiest to maintain which seems to be appimage or flatpak for most projects. ✏ ↺
-
notbenh
[RE: failure to paste] thanks for the sanity check @EdwardLoveall, I found the issue by default paste is ctrl+shift+v which is a combo I've never run in to before. I attempted to add new keybindings to the standard OSX cmd+(c|v) and in both cases they fail stating that Action `editor: copy` or `editor: paste` is not found even though these are the value in the action column of that view? Am I confused on how to build a new keybinding?
-
krig
Through the command palette (usually command+P) you can get back to the welcome screen and pick a different base keymap. The default is Emacs which is probably why you are confused :) If you pick VS Code there I suspect things will feel more familiar
-
krig
For keybindings, they depend on context which can be confusing. I recommend looking through the documentation and the default keymaps for inspiration