Activity for Fuse - the Free Unix Spectrum Emulator
-
Fredrick Meunier committed [a583b7] on fuse
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
gitblobstore: checkandput manifest
-
Add mempool_strdup NULL guard
-
Improve make check: add displaytest
-
Add tests for libspectrum_creator API (tests 85-87)
-
Add some more ChangeLog entries for the next release
-
Unit tests for display.c
-
No better ideas in the last 9 years. Refreshed for latest and committed. May think more about testing frameworks in the future.
-
Move test target to top level Makefile.am
-
Improve isolation of display unit tests
-
Add tests for display_dirty_sinclair().
-
Add test for flashing colours.
-
Tidy up duplicated code and add one more test.
-
Add a test for reading from correct x.
-
Add a first non-trivial test.
-
A first actual test.
-
Initial commit of a display.c unit test code.
-
Allow tape2wav to write WAV files without libaudiofile
-
Allow tape2wav to write WAV files without libaudiofile
-
Add bitmap_ops_test to cover bitmap.h bit manipulation
-
Optimise reallocate_to_new_size()
-
Remove obsolete AC_C_CONST
-
debugger hex numbers prefix and variable prefix is the same
-
Thanks, fixed in version [0c1a3ce]
-
Bump actions/checkout@v3 to v4
-
Fix same-x overlap miss in x-dimension merge
-
Make stdatomic usage C23-compatible
-
Add const to libspectrum_creator getter function parameters
-
Update bundled pkg.m4 from serial 1 (0.24) to serial 12 (0.29.2)
-
Rectangle merge misses same-y overlap when frame skip enabled
-
Add tests for libspectrum_buffer_set and libspectrum_buffer_append
-
Upgrade SourceForge URLs from http:// to https://
-
Fuse Next Release Plan
-
You can see most of the things in the Wiki here https://sourceforge.net/p/fuse-emulator/wiki/Fuse%20Next%20Release%20Plan/ if that helps clarify things.
-
Fuse Next Release Plan
-
Fix typo and remove redundant autoreconf in macOS GitHub Actions workflow
-
Use __builtin_ctz to speed up display dirty-bit scanning
-
Alberto Garcia posted a comment on ticket #510
Regardless of the tools that we may use to automate the work, I can help with the next releases if you want. Like that I can also have a better overview of what actually needs to be done.
-
Add utils_safe_strdup unit test
-
Uncrustify event.c
-
Remove unused libxml2 dependency from Linux and macOS GitHub workflows
-
Add mempool_strdup and edge-case coverage to unittests
-
Remove $-prefixed hex digit syntax from the debugger (fixes bug #407)
-
Add buffer write function tests
-
Traditionally, just try to review all commits since the last release for the project, write scripts to update dates and version numbers and so on. Frankly it has not been sustainable. The last release I used a coding agent to help do all that which helps, but in general lowering the amount of work required to do the task is vital to minimise the toil of just doing releases.
-
That should be easy to do, the appstream file only needs the changelog entries. What's your usual workflow when you make releases? Because the actual ChangeLog file is very verbose and you need to select what things to highlight for the release notes.
-
Use byte arrays in libspectrum_buffer_write_[word|dword]
-
Use macOS 26 runners for GitHub macOS actions
-
Update win32 link to fuse-utils 1.4.4
-
Thanks, fixed in version [0c1a3ce]
-
Thanks, fixed in version [0c1a3cee]
-
debugger hex numbers prefix and variable prefix is the same
-
Thanks, fixed in version 0c1a3cee
-
TBH it would be helpful if the release process is less manual and multi-step and more automated. If it could have a script to generate it from Changelog that would be very helpful.
-
Fuse - the Free Unix Spectrum Emulator released /fuse/1.7.0/fuse-1.7.0-sdl-setup.exe
-
-
-
Thanks! Remember that from now on we should add the release notes to the data/net.sourceforge.fuse_emulator.Fuse.metainfo.xml file, see the <release date="2026-03-24" version="1.7.0"> tag for an example. The list of items in the description are the ones that will appear in places like Flathub and such.
-
Thanks! Remember that from now on we should add the release notes to the data/net.sourceforge.fuse_emulator.Fuse.metainfo.xml file, see the <release date="2026-03-24" version="1.7.0"> tag for an example. The list of items in the ChangeLog are the ones that will appear in places like Flathub and such.
-
Provide AppStream metadata
-
Add AppStream metainfo file
-
https://sourceforge.net/p/fuse-emulator/fuse/merge-requests/35/
-
Add AppStream metainfo file
-
Thanks, can you make a merge request for it?
-
We are on the same page, I'm talking about always writing to $XDG_CONFIG_HOME. I wouldn't move the file so that if someone runs an old version again they keep their last preferences.
-
The question is not about reading, but about writing :) Reading $XDG_CONFIG_HOME and then falling back to $HOME/.fuserc is easy and I think that we should probably do it in any case. But when the user wants to save the configuration, do we always write to $XDG_CONFIG_HOME? One possibility is that we move the configuration file from $HOME/.fuserc to $XDG_CONFIG_HOME, so the former silently disappears. Or we can also leave the original in place, but then we'd have two copies and only one would be actually...
-
I just rebased the patch and created a fork: https://sourceforge.net/u/bertogg/fuse-emulator/ci/bug-510-appstream-metadata/tree/
-
Make Fuse headers C++ friendly
-
I think maintainers have little time, so I'll recommend sticking with the C linkage option and close this issue.
-
I think I'd be good with changing Fuse to use proper XDG_CONFIG_HOME support with support to read an existing $HOME/.fuserc as a fallback?
-
Fix out-of-tree builds by using full paths in generated #includes
-
Thanks, committed in 9a93922a
-
Fix out-of-tree builds by using full paths in generated #includes
-
X-Video extension for xlib UI
-
Xlib UIs are deprecated and unmaintained
-
menu for xlib UI
