| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
| |
This catches downstream consumers of neovim off guard when using neovim in an
esoteric environment not tested in our own CI.
Closes https://github.com/neovim/neovim/issues/22932
|
|
|
|
|
|
|
| |
Having to specify CI_BUILD for every CI job requires boilerplate. More
importantly, it's easy to forget to enable CI_BUILD, as seen by
8a20f9f98a90a7a43aea08fcde2c40a5356b4f7b. It's simpler to remember to
turn CI_BUILD off when a job errors instead of remembering that every
new job should have CI_BUILD on.
|
| |
|
|
|
|
|
| |
generate_type2_appimage is unmaintained, and lacks a way to rename the appimage file.
fix #9893
|
|
|
|
|
| |
closes #9320
closes #9128
|
|
|
|
|
|
|
|
|
| |
AppImage sets $ARGV0 which breaks zsh.
Hack around this in our appimage.
fixes #9341
ref https://github.com/AppImage/AppImageKit/issues/852
[ci skip]
|
|
|
|
|
|
| |
This will allow users to use AppImageUpdate to update their AppImage.
It requires publishing the created zsync file alongside the appimage
file for the releases.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Avoids attempt to install manpage to system location.
Also:
- Don't attempt `nvim --version` until after it was built.
- Remove unnecessary `mkdir`.
|
|
scripts/genappimage.sh produces an executable:
nvim-${NVIM_VERSION}-glibc${GLIBC_VERSION}-${ARCHITECTURE}.AppImage
Closes #6083
|