Open alextes opened 1 month ago
just ran into this again for a tracked file! bit surprised, thought it was probably due to the fact the file was untracked but trying to unstage a line from a hunk that's been staged yields the same "patch does not apply error"
example screenshot:
thanks for a great plugin btw 🙏 some rough edges but smooth overall!
@alextes did you try bisecting?
you mean bisecting in neogit or bisecting the neogit source itself and running the plugin to identify the specific commit where this functionality stopped working (if it ever worked)? in case of the latter, no i haven't tried that.
I suspect this never worked, as its attempting to apply a patch to the index for a file that is not yet in the index. I'll need to do sone git research on how to do this
@CKolkey Makes sense, then it's not related but just similar to the one I reported (#1354)
Description
when staging a new file, i sometimes want to unstage part of that file. perhaps its not done, perhaps it belongs to a different feature / commit. highlighting the lines in the unstaged file and staging that way works fine. decent workaround, but you don't always notice ahead of time you've staged lines you don't want to commit (on a new file).
trying to unstage yields the following error
Here's a screenshot that makes the situation visual:![Screenshot 2024-06-06 at 14 02 42](https://github.com/NeogitOrg/neogit/assets/2011351/edf87afd-63b5-4c41-b54b-66ba33d93516)
unstaging the commented lines at the end of the file will yield the error above.
Neovim version
NVIM v0.10.0 Build type: Release LuaJIT 2.1.1713773202
Operating system and version
macOS 14.5
Steps to reproduce
- name: Setup simulation nodes
hosts: simulation-nodes
become: yes
vars:
ansible_python_interpreter: /usr/bin/python3
roles:
- simulation-node
Expected behavior
No response
Actual behavior
See description.
Minimal config