Nothing beign echo'ed when over error

[dense-analysis]

Nothing beign echo'ed when over error

[FredrikAugust]

BTW my terminal is still receiving a bell signal every time I unfocus it and it's on a line
where there is an error.

On Sun, Oct 16, 2016, 12:44 Łukasz Jan Niemier [email protected]
wrote:

I also have no errors even despite that I am not using YCM.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#109 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHVdG30q-JqbrvRo1UOliKLpKvnNQK8Hks5q0f_2gaJpZM4KXS1n
.

[hauleth]

The same for me:

Setup:

• iTerm2
• NeoVim

The problem existed even when all plugins were disabled. So I believe that there is issue when using Ale with NeoVim.

[hauleth]

Setting set belloff=all resolves problem with bell, but still no error info.

Łukasz Niemier
[email protected]

Wiadomość napisana przez w0rp [email protected] w dniu 16.10.2016, o godz. 16:46:

I'm not sure what the issue is. If you could produce some kind of recording or some error output, that may help. The errors are just displayed with echomsg.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub #109 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AARzN7qFQ-FNNKwc2BNQpqTGdQE0AUPXks5q0jivgaJpZM4KXS1n.

[w0rp]

That makes sense. I'll change that.

[w0rp]

Right, give that a go.

[hauleth]

Works. But I have local copy of the Ale because I have added extra linters that I use in my work #113 so it need to wait a little :P

[w0rp]

Thanks for the info! You get weird errors on different setups for different people in Vim, and can be hard to figure out why something works for 80% of people, but not the other 20%.

[FredrikAugust]

It appears that it is also spamming "No matching autocommands" now.. Strange

[w0rp]

YouCompleteMe will likely conflict with this plugin.

I know about that other bug. I'll fix that right now.

[w0rp]

If you pull again, that autocmd problem will be gone.

[FredrikAugust]

Awesome! Do you know any workaround for the YCM thing?

[FredrikAugust]

[2016-10-14 20:19:16] > Error running :helptags /home/fredrik/.vim/bundle/ale/doc

This might also be of interest to you; pops up every time I update.

[w0rp]

https://github.com/Valloric/YouCompleteMe#the-gycm_echo_current_diagnostic-option

You might have to turn the similar option off in YCM.

[FredrikAugust]

For some reason it still seems to spam bell sessions for me though. Weird 😥

[w0rp]

Someone might have to open a pull request for YouCompleteMe to add support for this plugin.

[hauleth]

I also have no errors even despite that I am not using YCM.

[FredrikAugust]

I'm using standard vim

On Sun, Oct 16, 2016, 13:28 Łukasz Jan Niemier [email protected]
wrote:

The same for me:

Setup:

• iTerm2
• NeoVim

The problem existed even when all plugins were disabled. So I believe that
there is issue when using Ale with NeoVim.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#109 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AHVdG72r0xi8hXm04lQQVV9efra0UVdkks5q0gpSgaJpZM4KXS1n
.

[w0rp]

I fixed the documentation issue.

What do you mean by "spamming bell sessions" and "pinging?" Could you paste some output?

[FredrikAugust]

Hey, kind of busy right now, but I can do it later tonight. Basically; Konsole (KDE konsole) shows a little notification every time a bell signal is sent to the terminal and the terminal is not the focused window, and when I have my cursor over a line with an error it keeps on creating a new notification every appx. 1s

[w0rp]

Maybe you need :set noerrorbells or :set novisualbell.

[FredrikAugust]

I have :set noerrorbells in my vimrc

[FredrikAugust]

I can try adding novisualbell now

[FredrikAugust]

Nope, still receiving the error bell 😕

[w0rp]

I'm not sure what the issue is. If you could produce some kind of recording or some error output, that may help. The errors are just displayed with echomsg.

[FredrikAugust]

Thanks a lot @hauleth, that did indeed fix it.

[FredrikAugust]

@w0rp How should I get the error output when the problem is the lack of output? Is there any log I can look in or such?

[w0rp]

Do you see any signs in the sign column? Is the loclist being populated? Could you share your vimrc and version of Vim? Any information might help.

[hauleth]

You can use :lwindow or :lopen to show location list. But problem still exist as I would rather see it inline.

Łukasz Niemier
[email protected]

Wiadomość napisana przez Fredrik A. Madsen-Malmo [email protected] w dniu 16.10.2016, o godz. 16:50:

@w0rp https://github.com/w0rp How should I get the error output when the problem is the lack of output? Is there any log I can look in or such?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #109 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AARzN8KAr9XAxNGlkOMsQX1ciKLFYMw2ks5q0jnJgaJpZM4KXS1n.

[FredrikAugust]

I'm using a plugin to show the loclist, and I can confirm that it's being populated. I also get signs in the column.

http://i.imgur.com/xGBNRll.png

[FredrikAugust]

!! is error, while -- is warning.

[hauleth]

You can see issue there: https://asciinema.org/a/668m24qyvev4aieq04aa1u5dl

My NeoVim version:

NVIM 0.1.5
Build type: RelWithDebInfo
Compilation: /usr/local/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/build/config -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/src -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/deps-build/usr/include -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/build/src/nvim/auto -I/tmp/neovim-20160822-30240-1vpbim8/neovim-0.1.5/build/include
Skompilowany przez hauleth@niuniobook

Optional features included (+) or not (-): +acl   +iconv    +jemalloc +tui      
For differences from Vim, see :help vim-differences

       vimrc systemu: "$VIM/sysinit.vim"
   odwet dla $VIM-a: "/usr/local/Cellar/neovim/0.1.5/share/nvim"

[FredrikAugust]

I'm having the exact same issue as @hauleth showed here. Everything is working except for the echo part.

[w0rp]

What do you see if you try this?

setlocal shortmess+=T
let x = 'hello' 
exec "norm :echomsg x\n" 

Does it print "hello"?

[hauleth]

@w0rp no. But when I execute simply echomsg z then everything works. I do not know why have that additional level of indirection.

[FredrikAugust]

The example worked for me, though I had to change : to ; as I have remapped those in my config.

[w0rp]

norm is used because it's required for truncating messages. See here. http://vim.wikia.com/wiki/Get_shortened_messages_from_using_echomsg

[FredrikAugust]

Aaah, can you add an option so I can change it from using : to using ;?

[hauleth]

@FredrikAugust that could be issue, there should be call to norm! instead of norm as the following would use mappings, and first one forces to use default Vim.

[FredrikAugust]

Great!

[FredrikAugust]

Alright, one moment please.

[FredrikAugust]

Great, it works perfectly now! :)

[w0rp]

Nice. Does it work fro you, @hauleth?

[w0rp]

I'll have a look at that pull request, and we can get that merged soon enough.

[hauleth]

@w0rp and this is only first day of using Ale :D

[FredrikAugust]

Only used it for a couple of days myself, seems great so far :)