Beta release?

[Aman9das]

I use NixOS and the last update to the package is a few years old.. Kindly consider a beta or alpha release. It would be a great help!

[ahrm]

I have created a preview build of the development branch here: https://github.com/ahrm/sioyek/releases/tag/sioyek3-alpha0 . I have not tested the binaries on macos or windows though, it is quite possible that they don't work.

[badrbouslikhin]

Indeed the macOS ARM build can't be opened.

[tennysontbardwell]

@ahrm I am personally excited to have several bugfixes that are in development, and I daily-drive a macOS ARM device. I have a mix of Nix and Homebrew as my package manager. Is there something specific that I can do to assist?

For example, are their build instructions that I can follow, or can I modify the nix package dependencies (link) to build development.

I spent some time on this yesterday, but was unable to figure out how to upgrade from Qt5 to Qt6 in nix (new to nix).

If you think that I can help, lovely. Else, no pressure to fix prioritize a beta release for macOS ARM, since 2.0.0 is stable and more than usable.

[ahrm]

Is there any error when opening the mac binary from console? (the binary can be found if you open the package like a directory).

For example, are their build instructions that I can follow, or can I modify the nix package dependencies (link) to build development.

You can follow the build-mac steps which we use to create the preview release in https://github.com/ahrm/sioyek/blob/main/.github/workflows/preview_release.yml and see if you can reproduce the issue. Sorry I am not familiar with nix so I can't help you there.

[tennysontbardwell]

Oh, my apologies, this[1] does open. It is only the (probably overbearing) macOS quarantine security feature. The fix is:

xattr -c <path/to/sioyek.app>

[1] The arm version of sioyek3-alpha0

[tennysontbardwell]

A few other thoughts:

• I am having a few odd issues with key bindings.
  • (fixed with config change) At first d was unmapped, but I had both d, db, dh, and dp bound. It seems like the longer keybindings now win, so I changed the others.
  • (sill troubling me) <C-p> and <C-n> in menu bars no longer work. I am not sure what caused this. I found Some suggestions about menus #929 and tried to add [m]control_menu(prev_suggestion) <C-p> but nothing happened (including no error messages)
• While I have not seen any issues with database migration thus far, that was a concern. Still, I forgot to backup my database before opening the new version. When making breaking database api changes, maybe you could backup the database and/or warn the user? Just a thought

[ahrm]

tried to add [m]control_menu(prev_suggestion) <C-p> but nothing happened (including no error messages)

I assume you want <C-p> to go up in menus? In that case you should add something like this:

[m]control_menu('up')

When making breaking database api changes, maybe you could backup the database and/or warn the user?

This will indeed be the case for the final release of sioyek, that's why this is an alpha preview release.

[tennysontbardwell]

[m]control_menu('up') works will, thank you kindly.

[EBAdev]

I downloaded the alpha release for the Mac arm build, and did the fix that @tennysontbardwell mentioned. I am now able to open sioyek manually however the connection with VimTex seems to be broken. When I try to open the application via vimtex, to establish a synctex connection vimtex simply responds with:

"VimTeX: sioyek is not executable!"

Does anyone know how to fix this?

[Rudolfo00]

I downloaded the alpha release for the Mac arm build, and did the fix that @tennysontbardwell mentioned. I am now able to open sioyek manually however the connection with VimTex seems to be broken. When I try to open the application via vimtex, to establish a synctex connection vimtex simply responds with:

"VimTeX: sioyek is not executable!"

Does anyone know how to fix this?

You have to provide the explicit path to your sioyek executable via let g:vimtex_view_sioyek_exe = "/Applications/sioyek.app/Contents/MacOS/sioyek" (or wherever you've put the executable).