Skip to content

Conversation

@theothermutahhir
Copy link
Contributor

No description provided.

cben and others added 30 commits March 11, 2019 18:02
… Sans Pro

https://adobe-fonts.github.io/source-sans-pro/ is a proportional font
family by Adobe (the "Source" in the name refers to being open source).
https://adobe-fonts.github.io/source-code-pro/ is a matching monospace
font family.
Added pgsql keywords which were missing.
Improves the current behavior which auto closes every opening bracket.

- hardcodes a closeBefore list of characters that if the next character is in the list, opening a bracket should be auto-closed.
The list is : ")]}'\":;>"
Basically the closing characters in pairs  ; : and >.

- when opening a bracket, it will be auto-closed if:
1. there is no next character,
2. the next character is a white space character.
3. the next character is in the shouldClose list.
For example, "happy" to match "very-happy", "not-so-happy", "happy".
When creating an overlay mode from e.g. `gfm`, which has `markdown` as an
`innerMode`, we need to recursively compute `innerMode` via
`CodeMirror.innerMode` to correctly determine `markdown` descendant mode.
To avoid the mouse handling code getting confused
If typing attribute=" and by closetag it becomes attribute="" and user
presses Ctrl-Space to autocomplete and the completion is "x" then by
this fix instead of obnoxious attribute="x"" it becomes nice attribute="x".
When user types <atomic> substitute <atomic/> if so configured.
The scrollbar annotations may fail to match search query under
certain circumstances. This happens when the search cursor is
`multiline: false`.

The matchesonscrollbar addon does not have a way to indicate
`multiline: false`, the multiline status is heuristically
determined and because of this it may end up being opposite
of the status of the search cursor.
Rather than 'false', which is ignored

Issue #3403
To avoid treating it like 3 separate dot tokens

Closes #5861
ghik and others added 30 commits April 6, 2020 22:39
Currently, when a completion is triggered with part of the identifier already typed and backspace is hit, hints are immediately
closed (when cursor is moved before the original position that completion was triggered for).
After this change, they will be closed only when the entire identifier is erased (cursor is moved before the identifier start).
There is a small typo in addon/search/searchcursor.js, mode/python/python.js.

Should read `compatibility` rather than `compatiblity`.
**Fixes a minor visual bug:**
The picked hint might push the cursor out of the screen - this scrolls the cursor back into view. (Would normally happen after the next keypress.)
This adds support for WebAssembly text format, as used in the
browser DevTools (Firefox, Edge and Chrome DevTools all the like).
Since it causes jumps in the scroll position on Chrome.

Closes #6246
We use the standalone mode in DevTools in a worker, where `window`
does not exist. Instead, we can use `globalThis` which should be
the corresponding global scope in all scenarios. For older browsers
that do not support `globalThis`, we fallback to `window`.

Relevant DevTools change:
https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2174418/1/front_end/third_party/codemirror/package/addon/runmode/runmode-standalone.js
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.