doomemacs / doomemacs/core

Loading saved workspace does not open sudo'd buffers

Open
#8,254 2 comments 0 reactions 0 assignees View on GitHub
:ui workspaces is:bug re:remote
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, 28, or 29. *(Unstable versions end in .50, .60, or .9x)*

### Expected behavior

Loading a saved workspace should open or attempt to open tramp/sudo buffers.

### Current behavior

Currently, only buffers in the workspace which were not opened with sudo are restored, or sometimes none at all.

### Steps to reproduce

- create new named workspace
- create/open a file as normal user
- create/open another with sudo
- save workspace
- quit emacs then open emacs
- load the workspace you just saved
- notice that you are missing either the sudo buffer or both buffers
- weep gently

### System Information

https://gist.github.com/cccslater/e84753eea45ae84d303097a58f9221e0
I'm using emacs 30 day-to-day, this is the result of running 29 in a nix shell, hence there may be a slight config mismatch.

Contributor guide

Open the contributing guide

Research direction

No source file, test, or entry point is identified. First reproduce the issue by saving and reloading a named workspace containing both a normal buffer and a TRAMP/sudo buffer, then trace the workspace restore path. Done means loading the workspace restores or attempts to restore the sudo buffer without regressing normal buffers.

Written by the indexing model from the issue text.

Assessment

Tech stack
emacs-lisp
Domain
desktop-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.