jiebi/CodeConvo huggingface dataset:
Change:
export const EditorOptions = { acceptSuggestionOnCommitCharacter: register(new EditorBooleanOption( EditorOption.acceptSuggestionOnCommitCharacter, 'acceptSuggestionOnCommitCharacter', true, <del> { markdownDescription: nls.localize('acceptSuggestionOnCommitCharacter', "Controls whether suggestions should be accepted on commit characters. For example, in JavaScript, the semi-colon (`;`) can be a commit character that accepts a suggestion and types that character.") } </del> <ins> { markdownDescription: nls.localize('acceptSuggestionOnCommitCharacter', "Controls whether suggestions should be accepted on commit characters. For example, in JavaScript, the semi-colon (`; `) can be a commit character that accepts a suggestion and types that character.") } </ins> )), acceptSuggestionOnEnter: register(new EditorStringEnumOption( EditorOption.acceptSuggestionOnEnter, 'acceptSuggestionOnEnter',

Discussion:
Issue Type: <bFeature Request</bWhen I write code in VS Code I am constantly closing down intellisense popup suggestions. Worst case is when a popup will actually update the code I am writing and mangle it. If I want intellisense help I'll press Ctrl+space or Ctrl+shift+space when I want it. Give me a easy setting to disable ALL intellisense popups unless I press Ctrl+space and ask for help. I am a experienced developer and touch typist who does not need intellisense help. Having to constantly press the Esc key to close a intellisense popup menu while I am writing code is killing my productivity and making me hate VS Code. I have tried to disable this by having this in my but it doesn't stop the popups while I am writing code: "editor.quickSuggestions":{ "other": "off", "comments": "off", "strings": "off" } After some more searching it looks like adding this to stops that jarring parameter window popping up and covering up the code I want to see. "editor.parameterHints.enabled": false, But I still get suggestions for Properties Names and so on. What do I need to do to stop ALL intellisense suggestions from popping up? I understand how this is useful for more beginning programmers but while I am programming I really don't want anything popping up covering code I may be looking at as I write code. I think having a single setting to disable all Intellisense popups while writing code would be useful. From searching the internet I don't think I am alone in this thinking. VS Code version: Code 1.69.1 (, 2022-07-12T08:21:24.514Z) OS version: Windows_NT x64 10.0. Restricted Mode: No <!-- generated by issue reporter --
Also configure this setting:
Thanks that last setting is perfect, Ctrl+Space and Ctrl+Shift+Space still work when I need them and I can write code without being disturbed and stay in the zone...
Change:
function listFocusFirst(accessor: ServicesAccessor, options?: { fromFocused: boolean }): void { const focused = accessor.get(IListService).lastFocusedList; <del> // Ensure DOM Focus ensureDOMFocus(focused); </del> // List if (focused instanceof List || focused instanceof PagedList) { const list = focused;

Discussion:
I like the up / down keyboard navigation over notebook cells, but when you try to use to navigate the order is very unexpected. a notebook. I am using my- my work cell -Focus is on GitHub issues label -focus seems lost -focus is on the start of the document, even though I did not traverse until the end of the docuemnt Ideally tab should go in visual order. If that is not possible should move focus out of the notebook. Similarly tree tab is not used to move focus so users use up / down, but pressing tab focuses out of the tree and does not lead to unexpected jumping of focus.
Fixed in this change Get rid of output focus sink when cell has no output, to avoid a dead spot when tabbing through cell (step 3 in OP) Fix the toolbar losing focus shortly after tabbing onto it, by avoid context key churn Fix domFocus when focus is in a different element from the one that is selected (depends on an earlier PR in )
Much better now. Thanks for fixing this.
Change:
// acknowledged to shutdown and then might end up with partial backups // written to disk, or even empty backups or deletes after writes. // (https://github.com/microsoft/vscode/issues/138055) this.cancelBackupOperations(); // For the duration of the shutdown handling, suspend backup operations // and only resume after we have handled backups. Similar to above, we // do not want to trigger backup tracking during our shutdown handling // but we must resume, in case of a veto afterwards. const { resume } = this.suspendBackupOperations(); try {

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.73.0-insider OS Version: Windows_NT x64 10.0. Auto Save by onFocusChange does not sync internal cache when direct quitting by 'X' button. Steps to Reproduce: settings: "Files: Auto Save" =onFocusChange a text file and save it somewhere. the file a little more. But this time, do not save or change focus and just press 'X' button directly to quit. the text file again with vscode. to save the file. Now you can see this error message: "Failed to save '...': The content of the file is newer." <img width="341" alt="image" src="https://user-"
That is weird, we trigger auto save on shutdown unless auto save is turned off: Does this still reproduce in all projects?
Oh nice I can reproduce, looks really like a bug.
Great catch!
Thank you for your response and effort on this issue!
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
/verified
Change:
}; this._item.tooltip = this._currentHint.message; this._item.text = localize('large.label', "Configure Excludes"); <del> this._item.tooltip = localize('hintExclude.tooltip', "For better performance exclude folders with many files."); </del> <ins> this._item.tooltip = localize('hintExclude.tooltip', "To enable JavaScript/TypeScript IntelliSense, exclude large folders with source files that you do not work on."); </ins> this._item.color = '#A5DF3B'; this._item.show(); this._client.logTelemetry('js.hintProjectExcludes');

Discussion:
VSCode Version: Code - Insiders 1.8.0-insider (, 2016-12-06T16:53:46.634Z) OS Version: Darwin x64 15.6.0 Testing The current message seems to general: "For better performance exclude folders with many files." "better performance" is to weak because the typescript server basically shutdown and won't provide any of the advanced features. "folders with many files" is vague, it should mention JavaScript/TypeScript files that the user does not work on (like packages/libraries). could also mention that this happens in the js-, that would set the right expectation for the 'Configure Excludes' button and also inform the user how this can be done manually. Needs more thought: "Too many JavaScript/TypeScript files: To enable advanced editor features in JavaScript/TypeScript files exclude large folders with source files you do not work on." /cc
Also, the status bar button might benefit from being specific about the language it refers to.
Change:
} }, { <del> "name": "Function Call", "scope": "meta.function-call", "settings": { "fontStyle": "n    ttt", "foreground": "#0080FF" } }, { </del> "name": "Function Object", "scope": "meta.function-call.object", "settings": {

Discussion:
VSCode Version: 1.13.0 OS Version: Mint 18 Steps to Reproduce: to print `this.someMethod(); You can see, that "this" is colorless. It's so bad, because I need with this highlight when I work with classes. For example comparsion between VS code(left) and Sublime (right). Also highlight for arguments sometimes is in place, sometimes is not. !
You can install extension for this. I recommended or
This is not a bug in the grammar. Other themes colorize just fine: ! Monokai does not however
Change:
const codeLineClass = 'code-line'; <del> export interface CodeLineElement { element: HTMLElement; line: number; codeElement?: HTMLElement; </del> <ins> export class CodeLineElement { private readonly _detailParentElements: readonly HTMLDetailsElement[]; constructor( readonly element: HTMLElement, readonly line: number, readonly codeElement?: HTMLElement, ) { this._detailParentElements = Array.from(getParentsWithTagName<HTMLDetailsElement>(element, 'DETAILS')); } get isVisible(): boolean { return !this._detailParentElements.some(x => !x.open); } </ins> } const getCodeLineElements = (() => {

Discussion:
Thanks for the quick turnaround on preserving the open attribute! I'm still a little curious about the scrolling sync: I don't see anything in that looks like it would address the issue I'm seeing "scrolling past" a collapsed block where the code cursor makes the preview act as if it's much further down, seemingly by about as much as the length of the expanded . I can now leave my expanded to re-enable sync'd scrolling, but I was wondering if the intent was to not change the behavior when they're closed? Or, would it be helpful if I broke that part out into a new issue? Originally posted by in
Thanks. I've extracted this to it's own issue and will push a fix shortly
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
Change:
import { Event } from 'vs/base/common/event'; import { IViewDescriptorService } from 'vs/workbench/common/views'; import { ITextModelService } from 'vs/editor/common/services/resolverService'; <ins> import { ILifecycleService } from 'vs/workbench/services/lifecycle/common/lifecycle'; </ins> const folderName = 'test-folder'; const folderUri = URI.file(`/${folderName}`);

Discussion:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. -- introduces which controls when we attempt to restore an edit session for the current workspace. The user still has to remember to store their edit session or use the explicit Continue Working On trigger. In order to make it harder to lose edit sessions across , , , and RemoteHub on desktop, we should introduce a setting with initial setting values and . When set to , we'll attempt to store the current edit session (if any) before a workbench unload. This will only really reliably work in desktop because in web we cannot run long running tasks in the onbeforeunload handler (, tracked in ). To mitigate this we should also explore introducing an option to continuously sync edit sessions. That first requires tolerance of edit sessions originating from multiple VS Code clients concurrently.
On , we do have a service worker which is used primarily for caching. Service workers can outlive their associated pages, and can be synchronously 'd to like other workers. Perhaps we can use that service worker (or a new one) to allow the workbench to send information to save before it unloads.
Change:
})), [ { inlineDecorations: [{ startOffset: 8, endOffset: 23 }] }, <del> { inlineDecorations: [{ startOffset: 4, endOffset: 42 }] }, </del> <ins> { inlineDecorations: [{ startOffset: 4, endOffset: 30 }] }, </ins> { inlineDecorations: [{ startOffset: 4, endOffset: 16 }] }, { inlineDecorations: undefined }, { inlineDecorations: undefined },

Discussion:
With &#x60;"editor.wordWrap": "on"&#x60;, the color hints (inline color decorators) may be double-displayed near the wrapped view edges. &#x2D;--- Version: 1.75.1 Commit: User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/ Firefox/111.0 Embedder: <!-- generated by web issue reporter --
Can you share a screenshot?
<img src="https://user-" alt="" /
Hi could you post here the example from the image?
Update
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
/verified <img src="" alt="" /Basically alright. But the early wrapping may be optimized. (see near line 6 "#", "#")
Change:
for (const command of (this._session?.agent.slashCommands ?? []).sort((a, b) => b.name.length - a.name.length)) { const withSlash = `/${command.name}`; const firstLine = model.getLineContent(1); <del> if (firstLine.startsWith(withSlash)) { </del> <ins> if (firstLine.match(new RegExp(`^${escapeRegExpCharacters(withSlash)}(s|$)`))) { </ins> newDecorations.push({ range: new Range(1, 1, 1, withSlash.length + 1), options: { description: 'inline-chat-slash-command', inlineClassName: 'inline-chat-slash-command', <del> after: { // Force some space between slash command and placeholder content: ' ' } </del> } });

Discussion:
open inline chat type , accept suggestion and type :bug: you know have "/explainthis" even tho it isn't rendered as such !
Change:
public readonly id: string; public readonly displayName: string; <ins> public readonly providerDisplayName: string | undefined; </ins> public readonly priority: CustomEditorPriority; public readonly selector: readonly CustomEditorSelector[]; constructor(descriptor: { readonly id: string; readonly displayName: string; <ins> readonly providerDisplayName: string | undefined; </ins> readonly priority: CustomEditorPriority; readonly selector: readonly CustomEditorSelector[]; }) { this.id = descriptor.id; this.displayName = descriptor.displayName; <ins> this.providerDisplayName = descriptor.providerDisplayName; </ins> this.priority = descriptor.priority; this.selector = descriptor.selector; }

Discussion:
re This uses VS Code as hard-coded name, not the product name This reads a little cumbersome, why not "Text Editor" and as description (built-in) <img width="361" alt="Screenshot 2020-04-03 at 13 46 27" src="https://user-"
Fixed by
Change:
assert.deepEqual(labels.shorten(['xb', 'yb']), ['x…', 'y…']); assert.deepEqual(labels.shorten(['xa', 'xb']), ['xa', 'xb']); <ins> // same name ending assert.deepEqual(labels.shorten(['ab', 'ac', 'ae-b']), ['…b', '…c', '…e-b']); </ins> // same in the middle assert.deepEqual(labels.shorten(['abc', 'dbe']), ['…c', '…e']);

Discussion:
/cc Notice the middle tab is truncated as , it should be ! All folders share the same grandparent: !
Change:
data.language, data.outputs ? data.outputs.map(NotebookCellOutput.to) : undefined, data.metadata ? NotebookCellMetadata.to(data.metadata) : undefined, <ins> data.internalMetadata ? NotebookCellExecutionSummary.to(data.internalMetadata) : undefined </ins> ); } }

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: Insiders OS Version: Mac Steps to Reproduce: a serializer a document with cells having an execution order execution order is not available in the cells
Change:
export interface IFindInFilesArgs { query?: string; replace?: string; <ins> preserveCase?: boolean; </ins> triggerSearch?: boolean; filesToInclude?: string; filesToExclude?: string; isRegex?: boolean; isCaseSensitive?: boolean; matchWholeWord?: boolean; <ins> excludeSettingAndIgnoreFiles?: boolean; </ins> } export const FindInFilesCommand: ICommandHandler = (accessor, args: IFindInFilesArgs = {}) => {

Discussion:
When executing search from extension api 2 checkboxes are not exposed: Preserve Case Use Exclude Settings and Ignore Files !
Hey , Can you please explain a little more about the issue?
It's possible to trigger a search from extension by using this api: And it has a good amount of options: But 2 of them are missing:
Thank got the idea. I will raise a PR to fix the issue ASAP :)
I have raised the . If you get time please review :)
genuinely didn't notice the existing PR, apologies
Thanks :). No problem
It great now that it's possible to control it but why does it called ? Would it possible to have the same name as in label:
Updated to as per suggestion and for consistency with search editor post . Also these to the keybindings intellisense registry.
Change:
* Checks if the settings have enabled the new code action widget. */ private isCodeActionWidgetEnabled(model: ITextModel): boolean { <del> return this._configurationService.getValue('editor.experimental.useCustomCodeActionMenu', { </del> <ins> return this._configurationService.getValue('editor.useCustomCodeActionMenu', { </ins> resource: model.uri }); }

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: OS Version: Steps to Reproduce: In some color themes, like the Default Light themes, the selected object's text is hard to read in the code action widget. !
Change:
} private getVolumeInPercent(): number { <del> const volume = this.configurationService.getValue<number>('accessibilitySignals.volume'); </del> <ins> const volume = this.configurationService.getValue<number>('accessibility.signalOptions.volume'); </ins> if (typeof volume !== 'number') { return 50; }

Discussion:
Type: <bBug</bscreen ready accessiblity mode to be on. Look for screen reader optimized at the bottom bar of VS Code. settings, search for "accessibility volume". Set it to 0. an action in a VS Code editor that creates a sound (which you haven't configured to be "off"/"never"), eg trigger an inline copilot suggestion. a sound (make sure your computer audio is on) even though you set volume to 0. VS Code version: Code 1.91.1 (, 2024-07-09T22:07:46.768Z) OS version: Darwin arm64 23.5.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (71)</summaryExtensionVersion ------ better-comments3.0.2 quitcontrol-vscode4.0.0 solarized-light-custom4.0.1 solidjs3.0.7 vscode-tailwindcss0.12.5 turbo-console-log2.10.4 ruff2024.30.0 regex0.4.0 doxdocgen1.4.0 vscode-eslint3.0.10 xml2.5.1 es7-react-js-snippets3.1.1 gitlens15.2.0 prettier-vscode10.4.0 figma-vscode-extension0.3.5 auto-rename-tag0.1.10 shell-format7.2.5 kotlin0.2.34 macros1.2.1 copilot1.213.0 copilot-chat0.17. vscode-pull-request-github0.92.0 go0.41.4 gti-vscode0.6.1 vscode-graphql-syntax1.3.6 better-cpp-syntax1.27.1 vscode-go-template0.2.1 cmake-language-support-vscode0.0.9 Kotlin1.7.1 git-graph1.30.0 vscode-docker1.29.1 vscode-dotnet-runtime2.0.9 black-formatter2024.3. debugpy2024.9.

isort2023.10.1 python2024.10.0 vscode-pylance2024.7.1 jupyter2024.6.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 remote-containers0.375.1 remote-ssh0.112.0 remote-ssh-edit0.86.0 remote-wsl0.88.2 vscode-remote-extensionpack0.25.0 cmake-tools1.18.43 cpptools1.20.5 cpptools-extension-pack1.3.0 remote-explorer0.4.3 remote-server1.5.2 test-adapter-converter0.1.9 vsliveshare1.0.5932 vsix-viewer1.0.5 vscode-hack2.20.0 quicktype23.0.170 webgl-glsl-editor1.3.8 code-spell-checker3.0.1 tauri-vscode0.2.6 blueprint3.0.0 best-dark-themes-pack1.0.2 best-light-themes-pack1.0.2 cmake0.0.17 vscode-lldb1.10.0 vscode-swiftformat1.6.10 change-case1.0.0 luahelper0.2.28 pretty-ts-errors0.5.4 markdown-all-in-one3.6.2 material-theme3.17.2 (28 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
thanks for taking a look ! i believe this will resolve as well
Specifically the setting doesn't get saved to Even if you write it manually in , VSCode removes it on next start. Both and have this problem.
Change:
switch (type) { case DiffEntryType.Equal: if (originalLine === modifiedLine) { <del> ariaLabel = nls.localize({ key: 'unchangedLine', comment: ['The placholders are contents of the line and should not be translated.'] }, "{0} unchanged line {1}", lineContent, originalLine); </del> <ins> ariaLabel = nls.localize({ key: 'unchangedLine', comment: ['The placeholders are contents of the line and should not be translated.'] }, "{0} unchanged line {1}", lineContent, originalLine); </ins> } else { ariaLabel = nls.localize('equalLine', "{0} original line {1} modified line {2}", lineContent, originalLine, modifiedLine); }

Discussion:
nls.localize() generally involves human visible output. Technically there are 2-3 arguments and the main human facing one is the second. The first argument is often treated as an "opaque" string, but in most systems, it's used to communicate to localizers, so, to some extent, there is value in not having misspellings there either. I can split out the identifiers if requested... Does this issue occur when all extensions are disabled?: Yes
can you provide me with more details about this. We use Transifex to translate our strings and the system contains both the value and the key.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
Change:
} .monaco-editor .peekview-widget .head .peekview-title .dirname { <ins> overflow: hidden; text-overflow: ellipsis; </ins> white-space: nowrap; }

Discussion:
VS Code Version: 1.73.1 OS Version: Win 11 Steps to Reproduce: the PeekViewWidget (eg using Peek Definition, or Show Error) text in the title bar is misaligned Fix: I have a PR, it's trivial. !