Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use a dedicated configuration file for mintty. #32

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

RLessmann
Copy link

Adding a dedicated mintty rc file per launcher. The mintty rc file follows the same naming convention as the *.ini file and is passed as confg file option ('-c') to mintty. This will allow to configure the mintty appearance based on the launched MSYS environment.

The mintty rc file follows the same naming convention as the *.ini file
and is passed as confg file option ('-c') to mintty. This will allow to
configure the mintty appearance based on the launched MSYS
environment.
@Biswa96
Copy link
Member

Biswa96 commented Jan 17, 2025

Adding a dedicated mintty rc file per launcher.

What kind of config does mintty need separately other than ~/.minttyrc ? Would this new config file override the options in ~/.minttyrc ?

@RLessmann
Copy link
Author

Yes you are correct, the default config is ~/.minttyrc. But all the launchers start the mintty using the same config file. If someone likes to change the background for the Mingw64 tty, but not the Mingw32 tty, he cannot do this, due to the same config. Using different configuration files will allow this.

Also I'm suggesting to use the command line option -c in lower case. Mintty will read the default config file and afterwards the specific config file given by -c. Means also the ~/.minttyrc is fully considered.
Changes made to the configuration, by using the UI, will go to the specific configuration file.

I belief this can be a good improvement for the launchers. I used to configure my terminals different to easy differentiate Mingw32 from Mingw64, this was my main objective.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants