doomemacs / doomemacs/core

Custom workspace names overridden

Open
#8,381 3 comments 1 reaction 0 assignees View on GitHub
:ui workspaces is:regression
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, 29, or 30. *(Unstable versions end in .50, .60, or .9x)*

### Expected behavior

When I specify a custom workspace name via `projectile-project-name-function`, I expect that name to be used for the new workspace. Note that this override occurs when the new custom project name is unique.

### Current behavior

My custom workspace name (`projectile-project-name-function`) is overridden and the final directory name in the path is used. For example:

- Workspace directory: /home/me/foo/bar
- Output of my custom `projectile-project-name-function`: `some-custom-name`
- New workspace name: `bar`

### Steps to reproduce

1. Customize `projectile-project-name-function`
2. Create a new workspace
3. Notice the name is not equal to your custom function's output

### System Information

https://pastebin.com/utTUqk9L

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.