Revert "programs.neovim: link packpath dir in XDG_DATA_HOME"#3817
Merged
Revert "programs.neovim: link packpath dir in XDG_DATA_HOME"#3817
Conversation
This reverts commit deb2f59.
7 tasks
Contributor
|
Is there a reason for the revert? |
Member
Author
|
See the main thread: many reports of broken configurations; this change was not ready. |
15cm
pushed a commit
to 15cm/home-manager
that referenced
this pull request
Apr 22, 2023
…unity#3717)" (nix-community#3817) This reverts commit deb2f59.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Sep 25, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
6 tasks
teto
added a commit
to teto/home-manager
that referenced
this pull request
Oct 16, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Oct 16, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Oct 21, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Oct 29, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Nov 15, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Nov 27, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Dec 6, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Dec 11, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Dec 30, 2024
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Jan 3, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Jan 10, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Jan 16, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Jan 24, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Feb 2, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Feb 5, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Feb 6, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Feb 6, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Feb 6, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Feb 6, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 8, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 8, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 11, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 11, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 13, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 13, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 21, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 21, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 23, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 23, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 24, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 24, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 24, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 24, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 25, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Mar 25, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Apr 11, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Apr 11, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Apr 22, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Apr 22, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Apr 24, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Apr 24, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
Apr 26, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
Apr 26, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
May 3, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
May 3, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
May 4, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
May 4, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
teto
added a commit
to teto/home-manager
that referenced
this pull request
May 7, 2025
…munity#3717)" (nix-community#3817) This reverts commit 0e065e1. adjustements post cherry-pick fixes revert the wrapping args as argument change postrebase neovim
teto
added a commit
to teto/home-manager
that referenced
this pull request
May 7, 2025
See previous attempt at nix-community#3717 and its revert at nix-community#3817 - link the packpath in expected folder so that even unwrapped neovim can pick home-manager's plugins. Right now the path to plugins (`:h rtp` / `:h packpath`) is set in the neovim wrapper. Not only is this unusual but if you want to run an unwrapped neovim (a neovim GUI or when you hack on neovim for instance), the app doesn't find plugins installed by home-manager. With this change, neovim can discover HM-installed plugins by itself and hopefully we can make neovim configuration less magical and surprising to newcomers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts #3717