Skip to content

Bring the man pages up to date - #517

Open
bbatsov wants to merge 1 commit into
ocaml-community:masterfrom
bbatsov:update-man-pages
Open

Bring the man pages up to date#517
bbatsov wants to merge 1 commit into
ocaml-community:masterfrom
bbatsov:update-man-pages

Conversation

@bbatsov

@bbatsov bbatsov commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

I came across the man pages randomly while looking for the syntax highlighting config and figured the stale bits were worth fixing.

They still documented the pre-XDG paths (~/.utoprc), even though the config moved to $XDG_CONFIG_HOME/utop/utoprc in #484. I've updated utop(1) and utoprc(5) to document the current locations (noting the legacy fallbacks still work), added the previously undocumented history file to FILES, and pointed to the shipped utoprc-dark/utoprc-light configs.

Along the way I also fixed a few small errors: utop-full(1) claimed the binary is called utop, -safe-string no longer exists on OCaml >= 5.0, the Emacs section was missing reason-mode and utop-mode-compat-alist, plus a couple of typos.

The man pages predated the switch to XDG paths (ocaml-community#484) and had
accumulated some errors:

- utoprc lives in $XDG_CONFIG_HOME/utop/utoprc these days, with
  ~/.utoprc honored only as a legacy fallback
- document the history file and its location
- utop-full.1 claimed the binary is called "utop"
- mention reason-mode and utop-mode-compat-alist in the Emacs section
- note that -safe-string is gone with OCaml >= 5.0
- point to the shipped utoprc-dark/utoprc-light files and sync the
  example with utoprc-dark
- fix a couple of typos (top-kill, \fb)
@bbatsov
bbatsov requested a review from rgrinberg as a code owner July 12, 2026 09:26
@pmetzger

Copy link
Copy Markdown
Member

The changes look good to me, I don't understand why the CI failed...

@jg791

jg791 commented Jul 19, 2026

Copy link
Copy Markdown
Contributor

The changes look good to me, I don't understand why the CI failed...

It's doing the same to me on my PR here: #514

With no changes it went from succeeding to randomly failing on various builds. Sometimes if I re-run it it succeeds, other times not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants