Prev: gcc: no usable dependency style found ??
Next: Broadcast Reception
From: Jim Beard on 8 Aug 2007 21:56
This exchange piqued my curiousity, so I looked around
a bit. I shall ramble across findings to this point,
and then leave it for Blinky to follow up on.

1. Here may be a file .vimrc or .gvimrc in the home
directory, for personal touches. There may also be
a directory .vim or .gvim possibly containing a
directory plugin.

2. There may be files gvimrc and vimrc in /etc/vim.
These should contain configuration settings that are
intended to be system-wide. They also will contain
a line such as
source /usr/source/vim/gvimrc
source /usr/source/vim/vimrc
that will invoke configuration settings system-wide,
that will be overwritten the next time you update to
a new version of vim.

$HOME/.[g]vimrc for personal stuff
/etc/vim/[g]vimrc for permananent system stuff
/usr/share/vim/[g]vimrc for system stuff that
will change with every new version of vim.

3. Files /usr/share/vim/*menu.vim are the menu
files. Copies of these may exist elsewhere. The
problem is, how to get them picked up by vim?

In a *vimrc file, you can put a line such as
source /usr/source/vim/menu.vim
and I think that will pick up the menus in that
file.

Somewhere I ran across the notion that any file
ending in .vim is a vim script that can be placed
in a plugin directory. What are plugin directgories?
I think they may be things like $HOME/.[g]vimrc/plugin
/usr/share/vim/plugin and maybe some other places.
One might be able to put the *menu.vim files in
a plugin directory, and get them loaded that way.
NOT tested.

4. The gui/menus option have to be compiled into
the version of vim running for menus to work. My
version of vim does not have this stuff compiled in,
so I have not tested anything.

5. Blinky,
In vim, enter :help or hit F1 or maybe invoke :tutor
or start off with vimtutor at the command line, learn
to navigate around in the user manual [hjkl keys,
<Cntl>-] when the curson is beween |.....| bars, find
the user guide and reference manual (they were
somewhere in there), and read up on menus.

Tuning Vim
|usr_40.txt| Make new commands
|usr_41.txt| Write a Vim script
|usr_42.txt| Add new menus
|usr_43.txt| Using filetypes

cd to /usr/share/vim and /usr/share/vim/tutor and
nose around a bit in that area when you have time.
Interesting stuff.

Cheers!

jim b.


--
UNIX is not user-unfriendly; it merely
expects users to be computer-friendly.
From: Blinky the Shark on 8 Aug 2007 23:50
Jim Beard wrote:
> This exchange piqued my curiousity, so I looked around
> a bit. I shall ramble across findings to this point,
> and then leave it for Blinky to follow up on.
>
> 1. Here may be a file .vimrc or .gvimrc in the home
> directory, for personal touches. There may also be
> a directory .vim or .gvim possibly containing a
> directory plugin.
>
> 2. There may be files gvimrc and vimrc in /etc/vim.
> These should contain configuration settings that are
> intended to be system-wide. They also will contain
> a line such as
> source /usr/source/vim/gvimrc
> source /usr/source/vim/vimrc
> that will invoke configuration settings system-wide,
> that will be overwritten the next time you update to
> a new version of vim.
>
> $HOME/.[g]vimrc for personal stuff
> /etc/vim/[g]vimrc for permananent system stuff
> /usr/share/vim/[g]vimrc for system stuff that
> will change with every new version of vim.
>
> 3. Files /usr/share/vim/*menu.vim are the menu
> files. Copies of these may exist elsewhere. The
> problem is, how to get them picked up by vim?
>
> In a *vimrc file, you can put a line such as
> source /usr/source/vim/menu.vim
> and I think that will pick up the menus in that
> file.
>
> Somewhere I ran across the notion that any file
> ending in .vim is a vim script that can be placed
> in a plugin directory. What are plugin directgories?
> I think they may be things like $HOME/.[g]vimrc/plugin
> /usr/share/vim/plugin and maybe some other places.
> One might be able to put the *menu.vim files in
> a plugin directory, and get them loaded that way.
> NOT tested.
>
> 4. The gui/menus option have to be compiled into
> the version of vim running for menus to work. My
> version of vim does not have this stuff compiled in,
> so I have not tested anything.
>
> 5. Blinky,
> In vim, enter :help or hit F1 or maybe invoke :tutor
> or start off with vimtutor at the command line, learn
> to navigate around in the user manual [hjkl keys,
><Cntl>-] when the curson is beween |.....| bars, find
> the user guide and reference manual (they were
> somewhere in there), and read up on menus.

Been there, done that, complied.

I'll take this opportunity to thank you for the leg work and ideas, and
will revisit the rc files and will look for *menu files.

> Tuning Vim
>|usr_40.txt| Make new commands
>|usr_41.txt| Write a Vim script
>|usr_42.txt| Add new menus
>|usr_43.txt| Using filetypes
>
> cd to /usr/share/vim and /usr/share/vim/tutor and
> nose around a bit in that area when you have time.
> Interesting stuff.

Thanks again.


--
Blinky RLU 297263
Killing all posts from Google Groups.
Except in Thunderbird, which can't filter that well.
The Usenet Improvement Project: http://blinkynet.net/comp/uip5.html
From: Moe Trin on 9 Aug 2007 16:02
On Thu, 09 Aug 2007, in the Usenet newsgroup alt.os.linux.mandrake, in article
<pvuui.6703$I64.6460(a)trndny08>, Jim Beard wrote:

>This exchange piqued my curiousity, so I looked around
>a bit. I shall ramble across findings to this point,
>and then leave it for Blinky to follow up on.

Appreciate it - I don't use gvim, and am running out of ideas.

>1. Here may be a file .vimrc or .gvimrc in the home
>directory, for personal touches. There may also be
>a directory .vim or .gvim possibly containing a
>directory plugin.

Given that Blinky has reinstalled the main packages, I've a gut feeling
you're onto it here.

>2. There may be files gvimrc and vimrc in /etc/vim.
>These should contain configuration settings that are
>intended to be system-wide.

In theory, these should be back to "stock" as he removed/installed the
packages.

>3. Files /usr/share/vim/*menu.vim are the menu
>files. Copies of these may exist elsewhere. The
>problem is, how to get them picked up by vim?

I suspect they're hard coded in the binary. I noted

[ruble /]$ strings /usr/X11R6/bin/gvim | grep menu.vim
/usr/share/vim/vim57/menu.vim
/usr/share/vim/vim57/menu.vim
[ruble /]$

but that is an ancient version from 1999. Blinky seems to have found
a reference to "$VIMRUNTIME/menu.vim" which may point to them.

Old guy
 | 
Pages: 1
Prev: gcc: no usable dependency style found ??
Next: Broadcast Reception