nano -l N soft wrap vs -w nowrap for large logs over high-latency SSH

Direct answer

Use -w (nowrap) when column alignment with external tools is required, and accept horizontal scrolling. Use -l N (soft wrap) only when limiting horizontal scroll matters more than exact columns. Nano cannot do both at once: soft wrap reflows long lines into multiple visual rows, so displayed columns no longer match file byte offsets, while nowrap preserves one physical line per screen line and forces horizontal scroll past the terminal width.

Soft wrap changes the line mapping

With -l N, a single physical line can occupy several displayed lines. Cursor movement acts on displayed lines, so repeated down presses may stay inside the same physical line. When line numbers are enabled with -c, the numbers still refer to physical lines, not visual rows. That decouples screen position from file offset, making soft wrap unsuitable for correlating with grep, sed, or awk output.

External changes on write

GNU nano 6.x/7.x does not monitor an opened file for modifications by other processes. If a log is appended while nano is open, the buffer is stale. Saving with ^O writes the buffer back and silently overwrites the file, discarding concurrent changes. There is no change-detection prompt. Reload externally with ^R (Insert File) before saving, or open logs in view mode with -v to disable writing entirely.

Verification steps

1. Open the log: nano -l 80 -c file.log. Confirm line numbers advance only at physical-line boundaries while the cursor crosses wrapped visual lines.
2. Open the same log: nano -w -c file.log. Confirm one physical line per screen line and compare a column against awk output.
3. From another SSH session, append a line while nano is open. Save in nano with ^O, exit, and reopen. The appended line is missing, demonstrating silent overwrite.

Assumptions and missing detail

This assumes GNU nano 6.x or 7.x and a correctly reported terminal width. Confirm the installed version with nano --version, because older versions may differ. One detail changes the recommendation: do you need to save edits inside nano, or is this strictly read-only viewing? If read-only, use nano -v -w -c file.log so accidental saves are impossible.