Re: [fuse-emulator-devel] Is Fuse alive (and where)?

[Joerg P. <joe...@gm...>]

Hi Alberto,

it’s a bit sad to hear that Fuse is stalled. Did everybody move on to other things or is it because the project is so mature (almost) no changes are needed? :)

I am using Fuse as emulator in a multi-platform Z80 compiler environment I’ve been developing for a while now. I have a couple of issues, including a bigger one with multi-line debugger commands fed into Fuse via the command line. In the meantime, I’ve been able to solve the latter, but would still prefer a more „solid“ solution. From the back of my head, here’s my full list of issues/questions:

1) Could there be an alternative --debugger-command-file that points to a file containing the debugger commands? If there are many and complex breakpoints the command line gets extremely long, and those newlines scare me a lot when pushing everything though my tools and a shell process until it arrives in Fuse.

2) As an alternative idea to 1): The CSpect emulator uses certain invalid opcodes (such as $dd $01) as breakpoints. That means the opcodes would be part of the program itself and not have to be specified on the command line. Is that something you could consider?
 
3) Could the default behavior for 128K .sna files be changed? Currently the system interprets them as Pentagon snapshots, does not find the ROMs (I am not interested in Pentagon) and „crashes“ into a 48K machine. I understand this is possibly a „historical decision“, but in my opinion there’s nothing inherently Pentagon about the format. Would something like this work: If the Pentagon ROMs are not there and/or the user specified —machine 128 on the command line, treat this as a 128K snapshot, not as Pentagon? Or simply a checkbox in the preferences?

4) Could there be a „step over“ button in the debugger UI that basically does what „n“ does in the debugger commands (as a convenience)?

5) Last but not least, the Mac version seems to be a bit behind the latest upstream (and have some bugs of its own). Not sure if the main Mac developer is on this list, but is there a chance for an update? I’m very much willing to provide feedback for Intel and Arm Macs. I could also try building either locally, but I probably won’t be much help with the actual development because I don’t know the codebase.

Best regards
Joerg

> Am 14.09.2025 um 23:58 schrieb Alberto Garcia <be...@ig...>:
> 
> On Sun, Sep 14, 2025 at 10:32:08AM +0200, Joerg Pleumann wrote:
>> sorry for using the developer list for this question, but since all
>> the other places (especially the SourceForge project for Mac Fuse,
>> which is the flavor I am using) are so inactive, I was wondering
>> if the project might have moved elsewhere. Is there a Discord or
>> another place where one might ask questions, or are things really as
>> inactive as they seem?
> 
> You can ask questions here, I guess, but the project is certainly
> stalled at the moment...
> 
> Berto
> 
> 
> _______________________________________________
> fuse-emulator-devel mailing list
> fus...@li...
> https://lists.sourceforge.net/lists/listinfo/fuse-emulator-devel