4 ms·
In an older version there was autocompletion for typing. You could type /tmp/a. and it would autocomplete it to /tmp/a.png It is a good idea, but I type too f
by benibela 6y ago
In an older version there was autocompletion for typing.
You could type /tmp/a. and it would autocomplete it to /tmp/a.png
It is a good idea, but I type too fast. So I would write /tmp/a.png and then the autocompletion triggered and replace it with /tmp/a.pngpng
- enriquto 6y ago> You could type /tmp/a. and it would autocomplete it to /tmp/a.png > > It is a good idea, but I type too fast. So I would write /tmp/a.png and then the autocompletion triggered and replace it with /tmp/a.pngpng This is so sad. Autocompletion of filenames should work perfectly no matter the conditions. If "ls" can list tens of thousands of files in a fraction of a second, there's no reason that autocomplete has some delay. I can see why this happens, maybe you have a thousand images in /tmp and the file picker is opening them all to compute their thumbnails (which in my opinion is useless, but whatever). Then it uses quite a few kernel threads and it clogs the system, making the completion to fail. But it sounds like this problem should was already solved many years ago, and that modern "improvements" of the file picker made it fail.