Matching "python" as the parent process is too generic to force
filetype: sometimes it happens that a python program launches a shell
and from that shell vimpager would have a broken filetype detection.
You are absolutely right. I've learned a lot of things since I worked on this repo last, and I really need to get back to it and clean everything up. Hopefully soon. Thank you!
Matching "python" as the parent process is too generic to force filetype: sometimes it happens that a python program launches a shell and from that shell vimpager would have a broken filetype detection.
See the following example:
In the new subshell everything would look like a man page, e.g.:
$ python launch-shell.py $ vimpager launch-shell.py
In particular I experienced this with gst-build (https://gitlab.freedesktop.org/gstreamer/gst-build/) which launches a subshell with a modified environment.
So don't match against python when forcing the file type.
The same may apply to Ruby, vimpager is trying too hard sometimes. :)