Skip to content

Fix tide-rename-file bug on new buffer name;#409

Merged
ananthakumaran merged 1 commit intoananthakumaran:masterfrom
Sleepful:master
Dec 23, 2020
Merged

Fix tide-rename-file bug on new buffer name;#409
ananthakumaran merged 1 commit intoananthakumaran:masterfrom
Sleepful:master

Conversation

@Sleepful
Copy link
Contributor

fixes #408:
If the new name of a buffer clashes with an opened buffer then
tide-rename-file stops and doesn't apply after-rename-edits.
Especially problematic because tide leaves buffers open as it applies
code edits.

fixes ananthakumaran#408:
If the new name of a buffer clashes with an opened buffer then
tide-rename-file stops and doesn't apply after-rename-edits.
Especially problematic because tide leaves buffers open as it applies
code edits.
@ananthakumaran
Copy link
Owner

Thanks for debugging the issue. I have uniquify buffer enabled, which seem to do this automatically, because I never ran into the problem while testing.

(require 'uniquify)
(setq uniquify-buffer-name-style 'forward)

@ananthakumaran ananthakumaran merged commit ba09882 into ananthakumaran:master Dec 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Tide chokes when an open buffer shares the name of a renamed buffer

2 participants