I recently found LosslessCut (https://github.com/mifi/lossless-cut) that is basically a GUI for ffmpeg, you can make simple edits without re-encoding the stream.
git blame shows only who made the last change. Maybe that person only changed the name of a variable, applied a codestyle change, moved a function declaration to another file or many other things that the change was almost irrelevant to the code behavior.
There are a few options that help you out with this:
-M Detect moved or copied lines within a file
-C In addition to -M, detect lines moved or copied from other files that were modified in the same commit.
--ignore-rev <rev> Ignore changes made by the revision when assigning blame, as if the change never happened
--ignore-revs-file <file> Ignore revisions listed in file
I wish they would make long option names for everything, including -C and -M. (Perhaps I should contribute that..)
I use short options interactively on the command line, but in scripts and when communicating with other people, I prefer longer options because they are self-documenting and can catch most typos. (For a long option, typos are more likely to result in an invalid option, and thus an error message. For one-letter options, a typo could result in anything..)
I recommend just skipping blame and going to git log -L to see the full evolution of a range of lines, I set up a little keybind in vim which does this for the current visual selection and it works much better than blame.
This feature is built into Emacs, no Magit needed. It's the vc-region-history command, bound to `C-x v h` by default. It works across all version control systems Emacs supports, not just git.
My config is kind of cluttered so this is a simplified version without dependencies. Glogr is for range history, GLogf for file history and <leader>gc for showing a commit based on hash:
These are the things that can be a chore to find in man pages. There needs to be a way to "sort" man page elements to show most commonly used switches first.
They don't wear helmets because they aren't zooming around like Lance Armstrong. The risk of accidents with head injuries a helmet would help against is limited. Same thing why you don't wear a helmet when you go by car although an occupants risk of head injuries in a typical accident is comparable.
You can't really equate safety gear across different modes of transportation, otherwise if you wear a seat belt when riding in a car then why not wear a seat belt when riding a bicycle?
In large doses over extended periods of time, they do change how someone thinks and perceives the world, perhaps for the worse. See stories of amphetamine psychosis. Those somewhat mirror a type of extended bad experience after using psychedelics, often called dark nights.
He doesn't say it was written while high. He is wondering if H knew the effects of psychedelics and maybe tried to replicate the feeling in the reader.
