4 commits

Author	SHA1	Message	Date
Stefan Haller	0140e19eb2	Separate the runs in the debug log with a blank line ... This makes it much easier to find where a new run starts; previously you had to search for `git --version` for that.	2026-08-15 09:48:11 +02:00
Stefan Haller	d298a7ce4b	Use nano-second time stamp granularity in the debug log ... It's overkill for most purposes, but I'd say it doesn't hurt to have the extra resolution available in the raw JSON data for the few cases where it's useful. Have "lazygit -l" print them with milli-second resolution; that seems to be a good middle ground.	2026-08-15 09:47:32 +02:00
Jesse Duffield	e0ecc9e835	Allow global logging when developing ... I'll be honest, for all I know logging should be global in general: it is a pain to pass a logger to any struct that needs it. But smart people on the internet tell me otherwise, and I do like the idea of not having any global variables lying around. Nonetheless, I often need to log things when locally debugging and that's a different kind of logging than the kind you would include in the actual released binary. For example if I want to log something from gocui, I would rather not have gocui depend on lazygit's logging setup.	2023-05-25 18:31:32 +10:00
Jesse Duffield	cd5b041b0f	clearer separation of concerns when bootstrapping application	2022-05-07 16:02:04 +10:00