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
zsh: locking failed for /c/Users/Konfekt/.zsh_history: no such file or directory: reading anyway #129
Comments
I'm not zsh user. Feel free to investigate it. |
As a starting point for contribution to this project, perhaps one of the maintainers could explain to us users what msys2 patches in these unix packages to make them work under Msys2? |
Converting a package from Arch Linux to MSYS2 (as opposed to MSYS2/MinGW-w64) often involves nothing more than running makepkg .. and then when you find problems you investigate that problem and fix it and then create a patch. I don't really understand what you mean. We've got hundreds of patches, and they're all publicly available for you to look through. You should probably pick the package most similar to the one you're looking to patch, so for zsh, I'd examine the patches that were necessary for bash:
|
Ok, already this shed light on how your package conversion works as I had not the least idea before. I had the hope there is a general recipe other than trial and error to port packages that evolved over time and could be shared to speed up contributions. For example, do you take the patches from Cygwin and adapt them to msys2 or start patching straight from Arch Linux? |
We could/should document it better, but really, MSYS2 stuff is generally quite smooth thanks to Cygwin providing a good POSIX emulation layer (and patches as you mention). MSYS2/MinGW-w64 is more trouble mostly because our packages:
.. the best reference for all MSYS2 and MSYS2/MinGW-w64 is the work already done and when you run into specific problems ask on IRC (#msys2 on oftc) or the mailing list, or even as issues in your WIP branches in fork(s) of this or MINGW-packages using @ syntax. |
Thanks! |
If there is a file
zsh_history
then the error messageappears. If there is no such file, then no error message, but also no zsh history.
The text was updated successfully, but these errors were encountered: