view

Open a file

$ view [path/to/file]

view [options] [file ...]

file ...
    One or more files to be opened in read-only mode. If multiple files are specified, view will open them in separate buffers.

-c {command}
    Executes the specified command immediately after the first file is loaded. This is useful for jumping to a specific line (e.g., view -c '100' myfile.txt to go to line 100) or performing a search on startup.

+{num}
    Starts editing at the line number num. Equivalent to -c '{num}'.

-S {scriptfile}
    Sources the commands from scriptfile after loading the first file. This allows for automated setup or viewing operations.

-R
    Explicitly sets read-only mode. While view implicitly does this, this option is generally associated with vi/vim and is the mechanism view uses.

--help
    Displays a summary of command-line options and exits.

--version
    Displays version information and exits.

The view command is a specialized invocation of the vi or vim text editor, designed specifically for read-only file viewing. Its primary purpose is to allow users to inspect the contents of a file without the risk of accidentally making or saving modifications. When invoked, view automatically sets the 'readonly' option within the editor, preventing write operations unless explicitly overridden (e.g., using :w!).

This command is particularly useful for examining configuration files, log files, or source code where no changes are intended. It provides all the powerful navigation, searching, and syntax highlighting features of vi or vim, but with an added layer of safety. While view might appear to be a separate utility, it is often a symbolic link to vi or vim with the -R (read-only) option enabled by default, making it a convenient shortcut for secure file inspection.

Although view enables read-only mode, it is not foolproof. A determined user can still force a write operation using commands like :w! (write forcefully) or by disabling the 'readonly' option (:set noro) from within the editor. Its primary purpose is to prevent accidental modifications, not to enforce strict access control. The exact behavior and available options of view are dependent on the underlying vi or vim installation it links to.

While view enforces read-only by default, it's possible to override this from within the editor. To save changes (if any were made despite the warning), you can use :w!. To completely disable the read-only flag for the current buffer, type :set noro and press Enter. This will allow normal write operations without force-writing. Conversely, :set ro will re-enable read-only mode.

When a file is opened with view (or vi -R), vim typically indicates the read-only status in the status line at the bottom of the screen, often showing [RO] or [readonly] next to the filename. This provides a clear visual cue to the user that modifications are restricted.

The view command emerged as a convenient wrapper around the vi (Visual editor) and later vim (Vi IMproved) text editors. vi itself originated in the late 1970s, based on the ex line editor. As text editors evolved, the need for a simple, safe way to view files without risk of modification became apparent. Rather than creating a separate viewing utility with an entirely different interface, it was more practical to leverage the existing, powerful features of vi/vim and simply default to read-only mode. Thus, view was implemented, often as a symbolic link to vi or vim with the -R (read-only) flag automatically set, providing a familiar interface for secure file inspection.

vi(1), vim(1), less(1), more(1), cat(1), grep(1)