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

[Feature request] Ability to change console title from w64devkit.ini #115

Closed
MagicalDrizzle opened this issue Mar 2, 2024 · 3 comments
Closed

Comments

@MagicalDrizzle
Copy link

I frequently have both w64devkit and w64devkit-i686 open at the same time, and it can be difficult to check which window belong to which.
I propose the ability to configure the console title from the w64devkit.ini file, like this:

;home = ..\home
;home = %HOMEDRIVE%%HOMEPATH%
;title = w64devkit-i686

For now, a workaround I found is to simply change the code that set the console title: SetConsoleTitleW(u"w64devkit-i686");, and recompile.

@rmyorston
Copy link

It's possible to set the console title with:

printf "\033]0;w64devkit-i686\007"

skeeto added a commit that referenced this issue Mar 2, 2024
While already possible using an ANSI escape sequence, the INI option
affords additional flexibility. It also supports wide titles, which
cannot be done with the busybox-w32 included in w64devkit. See #115.

To support this, I broke up homeconfig() into several functions to be
re-used and composed when handling the new option, such as expanding
environment variables. While doing so, I took the opportunity to remove
several maximum length limitations, like MAX_PATH, and so long paths are
now supported, at least as far as the launcher. I also simplified the
arena to a pair of pointers.

The program now sets $W64DEVKIT before loading the INI so that it is
available during variable expansion of titles.
@skeeto
Copy link
Owner

skeeto commented Mar 2, 2024 via email

skeeto added a commit that referenced this issue Mar 2, 2024
While already possible using an ANSI escape sequence, the INI option
affords additional flexibility. It also supports wide titles, which
cannot be done with the busybox-w32 included in w64devkit. See #115.

To support this, I broke up homeconfig() into several functions to be
re-used and composed when handling the new option, such as expanding
environment variables. While doing so, I took the opportunity to remove
several maximum length limitations, like MAX_PATH, and so long paths are
now supported, at least as far as the launcher. I also simplified the
arena to a pair of pointers.

The program now sets $W64DEVKIT before loading the INI so that it is
available during variable expansion of titles.
@MagicalDrizzle
Copy link
Author

They works fine for me!
Actually with this commit, this may have turned to a "general MinGW launcher", you can put w64devkit.exe and busybox into another mingw "distro", like winlib or llvm-mingw.

skeeto added a commit that referenced this issue Mar 4, 2024
While already possible using an ANSI escape sequence, the INI option
affords additional flexibility. It also supports wide titles, which
cannot be done with the busybox-w32 included in w64devkit. See #115.

To support this, I broke up homeconfig() into several functions to be
re-used and composed when handling the new option, such as expanding
environment variables. While doing so, I took the opportunity to remove
several maximum length limitations, like MAX_PATH, and so long paths are
now supported, at least as far as the launcher. I also simplified the
arena to a pair of pointers.

The program now sets $W64DEVKIT before loading the INI so that it is
available during variable expansion of titles.
@skeeto skeeto closed this as completed Mar 4, 2024
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

No branches or pull requests

3 participants