-
Notifications
You must be signed in to change notification settings - Fork 235
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
Comments
It's possible to set the console title with:
|
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.
I've personally been using the escape sequence suggested by @rmyorston,
but I like the idea of an .ini option as an alternative. The ini-title
branch has an implementation I just whipped up, which I'll merge after
further testing and review. I encourage you to try it out yourself! You
don't even need to build the entire w64devkit to do so, just w64devkit.c.
|
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.
They works fine for me! |
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:For now, a workaround I found is to simply change the code that set the console title:
SetConsoleTitleW(u"w64devkit-i686");
, and recompile.The text was updated successfully, but these errors were encountered: