Sigil 2.8.0 Released

[democrite]

Will do. Thank you very much.

[KevinH]

Got it and I can recreate the bug with a simple rename of just the image file pointed to by that altimage.

After the rename the altimage link was not updated.

I am on it.

[democrite]

Thank you Kevin.

[KevinH]

Thank you for your bug report! I just pushed a fix for this to master. It seems the previous fix was slightly incomplete depending on conditions. That has been rectified.

If you desperately need an updated build with this fix, please let me know for what platform and I will grab the CI build being made with this change and post it for you.

[democrite]

Thank you very much Kevin. I have no urgent need of such since I think it's the first time I encountered that issue as I don't typically have epubs with math tags. Whenever the next release comes out, that'll be a-okay.

[democrite]

Concerning the issue with opening files in an external editor whether BBEdit on macOS or other, I'm not that familar but asking Perplexity, it recommended using native Qt methods. Maybe that'd help with keeping PageEdit open on macOS. Seems one can also have PageEdit open a file at a particular line such as if one wanted to maintain scroll position.

The shell command open is convenient, but it is a wrapper around the same macOS launching/opening machinery rather than the primary API you should build against. If you use Qt or AppKit APIs directly, you avoid shell quoting issues, argument parsing ambiguity, and the mismatch between command-line flags and already-running GUI apps that only receive open events.

https://www.perplexity.ai/search/iss...RM6OSWhHEfW90A

I have no opinion on if it is better or not, but it's an option.

[KevinH]

That has already been fixed with in master, so no worries but using Qt directly to launch an app is also possible if trouble happens in the future, but Qt strongly recommends using "open" in its SubProcess calls on MacOS.

[democrite]

Sounds good.

Curious about one thing. The environment variable to use native file dialogs, does it seem like maybe some places such is not used such as Add Existing Files, Save As, Save A Copy, and perhaps other? I've had it set for a while and it appears fine within plugins when prompting to save the file. The above mentioned I just tried and they appear with the Qt style dialog.

At least on macOS, when there are instances such as when I want to navigate to some random folder, I can drag and drop from the Finder which makes some operations quicker. If possible, it'd be nice.

[KevinH]

There is an environment var to force native file dialogs but like all environment vars on MacOS, unless you are launching a gui Mac app via Terminal.app they are ignored. Over the years, there have been many ways to pass env vars to Mac gui apps but Apple kept changing and breaking them. That is one of the reasons that Sigil has its own env-vars.txt file that can be created in your Sigil Preferences folder where you can set env vars that will be remembered and used by Sigil.

You can navigate to any folder and remember any place with the non-native file dialog. It just looks different but frankly it is much much more stable than using the native file dialogs in Qt and has been for years.

If you navigate in Finder, you can now drag and drop files to add the to the epub easily.

[democrite]

I thought I had it set correctly. I was using a .plist:

Spoiler:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.user.environment</string>
    <key>ProgramArguments</key>
    <array>
				<string>/bin/sh</string>
				<string>-c</string>
			  <string>
				launchctl setenv QT_LOGGING_RULES nextcloud.sync.discovery=false;
				launchctl setenv SIGIL_FORCE_NATIVE_FILE_DIALOG 1
				</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
</dict>
</plist>

I don't really use Save or Save As, but merely command-S so never noticed. Anytime I used a plugin, the save prompt appeared native so I thought it was ok. After trying the plugin to set env variables it looked set ok, but seems I just had to disable and renable again and now it's fine.

[KevinH]

Yes, after any change to env-vars.txt you must shutdown Sigil completely and re launch it.

BTW, where are you storing that plist? I thought env vars needed to be set inside the App's own plist but changes to it now violate the App's code signing.

Using Sigil's own env-vars.txt is the easiest especially for MacOS.

Also note: all plugins control their own file dialogs and they can opt for native or non-native. I have never had a non-native file dialogs crash on me in Qt. The same can not be said for native file dialogs.

[democrite]

That .plist is in ~/Library/LaunchAgents. Perhaps that is not the right place or maybe the format isn't correct.

As mentioned, I rarely use Save or Save As but merely Command-S so perhaps I never saw that it may not have been correct. Maybe that .plist or something similar might work but I didn't have it right. Since I mainly see save dialogs from plugins and they all appeared native, I thought it was ok.

As far as the plugin to change environment variables. I had set it and restarted Sigil multiple times but it didn't take effect. I had to unset, set, and restart more than once. Yet maybe that was not the issue. Perhaps macOS has some cache; perhaps as with app preferences such is cfprefsd (or something) and if such does not take effect, one can run something such as "killall -u "$USER" cfprefsd".

Thank you very much for all the help, your responses, help, updates, and all else, thank you both.