Skip to content

Add FAQ entry about edit() returning immediately - #3780

Open
kdeldycke wants to merge 1 commit into
pallets:stablefrom
kdeldycke:spawned-editor-faq
Open

Add FAQ entry about edit() returning immediately#3780
kdeldycke wants to merge 1 commit into
pallets:stablefrom
kdeldycke:spawned-editor-faq

Conversation

@kdeldycke

@kdeldyckekdeldycke commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator

This explain why some editors are returning immediately and does not respect the contract of the edit() utility.

Also added a warning admonition to the edit() docstring itself so developers relying on it get informed about the limitations.

Closes#2582.

@kdeldyckekdeldycke added windows Windows-specific behavior prompt Interactive input and confirmation labels Aug 19, 2026
@kdeldyckekdeldycke added this to the 8.5.0 milestone Aug 19, 2026
@kdeldyckekdeldycke removed the windows Windows-specific behavior label Aug 19, 2026
@Rowlando13Rowlando13 modified the milestones: 8.5.0, 8.5.1Aug 22, 2026
@kdeldycke
kdeldycke changed the base branch from main to stableAugust 27, 2026 14:25
@Rowlando13

Copy link
Copy Markdown
Member

@kdeldycke still 2 comments on this

@kdeldycke

Copy link
Copy Markdown
CollaboratorAuthor

@kdeldycke still 2 comments on this

Ah? Where? Maybe you left them on your side in a pending review but did not submit them, which is why I don't see them. Happened to me last time: your GitHub review comments are not public until you submit the whole review.

Comment threaddocs/faqs.md Outdated
Comment threaddocs/faqs.md Outdated
@Rowlando13

Copy link
Copy Markdown
Member

That was it.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

promptInteractive input and confirmation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The edit utility does not work on Windows for Visual Studio Code

3 participants

@kdeldycke@Rowlando13@davidism