Merge pull request #11003 from MicrosoftDocs/main638904710626561837sync_temp

For protected branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

.openpublishing.redirection.json

@@ -1,5 +1,20 @@
 {
   "redirections": [
+    {
+      "source_path": "docs/ide/reference/options-text-editor-all-languages-tabs.md",
+      "redirect_url": "/visualstudio/ide/options-text-editor-all-languages-tabs",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/paste-json-xml.md",
+      "redirect_url": "/visualstudio/ide/paste-json-xml",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "docs/ide/reference/immediate-window.md",
+      "redirect_url": "/visualstudio/ide/immediate-window",
+      "redirect_document_id": false
+    },
     {
       "source_path": "docs/ide/reference/miscellaneous-files.md",
       "redirect_url": "/visualstudio/ide/miscellaneous-files",

docs/debugger/debugger-windows.md

@@ -22,7 +22,7 @@ You can open most debugger windows while you're debugging your program. To see a
 |Autos|CTRL+ALT+V, A|[Autos and Locals Windows](../debugger/autos-and-locals-windows.md)|
 |Locals|CTRL+ALT+V, L|[Autos and Locals Windows](../debugger/autos-and-locals-windows.md)|
 |Call Stacks|CTRL+ALT+C|[How to: Use the Call Stack Window](../debugger/how-to-use-the-call-stack-window.md)|
-|Immediate|CTRL+ALT+I|[Immediate Window](../ide/reference/immediate-window.md)|
+|Immediate|CTRL+ALT+I|[Immediate Window](../ide/immediate-window.md)|
 |Parallel Stacks|CTR:+SHIFT+D, S|[Using the Parallel Stacks Window](../debugger/using-the-parallel-stacks-window.md)|
 |Parallel Watch|CTR:+SHIFT+D, (1, 2, 3, 4)|[Get started Debugging Multithreaded Applications](../debugger/get-started-debugging-multithreaded-apps.md)|
 |Threads|CTRL+ALT+H|[View threads in the Visual Studio debugger](../debugger/walkthrough-debugging-a-multithreaded-application.md)|

docs/debugger/toc.yml

@@ -362,8 +362,8 @@
       href: /visualstudio/bridge/bridge-to-kubernetes-vs
     - name: Debug with Container Tools >>
       href: ../containers/edit-and-refresh.md
-  - name: Immediate window
-    href: ../ide/reference/immediate-window.md
+  - name: Use the Immediate window
+    href: ../ide/immediate-window.md
   - name: Work with...
     items:
     - name: .NET

docs/debugger/walkthrough-debugging-at-design-time.md

@@ -23,7 +23,7 @@ To debug XAML code behind an app from the XAML designer, such as declarative dat
 
 ## Use the Immediate window
 
-You can use the Visual Studio **Immediate** window to execute a function or subroutine without running your app. If the function or subroutine contains a breakpoint, Visual Studio will break at the breakpoint. You can then use the debugger windows to examine your program state. This feature is called *debugging at design time*. For detailed information, see [Use the Immediate window](../ide/reference/immediate-window.md)
+You can use the Visual Studio **Immediate** window to execute a function or subroutine without running your app. If the function or subroutine contains a breakpoint, Visual Studio will break at the breakpoint. You can then use the debugger windows to examine your program state. This feature is called *debugging at design time*. For detailed information, see [Use the Immediate window](../ide/immediate-window.md)
 
 The following example is in Visual Basic. You can also use the **Immediate** window at design time in C#, F#, and C++/CLI apps. For C++/CLI, compile without the /clr option to use the Immediate window.
 

docs/ide/reference/immediate-window.md renamed to docs/ide/immediate-window.md

@@ -26,7 +26,7 @@ The **Immediate** window supports IntelliSense.
 
 ## Display the values of variables
 
-The **Immediate** window is useful when you debug an app. For example, to check the value of a variable `varA`, you can use the [Print command](../../ide/reference/print-command.md):
+The **Immediate** window is useful when you debug an app. For example, to check the value of a variable `varA`, you can use the [Print command](../ide/reference/print-command.md):
 
 ```cmd
 >Debug.Print varA
@@ -41,7 +41,7 @@ The question mark (`?`) is an alias for `Debug.Print`, so this command can also
 Both versions of this command return the value of the variable `varA`.
 
 > [!TIP]
-> To issue a Visual Studio command in the **Immediate** window, you must preface the command with a greater than sign (`>`). To enter multiple commands, switch to the [Command window](command-window.md).
+> To issue a Visual Studio command in the **Immediate** window, you must preface the command with a greater than sign (`>`). To enter multiple commands, switch to the [Command window](../ide/reference/command-window.md).
 
 ## Design-time expression evaluation
 
@@ -71,7 +71,7 @@ You can use the **Immediate** window to execute a function or subroutine at desi
 
     The **Immediate** window runs `MyFunction` and displays `4`.
 
-If the function or subroutine contains a breakpoint, Visual Studio breaks execution at the appropriate point. You can then use the debugger windows to examine your program state. For more information, see [Walkthrough: Debug at design time](../../debugger/walkthrough-debugging-at-design-time.md).
+If the function or subroutine contains a breakpoint, Visual Studio breaks execution at the appropriate point. You can then use the debugger windows to examine your program state. For more information, see [Walkthrough: Debug at design time](../debugger/walkthrough-debugging-at-design-time.md).
 
 You can't use design-time expression evaluation in project types that require starting up an execution environment, including Visual Studio Tools for Office projects, web projects, Smart Device projects, and SQL projects.
 
@@ -124,9 +124,9 @@ In some settings configurations, first-chance exception notifications are displa
 
 ## Related content
 
-- [Navigating through code by using the debugger](../../debugger/navigating-through-code-with-the-debugger.md)
-- [Command Window](../../ide/reference/command-window.md)
-- [Overview of the debugger](../../debugger/debugger-feature-tour.md)
-- [Debug at design time](../../debugger/walkthrough-debugging-at-design-time.md)
-- [Visual Studio Command Aliases](../../ide/reference/visual-studio-command-aliases.md)
-- [Use regular expressions in Visual Studio](../../ide/using-regular-expressions-in-visual-studio.md)
+- [Navigating through code by using the debugger](../debugger/navigating-through-code-with-the-debugger.md)
+- [Command Window](../ide/reference/command-window.md)
+- [Overview of the debugger](../debugger/debugger-feature-tour.md)
+- [Debug at design time](../debugger/walkthrough-debugging-at-design-time.md)
+- [Visual Studio Command Aliases](../ide/reference/visual-studio-command-aliases.md)
+- [Use regular expressions in Visual Studio](../ide/using-regular-expressions-in-visual-studio.md)

docs/ide/reference/media/paste-class-placeholder.png renamed to docs/ide/media/paste-class-placeholder.png

@@ -0,0 +1,94 @@
+---
+title: Configure indent and tab settings
+description: Learn how to use the Tabs page in the All Languages section to change the default behavior of the code editor tabs within Visual Studio.
+ms.date: 08/08/2025
+ms.topic: reference
+f1_keywords:
+- VS.ToolsOptionsPages.Text_Editor.All_Languages.Tabs
+- VS.ToolsOptionsPages.Text_Editor.Basic.Tabs
+- VS.ToolsOptionsPages.Text_Editor.CSharp.Tabs
+- VS.ToolsOptionsPages.Text_Editor.C%2FC%2B%2B.Tabs
+- VS.ToolsOptionsPages.Text_Editor.CoffeeScript.Tabs
+- VS.ToolsOptionsPages.Text_Editor.CSS.Tabs
+- VS.ToolsOptionsPages.Text_Editor.Dockerfile.Tabs
+- VS.ToolsOptionsPages.Text_Editor.F%2523.Tabs
+- VS.ToolsOptionsPages.Text_Editor.HQL.Tabs
+- VS.ToolsOptionsPages.Text_Editor.HTML.Tabs
+- VS.ToolsOptionsPages.Text_Editor.HTMLX.Tabs
+- VS.ToolsOptionsPages.Text_Editor.JavaScript.Tabs
+- VS.ToolsOptionsPages.Text_Editor.TypeScript.Tabs
+- VS.ToolsOptionsPages.Text_Editor.JSON.Tabs
+- VS.ToolsOptionsPages.Text_Editor.LESS.Tabs
+- VS.ToolsOptionsPages.Text_Editor.Plain_Text.Tabs
+- VS.ToolsOptionsPages.Text_Editor.ResJSON.Tabs
+- VS.ToolsOptionsPages.Text_Editor.SCSS.Tabs
+- VS.ToolsOptionsPages.Text_Editor.SQL_Server_Tools.Tabs
+- VS.ToolsOptionsPages.Text_Editor.StreamAnalytics.Tabs
+- VS.ToolsOptionsPages.Text_Editor.T-SQL90.Tabs
+- VS.ToolsOptionsPages.Text_Editor.U-SQL.Tabs
+- VS.ToolsOptionsPages.Text_Editor.XAML.Tabs
+- VS.ToolsOptionsPages.Text_Editor.XML.Tabs
+helpviewer_keywords:
+- indents, Code Editor
+- Code Editor, default behavior
+- tabs, setting in Code Editor
+- All Languages Text Editor Options dialog box
+- editors, Code Editor
+- Code Editor, indenting
+- Code Editor, tabs
+ms.custom: "ide-ref"
+author: anandmeg
+ms.author: meghaanand
+manager: mijacobs
+ms.subservice: general-ide
+---
+# Configure indent and tab settings in Visual Studio
+
+Learn how to change the default tab and indentation behavior for the Code Editor in Visual Studio using the text editor configuration options.
+
+## Access the All Languages Tabs options
+
+1. Open Visual Studio.
+2. On the menu bar, select **Tools** > **Options**.
+3. In the Options dialog, expand the **Text Editor** node.
+4. Expand **All Languages**, then select **Tabs**.
+
+> [!CAUTION]
+> Changes made here apply to all development languages. Resetting options in this dialog will override individual language settings. To configure options for a specific language, select its subfolder under **Text Editor**.
+
+## Resolve conflicting settings
+
+If you select different tab or indent settings for individual languages, Visual Studio displays a warning message:
+- "The indentation settings for individual text formats conflict with each other," for differing **Indenting** options.
+- "The tab settings for individual text formats conflict with each other," for differing **Tab** options.
+
+For example, if **Smart indenting** is set for Visual Basic and **Block indenting** for Visual C++, you’ll see a reminder about the conflict.
+
+## Configure indenting options
+
+In the **Indenting** section, choose one of the following indenting styles:
+
+- **None**: New lines are not indented; the cursor starts at the first column.
+- **Block**: New lines are automatically indented to match the previous line.
+- **Smart**: New lines are indented based on code context and IntelliSense conventions. Not available for all languages.
+
+For example, lines between braces `{ }` may be indented an extra tab stop.
+
+## Configure tab options
+
+In the **Tabs** section, choose the following options.
+
+- **Tab size**: Sets the number of spaces per tab stop (default: 4).
+- **Indent size**: Sets the number of spaces for each indentation (default: 4). Tabs, spaces, or both are used to fill the size.
+- **Insert spaces**: Indent operations insert only space characters.
+- **Keep tabs**: Indent operations insert as many tab characters as possible; spaces fill any remainder.
+
+## Troubleshooting
+
+> [!TIP]
+> Adaptive formatting may override your custom tab settings. To disable adaptive formatting, go to **Text Editor** > **Advanced** and toggle **Use adaptive formatting**. You can also use an [.editorconfig](../ide/create-portable-custom-editor-options.md) file to manage indent styles.
+
+## Next steps
+
+- [Options, Text Editor, All Languages](../ide/reference/options-text-editor-all-languages.md)
+- [General, Environment, Options Dialog Box](../ide/reference/general-environment-options-dialog-box.md)