How to ignore empty lines in composer?

How To
1

Hi,

I’m experiencing an issue with Composer when It wants code changes. The differences are displayed like this:

image
image817×440 46.8 KB

The problem is that it shows 90+ empty lines change, while it should show only 11 lines with actual code change.

Is there any setting that I need to change to fix it?

Thanks

1 Like
2

I came to ask the same question - the agent modifies files and shows a bunch of empty lines at the top, so I have to accept all, and then find out that it forgot some property on line 443.

image
image446×363 7.94 KB

3

Hey, this was reported in another thread and we believe we have pushed a fix for this already, are either of you still facing this issue in Composer?

4

Yes, same problem. Cursor version:

image
image474×369 10.4 KB

Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

5

Same issue for me. I’m on a slightly older version than puliczek… Will try updating…

Version: 0.44.9
VSCode Version: 1.93.1
Commit: 316e524257c2ea23b755332b0a72c50cf23e1b00
Date: 2024-12-26T21:58:59.149Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

6

I have the same issue. It’s super annoying

image
image367×283 7.9 KB

7

The problem with whitespace in agent mode persists in
Cursor Setup 0.44.11 - x64.exe

image
image742×538 18.8 KB

8

Hey, we are aware of this and are working on a fix currently!
Sorry you are seeing this in the meantime…

1 Like
9

Hi, been facing this issue for a few days now… Not all the time, but most of the time… Very annoyed!!! I mean, how hard is it to mitigate this issue??? its just a bunch of empty lines that do no purpose, a simple find and replace should be sufficient. These lines aren’t even rendered in the file itself, only in composer… I am curious what causes this issue, I initially thought its anthropic trying to sneak in extra token costs, because I see no other feasible reason this shouldn’t be fixed in like 5 minutes… and its been weeks already

10

How is it going? The error is still here

image
image363×278 7.78 KB

11

Still seeing this error

image
image356×271 7.46 KB

12

Hey, this issue should be fixed in v0.46, so let us know if you are still seeing this issue in that version!

If not yet available to you, v0.46 should be rolled out to all users in the next day or two.

1 Like
13

I can confirm, it is fixed now :slight_smile: Thanks a lot!