Exercise 3: Status Bar Investigation — Possible Solution
====================================================================

STEPS
------------------------------
1. With any file open in the Editor Group, look at the Status Bar
   (bottom strip). Towards the right side, you'll see the file's
   detected language (e.g. "Python", "JavaScript", "Plain Text").
2. Click directly on that language name. A dropdown/quick-pick list
   opens at the top of the window, letting you manually select a
   different language mode for the current file (useful for a file
   VS Code guessed wrong, or a file extension it doesn't recognize).
3. Press Escape to close it without changing anything, or pick a new
   language to see the syntax highlighting update immediately.
4. Also in the Status Bar, find the "Ln X, Col Y" indicator (showing
   your cursor's current line and column). Click it — a small input
   box appears at the top asking "Type a line number, followed by an
   optional colon and a character number to navigate to".
5. Type a line number (e.g. 10) and press Enter — the cursor jumps to
   that line in the editor.

WHAT TO NOTE
------------------------------
The language-mode picker shows VS Code's own guess highlighted, plus
every other language it knows about via installed extensions — this
list grows as more language-specific extensions are installed
(Chapter 4). The line-jump input accepts "line:column" together
(e.g. "10:5") to jump to an exact cursor position, not just a line.

WHY THIS WORKS AS AN ANSWER
------------------------------
Both indicators demonstrate that the Status Bar isn't just a passive
display — per the chapter's own concept-grid description of it as
showing "language mode, line/column position," this exercise proves
both are also interactive CONTROLS, not just readouts, which is easy
to miss on a first glance at the interface. Recognizing the Status Bar
as clickable is a small but genuinely time-saving habit once
internalized, since both actions would otherwise require digging
through menus.