Git already keeps the last modified date (mtime) in the index and I thought it could be accessed through appropriate commands (git ls-files), though a check of the man pages failed me), also the --format option is slowly being added to more commands. Is the file mtime what is needed?
I don't think that there are easy ways of Git remembering which files you were recently interested in (last opened times?) especially if it wasn't Git that opened the file - you could have opened the file in one of many file editors or IDEs. There is a similar problem in trying to mark as file as being 'no longer interesting' (remove from the interesting list until next time..) I can see one option that is that the IDE maintains a very long list of 'recently opened' files and their times, and then filters that based on the mtimes that are found in the current branch's index, so that only those files that are in/on the current branch tip will be shown in the recently used list. So the IDE lists (internally) the files f1, f5, f3, f2, f9 in order that it opened those files, and then when on 'master' you only see f1, f3, f2 (as that their order for 'master' branch), and when on `feature` you see f1, f3, f9. You (the IDE) could even have a selector to allow 'all' 'current' 'branch-by-name' selections. All that is within the gift of the IDE designers, rather than Git. HtH (Hope that Helps) On Friday, July 1, 2022 at 3:01:07 PM UTC+1 [email protected] wrote: > Hi, > Changing branch is always annoying because IDE only shows most recent used > files independently from the branch you are on. So especially in big > project, after a branch switch you usually have to go find your files > manually. > > What do you think about introducing a new feature for keeping track of > recently used file separately for each branch ? > > e.g > master > file 1 file 2 file 3 > feature > file 1 file 5 file 9 > > Then IDE developer can rely on this file in order to populate recently > used file list. Please let me know your thoughts. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/8baf3340-1a4d-4155-90c0-2367939562fbn%40googlegroups.com.
