wopian / agc-assembly Goto Github PK

View Code? Open in Web Editor NEW

15.0 3.0 3.0 916 KB

☄️ VS Code syntax highlighting for Apollo Guidance Computer source code

Home Page: https://marketplace.visualstudio.com/items?itemName=wopian.agc-assembly

License: MIT License

TypeScript 100.00%

vscode vscode-extension typescript agc ags argus binsource

agc-assembly's Introduction

AGC Assembly

Visual Studio Code extension for syntax highlighting Apollo Guidance Computer (AGC) assembly source code.

Based on AGC Assembly for Sublime Text.

Languages
Marketplace
Sideloading
Development
Releases

Languages

agc - AGC (Command Module and Lunar Module) assembly language,
ags - AGS (Lunar Module Abort Guidance System) assembly language,
argus - ARGUS Honeywell 800 assembly language,
binsource - AGC core rope memory binary source files.

Marketplace

Install AGC Assembly from VS Code Marketplace.

Launch VS Code Quick Open (Ctrl+P)
Input ext install agc-assembly
Reload VS Code

Sideloading

From Source

Download the latest release
Extract the zip into:
- Windows %HOMEPATH%/.vscode/extensions
- Mac ~/.vscode/extensions
- Linux ~/.vscode/extensions
Reload VS Code

From VSIX

Download the VSIX binary from the latest release
Launch VS Code Command Palette (Ctrl+Shift+P or F1)
Input install vsix
Navigate to VSIX binary
Reload VS Code

Development

Setup

# Check you're using NodeJS 7.0.0 or above
node -v
# Check you're using npm 4.0.0 or above
npm -v
# Download source code
git clone https://github.com/wopian/agc-assembly.git
cd agc-assembly
# Install dependencies
npm i

Building

# Compile typescript & yaml
npm run b

Testing

npm t

Packaging

npm i -g vsce
vsce package

Releases

See CHANGELOG

agc-assembly's People

Contributors

Stargazers

Watchers

Forkers

teodorov loesterfranco

agc-assembly's Issues

An in-range update of @types/node is breaking the build 🚨

Version 7.0.25 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.24
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Decoration stays enabled after switching languages

Steps to reproduce:

Type ## Test in any language other than AGC Assembly
- ## Test should not be decorated
Switch language to AGC Assembly
- ## Test should be correctly decorated
Switch language to any other language
- ## Test will still have decoration

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Warning

These dependencies are deprecated:

Datasource	Name	Replacement PR?
npm	`@types/mkdirp`
npm	`@types/rimraf`
npm	`q`
npm	`tslint`
npm	`vscode`

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

build(deps): lock file maintenance

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

build(deps): update simek/yarn-lock-changes digest to 5b249bc
build(deps): update devdependency chai-as-promised to ~8.0.0
build(deps): update devdependency rimraf to ~6.0.0
Click on this checkbox to rebase all open PRs at once

Detected dependencies

github-actions

.github/workflows/codeql-analysis.yml

actions/checkout v4

github/codeql-action v3

github/codeql-action v3

github/codeql-action v3

.github/workflows/lockfile.yml

actions/checkout v4

Simek/yarn-lock-changes c36e94d0c024da36a17d48e2247f35b1e1565f3b

npm

package.json

@types/chai ~4.3.0

@types/chai-as-promised ~7.1.0

@types/mkdirp ~2.0.0

@types/mocha ~10.0.0

@types/node ~22.2.0

@types/rimraf ~4.0.0

chai ~5.1.0

chai-as-promised ~7.1.0

converter ~0.0.5

mkdirp ~3.0.0

mocha ~10.7.0

q ~1.5.0

rimraf ~5.0.0

tslint ~6.1.0

typescript ~5.5.0

vscode ~1.1.0

vscode >=1.13.1

node >=8.0.0

npm >=5.0.0

travis

.travis.yml

node 12.22.12

Check this box to trigger a request for Renovate to run again on this repository

Tests broken on Linux, OS X & Windows via CLI

See microsoft/vscode#17993

An in-range update of @types/node is breaking the build 🚨

Version 8.0.1 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	8.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/mocha is breaking the build 🚨

Version 2.2.41 of @types/mocha just got published.

Branch	Build failing 🚨
Dependency	@types/mocha
Current Version	2.2.40
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

- ✅ **continuous-integration/appveyor/branch** AppVeyor build succeeded [Details](https://ci.appveyor.com/project/wopian/agc-assembly/build/61),- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/wopian/agc-assembly/builds/226790087)

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 8.0.4 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	8.0.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 8.0.3 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	8.0.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of typescript is breaking the build 🚨

Version 2.3.4 of typescript just got published.

Branch	Build failing 🚨
Dependency	typescript
Current Version	2.3.3
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

TypeScript 2.3.4

This release includes a new flag for tsserver to specify location of npm for nvm users.

Download:

Commits

The new version differs by 12 commits.

1a579d9 Update LKG
e023dc3 Merge pull request #16113 from Microsoft/fixNpmLocationWithSpaces
d7555ed Fix equals
47a0a7c Wrap npmLocation if needed
47bd5af Allow configurable npmLocation for typingsInstaller (#16084) (#16102)
d333378 Merge branch 'release-2.3' of https://github.com/Microsoft/TypeScript into release-2.3
f80ca90 Add project telemetry (#16085)
fc4d109 Fix build breaks with the instrumenter
196aba6 Merge pull request #16051 from Microsoft/PortRulesProviderFixToRelease-2.3
9919b58 Updating compiler release version to 2.3.4
3b9ef4e Changes from CR feedback
dcab328 RulesProvider performance improvements

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of tslint is breaking the build 🚨

Version 5.4.3 of tslint just got published.

Branch	Build failing 🚨
Dependency	tslint
Current Version	5.4.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As tslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes

v5.4.3

🛠 Bugfixes

[bugfix] Fixed regression with empty --out file (#2867)
[bugfix] unified-signatures: Don't suggest to unify rest parameters. (#2874)
[bugfix] binary-expression-operand-order: Allow if both sides of the binary expression are literals. (#2873)
[bugfix] Restore compatibility with [email protected] and 2.2 for whitespace, space-before-function-paren and deprecation (#2893)
[docs] no-string-literal: Fix documentation (#2875)

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/chai is breaking the build 🚨

Version 3.5.1 of @types/chai just got published.

Branch	Build failing 🚨
Dependency	@types/chai
Current Version	3.5.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As @types/chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/appveyor/branch AppVeyor build succeeded Details
❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 7.0.22 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.21
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

✅ continuous-integration/travis-ci/push The Travis CI build passed Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 7.0.28 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.27
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 7.0.29 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.28
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 6.0.56 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	6.0.55
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/chai is breaking the build 🚨

Version 4.0.1 of @types/chai just got published.

Branch	Build failing 🚨
Dependency	@types/chai
Current Version	4.0.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

Language specific settings

Action Required: Fix Renovate Configuration

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Location: package.json
Error type: The renovate configuration file contains some invalid settings
Message: Configuration option 'packageRules[0].node' should be a json object, Configuration option 'packageRules[0].npm' should be a json object, Invalid configuration option: bugs, Invalid configuration option: categories, Invalid configuration option: contributes, Invalid configuration option: displayName, Invalid configuration option: galleryBanner, Invalid configuration option: homepage, Invalid configuration option: icon, Invalid configuration option: keywords, Invalid configuration option: license, Invalid configuration option: name, Invalid configuration option: packageRules[0].vscode, Invalid configuration option: packageRules[1].@types/chai, Invalid configuration option: packageRules[1].@types/chai-as-promised, Invalid configuration option: packageRules[1].@types/mkdirp, Invalid configuration option: packageRules[1].@types/mocha, Invalid configuration option: packageRules[1].@types/node, Invalid configuration option: packageRules[1].@types/rimraf, Invalid configuration option: packageRules[1].chai, Invalid configuration option: packageRules[1].chai-as-promised, Invalid configuration option: packageRules[1].converter, Invalid configuration option: packageRules[1].mkdirp, Invalid configuration option: packageRules[1].mocha, Invalid configuration option: packageRules[1].q, Invalid configuration option: packageRules[1].rimraf, Invalid configuration option: packageRules[1].tslint, Invalid configuration option: packageRules[1].typescript, Invalid configuration option: packageRules[1].vscode, Invalid configuration option: publisher, Invalid configuration option: renovate, Invalid configuration option: scripts, Invalid configuration option: version, The "node" object can only be configured at the top level of a config but was found inside "packageRules[0]", The "npm" object can only be configured at the top level of a config but was found inside "packageRules[0]"

An in-range update of @types/node is breaking the build 🚨

Version 7.0.32 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.31
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 8.0.2 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	8.0.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build is in progress Details
❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

An in-range update of @types/node is breaking the build 🚨

Version 7.0.31 of @types/node just got published.

Branch	Build failing 🚨
Dependency	@types/node
Current Version	7.0.30
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/appveyor/branch AppVeyor build failed Details
❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

wopian / agc-assembly Goto Github PK

agc-assembly's Introduction

AGC Assembly

Contents

Languages

Marketplace

Sideloading

From Source

From VSIX

Development

Setup

Building

Testing

Packaging

Releases

agc-assembly's People

Contributors

Stargazers

Watchers

Forkers

agc-assembly's Issues

Version 7.0.25 of @types/node just got published.

Awaiting Schedule

Open

Detected dependencies

Version 8.0.1 of @types/node just got published.

Version 2.2.41 of @types/mocha just got published.

Version 8.0.4 of @types/node just got published.

Version 8.0.3 of @types/node just got published.

Version 2.3.4 of typescript just got published.

Version 5.4.3 of tslint just got published.

🛠 Bugfixes

Version 3.5.1 of @types/chai just got published.

Version 7.0.22 of @types/node just got published.

Version 7.0.28 of @types/node just got published.

Version 7.0.29 of @types/node just got published.

Version 6.0.56 of @types/node just got published.

Version 4.0.1 of @types/chai just got published.

Version 7.0.32 of @types/node just got published.

Version 8.0.2 of @types/node just got published.

Version 7.0.31 of @types/node just got published.

Recommend Projects

Recommend Topics

Recommend Org