Stefan Haller 0df5e08828 Don't set showOutput explicitly ...

It is false by default. This way there's one less change to make in the next
commit.

2025-02-28 10:00:59 +01:00

..

access_commit_properties.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

basic_command.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

check_for_conflicts.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

form_prompts.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

global_context.go

Don't set showOutput explicitly

2025-02-28 10:00:59 +01:00

menu_from_command.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

menu_from_commands_output.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

multiple_contexts.go

Don't set showOutput explicitly

2025-02-28 10:00:59 +01:00

multiple_prompts.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

selected_commit_range.go

Expose {{.SelectedCommitRange}} to custom commands

2025-01-27 08:53:50 +01:00

selected_commit.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

selected_path.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

show_output_in_panel.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

suggestions_command.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00

suggestions_preset.go

Use getters for AppState and UserConfig instead of accessing the fields directly

2024-08-18 10:24:52 +02:00