Sigil 2.7.6 Released

[DiapDealer]

Sigil 2.7.6

Sigil 2.7.6 is mainly a maintenance release.

New Features

• add ability to unset environment variables using the env-vars.txt file

Bug Fixes

• fix many translations from Transifex that somehow were improperly updated
• Fix bug in Clips Window (dock widget) that messed up its layout

--------------------------------Notes -----------------------------------

It's possible that Windows users may need to update their Visual Studio VC++ Redistributable runtimes if Sigil doesn't run.

The Sigil Linux AppImage is built on Ubuntu Jammy (22.04) and is targeting glibc 2.35 and higher. Use ldd --version to see if your system at least has a shot at being able to use the AppImage. Don't forget to make sure the AppImage is executable after downloading. Trouble is not expected but be safe and backup your existing Sigil preferences (if you have any) before trying the AppImage.

The latest version of the Sigil User Guide can always be downloaded from the Sigil website, or from its own GitHub repository.

Please check the Sigil website for important Sigil support links, additional resource downloads, and platform-specific trouble-shooting tips/requirements.

The MacOS builds are signed AND notarized.

PGP Fingerprint (for signed tags and source archives): B5A5 6206 AB0F BC1A 24EF AB8A A166 D29A 8FCD AC63

All Sigil binary (and source) downloads can also be found as assets at the bottom of The Sigil-2.7.6 Github Release page.

[DiapDealer]

** Post reserved for future use **

[Capricorn]

When I download Sigil 2.7.6 on my windows 11 25H2 (with latest updates) machine,
windows defender immediately puts it into quarantine with the message: Trojan:Win32/Wacatac.B!ml found
I cannot remember ever having had a problem with sigil and windows defender.
I assume this is a false positive.

[Doitsu]

Originally Posted by Capricorn

When I download Sigil 2.7.6 on my windows 11 25H2 (with latest updates) machine,
windows defender immediately puts it into quarantine with the message: Trojan:Win32/Wacatac.B!ml found.

I only got the usual warning that the installer isn't commonly downloaded,

Originally Posted by Microsoft Defender SmartScreen

Microsoft Defender SmartScreen couldn't verify if this file is safe because it isn't commonly downloaded. Make sure you trust the file you're downloading or its source before you open it.

Name: Sigil-2.7.6-Windows-x64-Setup.exe
Publisher: Unknown

but Microsoft Defender SmartScreen didn't complain about it and Virustotal also said it's safe.
If you downloaded the installer from a third-party website, that website might have added a PUA.

[Capricorn]

I downloaded it from the sigil website first https://sigil-ebook.com/sigil/download/, and then from the github pages for sigil. In both cases the same result. I never use any other sources.

[Capricorn]

Virustotal gave this:
DeepInstinct - Malicious - Microsoft - Trojan:win32/Wacatac.b!ml
All others undetected.

Thanks for reminding me to check with virustotal.

[Capricorn]

I ran, via windows update, a security intelligence update.
Now, when I scan the downloaded setup file with windows defender, it does not complain anymore. Ah well........

[DiapDealer]

Defender's random detection of Trojan:Win32/Wacatac.B!ml is like the smoke detector going off when you're cooking. It's typically heuristic nonsense. Especially when only one out of 100 or so anti-malware systems "detect" it. It's heuristics include "cloud reputation.". Which means that "not very many people have downloaded it" is one of the determining factors for flagging it as wacatac.b!ml.

For the record, whether you download Sigil's installer with links from its website, or directly from GitHub, or via Windows' built-in winget tool, the exact same file is being downloaded (directly from Sigil's github release page). Winget has the advantage of avoiding the unsafe, unknown, uncommon download warnings that Microsoft throws at users to scare them into not using software that hasn't paid the ransom to "maybe" get off the "heuristically possible to be" naughty list. Winget vets installers before accepting them. As does Chocolatey. So you tend to get safe, silent installations of Sigil with them.

[Capricorn]

I must have done some heavy cooking.
If I had gotten a nice juicy grilled steak out of it, it would have been worthwhile. But now.........

Ah..yes, I should have used winget...my brain is clearly not working properly today...........

[philja]

I'm finding the recently added clip numbers very handy when using keyboard shortcuts on linux and windows but I can't find an equivalent to Crtl+Alt+(a number) on my Macbook.

I've Googled for a solution but without success. Do I have to redefine all the keyboard shortcuts on the Macbook?

[KevinH]

No, In Sigil User's Guide, it explains that in the Mac, the shortcut keys have been remapped. For example, the Ctrl key is mapped to the Apple/Command key. It has been that way since Sigil began over 15 years ago and will not change.

The reason is to make cross-platform shortcuts work. For example Ctrl+C and Ctrl+V on Windows and linux has long been Copy and Paste, but on a Mac that has always been Command+C and Command+V. So the remapping makes all platforms happy for standard shortcuts.

So replace the Ctrl with Command on a Mac. Or just enable the Clips 1 Toolbar and use that instead.

[philja]

Originally Posted by KevinH

No, In Sigil User's Guide, it explains that in the Mac, the shortcut keys have been remapped. For example, the Ctrl key is mapped to the Apple/Command key. It has been that way since Sigil began over 15 years ago and will not change.

The reason is to make cross-platform shortcuts work. For example Ctrl+C and Ctrl+V on Windows and linux has long been Copy and Paste, but on a Mac that has always been Command+C and Command+V. So the remapping makes all platforms happy for standard shortcuts.

So replace the Ctrl with Command on a Mac. Or just enable the Clips 1 Toolbar and use that instead.

The Ctrl = Cmd is the one equivalent that I learned early on. I couldn't find the equivalent of Alt so I tried them all and none would work on my Macbook.

But that has turned out not to be at the root of my problem on the Macbook.

I tried your suggestion of using the Clips 1 Toolbar but found that it was not populated - completely blank. Previously, I had found that in the Clips Editor none of my clips were numbered. I couldn't remember numbering them by hand in Linux, but I tried adding the numbers manually in the Macbook without success in getting the shortcut to work.

I tried the Sigil Users Guide (_20250912 edition) but found nothing relevant to Clip numbers.

Eventually I found the problem. My clips in the Macbook were created by 'Autofill' and they were all situated below the Examples. As soon as I raised them above the examples, the clip numbers magically appeared and Option + Command + 'number' worked as it should.

BTW: the format menu drop down in the Macbook shows Cmd+Space as the way to delete formatting. Sadly, Mac seems to have hijacked this combination to open their 'Spotlight search' bar.

Turning my attention to Windows, where I have never really used the clips, I exported my clips from linux and imported them into Windows Sigil. They do appear above the built-in examples in the Clip Editor, but un-numbered. Restarting Sigil doesn't change anything. Numbering them by manual editing doesn't enable the shortcuts to work. Nor is the clip bar populated.

I guess I've missed something somewhere.

[KevinH]

Yes, only base path clips (those *not* in any folder) can be assigned to a clip tool bar and be assigned a shortcut. Sigil's clips have always work that way. If you import them inside folders, then you must use the Clips Editor to move them up to the top area (before any folders) for them to appear on a clips toolbar and get assigned a Clip number so that shortcuts can be used.

Again, this is how clips have always been done in Sigil. Most clips are created there by default. Others move a few of the Example clips up and out. Clips in folders can not be assigned to a clip toolbar, nor have a shortcut defined. There are room for 60 clips that can be present on the toolbars.

The only new feature is the autofilling column that shows the Clip number so you can assign them more easily to short cuts. You should not be able to manually edit that auto-numbered column. If so, that is a bug I need to fix.

[philja]

Originally Posted by KevinH

Yes, only base path clips (those *not* in any folder) can be assigned to a clip tool bar and be assigned a shortcut. Sigil's clips have always work that way. If you import them inside folders, then you must use the Clips Editor to move them up to the top area (before any folders) for them to appear on a clips toolbar and get assigned a Clip number so that shortcuts can be used.

Again, this is how clips have always been done in Sigil. Most clips are created there by default. Others move a few of the Example clips up and out. Clips in folders can not be assigned to a clip toolbar, nor have a shortcut defined. There are room for 60 clips that can be present on the toolbars.

The only new feature is the autofilling column that shows the Clip number so you can assign them more easily to short cuts. You should not be able to manually edit that auto-numbered column. If so, that is a bug I need to fix.

Ah!!! base path only !! That's the answer in Windows. The clip collection I imported from linux was placed into an 'Imported' folder. This was done automatically - I was not offered any choice.

Fortunately I was able to highlight the lot of them and slide them out of the Imported folder into the base in one go. And, voila! they all got numbered before my eyes.

The auto-numbered column items seems to be manually editable - you just have to double click on the name and type in a change. For example, I changed Clip6 to a simple '6' and it seemed to be accepted and saved, at least while that instance of Sigil is open. The shortcut still worked, but after closing and restarting Sigil, the 6 had been automatically rewritten to Clip6.

Whether you regard that as editable or not, I don't know.

However, what is the secret for using a shortcut numbered with double digits? On linux and windows, Ctrl+Alt+11 doesn't enter Clip11 but does enter Clip1 twice.

[KevinH]

You must use Sigil's Preferences to Manage Shortcuts and assign a working shortcut to to that clip number. Only the first 10 clips are autoassigned shortcuts. But those can be changed in the Shortcut manager as well.