microsoft / microsoft/vscode-cpptools

Group source and header in open editor tabs

Open
#2,307 8 comments 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Request Language Service
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

Type: LanguageService

Hello,
i posted the following request in the VSCode repository, but they said it is an issue for the extension, therefore i would like to request this feature here:

Issue Type: Feature Request

Hello,

when editing C++ projects most times i have the implementation and header file for the classes (i am currently editing) open at the same time. I like to have the editor tabs grouped so that the header is next to the implementation file (xx.cpp | xx.h | xy.cpp | xy.h ...).

Is it possible if a new tab is openend that it is moved automatically right beside the one with the same name (except for the file extension)? And e.g. if i Ctrl+Click on a Symbol in xy.cpp the file where the symbol is declared will be opened to the right, could this be changed so that the new editor tab would be opened at the right edge of all opened editors or to the right of the "Group" of implementation and header?

Best regards,
Jan Masak

VS Code version: Code 1.25.0 (0f080e5, 2018-07-05T13:11:58.697Z)
OS version: Windows_NT x64 6.1.7601
C/C++ Extension Version: 0.17.6

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.

Research direction

No source files or tests are named. Start by reviewing how the C/C++ extension handles VS Code editor tabs and Ctrl+Click symbol navigation; done means matching .cpp and .h files open beside each other and newly opened declaration tabs follow the requested group or edge behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, vscode
Domain
desktop, developer-experience
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.