-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Neovim) Using hindent to save haskell files puts cursor to top of file #11
Comments
Thanks for reporting it! The exact same issue was solve recently in #9 , maybe you're using a previous version before that fix (?) please try removing the plugin (followed by If that doesn't help, please let me know the output of |
Hey there, unfortunately I did not get the same results as the issue you mentioned. I also apologise for taking so long to get back to you. Here is the output of Thanks for reading!
|
I'm having trouble to reproduce this, didn't manage to get There are quite a few variables in play here, so can't really tell if it's the Neovim version, you think you could try and update your neovim to see if that helps? Alternatively, temporarily cleaning |
Thank you for prompting me to update I have commented out and uninstall every other plugin and I am still experiencing this issue (I " Start loading plugins
call plug#begin('~/.config/nvim/plugged')
Plug 'alx741/vim-hindent'
call plug#end() To make sure we're on the same page (and to fix the issue if it indeed is an issue), here's a link to my You manually copied the file but you did not use Plug, is there something different involved with this process even though it uses your git repo? I don't understand and I'm not good enough at all this :( |
I have this issue also. Can I somehow help with debugging this? |
@Janiczek I unfortunately stopped using this plugin as it was an unbearable issue and I just couldn't fathom what was going on. It clearly isn't a conflict with other plugins as I didn't use any others when I tested previously. |
That would be great actually! I failed at reproducing this issue, and thus couldn't fix it :/ |
I also have this issue. I'm also having the issue where either |
I'm having the same issue, with |
Right now I can't even get hindent on my system. Archlinux's hindent package was removed, the latest version (5.3.1) only compiles with ghc 7.6.3 (https://matrix.hackage.haskell.org/#/package/hindent) ghcup currently supports down to ghc 7.10.3. It's all a big mess. I haven't given up on this completely though, the issue should in theory also occur for |
@alx741 Don't use the arch packages for haskell on arch. Just use stack in a given project directory. |
Hi, I know this is quite an old issue by now, but I had this issue as well and found some things while fixing it. It appears that this problem has something to do with For those who can't install hindent, this issue states that you should run
to install it for now. For me, this installed to Bear in mind that hindent is currently looking for a maintainter, and has been since November, so it likely won't compile under latest versions for a while... Hopefully this helps. I'm gonna take a look at the code and see if I can resolve this in the meantime. |
@thytom thanks for having a look at it! |
Okay, after a bit of digging, I can't actually reproduce the error anymore... I think this is to do with hindent's current compilation issues, however, and not a bug in this plugin, as I vaguely remember manually removing Seems like the solution is to just re-install hindent through stack like I explained, this doesn't look like an issue with the plugin. |
After disabling this plugin, this behaviour is no longer experienced so it's something to do with vim-hindent. This happens with the simple
:w
as well as any additional bindings.If you need more info, just ask, but I'm only using this,
haskell-vim
andintero
for haskell development. I useALE
andDeoplete
for all languages. As stated though, the problem disappears when I disable this plugin. I'm using Plug, if that matters.Thanks for reading!
The text was updated successfully, but these errors were encountered: