Closed Bug 1629708 Opened 4 years ago Closed 4 years ago

Port some of the MDN editor docs to the in-tree docs.

Categories

(Core :: General, task)

task

Tracking

()

RESOLVED FIXED
mozilla77
Tracking Status
firefox77 --- fixed

People

(Reporter: emilio, Assigned: emilio)

References

Details

Attachments

(4 files)

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: General → DOM: Editor
Product: Firefox → Core

Frigging AI.

Component: DOM: Editor → General
Depends on: 1629932

And tweak it so that if people want it can work outside-of the box (as
long as they have eslint in their path).

I've checked that mozilla-specific plugins also work with the setup I
mentioned.

Maybe we should move that in-tree, at some point.

Depends on D71052

Flags: needinfo?(emilio)

I wrote a blog post about using VSCode for developing Mozilla C++ code. Perhaps it would be useful to either link to that, or incorporate some of its content into this page?

(In reply to Botond Ballo [:botond] from comment #7)

I wrote a blog post about using VSCode for developing Mozilla C++ code. Perhaps it would be useful to either link to that, or incorporate some of its content into this page?

I think that blog post would be great to have a link to!

Pushed by ealvarez@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/433e3631f988
Port ESLint VIM config from WebExtensions wiki to the in-tree docs. r=robwu
https://hg.mozilla.org/integration/autoland/rev/c16a7f35cedf
Fix title level and wrap the VSCode section. r=sylvestre
https://hg.mozilla.org/integration/autoland/rev/0b99c0faa53d
Port emacs docs to the in-tree docs. r=sylvestre
https://hg.mozilla.org/integration/autoland/rev/b4b5a74e2273
Point to the Eclipse CDT docs from the in-tree docs. r=sylvestre
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: