The pushbuffer, popbuffer APIs are intended to capture internal output.
They will prevent ui.write from writing to the actual ui.fout. So a
pager won't receive the output and do the right thing. In general, it does
not make sense to start a pager if ui is in the "pushbuffer" mode.
Details
Details
- Reviewers
- None
- Group Reviewers
hg-reviewers - Commits
- rHG31a2eb0f74e5: pager: do not start pager if `ui` has been `pushbuffer`-ed
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
Comment Actions
Makes sense, but how did you even notice this? I would have thought that we start the pager at a pretty high level, before pushbuffer would normally be called.