0

When I enter magit-blame it shows the following lines.

jihae 2020-04-07 14:51 불필요한 파일 삭제, yarn 빠진 부분 추가, public path Eugene Kim 2020-06-04 17:50 config process.env.__DEV__ = isEnvProduction Eugene Kim 2020-03-14 21:43 web start

Although the process.env.__DEV__ = isEnvProduction line is added by jihae

If I do magit-blame-addition on the process.env.__DEV__ = isEnvProduction the lines change to the following

jihae 2020-04-07 14:51 불필요한 파일 삭제, yarn 빠진 부분 추가, public path const isEnvDevelopment = process.env.NODE_ENV === 'development' const isEnvProduction = process.env.NODE_ENV === 'production' process.env.__DEV__ = isEnvProduction Eugene Kim 2020-04-09 15:07 __DEV__

I'm trying to understand what magit is telling me, on first invocation, the line in question is added by Eugene Kim and if i do magit-blame-addition (not sure what exactly it does) it shows the line is added by jihae.

What is going on?

Additionally, if I do magit-blame-quit multiple times after the magit-blame-addition, I end up with modified file content that I'm visiting..

(From file A, if I do magit-blame, magit-blame-addition, magit-blame-quit, mgit-blame-quit, file A is different from what I started with..)

Improve this question
2
  • Do you seem to get the same information if you magit-blame-cycle-style (type c)? Does C-x v g show you different information? Commented Nov 11, 2020 at 2:59
  • How do you "enter magit-blame"? Mention the keys you press. Commented Dec 5, 2020 at 12:24

1 Answer 1

Reset to default
1

Magit provides different "blame variants", which show different information.

Information about these variants can be found in the manual, the most relevant part of that is:

‘C-c M-g b’ (‘magit-blame-addition’) ‘C-c M-g B b’ This command augments each line or chunk of lines in the current file-visiting or blob-visiting buffer with information about what commits last touched these lines. If the buffer visits a revision of that file, then history up to that revision is considered. Otherwise, the file's full history is considered, including uncommitted changes. If Magit-Blame mode is already turned on in the current buffer then blaming is done recursively, by visiting REVISION:FILE (using ‘magit-find-file’), where REVISION is a parent of the revision that added the current line or chunk of lines. ‘C-c M-g r’ (‘magit-blame-removal’) ‘C-c M-g B r’ This command augments each line or chunk of lines in the current blob-visiting buffer with information about the revision that removes it. It cannot be used in file-visiting buffers. Like ‘magit-blame-addition’, this command can be used recursively. ‘C-c M-g f’ (‘magit-blame-reverse’) ‘C-c M-g B f’ This command augments each line or chunk of lines in the current file-visiting or blob-visiting buffer with information about the last revision in which a line still existed. Like ‘magit-blame-addition’, this command can be used recursively.
Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.