main.js · part 129

60 text occurrences from desktop/Cursor.app/Contents/Resources/app/extensions/cursor-local-agent-runtime/dist/main.js, part 129. Every entry preserves the shipped literal and its saved verdict or selection reason.

File contents and all parts · All files

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

The patch to apply to the file

Use this tool to edit files.
Your patch language is a stripped-down, file-oriented diff format designed to be easy to parse and safe to apply. You can think of it as a high-level envelope:

*** Begin Patch
[ one file section ]
*** End Patch

Within that envelope, you get one file operation.
You MUST include a header to specify the action you are taking.
Each operation starts with one of two headers:

*** Add File: <path> - create a new file. Every following line is a + line (the initial contents).
*** Update File: <path> - patch an existing file in place (optionally with a rename).

Then one or more "hunks", each introduced by @@ (optionally followed by a hunk header).
Within a hunk each line starts with:

For instructions on [context_before] and [context_after]:
- By default, show 3 lines of code immediately above and 3 lines immediately below each change. If a change is within 3 lines of a previous change, do NOT duplicate the first change's [context_after] lines in the second change's [context_before] lines.
- If 3 lines of context is insufficient to uniquely identify the snippet of code within the file, use the @@ operator to indicate the class or function to which the snippet belongs. For instance, we might have:
@@ class BaseClass
[3 lines of pre-context]
- [old_code]
+ [new_code]
[3 lines of post-context]

- If a code block is repeated so many times in a class or function such that even a single `@@` statement and 3 lines of context cannot uniquely identify the snippet of code, you can use multiple `@@` statements to jump to the right context. For instance:

@@ class BaseClass
@@ 	def method():
[3 lines of pre-context]
- [old_code]
+ [new_code]
[3 lines of post-context]

The full grammar definition is below:
Patch := Begin { FileOp } End
Begin := "*** Begin Patch" NEWLINE
End := "*** End Patch" NEWLINE
FileOp := AddFile | UpdateFile
AddFile := "*** Add File: " path NEWLINE { "+" line NEWLINE }
UpdateFile := "*** Update File: " path NEWLINE { Hunk }
Hunk := "@@" [ header ] NEWLINE { HunkLine } [ "*** End of File" NEWLINE ]
HunkLine := (" " | "-" | "+") text NEWLINE

Example for Update File:
*** Begin Patch
*** Update File: pygorithm/searching/binary_search.py
@@ class BaseClass
@@     def search():
-          pass
+          raise NotImplementedError()

@@ class Subclass
@@     def search():
-          pass
+          raise NotImplementedError()
*** End Patch

Example for Add File:
*** Begin Patch
*** Add File: [path/to/file]
+ [new_code]
*** End Patch

It is important to remember:
- You must only include one file per call
- You must include a header with your intended action (Add/Update)
- You must prefix new lines with ` +` even when creating a new file

All file paths must be absolute paths. Make sure to read the file before applying a patch to get the latest file content, unless you are creating a new file.

Missing *** Add/Update File header.

Invalid patch format. Your diff must begin with ${VRe} and end with ${KRe}.

Invalid patch format

*** Add File

*** Update File

*** Add File

The file ${p} has been updated.

No changes to the file were made.

There was an error applying the patch, and it was NOT applied. Make sure to follow the patch format and add `+` to the beginning of each line.

There was an error applying the patch, and it was NOT applied. Read the file before trying again as the user may have changed the file since you last read it.

Invalid patch provided

Unknown error

Error applying patch

Invalid patch format. Your diff must begin with ${VRe} and end with ${KRe}.

Invalid patch format

*** Update File

*** Add File

There was an error applying the patch, and it was NOT applied. Make sure to follow the patch format and add `+` to the beginning of each line.

Invalid patch provided

There was an error applying the patch, and it was NOT applied. Make sure to follow the patch format and add `+` to the beginning of each line.

Invalid patch provided

Success. Updated the following files:
A ${p}

start: begin_patch hunk end_patch
begin_patch: "*** Begin Patch" LF
end_patch: "*** End Patch" LF?

hunk: add_hunk | update_hunk
add_hunk: "*** Add File: " filename LF add_line+
update_hunk: "*** Update File: " filename LF change?

filename: /(.+)/
add_line: "+" /(.*)/ LF -> line

change: (change_context | change_line)+ eof_line?

change_context: ("@@" | "@@ " /(.+)/) LF
change_line: ("+" | "-" | " ") /(.*)/ LF
eof_line: "*** End of File" LF

%import common.LF

Failed to parse notebook as JSON

The notebook file is not valid JSON

${e.path.join(".")}: ${e.message}

Invalid notebook structure: ${e}

The notebook file does not match the expected Jupyter notebook format: ${e}

Object expected.

Symbol.asyncDispose is not defined.

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

The path to the notebook file you want to edit. You can use either a relative path in the workspace or an absolute path. If an absolute path is provided, it will be preserved as is.

The index of the cell to edit (0-based)

If true, a new cell will be created at the specified cell index. If false, the cell at the specified cell index will be edited.

The language of the cell to edit. Should be STRICTLY one of these: 'python', 'markdown', 'javascript', 'typescript', 'r', 'sql', 'shell', 'raw' or 'other'.

The text to replace (must be unique within the cell, and must match the cell contents exactly, including all whitespace and indentation).

The edited text to replace the old_string or the content for the new cell.

Unhandled version: ${e}

Use this tool to edit a jupyter notebook cell.
Cell indices are 0-based. 'old_string' and 'new_string' should be a valid cell content, i.e. WITHOUT any JSON syntax that notebook files use under the hood. If you need to create a new notebook, just set 'is_new_cell' to true and cell_idx to 0.

Use this tool to edit a jupyter notebook cell. Use ONLY this tool to edit notebooks.

This tool supports editing existing cells and creating new cells:
	- If you need to edit an existing cell, set 'is_new_cell' to false and provide the 'old_string' and 'new_string'.
		-- The tool will replace ONE occurrence of 'old_string' with 'new_string' in the specified cell.
	- If you need to create a new cell, set 'is_new_cell' to true and provide the 'new_string' (and keep 'old_string' empty).
	- It's critical that you set the 'is_new_cell' flag correctly!
	- This tool does NOT support cell deletion, but you can delete the content of a cell by passing an empty string as the 'new_string'.

Other requirements:
	- Cell indices are 0-based.
	- 'old_string' and 'new_string' should be a valid cell content, i.e. WITHOUT any JSON syntax that notebook files use under the hood.
	- The old_string MUST uniquely identify the specific instance you want to change. This means:
		-- Include AT LEAST 3-5 lines of context BEFORE the change point
		-- Include AT LEAST 3-5 lines of context AFTER the change point
	- This tool can only change ONE instance at a time. If you need to change multiple instances:
		-- Make separate calls to this tool for each instance
		-- Each call must uniquely identify its specific instance using extensive context
	- This tool might save markdown cells as "raw" cells. Don't try to change it, it's fine. We need it to properly display the diff.
	- If you need to create a new notebook, just set 'is_new_cell' to true and cell_idx to 0.
	- ALWAYS generate arguments in the following order: target_notebook, cell_idx, is_new_cell, cell_language, old_string, new_string.
	- Prefer editing existing cells over creating new ones!
	- ALWAYS provide ALL required arguments (including BOTH old_string and new_string). NEVER call this tool without providing 'new_string'.

Invalid notebook format

old_string must be empty when creating a new cell

Invalid arguments for creating new cell

old_string must be empty when is_new_cell is true

A new ${s.cell_language} cell was created at index ${s.cell_idx} in notebook ${s.target_notebook}.

Cell index ${s.cell_idx} out of range

Cell index out of range

Cell index ${s.cell_idx} is out of range. The notebook has ${o.cells.length} cells (indices 0-${o.cells.length-1}).

Cell at index ${s.cell_idx} is invalid

Invalid cell

Cell at index ${s.cell_idx} does not have a valid source field

old_string is empty but cell has content