---

6 Visiting Topics ¶

The commands, accessible from forge-topic-menu (on C-return), act on the topic at point; so this menu is useful in buffers dedicated to listing topics and notifications (which correspond to topics), but also in the status buffer (which also lists topics). In buffers dedicated to showing details about a single topic, these commands act on that topic; so this menu can be used there too.

To switch to this menu from another menu use m s. If the cursor is on a topic or the current buffer visits a topic.

To display details about a topic in a separate buffer and at the same time display the topic menu, invoke forge-topic-menu with a prefix argument, i.e., C-u RET.

RET [on topic] (forge-visit-this-topic) ¶

This commands visits the topic at point in a separate buffer. When invoked with a prefix argument then it not only visits the topic in a separate buffer, it at the same time displays

N v t (forge-visit-topic) ¶

N v i (forge-visit-issue)

N v p (forge-visit-pullreq)

These commands read a topic, issue or pull-request and visit it in a separate buffer.

C-c C-o (forge-browse) ¶

o [on topic in topic list] (forge-browse-this-topic)

o [on repository in repository list] (forge-browse-this-repository)

These commands visit the topic, issue(s), pull-request(s), post, branch, commit, remote, repository or blob at point in a browser.

Command: forge-browse-commit ¶

Command: forge-browse-branch ¶

Command: forge-browse-repository ¶

N b t (forge-browse-topic) ¶

N b i (forge-browse-issue)

N b p (forge-browse-pullreq)

N b r (forge-browse-remote)

N b I (forge-browse-issues)

N b P (forge-browse-pullreqs)

These commands read a topic, issue(s), pull-request(s), branch, commit, remote or repository, and open it in a browser.

Command: forge-browse-commit ¶

This command visit a blob in a browser.

When invoked from a blob- or file-visiting buffer, visit that blob without prompting. If the region is active, try to jump to the marked line or lines, and highlight them in the browser. To what extend that is possible depends on the forge. When the region is not active just visit the blob, without trying to jump to the current line. When jumping to a line, always use a commit hash as part of the URL. From a file in the worktree with no active region, instead use the branch name as part of the URL, unless a prefix argument is used.

When invoked from any other buffer, prompt the user for a branch or commit, and for a file.