Re: why vim give error on removing non existing mapping

2013-07-13 Fir de Conversatie Ingo Karkat
On 13-Jul-2013 19:00 +0200, Albert Netymk wrote: >> For a command called unmap this behavior is indeed intuitive: you >> asked to perform an action (*delete* mapping, *unmap*) and if action >> cannot be performed (no such mapping) reporting failure is expected. >> If it was mapclear and it accepte

Re: why vim give error on removing non existing mapping

2013-07-13 Fir de Conversatie Nikolay Pavlov
On Jul 13, 2013 8:59 PM, "Albert Netymk" wrote: > > > > For a command called unmap this behavior is indeed intuitive: you asked to perform an action (*delete* mapping, *unmap*) and if action cannot be performed (no such mapping) reporting failure is expected. If it was mapclear and it accepted arg

Re: why vim give error on removing non existing mapping

2013-07-13 Fir de Conversatie Albert Netymk
> For a command called unmap this behavior is indeed intuitive: you asked to > perform an action (*delete* mapping, *unmap*) and if action cannot be > performed (no such mapping) reporting failure is expected. If it was mapclear > and it accepted argument like unmap I would call *this* command's

Re: why vim give error on removing non existing mapping

2013-07-13 Fir de Conversatie Albert Netymk
> For a command called unmap this behavior is indeed intuitive: you asked to > perform an action (*delete* mapping, *unmap*) and if action cannot be > performed (no such mapping) reporting failure is expected. If it was mapclear > and it accepted argument like unmap I would call *this* command

Re: why vim give error on removing non existing mapping

2013-07-13 Fir de Conversatie ZyX
> Vim has nice batteries included, such as -V20/tmp/log to trace what's > going on. So its easy to find most issues you may hit. Using 'verbose' produces too much crap. Additionally it throws an error once it encounters recursive data structure returned (e.g. dictionary containing reference to i

Re: why vim give error on removing non existing mapping

2013-07-13 Fir de Conversatie Marc Weber
Excerpts from Nikolay Pavlov's message of Sat Jul 13 08:40:45 +0200 2013: > :silent! should be used only if you are absolutely sure you know all error > messages you are trying to suppress. I normally avoid it, explicitly > matching a set of exceptions I am suppressing. In the umap case the errors

Re: why vim give error on removing non existing mapping

2013-07-12 Fir de Conversatie Nikolay Pavlov
On Jul 13, 2013 1:30 AM, "Marc Weber" wrote: > > for completness: > > such errors should only change execution flow if fun .. abort is used or > such. Meaning that if there is possibility of such error you should change your code to transform it into exception always because it is possible for us

Re: why vim give error on removing non existing mapping

2013-07-12 Fir de Conversatie Marc Weber
for completness: such errors should only change execution flow if fun .. abort is used or such. silent[!] unmap doesnotexist is a shorter way than try .. except This reply is about "working around" about what you would have done differently. Marc Weber -- -- You received this message from

Re: why vim give error on removing non existing mapping

2013-07-12 Fir de Conversatie Nikolay Pavlov
On Jul 13, 2013 12:44 AM, "Albert Netymk" wrote: > > Background scenario: When I was debugging one VimScript, some code is not executed. The reason is that unmap raises one error and the VimScript exits on this error. Because one empty try-catch is place around the code, it's not very obvious what

why vim give error on removing non existing mapping

2013-07-12 Fir de Conversatie Albert Netymk
Background scenario: When I was debugging one VimScript, some code is not executed. The reason is that unmap raises one error and the VimScript exits on this error. Because one empty try-catch is place around the code, it's not very obvious what's the problem. After locating the problem finally,