[FEATURE REQUEST]: Allow automatic export after compilation
See original GitHub issueIn the discussion about SpectNetIDE-ZEsarUX integration (with Mike van der Lee), it came to light that an automatic export of the compilation could be a useful solution.
Here is a private build of SpectNetIDE, which contains this feature:
(Do not forget to rename the file to .vsix
before install.)
You can find the documentation of this new feature here: https://dotneteer.github.io/spectnetide/getting-started/export-a-z80-program-2#auto-export
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
fix mode to automatically remove unused exports · Issue ...
Feature request : --fix mode to automatically remove unused exports #23 ... handful of erroneously removed exports until everything compiled.
Read more >Automatic Export Add-on
Introduction. Goal. Automatically export changes made in the development content repository to the repository data modules in your project.
Read more >Salesforce Data Export: All Options Explained
The all-in-one guide on how to export data from Salesforce natively as a CSV file, as well as how you can export Salesforce...
Read more >Feature Requests: How to Track, Prioritize, and Manage
Feature requests are demands for improvement in a company's product. Click to learn how to track and prioritize these requests efficiently!
Read more >Migrating projects using file exports
Enable file exports as an import source for the destination instance. On GitLab.com, file exports are already enabled as an import source.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi, István.
Just want to thank you for the build. I’ve been low on time lately but will try to test it in the following days.
Mike, today I examined the project you sent me. The issue with the code is that the the
exdos.bas
file contains thelocal
,proc
, andendp
assembly keywords with uppercase first letters:Local
,Proc
, andEndp
. Thus, the Assembler takes these words into account as label names, and not as statements. SpectNetIDE accepts either full lowercase or full uppercate keywords, soLOCAL
,PROC
, andENDP
are also valid. I already had had to add some tweaks to the SpectNetIDE assembler to handle ZX BASIC-specific issues that caused incompatibilities, the one you found is just a new of them 😃. I try to find out a tweak to solve this issue. I examine the files you sent me further, I guess there might be still other issues with them hidden by the wrong keywords. As soon as possible, I will send you a new private build for testing.