You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi everyone, I was wondering if I could get your agreement on a couple of notes regarding the next version of Cmder:
Firstly, we should not release another 1.3.x and should instead make a 1.4 release due to the new exciting features by @daxgames (including speed optimization and built-in Windows Terminal support). In addition to this, I propose updating the main screenshot at README.md to reflect the Windows Terminal + Cmder to give Cmder a more fresh look. I'll also update the website for a more modern, stream-lined and clean look.
Second, I propose organizing cluttered information from the README.md into groups. I'd like to move details from README.md into the Wiki and keep README.md simple and clean, and provide links to the Wiki in the README.md. Besides being more organized, this also allows us to update the documentation more frequently and also make use of community edits. I will monitor changes for possible vandalism.
We should consider to either completely dropping x86 (32-bit) binaries that are included in the package (e.g. both ConEmu and Clink has those), or alternatively provide an optional launcher file that is capable of running under 32 bit. I can only recall one individual that was still using a 32-bit machine and was asking for this. Personally I'm in favor of completely removing 32-bit support from Cmder to reduce the size and improve simplicity. This also involves updating the init.bat to de-reference x86 32-bit in it. In my opinon, the only supported arches in init.bat should be x86_64, ARM and ARM64. (Hopefully ARM32 will also be deprecated soon). Preferably this should be done now since git-for-windows has already dropped 32-bit support. If you accept, I'll modify the vendor scripts to strip any x84 32-bit editions of the vendored dependencies.
I'll be happy to hear your opinions; if you agree with the notes above, I'm planning to apply them soon.
The Windows Terminal support development is a great and welcomed new addition to the Cmder, and I'm sure together with the speed optimizations by Dax they're going to hugely improve the user experience of Cmder.
In the meantime, I'd appreciate it if you could please also take a look at the backlog at #2788 and tell me your opinions; once I'm a bit free from my ongoing projects I'm planning to merge the current PRs by Dax and others, and then work on the backlog items as well.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
@cmderdev/trusted-contributors @Stanzilla @daxgames
Hi everyone, I was wondering if I could get your agreement on a couple of notes regarding the next version of Cmder:
init.bat
to de-reference x86 32-bit in it. In my opinon, the only supportedarch
es ininit.bat
should be x86_64, ARM and ARM64. (Hopefully ARM32 will also be deprecated soon). Preferably this should be done now since git-for-windows has already dropped 32-bit support. If you accept, I'll modify the vendor scripts to strip any x84 32-bit editions of the vendored dependencies.I'll be happy to hear your opinions; if you agree with the notes above, I'm planning to apply them soon.
The Windows Terminal support development is a great and welcomed new addition to the Cmder, and I'm sure together with the speed optimizations by Dax they're going to hugely improve the user experience of Cmder.
In the meantime, I'd appreciate it if you could please also take a look at the backlog at #2788 and tell me your opinions; once I'm a bit free from my ongoing projects I'm planning to merge the current PRs by Dax and others, and then work on the backlog items as well.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions