Yeah, and then filter out the events in the directory to find out when the correct file changed, etc. That is exactly what I would want the tool to abstract for me.
Finding a file I already know the name of is not a problem. And Ctrl/Cmd+F works just fine for that.
What I personally use the file explorer in a PR for is for various other things.
* Quick overview of the "complexity" of the change. If I see a huge list of files or files "all over the place" that let's my spidey senses tingle. Much more so than a simple "X files changed" bit of text could.
* Navigating around the changeset by most interesting area first. E.g. I might see at a glance that there are changes in three folders of interest and the rest are less important. I don't read PRs from top to bottom like Github tries to make you. I find that unnatural.
* I can also easily, visually, jump around between these areas/files to cross references changes without having to remember their names or scrolling a lot.
* In large changes (lots of files in lots of places - it happens sometimes) I can collapse folders that are not interesting or that I'm done with. The fact that I already opened a file once does not tell me anything really as I tend to jump around between files to cross reference things. In fact one great feature to have is to mark a file as "unread" again. Which IIRC Crucible had.
YMMV as always and Github does have this as well now, so we're good :)
seems a way to gather all kinds of extra clutter on your box. keep notes of things you do :-) it just requires a txt editor present in most operating systems by default. if you document carefuly, you can even just add #!/bin/sh in the top to automate ;D but it's atleast honest comment :D
I found myself using this each day more. If you want to watch everything that happens inside a directory (merged into a single window) - like I always do, you will need a command similar to:
Multitail is smart enough to figure out if files were erased/created/re-created etc - on the fly. This saves quite a bit of time for me. Since I only heard of this recently, I figured it might be a good idea to spread the word...
The software is a big buggy, but I still like it a lot.
well I usually have trouble remembering the exact name of the file I was editing 2 months ago? :) . Now if there is a plugin to have rg look through the last few hundred files that I've edited that would be a game changer.
What I appreciated most about 'abcde' was that just prior to the rip it would open up the CDDB output in 'vim' and allow quick and easy edits to what are, sometimes, horrific titling and track entries ...
It's a very nice workflow and avoids a lot of cleanup ...
Note that the linked project was not developed by me.
However I find it extremely useful when dealing with large file-systems, especially in migration scenarios. (I used to achieve this with complex `bash` scripts, but next time I'll give it a try.)
reply