3 ms·

> * super powerful, easy to use, integrated command and fuzzy file search, also with a good UX. Sounds like you should try ivy and its companions. Ivy offers

> * super powerful, easy to use, integrated command and fuzzy file search, also with a good UX. Sounds like you should try ivy and its companions. Ivy offers fuzzy matching for all operations in Emacs (e.g., switching buffers, opening files, looking up documentation) and the counsel packages (e.g., counsel-rg) use that same interface to interact with external tools such as ripgrep or git grep. Ivy has completely taken over my Emacs experience, and it did not require a lot of configuration, just a few keybindings. As for a terminal, I don't have a Windows machine to test, but `M-x ansi-term` is pretty much exactly like a regular terminal: you can run any program in it, including htop or even vim.

oblio 8y ago
M-x ansi-term ask for [...]/emacs/libexec/emacs/26.1/x86_64-w64-mingw32/cmdproxy.exe and then throws "Spawning child process: Invalid argument". M-x term does the same. Those lead down this rabbit hole: https://stackoverflow.com/questions/4535432/terminal-in-emacs-in-windows-error-message-spawning-child-process-invalid-a https://stackoverflow.com/questions/4535432/terminal-in-emac... M-x shell seems kind of dumb. M-x eshell is not a usable shell. Anyway, everything feels and is very stitched together. (I also don't understand why declaring VS Code better than Emacs for my use case is downvoted, since it's the truth...).
- gnuvince 8y ago
  > M-x ansi-term ask for [...]/emacs/libexec/emacs/26.1/x86_64-w64-mingw32/cmdproxy.exe and then throws "Spawning child process: Invalid argument". Ah, that's too bad.
  - oblio 8y ago
    I guess that's what I get for being a Vim user :o)
xte 8y ago
EXWM/Fulltime Emacs user here... Well... No, ansi-term, sane-term etc are not like regular terminals, they can work for simple things but they are limited, limiting and buggy... When I start living in Emacs I reduce significantly the dependency of the shell (tramp and dired do most of the business) and start using eshell a bit, but I still use terminator when I need a real terminal...
- oblio 8y ago
  For all its flaws, the VS Code terminal is quite strong. I've been putting it through its paces recently and if only they'd offer an option for real full screen and proper splits, it could almost get all the way there.

oblio 8y ago

M-x ansi-term ask for [...]/emacs/libexec/emacs/26.1/x86_64-w64-mingw32/cmdproxy.exe and then throws "Spawning child process: Invalid argument". M-x term does the same. Those lead down this rabbit hole: https://stackoverflow.com/questions/4535432/terminal-in-emacs-in-windows-error-message-spawning-child-process-invalid-a https://stackoverflow.com/questions/4535432/terminal-in-emac... M-x shell seems kind of dumb. M-x eshell is not a usable shell. Anyway, everything feels and is very stitched together. (I also don't understand why declaring VS Code better than Emacs for my use case is downvoted, since it's the truth...).

gnuvince 8y ago
> M-x ansi-term ask for [...]/emacs/libexec/emacs/26.1/x86_64-w64-mingw32/cmdproxy.exe and then throws "Spawning child process: Invalid argument". Ah, that's too bad.
- oblio 8y ago
  I guess that's what I get for being a Vim user :o)

xte 8y ago

EXWM/Fulltime Emacs user here... Well... No, ansi-term, sane-term etc are not like regular terminals, they can work for simple things but they are limited, limiting and buggy... When I start living in Emacs I reduce significantly the dependency of the shell (tramp and dired do most of the business) and start using eshell a bit, but I still use terminator when I need a real terminal...

oblio 8y ago
For all its flaws, the VS Code terminal is quite strong. I've been putting it through its paces recently and if only they'd offer an option for real full screen and proper splits, it could almost get all the way there.