Marius Gedminas

> On cloning the repo, the file in question is hidden in a zip file: Oh, interesting! It must've been extracted while running the test suite. A quick `git clean...

(For the record, using :CommandTFlush instead of Ctrl+F does pay attention to changes in &wildignore)

Please don't use 2to3. Many projects started on that road and ended up regretting it. It's not that hard to have a single codebase that supports Python 2 and Python...

I am baffled: I have a machine with Ubuntu 18.04 LTS (bash 4.4.20(1)-release, bash-completion 1:2.8-1ubuntu1) where `mutt -f =` eats the `=` and where a similar fix would be needed....

I've found a solution that works on both Ubuntu 18.04 and 20.10, but I don't entirely understand the situation: https://github.com/mgedmin/dotfiles/commit/4758e78e2ea8e57636873d79e796691eff237ed2 Update: I've incorporated that solution into this PR. The more...

Welp this doesn't actually work on Ubuntu 20.10. I thought I'd tested it! Back to the drawing board...

> Welp this doesn't actually work on Ubuntu 20.10. I thought I'd tested it! I did test it, and `mutt -f =fold` is correctly expanded to `mutt -f =folder`. What...

I now have tests for this in #467. Without this fix they fail as follows: ``` ____________________________________ TestMutt.test_plus_is_not_eaten ____________________________________ self = , completion = @pytest.mark.complete("mutt -F muttrc -f +f", require_cmd=True,...

> Packages get included in docker images automatically, the image builds reference test/test-cmd-list.txt to determine what gets pulled in, neomutt in debian buster (10) is old enough that it still...

So I have some tests in #467. In my environment 'mutt' is an alias for 'neomutt', so the tests I added fail without this fix. I could copy the `_muttconfvar`...