emacs-libvterm VS vlfi

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.

That is essentially what VLF[1] does in Emacs. It reads in discrete chunks of the file at a time and doesn’t load the next one till you try to display it. Doesn’t require any fancy data structures, just some extra book keeping and mechanics.

[1] https://github.com/m00natic/vlfi

That is an issue both related to Emacs' internal representation of buffers and modes working in the background on the data in buffers of very large files, for which there are some workarounds like vlf-mode. See for example (info "(emacs) Long Lines") for similar issues with long lines and a solution more similar to what all those other editors you mention are doing to mitigate the issue of large files and large lines.

You can edit gigabyte-large files with no trouble vlf.el https://github.com/m00natic/vlfi – though it's a bit of a separate universe, you have to use vlf-occur instead of occur to find matches over all gigabytes of the file

;; To have it offered when opening large files:

For arbitrarily large files (think GB) in terms of size of the data stored you may use e.g. vlfi.

You can use vlf package to open large files

You know how "there's an app for that" used to be a thing? Well, there's an elisp package for that: https://github.com/m00natic/vlfi

Theres always: https://github.com/m00natic/vlfi

I’m aware of a few potential solutions including: dired-async and async-shell-command. There’s also https://github.com/m00natic/vlfi for viewing large files, but I don’t know how to address GPG pinentry and TRAMP issues very well.

I think you might enjoy this mode: vlfi. It is available in the standard Elpa package listing.