#vterm — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #vterm, aggregated by home.social.
-
I have just released version 1.0.0 of ESR: an R tree sitter mode for #emacs
It is the first version independent of #ESS although tree sitter can be paired with ESS.
ESR's interaction mode can use comint or #vterm The second one plays well with #radian Coding tools for now are supported by R's package #languageserver and can be connected with #eglot
A big step for the #rstats users of Emacs
-
I have just released version 1.0.0 of ESR: an R tree sitter mode for #emacs
It is the first version independent of #ESS although tree sitter can be paired with ESS.
ESR's interaction mode can use comint or #vterm The second one plays well with #radian Coding tools for now are supported by R's package #languageserver and can be connected with #eglot
A big step for the #rstats users of Emacs
-
I have just released version 1.0.0 of ESR: an R tree sitter mode for #emacs
It is the first version independent of #ESS although tree sitter can be paired with ESS.
ESR's interaction mode can use comint or #vterm The second one plays well with #radian Coding tools for now are supported by R's package #languageserver and can be connected with #eglot
A big step for the #rstats users of Emacs
-
I have just released version 1.0.0 of ESR: an R tree sitter mode for #emacs
It is the first version independent of #ESS although tree sitter can be paired with ESS.
ESR's interaction mode can use comint or #vterm The second one plays well with #radian Coding tools for now are supported by R's package #languageserver and can be connected with #eglot
A big step for the #rstats users of Emacs
-
I have just released version 1.0.0 of ESR: an R tree sitter mode for #emacs
It is the first version independent of #ESS although tree sitter can be paired with ESS.
ESR's interaction mode can use comint or #vterm The second one plays well with #radian Coding tools for now are supported by R's package #languageserver and can be connected with #eglot
A big step for the #rstats users of Emacs
-
My vterm-editor.el package is now available on MELPA.
https://git.andros.dev/andros/vterm-editor.el
https://melpa.org/#/vterm-editor
#emacs #melpa #elisp #vterm -
My vterm-editor.el package is now available on MELPA.
https://git.andros.dev/andros/vterm-editor.el
https://melpa.org/#/vterm-editor
#emacs #melpa #elisp #vterm -
My vterm-editor.el package is now available on MELPA.
https://git.andros.dev/andros/vterm-editor.el
https://melpa.org/#/vterm-editor
#emacs #melpa #elisp #vterm -
My vterm-editor.el package is now available on MELPA.
https://git.andros.dev/andros/vterm-editor.el
https://melpa.org/#/vterm-editor
#emacs #melpa #elisp #vterm -
My vterm-editor.el package is now available on MELPA.
https://git.andros.dev/andros/vterm-editor.el
https://melpa.org/#/vterm-editor
#emacs #melpa #elisp #vterm -
When working inside a vterm terminal, editing multi-line text can be awkward: you lose access to Emacs keybindings, navigation, and editing commands. vterm-editor solves this by opening a temporary buffer where you can write comfortably using all of Emacs, then send the result back to vterm.
https://git.andros.dev/andros/vterm-editor.el
#emacs #vterm -
When working inside a vterm terminal, editing multi-line text can be awkward: you lose access to Emacs keybindings, navigation, and editing commands. vterm-editor solves this by opening a temporary buffer where you can write comfortably using all of Emacs, then send the result back to vterm.
https://git.andros.dev/andros/vterm-editor.el
#emacs #vterm -
When working inside a vterm terminal, editing multi-line text can be awkward: you lose access to Emacs keybindings, navigation, and editing commands. vterm-editor solves this by opening a temporary buffer where you can write comfortably using all of Emacs, then send the result back to vterm.
https://git.andros.dev/andros/vterm-editor.el
#emacs #vterm -
When working inside a vterm terminal, editing multi-line text can be awkward: you lose access to Emacs keybindings, navigation, and editing commands. vterm-editor solves this by opening a temporary buffer where you can write comfortably using all of Emacs, then send the result back to vterm.
https://git.andros.dev/andros/vterm-editor.el
#emacs #vterm -
When working inside a vterm terminal, editing multi-line text can be awkward: you lose access to Emacs keybindings, navigation, and editing commands. vterm-editor solves this by opening a temporary buffer where you can write comfortably using all of Emacs, then send the result back to vterm.
https://git.andros.dev/andros/vterm-editor.el
#emacs #vterm -
A question for emacs users who have a python REPL workflow and use corfu (so a very small, possibly 0-member group).
Has anyone been able to get completions to work on the REPL in vterm ? I keep getting:
>>> ["0__dummy_completion__", "Path", "1__dummy_completion__"]
or much larger walls of text. Makes using the REPL impossible.
-
A question for emacs users who have a python REPL workflow and use corfu (so a very small, possibly 0-member group).
Has anyone been able to get completions to work on the REPL in vterm ? I keep getting:
>>> ["0__dummy_completion__", "Path", "1__dummy_completion__"]
or much larger walls of text. Makes using the REPL impossible.
-
A question for emacs users who have a python REPL workflow and use corfu (so a very small, possibly 0-member group).
Has anyone been able to get completions to work on the REPL in vterm ? I keep getting:
>>> ["0__dummy_completion__", "Path", "1__dummy_completion__"]
or much larger walls of text. Makes using the REPL impossible.
-
A question for emacs users who have a python REPL workflow and use corfu (so a very small, possibly 0-member group).
Has anyone been able to get completions to work on the REPL in vterm ? I keep getting:
>>> ["0__dummy_completion__", "Path", "1__dummy_completion__"]
or much larger walls of text. Makes using the REPL impossible.
-
A question for emacs users who have a python REPL workflow and use corfu (so a very small, possibly 0-member group).
Has anyone been able to get completions to work on the REPL in vterm ? I keep getting:
>>> ["0__dummy_completion__", "Path", "1__dummy_completion__"]
or much larger walls of text. Makes using the REPL impossible.
-
I'm experimenting with using #Emacs for my terminals, especially using the #vterm package. It could be a really nice environment: cross-platform, easy copy-pasting with keyboard commands only, etc.
However, when I started up the #Gemini CLI in the vterm buffer, I found that it renders quite differently. See https://github.com/akermu/emacs-libvterm/issues/776. Basically, there are soft stripes between the #Unicode block characters and the shade characters are dithered instead of being nice solid blocks.
-
I'm experimenting with using #Emacs for my terminals, especially using the #vterm package. It could be a really nice environment: cross-platform, easy copy-pasting with keyboard commands only, etc.
However, when I started up the #Gemini CLI in the vterm buffer, I found that it renders quite differently. See https://github.com/akermu/emacs-libvterm/issues/776. Basically, there are soft stripes between the #Unicode block characters and the shade characters are dithered instead of being nice solid blocks.
-
I'm experimenting with using #Emacs for my terminals, especially using the #vterm package. It could be a really nice environment: cross-platform, easy copy-pasting with keyboard commands only, etc.
However, when I started up the #Gemini CLI in the vterm buffer, I found that it renders quite differently. See https://github.com/akermu/emacs-libvterm/issues/776. Basically, there are soft stripes between the #Unicode block characters and the shade characters are dithered instead of being nice solid blocks.
-
I'm experimenting with using #Emacs for my terminals, especially using the #vterm package. It could be a really nice environment: cross-platform, easy copy-pasting with keyboard commands only, etc.
However, when I started up the #Gemini CLI in the vterm buffer, I found that it renders quite differently. See https://github.com/akermu/emacs-libvterm/issues/776. Basically, there are soft stripes between the #Unicode block characters and the shade characters are dithered instead of being nice solid blocks.
-
I'm experimenting with using #Emacs for my terminals, especially using the #vterm package. It could be a really nice environment: cross-platform, easy copy-pasting with keyboard commands only, etc.
However, when I started up the #Gemini CLI in the vterm buffer, I found that it renders quite differently. See https://github.com/akermu/emacs-libvterm/issues/776. Basically, there are soft stripes between the #Unicode block characters and the shade characters are dithered instead of being nice solid blocks.
-
🚀 4 Terminali per GNU/Emacs! 🚀
Vuoi un terminale integrato in Emacs? In questo video ti mostro vterm, eshell, ansi-term e shell-mode, con i loro pro e contro.
📺 Guarda ora: https://youtu.be/btkNrqTzfMA
💬 Quale usi?
#Emacs #Terminale #vterm #eshell #Linux #FOSS #CLI #Productivity
-
ok, so #vterm doesn't actually run bash upon start. If I run /bin/bash, all my usual environment is working.
-
ok, so #vterm doesn't actually run bash upon start. If I run /bin/bash, all my usual environment is working.
-
ok, so #vterm doesn't actually run bash upon start. If I run /bin/bash, all my usual environment is working.
-
ok, so #vterm doesn't actually run bash upon start. If I run /bin/bash, all my usual environment is working.
-
Solved! Thanks to this post: https://discourse.nixos.org/t/non-interactive-bash-errors-from-flake-nix-mkshell/33310
Solution: add bashInteractive as a package in the nix shell.
-
This is a bit niche but any #nix #emacs #vterm users out there? Lately, if I'm in a nix-shell (or nix develop), vterm completely breaks down. Control characters to navigate command line no longer work, the shell prompt has extra characters in it, history is inaccessible etc. So it's unusable. What have I done?
-
This is a bit niche but any #nix #emacs #vterm users out there? Lately, if I'm in a nix-shell (or nix develop), vterm completely breaks down. Control characters to navigate command line no longer work, the shell prompt has extra characters in it, history is inaccessible etc. So it's unusable. What have I done?
-
This is a bit niche but any #nix #emacs #vterm users out there? Lately, if I'm in a nix-shell (or nix develop), vterm completely breaks down. Control characters to navigate command line no longer work, the shell prompt has extra characters in it, history is inaccessible etc. So it's unusable. What have I done?
-
This is a bit niche but any #nix #emacs #vterm users out there? Lately, if I'm in a nix-shell (or nix develop), vterm completely breaks down. Control characters to navigate command line no longer work, the shell prompt has extra characters in it, history is inaccessible etc. So it's unusable. What have I done?
-
This is a bit niche but any #nix #emacs #vterm users out there? Lately, if I'm in a nix-shell (or nix develop), vterm completely breaks down. Control characters to navigate command line no longer work, the shell prompt has extra characters in it, history is inaccessible etc. So it's unusable. What have I done?
-
Did you know that you can call #Emacs functions in #vterm like you can do in Eshell?
Using vterm-eval-cmds you can either commands that don't exist in a shell or replace those that exist.
E.g. instead of man you can call the Emacs manapge mode.
You just have to print something to the terminal with the right escape sequence so vterm receives
the right control sequence to know what to call.Look at my config for more examples:
https://github.com/Thaodan/emacs.d/blob/master/init.org#vterm -
Did you know that you can call #Emacs functions in #vterm like you can do in Eshell?
Using vterm-eval-cmds you can either commands that don't exist in a shell or replace those that exist.
E.g. instead of man you can call the Emacs manapge mode.
You just have to print something to the terminal with the right escape sequence so vterm receives
the right control sequence to know what to call.Look at my config for more examples:
https://github.com/Thaodan/emacs.d/blob/master/init.org#vterm -
Did you know that you can call #Emacs functions in #vterm like you can do in Eshell?
Using vterm-eval-cmds you can either commands that don't exist in a shell or replace those that exist.
E.g. instead of man you can call the Emacs manapge mode.
You just have to print something to the terminal with the right escape sequence so vterm receives
the right control sequence to know what to call.Look at my config for more examples:
https://github.com/Thaodan/emacs.d/blob/master/init.org#vterm -
Did you know that you can call #Emacs functions in #vterm like you can do in Eshell?
Using vterm-eval-cmds you can either commands that don't exist in a shell or replace those that exist.
E.g. instead of man you can call the Emacs manapge mode.
You just have to print something to the terminal with the right escape sequence so vterm receives
the right control sequence to know what to call.Look at my config for more examples:
https://github.com/Thaodan/emacs.d/blob/master/init.org#vterm -
Did you know that you can call #Emacs functions in #vterm like you can do in Eshell?
Using vterm-eval-cmds you can either commands that don't exist in a shell or replace those that exist.
E.g. instead of man you can call the Emacs manapge mode.
You just have to print something to the terminal with the right escape sequence so vterm receives
the right control sequence to know what to call.Look at my config for more examples:
https://github.com/Thaodan/emacs.d/blob/master/init.org#vterm -
-
-
Another simple #Emacs function, this time for sending selected line or region to #vterm:
https://gist.github.com/rytswd/20cd6995d2de05bdc64b9235d0d0d19eI just needed something quick, and put this together, which works as expected. But the visual cue of command is not great, I'll probably work more on this.
-
@emaksovalec EAT (https://codeberg.org/akib/emacs-eat) or #vterm (https://github.com/akermu/emacs-libvterm) may be better for you. I still use #eshell for smaller things that I don't mind blocking, such as waiting for a repo sanity check with #Gentoo.
-
@emaksovalec EAT (https://codeberg.org/akib/emacs-eat) or #vterm (https://github.com/akermu/emacs-libvterm) may be better for you. I still use #eshell for smaller things that I don't mind blocking, such as waiting for a repo sanity check with #Gentoo.
-
🔴 Today on #SystemCrafters Live, we'll take a look at a few different options for using Emacs as a shell or terminal emulator: Eshell, vterm, and Eat! We'll compare them to find the overall best experience in terms of speed, terminal emulation quality, and efficiency of use.
Join us on YouTube or Twitch:
- https://youtube.com/live/HG7pVCa0DVY
- https://twitch.tv/SystemCrafters
- https://systemcrafters.net/live-streams/july-28-2023/🕐 in your time zone: https://time.is/compare/1800_in_Athens
#gnu #emacs #eshell #vterm #eat #terminal #shell #freesoftware
-
🔴 Today on #SystemCrafters Live, we'll take a look at a few different options for using Emacs as a shell or terminal emulator: Eshell, vterm, and Eat! We'll compare them to find the overall best experience in terms of speed, terminal emulation quality, and efficiency of use.
Join us on YouTube or Twitch:
- https://youtube.com/live/HG7pVCa0DVY
- https://twitch.tv/SystemCrafters
- https://systemcrafters.net/live-streams/july-28-2023/🕐 in your time zone: https://time.is/compare/1800_in_Athens
#gnu #emacs #eshell #vterm #eat #terminal #shell #freesoftware
-
🔴 Today on #SystemCrafters Live, we'll take a look at a few different options for using Emacs as a shell or terminal emulator: Eshell, vterm, and Eat! We'll compare them to find the overall best experience in terms of speed, terminal emulation quality, and efficiency of use.
Join us on YouTube or Twitch:
- https://youtube.com/live/HG7pVCa0DVY
- https://twitch.tv/SystemCrafters
- https://systemcrafters.net/live-streams/july-28-2023/🕐 in your time zone: https://time.is/compare/1800_in_Athens
#gnu #emacs #eshell #vterm #eat #terminal #shell #freesoftware
