Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

✨ Scroll and cursor position in file are lost when switching to another file and then back

Open
#1,930 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
swift
Domain
desktop

Research direction

No file or test is named in the issue. Start by reproducing the tab-switching flow in CodeEdit and trace where the open file's cursor and scroll state are handled; done means returning to a previously opened file restores both positions.

Written by the indexing model from the issue text.

Description

bug
Description

When you navigate inside a file, then you go to another file keeping the previous one open and when you get back to the first file, the scroll position and of the cursor location in the first file are lost, so it automatically shows up the top of that file.

To Reproduce
  1. Open the file a.cpp and navigate through it so you go to a specific cpp function inside that file.
  2. Open the file b.cpp in another tab while keeping the file a.cpp open in its tab.
  3. When you get back to the opened tab of the file a.cpp, you are redirected to the top of the file a.cpp.
    So when you are focusing much on a specific function in a.cpp and just wanted to check something related to that in b.cpp, when you get back to the open tab of a.cpp, you completely lost the position of the cursor on the function that you were working on.
Expected Behavior

The position of the cursor in the open file that you left open in a tab for a while should be the same when you get back to it.

Version Information

CodeEdit: [0.3.2]
macOS: [14.1.2 (23B92)]

Additional Context

No response

Screenshots

No response

Dominant language
Swift
Stars
23k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CodeEditApp/CodeEdit

All issues in CodeEditApp/CodeEdit

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.