Gary,

Thank you for all you've said, including explaining.  Roger all that!
I fixed the 'set nocompatible' as you pointed out into my core .vimrc.

I echo'd  "*map! <f1> <nop*"  > f1test

Next I did:  "*/usr/bin/vim -N -u f1test --noplugin*"

<F1> in CommandMode brought up help.  Did ":q".
Did 'i' for insert mode and <F1>  and NADA!!!
Very helpful directive troubleshooting.

I then added "*map <f1> <nop*" into f1test; now it looks like:

*map <F1> <Nop>map! <F1> <Nop>*
Retried "*/usr/bin/vim -N -u f1test --noplugin*"--- and
CommandMode/InsertMode attempts to <F1> properly FAIL!
VOILA!!


*My fallacy was that I KNEW everything else in my .vimrc was good to
go---just needed one more little detail to 'work right'.*

Ok, I'm off to layer back in my .vimrc content to find the real source of
my problem.
I'll follow up with what I find.

Thank you, Gary (and everyone else who has helped)!!

R,
-Joe Wulf;
*RHCSA(RHEL7), FITSP-D, CISSP, VCP3, CPO(USN/RET)*Tony Robbins:  "
*Management* is focusing on getting someone to get a result. *Leadership*
is producing a standard in someone that when you’re gone, they will live by
to produce higher level results consistently".




On Fri, Jan 21, 2022 at 3:04 AM Gary Johnson <[email protected]> wrote:

> On 2022-01-21, Joseph Wulf wrote:
> > Gary,
> >
> > I moved .vimrc out of the way.
> > Executed "\vim"   to negate my bash alias which does:  "alias
> vim='/usr/bin/vim
> > -u ~/.vimrc'"
> >
> > I first did '<F1>' and got the help, and quit out of it ":q"
> > I next did 'a' and then did '<F1>' and got the help, and quit out of it
> ":q"
> >
> > The results from ":verbose map! <F1>" was "No mapping
> found"---------same for "
> > :verbose map <F1>.
> >
> > Thank you... I appreciate the help.
> > I've spent a couple hours this evening browsing through the VIM
> ":help".... to
> > see what more I could learn.
>
> Joe,
>
> The point of the experiment was to try to discover what it is in
> your setup that causes the insert- and command-mode mapping of <f1>
> (i.e., "map! <f1> <nop>") to disappear or become ineffective.  If
> you move your ~/.vimrc out of the way, we don't learn anything.
>
> That said, it may not have been a very good experiment because the
> :verbose command would not have said where F1 became unmapped.
> (I'm experimenting with a very old 7.2.330 Vim on an even older
> Ubuntu 10.04 system.)
>
> One approach would be to create a file, say f1test, put in this one
> line:
>
>     map! <f1> <nop>
>
> and start vim like this:
>
>     /usr/bin/vim -N -u f1test
>
> Then see if typing the F1 while in insert mode still brings up help.
>
> If that works to stop F1 from bringing up help, then slowly add
> lines to f1test from your ~/.vimrc until it fails.
>
> If that doesn't work, then it may be a plugin.  You can start Vim as
>
>     /usr/bin/vim -N -u f1test --noplugin
>
> to see if that works.
>
> I did see something in your ~/.vimrc that you should change.
> I don't know whether or not it affects this problem, but it will
> likely cause other problems.  You have
>
>     set nocompatible
>
> in the middle of that file.  It should be at the very top, the first
> thing executed.  See
>
>     :help 'compatible'
>
> Regards,
> Gary
>
> --
> --
> You received this message from the "vim_use" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>
> ---
> You received this message because you are subscribed to the Google Groups
> "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vim_use/20220121080435.GC14109%40phoenix
> .
>

-- 
-- 
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vim_use/CAJ8cad-Y43XFgW%2BTfXSZVXT-wtJBxYQskVe_WziOULbNrQtcDA%40mail.gmail.com.

Reply via email to