main.js · part 222

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

File contents and all parts · All files

Symbol.dispose is not defined.

Object not disposable.

An error was suppressed during disposal.

Permission denied: ${e}

Permission denied: ${e}

Permission denied: ${e}

The absolute path of the file to delete

The path of the file to delete, relative to the workspace root.

One sentence explanation as to why this tool is being used, and how it contributes to the goal.

Unhandled version: ${e}

Deletes a file at the specified path. The operation will fail gracefully if:
    - The file doesn't exist
    - The operation is rejected for security reasons
    - The file cannot be deleted

Delete file at specified path relative to workspace root; fails gracefully if file doesn't exist, security rejection, or undeletable.

Unhandled version: ${e}

File not found: ${r.result.value.path}

Path is not a file (${r.result.value.actualType}): ${r.result.value.path}

File is busy: ${r.result.value.path}

File deletion rejected

Error deleting file ${r.result.value.path}: ${r.result.value.error}

Unexpected result case: ${r.result.case}

Successfully deleted file: ${t.value.path} (${Number(t.value.fileSize)} bytes)

File not found: ${t.value.path}

Path is not a file (${t.value.actualType}): ${t.value.path}

Permission denied: ${t.value.path}

File is busy: ${t.value.path}

Error deleting file ${t.value.path}: ${t.value.error}

File deletion rejected: ${t.value.reason}

File deletion rejected: ${t.value.path}

Unknown error

Unhandled result case: ${t}

*** Begin Patch

*** End Patch

*** End of File

Index: ${this.index} >= ${this.lines.length}

Expected update hunk to start with a @@ context marker, got: '${this.lines[this.index]}'

Failed to find context:
${e}

*** Delete File:

Delete File is not supported for apply_patch. Please use the delete_file tool instead. Be very careful deleting files that have existing code from the user; ask the user for confirmation first!

Unexpected line found in update hunk: '${t}'. Every line should start with ' ' (context line), '+' (added line), or '-' (removed line)

Object expected.

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 ${Ude} and end with ${Lde}.

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 ${Ude} and end with ${Lde}.

Invalid patch format