.bash_history gets updated? No, crap, must be something else. BTW, on my system
geany and
gedit-plugin-terminal require VTE which installs
/etc/profile.d/vte.sh which, in turn, sets PROMPT_COMMAND thusly:
Code:
$ echo $PROMPT_COMMAND
history -a; history -n; printf "\033]0;%s@%s:%s\007" "${USER}" "${HOSTNAME%%.*}" "${PWD/#$HOME/\~}"
The thread name is wrong. What
ls -l shows by default is the modification time (mtime). It's the time of the last write.
Use
ls -cl to display the status change time (ctime) instead. It changes e.g. when the file gets moved/renamed or its ownership/permissions are changed.
Use
stat %w to display the file creation time (birthtime).
From the
GNU Coreutils manual:
Quote:
Naively, a file’s atime, mtime, and ctime are set to the current time whenever you read, write, or change the attributes of the file respectively, and searching a directory counts as reading it. A file’s atime and mtime can also be set directly, via the touch command (see touch invocation). In practice, though, timestamps are not updated quite that way.
For efficiency reasons, many systems are lazy about updating atimes: when a program accesses a file, they may delay updating the file’s atime, or may not update the file’s atime if the file has been accessed recently, or may not update the atime at all. Similar laziness, though typically not quite so extreme, applies to mtimes and ctimes.
|
