hluk/CopyQ

CopyQ overwrites save-as location instead of adding to it

Open

#3464 opened on Mar 6, 2026

View on GitHub
 (5 comments) (0 reactions) (0 assignees)C++ (7,372 stars) (419 forks)batch import
Windowsbughelp wanted

Description

Describe the bug When I paste into a Win11 save-as dialog's 'filename' field, the text already in the box is completely over-written instead of adding text where the curser is, or replacing selected text.

To Reproduce Edit an existing file with MSword/Excel Click save-as in MSword/Xcel The existing filename is highlighted in the filename field. Click at the end of the filename indicating that you want to add to the end of the existing text. Double click in copyq and it replaces the entire text in the filename field.

Expected behavior Copyq should paste text where the cursor is, instead of replacing all the text. Or, if a portion of the text is selected, it should replace only that portion.

Version, OS and Environment copyq version 13.0.0 Windows 11

Contributor guide

Tech stack
cpp
Domain
desktop
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C++QtWindows clipboard API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Examine the paste event handling in CopyQ’s source code, specifically the clipboard monitoring and text insertion logic. Check if the issue relates to how CopyQ interacts with the Windows clipboard API when targeting native edit controls in save as dialogs. Look for existing comments or tests about paste behavior in dialogs. Consider debugging the event flow to identify where the full replacement occurs.