doomemacs / doomemacs/core

The buffer is deleted after the frame is closed

Open
#6,969 0 comments 0 reactions 0 assignees View on GitHub
is:bug needs-triage
Dominant language
Emacs Lisp
Stars
22.7k
Forks
3.1k
Avg merge
10h 46m
Merged PRs (30d)
4

Description

### I confirm that...

- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.

- [X] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.

- [X] The issue can be reproduced on the **latest** available commit of Doom.

- [X] The issue can be reproduced on a stable release of Emacs, such as 27 or 28. *(Doom does not support development builds like 29+ or any version ending in .50 or .9x)*

### Expected behavior

When I close the frame, the buffer should continue to exist.

### Current behavior

[Windows OS]

The buffer is deleted after the frame is deleted

### Steps to reproduce

I am launching the Emacs server:

`runemacs.exe --daemon`

The process appears in the Task manager. There are no open windows (Frames).
Then I transfer the file to the server:

`emacsclientw.exe --no-wait --server-file "c:\Users\user\AppData\Roaming\.emacs.d\server\server" "d:\text.txt"`

A frame with the specified buffer opens.
Everything works normally, but as soon as I close the window (Frame), the buffer with the newly opened file ceases to exist
That is, if you open a new file or open the Emacs window and look at the list of buffers, then it will be empty.
If you run the server-edit (C-x #) command, the program responds:

`No server editing buffers exist`

### System Information

https://gist.github.com/slideray/e617dcc97931c161d3c1accf1b1e09db

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.