typometer VS .emacs.d

You can download the tool here: https://github.com/pavelfatin/typometer

Thanks, that's a really nice offer. Well, if your pi can run typometer that would be an ideal thing to test. Use an editor that has good typing latency. That is nothing based on electron or java. Geany or Kate should work. Don't use vim or emans on a terminal as most terminals have terrible typing latency (except xterm and mlterm)

Typometer with 200 characters

There is a great comparison between various terminals' latency https://danluu.com/term-latency/ (it comes up periodically on HN too - https://news.ycombinator.com/item?id=19443076), so once when I was curious if it was just me or if RDP was indeed slower, I did a quick test using the same toolset - https://github.com/pavelfatin/typometer

It is not a super-scientific test since:

0) I didn't spend too much time on this

open -a Spotify --args --disable-smooth-scrolling

You used to be able to disable Chrome's smooth scrolling with chrome://flags/#disable-smooth-scrolling, but that flag was removed for whatever reason.

I'm also surprised by how much faster Firefox's builtin middle mouse click autoscroll is compared to Chrome's ersatz AutoScroll[2] extension.

[0]: https://download.developer.apple.com/Developer_Tools/Additio...

[1]: https://pavelfatin.com/typometer/

[2]: https://chrome.google.com/webstore/detail/autoscroll/occjjkg...

First, about the methodology: I took all my measurements with typometer on an Ubuntu 18.04 computer running X11. I tried Firenvim (both in Firefox and Chrome), Fvim, Gnvim, Goneovim, Neovim-Gtk, Nvim-Qt, Nwin and Uivonim. I couldn't try Neovide because it didn't run on my computer. The terminal I tried was Kitty, which has better latency than Alacritty.

The first thing to do is to try and measure latency to confirm your feeling. You can use something like typometer ( https://github.com/pavelfatin/typometer ) to do that.

In my Helm, I have to actively choose the candidate to confirm it. So I can type in both paths that are shorter or longer then existing ones. I even made a video to demonstrate it, the thread was relatively recently up I think. My Helm setup is here it if helps you, find Helm in the list of packages.

I also use Helm, and I have no problems. Just keep typing, once you typed a letter that does not exist in a path name it will stop completing. I don't know if I have some special option enabled/disabled; I don't think you need it, but you can see my Helm config (just scroll down untill you find "Helm").

When all deps are installed,my config is over 200 packages. On my Arch Linux desktop I built in 2016, with i7 4.6k (haswell) it starts ~0.7 secs, but init time will be anything between 0.5 ~ 0.8 secs, i guess depending on what system does. So all things same, init time will vary.

I am using it in my literate org-config. If you scroll down, there is a big list of packages, and I have done a small wrapper around helm-imenu, to jump to a package configuration. Looks like this.

That does not work for completions, at least not for me. It works for keymaps, so you can have mode specific (or really any) keymap in src blocks. I have been using his method myself in my init file generator for quite a while now. If you (or anyone) knows/have an idea how to expand it for completions and eldoc, I would be really happy to hear.

I don't know what if it is more robust but I use more or less plain dired with just some options turned on to make it less noisy to look at, but I don't "manage" my files so much to be honest. I do use some extras from dired-hacks, and my own dired-auto-readme, but that is about it. You can check my setup if you wish, look at "dired" under packages and in Lisp folder for "dired-extras.el".

I personally put all custom lisp in a special directory and scrape autoloads myself. If you are curious, you can check under "generator", functions generate-autoloads and collect-autoloads, but there is nothing special, just plain text search and copy-paste programmatically. I don't recommend to use it though.