code-pointer

Open files at precise line numbers using `code -g path/to/file.js:42`. This command launches VSCode and positions the cursor at line 42. For line and column positioning, use `code -g path/to/file.js:42:10` to jump to line 42, column 10. Use absolute paths and quote paths containing spaces for reliable navigation.

Yes. The `-g` flag with line and column syntax guides reviewers directly to code sections: `code -g file.js:42:10` opens the file with cursor at the specified position. This streamlines code review workflows by eliminating manual navigation and ensuring all reviewers reference the same location.

Use `code -g path/to/file.js:line:column` to open files at exact debugging locations. Validate file existence and use absolute paths beforehand. Optional window controls (`-n`, `-r`, `-w`) manage how VSCode opens the file, making it ideal for automated debugging workflows and documentation references.

The `-g` flag works across any file type—source code, configs, and documentation. Combine absolute path resolution with line targeting: `code -g config.yml:15` jumps directly to the TODO or reference. Quote paths with spaces; validate existence to avoid errors in navigation workflows.

Yes, provided you quote the file path. For example: `code -g "path/with spaces/file.js:42"`. Path quoting prevents shell interpretation errors. Always use absolute paths and validate file existence before constructing the command to ensure reliable cursor positioning.

The command requires valid absolute paths and existing files; non-existent files will fail silently or open VSCode without cursor positioning. Column positioning works only for valid line numbers. Window controls (`-n`, `-r`, `-w`) affect display behavior but cannot override VSCode's default file-handling rules.