ace-window VS emacs-libvterm

Thanks that is helpful. I do have a question though. Is there any plugin similar to ace-window? I frequently have a situation where I have two frames (basically two windows) that are connected to the same Emacs process, and I am jumping between buffers in both frames.

Looks good. But https://github.com/abo-abo/ace-window was a game-changer for me :-)

take a look at https://github.com/abo-abo/ace-window

I recently started using workspaces in my workflow, and although I know many packages are available in Emacs such as the ones mentioned in the comments, but what worked for me so far is just make a second frame and use ace-window with the variable aw-scope set to 'frame. And from there I just move one frame to the appropriate workspace in my desktop environment and that's it. It's worth keeping in mind that the buffers are still shared so might not be the perfect workspace experience, but I don't think that matters in Emacs.

Try the ace-window package. I think you're referring to C-x o which is bound to other-window.

Also highly recommend ace-window.

I'd like to use ffap (to open files/dirs) in windows I select with ace-window (https://github.com/abo-abo/ace-window). Similar to what aw-switch-buffer-in-window and aw-switch-buffer-other-window do, but with find-file-at-point instead of buffer selection. Crucially, the point means the where I am when the function is called.

If someone has a big monitor I recommend changing C-x 1 delete-other-windowsto revert to have 2 windows open, (like in this config) and using ace-window to navigate to your many windows.

Ace-Window is meant to replace `other-window' by assigning each window a short, unique label

Also, look into vterm_prompt_end to get this updated vterm-buffer-local anytime your prompt emits the cwd. https://github.com/akermu/emacs-libvterm

Emacs or term? If the latter, I'd recommend using vterm if it is a possibility for you - https://github.com/akermu/emacs-libvterm

They are actually working on even better Emacs integration. Granted, vterm is an external library, so there will always be a layer between the editor and the terminal.

I've followed the steps shown in the README: sh vterm_printf() { if [ -n "$TMUX" ] && ([ "${TERM%%-*}" = "tmux" ] || [ "${TERM%%-*}" = "screen" ]); then # Tell tmux to pass the escape sequences through printf "\ePtmux;\e\e]%s\007\e\\" "$1" elif [ "${TERM%%-*}" = "screen" ]; then # GNU screen (screen, screen-256color, screen-256color-bce) printf "\eP\e]%s\007\e\\" "$1" else printf "\e]%s\e\\" "$1" fi } vterm_prompt_end() { vterm_printf "51;A$(whoami)@$(hostname):$(pwd)" } setopt PROMPT_SUBST PROMPT=$PROMPT'%{$(vterm_prompt_end)%}' but it is simply not working.

[1]https://github.com/ohmyzsh/ohmyzsh/tree/master/plugins/fzf [2]https://github.com/romkatv/powerlevel10k [3]https://starship.rs/ [4]https://github.com/tmux/tmux [5]https://github.com/ahendriksen/ob-tmux [6]https://github.com/akermu/emacs-libvterm [7]https://github.com/tmux-plugins/tpm

Have checked out https://github.com/akermu/emacs-libvterm? It has everything you need to know. Since you are a developer I expect it will be easy for you. Thanks for sharing your experience:)

Install the absolutely excellent vterm package: https://github.com/akermu/emacs-libvterm

https://github.com/akermu/emacs-libvterm is a possible best of both worlds that I haven't tried yet.