Kurt's questions

I am on Ubuntu 18.04/20.04.

While editing text in a terminal or in any text editing environments, I can navigate back and forth between neighboring words or delimiters of a string with Ctrl + → (or ←). These delimiters seem to be special characters but alphabets and numbers, and include ;, ., -, /, \, (the space), etc.

In Ubuntu, is there any way to change the default behavior of these keybindings? Specifically, I want Ctrl + → to regard every special character except as a part of a word, so I can move between words without stopping before/after ., -, / which are quite common in file names. vi editor allows to customize it (Customising word separators in vi), and I am curious if there is an equivalent that works for bash and GNOME.

I'm on a newly installed Ubuntu 20.04 laptop (ASUS M413). I shortly found . (and >) cannot be typed after a screen timeout, while every other key works fine. Reboot fixes every problem but neither driver nor firmware updates do work. I should try reinstalling Ubuntu, but before that I'd like to ask somebody had similar problem to this.

In GNOME desktop, how can I minimize/restore all windows of a specific application?

I know the shortcut Super + d hides all normal windows and then restores them, but I'm looking for its equivalent that works only for windows of a given application (for example, the application running in the current window).

I'm using inotifywait to keep track of events on a single file (instead of a directory), as

$ inotifywait -m -e open -e close -e move myfile.txt

When I open and edit the file, the logs are printed as expected.

Setting up watches.
Watches established.
myfile.txt OPEN 
myfile.txt CLOSE_NOWRITE,CLOSE 

But inotify never emits either MOVED_IN, MOVED_FROM events (not even DELETE_SELF) when I rename the file. On the other hand, if I watch the directory containing myfile.txt, rather than a single file, the events are emitted as usual.

One strange point to me is that, opening and closing the renamed file still log events.

myfile.txt OPEN 
myfile.txt CLOSE_NOWRITE,CLOSE 

At this point, my file is not myfile.txt but has another name. Notably, inotify does not track any event evoked working with a newly created myfile.txt.

My questions are:

1. How can I correctly track the "renaming" events of a single file with inotifywait, while not watching a full directory?

2. How can I get the current name of a single file watched? --format "%f" option seems to always print the original file name passed to inotifywait even though the file is renamed, as shown above.

3. I'm looking for a sort of "rename history logger" that works for a given set of files scattered in the filesystem. Are there any alternatives to inotify, which can be used for this specific purpose?