Skip to content

README: document using current window for dedicated chat buffer #998

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

README: document using current window for dedicated chat buffer #998

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
174e4fc
README: document using current window for dedicated chat buffer
jasalt Aug 5, 2025
9fc61df
Merge branch 'karthink:master' into patch-1
jasalt Sep 13, 2025
7c031aa
docs: New chat UI current window placement to FAQ section
jasalt Sep 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions README.org
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1613,6 +1613,17 @@ Anywhere in Emacs: Use =gptel-pre-response-hook= and =gptel-post-response-functi

#+html: </details>
#+html: <details><summary>

**** How to open the chat buffer in current window?
#+html: </summary>
By default, gptel opens a new buffer for chat UI according to =display-buffer-alist= setting. This can be modified to use the current window with following:

#+begin_src emacs-lisp
(setopt gptel-display-buffer-action '(pop-to-buffer-same-window))
#+end_src
#+html: </details>
#+html: <details><summary>

**** How does gptel distinguish between user prompts and LLM responses?
#+html: </summary>

Expand Down