Whenever my NFS mount becomes unavailable, e.g. because I switched my WLAN, trying tab-completion results in a frozen terminal.
I mount it like that: sudo mount -t nfs -o soft 192.168.2.XXX:/XXX /mnt/XXX, and I use v22.5.1 on Linux Mint 20.1.
I'm not sure how much of an edge case that is for the average user, but I personally would really like to see some kind of timeout and error-handling for unavailable directories.
Here is a stack trace that may or may not be helpful:
Traceback (most recent call last):
File "/usr/bin/autojump", line 320, in <module>
sys.exit(main(parse_arguments()))
File "/usr/bin/autojump", line 266, in main
handle_tab_completion(
File "/usr/bin/autojump", line 220, in handle_tab_completion
print_tab_menu(
File "/usr/share/autojump/autojump_utils.py", line 159, in print_tab_menu
for i, entry in enumerate(tab_entries):
File "/usr/bin/autojump", line 193, in <lambda>
lambda entry: not is_cwd(entry) and path_exists(entry),
File "/usr/bin/autojump", line 180, in is_cwd
return os.path.realpath(entry.path) == pwd
File "/usr/lib/python3.8/posixpath.py", line 391, in realpath
path, ok = _joinrealpath(filename[:0], filename, {})
File "/usr/lib/python3.8/posixpath.py", line 425, in _joinrealpath
if not islink(newpath):
File "/usr/lib/python3.8/posixpath.py", line 167, in islink
st = os.lstat(path)
KeyboardInterrupt
Whenever my NFS mount becomes unavailable, e.g. because I switched my WLAN, trying tab-completion results in a frozen terminal. I mount it like that:
sudo mount -t nfs -o soft 192.168.2.XXX:/XXX /mnt/XXX
, and I use v22.5.1 on Linux Mint 20.1.I'm not sure how much of an edge case that is for the average user, but I personally would really like to see some kind of timeout and error-handling for unavailable directories.
Here is a stack trace that may or may not be helpful: