Nabble - VIM

Re: [ANN] pyclewn release 1.0

2009-12-20T07:36:35Z

The site tells that pyclewn runs on all unix platforms supported by
python and Windows!

I was thinking of porting clewn to Windows for years, now I don't have to :)

--
Sergey Khorev
http://sites.google.com/site/khorser
Can anybody think of a good tagline I can steal?

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: To print module's name

2009-12-20T07:10:58Z

Hi.

A simply code .

map <F8> <ESC>:echo getline(search('^\s*\<$entity\|module$\>\s*\w\+','bWn'))<CR>

ps: my outlook express can't post bottom.. - -!,,

While browsing in verilog or vhdl code, there is a need to get which "module" or "entity" (these are the required keywords) the line is.

My solution is maybe writing a function and map a key to call this function.

Any example code for the function would be very well...

Thanks,

Burak

PS:

The case is
--------------------------------------
module aaa
...
<the cursor here somewhere>
...
endmodule
--------------------------------------
Just press a key (or key combination) to get (or print) aaa

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: To print module's name

2009-12-20T07:04:52Z

The case is
--------------------------------------
module aaa
...
<the cursor here somewhere>
...
endmodule
--------------------------------------
Just press a key (or key combination) to get (or print) aaa

adf

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: vimrc ignores formatoptions

2009-12-20T06:35:55Z

> yet when I edit a file with vim and type:
> :set fo
> I see formatoptions=croql
>
> which vi produces:
> vi /usr/bin/vim
>
> When I change ts=8 and re-run vi, it changes, so it appears
> its reading my file but ignoring 'fo'. Can someone tell me how
> to fix this or why its happening? Maybe its a bug?

you can set like this :
au filetype yourfiletype set fo-=r

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

[ANN] pyclewn release 1.0

2009-12-20T05:37:26Z

Pyclewn 1.0 has been released at http://pyclewn.sourceforge.net/
Pyclewn is a python program that allows the use of gvim as a front end
to a debugger.

Xavier

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: automatic lines setting?

2009-12-20T03:31:48Z

Earler, I said:
> If I do
>
> :set lines=500|echomsg &lines
>
> I get 500 in the message history, but with
>
> :set lines=500|redraw|echomsg &lines
>
> I get 87.

I just tried that on windows (earlier was vim-gtk) and set lines=500|
echomsg &lines gives 76, but adding your lines code to _gvimrc doesn't
work, with or without a redraw.

:help gui suggests using the GUIEnter event. I tried:

func Autolines()
set lines=500 " over zealous numbers of lines
let &lines = ((float2nr(0.85*&lines)>52)?float2nr(0.85*&lines):52)
endfunc
autocmd GUIEnter * call Autolines()

in my _gvimrc on windows and it seemed to work, lines was set to 64.
I'll try it tomorrow on my vim-gtk on Kubuntu.

Regards, John

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: backup filename including date+time (was: Setting up my vimrc)

2009-12-19T20:30:47Z

Oh hey I got it fixed. i added this to ~/.vim/plugin/backupsetting and
it works great!

yea when I posted that I hadn't really thought through the vimrc
commands at the bottom, i just thought it would make the directories
automatically.

if !has_key(s:, 'origbdir')
let s:origbdir = &bdir
endif

function! s:ChangeBackupSettings()
let dir = $HOME . "/Shortcuts/Backups/" . strftime("%y%m%d")

let &backupext ='.' . strftime("%H%M%S") . '.bak'

if ! filewritable(dir)
call mkdir(dir, "p")
if filewritable(dir)
let &bdir = dir . ',' . s:origbdir
else
echoerr "Failed to create backup directory, leaving unchanged!"
endif
endif
endfunction

augroup BackupSettings
au!
autocmd BufWritePre * call s:ChangeBackupSettings()
augroup END

On Dec 19, 10:07 pm, Sven Guckes <guc...@...> wrote:

> * kennethadammiller <kennethadammil...@...> [2009-12-20 04:54]:
>
>
>
> > I'm a beginner and newbie to vim.
> > I was just going to ask about how to set up my vimrc to
> > backup files to a directory that is depended on the date
> > with a file extension that is dependent on the time.
> > This is the current contents of my vimrc.
>
> > set nocompatible autoindent ruler incsearch history=300 so=4
> > syntax enable
> > filetype on
> > set patchmode=.orig
> > set backup
> > let &backupdir="/home/adam/Shortcuts/Backups/" . strftime("%y%m%d")
> > let &backupext=strftime("%H%M%S") . ".bak"
>
> > I was guided to use :let &back... by some
> > good folks on the IRC channel...
> > whenever I try to do it, though, I get
> > "E510: Can't make backup file (use ! to override)"
>
> so.. you are creating a name for a *directory* -
> but where is the command that *creates* it, too?
> vim does not creates directories for you - sorry!
>
> > how do i get it to do what I want?
>
> i suppose you need to run a command that
> creates the directory before you use it:
>
> :!mkdir &backupdir
>
> i think you should have added the year+month+day
> as part of the filename rather than the directory:
>
> let &backupdir="/home/adam/Shortcuts/Backups/"
> let &backupext=strftime("%y-%m-%d.%H%M%S.bak")
>
> mind you: untested. just some ideas.
>
> Sven

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

backup filename including date+time (was: Setting up my vimrc)

2009-12-19T20:07:36Z

* kennethadammiller <kennethadammiller@...> [2009-12-20 04:54]:

> I'm a beginner and newbie to vim.
> I was just going to ask about how to set up my vimrc to
> backup files to a directory that is depended on the date
> with a file extension that is dependent on the time.
> This is the current contents of my vimrc.
>
> set nocompatible autoindent ruler incsearch history=300 so=4
> syntax enable
> filetype on
> set patchmode=.orig
> set backup
> let &backupdir="/home/adam/Shortcuts/Backups/" . strftime("%y%m%d")
> let &backupext=strftime("%H%M%S") . ".bak"
>
> I was guided to use :let &back... by some
> good folks on the IRC channel...
> whenever I try to do it, though, I get
> "E510: Can't make backup file (use ! to override)"

so.. you are creating a name for a *directory* -
but where is the command that *creates* it, too?
vim does not creates directories for you - sorry!

> how do i get it to do what I want?

i suppose you need to run a command that
creates the directory before you use it:

:!mkdir &backupdir

i think you should have added the year+month+day
as part of the filename rather than the directory:

let &backupdir="/home/adam/Shortcuts/Backups/"
let &backupext=strftime("%y-%m-%d.%H%M%S.bak")

mind you: untested. just some ideas.

Sven

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: vimrc ignores formatoptions

2009-12-19T19:50:12Z

* Bob <jeep@...> [2009-12-19 15:41 -0800]:

> Hi-
>
> in my ~/.vimrc file I have:
>
> :set ts=4
> :set nobackup
> :set ai
> :set nocindent
> :set nosi
> :set fo-=r
> :set ruler
> :set tags=./tags
>
> yet when I edit a file with vim and type:
> :set fo
> I see formatoptions=croql
>
> which vi produces:
> vi /usr/bin/vim
>
> When I change ts=8 and re-run vi, it changes, so it appears
> its reading my file but ignoring 'fo'. Can someone tell me how
> to fix this or why its happening? Maybe its a bug?

Try ':verbose set fo' to see where formatoptions is being (re)set. It
may be an override from a filetype plugin or a local vimrc if you have
exrc set.

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: vimrc ignores formatoptions

2009-12-19T19:40:34Z

On Saturday 19 December 2009 05:41:10 pm Bob wrote:

> Hi-
>
> in my ~/.vimrc file I have:
> :set ts=4
> :set nobackup
> :set ai
> :set nocindent
> :set nosi
> :set fo-=r
> :set ruler
> :set tags=./tags
>
> yet when I edit a file with vim and type:
> :set fo
>
> I see formatoptions=croql
>
> which vi produces:
> vi /usr/bin/vim
>
> When I change ts=8 and re-run vi, it changes, so it appears
> its reading my file but ignoring 'fo'. Can someone tell me
> how to fix this or why its happening? Maybe its a bug?

many things can change your formatoption setting

one might be exposed by executing

:verbose set fo?

more clues might come from

:scriptnames

poke around

sc

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Setting up my vimrc

2009-12-19T19:09:49Z

I'm a beginner and newbie to vim.
I was just going to ask about how to set up my vimrc to backup files
to a directory that is depended on the date with a file extension that
is dependent on the time
This is the current contents of my vimrc.

:set nocompatible
:set autoindent
:set history=300
:set ruler
:set incsearch
:syntax enable
:filetype on
:set so=4
:set patchmode=.orig
:set backup
:let &backupdir="/home/adam/Shortcuts/Backups/" . strftime("%y%m%d")
:let &backupext=strftime("%H%M%S") . ".bak"

I was guided to use :let &back... by some good folks on the IRC
channel...
whenever I try to do it, though, I get "E510: Can't make backup file
(use ! to override)`
I'm sure you can understand from what I've got here what I want it to
do. Please help me.
how do i get it to do what I want?

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: automatic lines setting?

2009-12-19T18:37:18Z

John,

redraw works, but it leaves a lot of crap at the terminal (very long,
see pastebin link here:)
http://pastebin.com/m4cecfb20

here the output counts up to 100 because I used set lines=100 instead
of 500.

--
MZ

On Dec 19, 4:06 pm, John Little <john.b.lit...@...> wrote:

> On Dec 19, 2:14 pm, Mathieu <lingfe...@...> wrote:
>
>
>
> > $ head .gvimrc
> > set lines=500 " over zelous numbers of lines
> > let &lines = ((float2nr(0.85*&lines)>52)?float2nr(0.85*&lines):52)
> > ...If I issue the first two commands by hand after
> > gvim has open. It will do what I want it to do. Why don't it work as
> > part of .gvimrc?
>
> There is an implicit redraw between them when "issue" them by hand.
> If I do
>
> :set lines=500|echomsg &lines
>
> I get 500 in the message history, but with
>
> :set lines=500|redraw|echomsg &lines
>
> I get 87.
>
> You could try putting a redraw in your .gvimrc, after the set
> lines=500.
>
> Regards, John

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: automatic lines setting?

2009-12-19T17:37:10Z

Mathieu wrote:

> Here the first few lines of my .gvimrc:
>
> $ head .gvimrc
> set lines=500 " over zelous numbers of lines
> let &lines = ((float2nr(0.85*&lines)>52)?float2nr(0.85*&lines):52)
>
> set columns=85
> " double the size of window if running diff
> if &diff
> let &columns = ((&columns * 2 > 160)? 160: &columns*2)
> endif
>
> I wanted gvim to use 85% of the height of the screen or 52 lines,
> whichever is greater. If I issue the first two commands by hand after
> gvim has open. It will do what I want it to do. Why don't it work as
> part of .gvimrc?

From eval.txt line 665
You should always put a space before the ':', otherwise it can be
mistaken for use in a variable such as "a:1".

Does that help?
--
Bill
Santa Cruz, California

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: Weird behaviour with the manpage view plugin

2009-12-19T16:54:11Z

Unfortunately, after installing v23d, I'm still having the same
issue. Happening in both vim and gvim v7.2.245. ":Man <fn_name>"
continues to work.

Thanks,
Andrew

On Dec 18, 11:09 am, Charles Campbell <Charles.E.Campb...@...>
wrote:

> andrewashbacher wrote:
> > Dr Chip,
>
> > Thanks for a great plugin. I also am having this problem.
>
> > Here is how I replicate the issue (CLI or GUI):
>
> > 1. Open a php file.
> > 2. Type <?php ltrim('__abc', '_'); ?>
> > 3. Move cursor anywhere on top of 'ltrim'.
> > 4. Press K -- this should work bringing up the PHP manual entry for
> > ltrim in links.
> > 5. :q to close the manual
> > 6. Press K again -- this returns "E129: Function name required".
>
> > Note that :Man ltrim continues to work. Hope this helps.
>
> Please try manpageview v23d; I haven't finished working with it, but at
> least it works for your example.
> (http://mysite.verizon.net/astronaut/vim/index.html#MANPAGEVIEW)
>
> Regards,
> Chip Campbell

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: automatic lines setting?

2009-12-19T16:06:24Z

On Dec 19, 2:14 pm, Mathieu <lingfe...@...> wrote:
>
> $ head .gvimrc
> set lines=500 " over zelous numbers of lines
> let &lines = ((float2nr(0.85*&lines)>52)?float2nr(0.85*&lines):52)

> ...If I issue the first two commands by hand after
> gvim has open. It will do what I want it to do. Why don't it work as
> part of .gvimrc?

There is an implicit redraw between them when "issue" them by hand.
If I do

:set lines=500|echomsg &lines

I get 500 in the message history, but with

:set lines=500|redraw|echomsg &lines

I get 87.

You could try putting a redraw in your .gvimrc, after the set
lines=500.

Regards, John

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

vimrc ignores formatoptions

2009-12-19T15:41:10Z

Hi-

in my ~/.vimrc file I have:

:set ts=4
:set nobackup
:set ai
:set nocindent
:set nosi
:set fo-=r
:set ruler
:set tags=./tags

yet when I edit a file with vim and type:
:set fo
I see formatoptions=croql

which vi produces:
vi /usr/bin/vim

When I change ts=8 and re-run vi, it changes, so it appears
its reading my file but ignoring 'fo'. Can someone tell me how
to fix this or why its happening? Maybe its a bug?

Thanks

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: timed commands?

2009-12-19T09:45:36Z

On 24/11/09 17:39, Lev Lvovsky wrote:
>
> I'd like to run an ':mksession!' on a regular basis (automatically) -
> is there a generic timer function which I can wrap around that command
> (running it ever hour for example)?
>
> thanks,
> -lev

IIUC, you want to make sure that Vim will restart with "the same windows
as when it last closed", right? For that purpose I would recommend the
following:

a) to have Vim save the session at shutdown:

autocmd VimLeave *
\ if exists('v:dying') && v:dying < 2 | mksession! | endif

I _think_ this will even run at interruptible crashes (e.g., after an
illegal opcode or a memory protect violation, but not if the operator
forces an uninterruptible hard crash). It may or may not run at an AC
power failure, depending on whether your computer can run a few seconds
after the AC fails, and on how long the OS will leave Vim for its
"emergency closedown".

The test for v:dying < 2 is to avoid doing it again if you get a second
crash after intercepting a first one (however, IIUC on non-Unix-like
OSes this variable is always either 0 or undefined, I'm not sure which)
-- see ":help v:dying".

b) to make it easier on you to save your session while working:

nnoremap <F12> :mks!<CR>
xnoremap <F12> :<C-U>mks!<CR>
snoremap <F12> <C-O>:<C-U>mks!<CR>
inoremap <F12> <C-O>:mks!<CR>

c) Educate yourself to type :qa or :xa or some variation on them
_before_ you close the OS, so that a "normal" system shutdown won't
cause a "crash" of Vim.

Note that (b) above is not strictly necessary on Linux if running gvim
with GTK2/Gnome2 GUI under KDE (KDE3, at least), where it will save its
session transparently at X11 closedown; but, strangely enough, the same
doesn't apply in a Gnome2 winmanager -- or at least that's what I'm
experiencing at the moment.

Best regards,
Tony.
--
The more things change, the more they stay insane.

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: syntax highlight :g/pattern/p in separate buffer?

2009-12-19T07:43:55Z

On 19/12/2009 12:05, Reckoner wrote:
> I use :g/pattern/p frequently to see where functions are used in a
> very large program. It would be very helpful to be able to see the
> output of this in a separate buffer with corresponding syntax
> highlighting.
>
> Is this possible? Is there a plug-in for this?

You might want to give the Tag List plugin a try:

<http://vim-taglist.sourceforge.net/>

From its "Features" page:

> The taglist plugin provides the following features:
>
> * Displays the tags (functions, classes, structures, variables, etc.) defined in a file in a vertically or horizontally split Vim window.
> * In GUI Vim, optionally displays the tags in the Tags drop-down menu and in the popup menu.
> * Automatically updates the taglist window as you switch between files/buffers. As you open new files, the tags defined in the new files are added to the existing file list and the tags defined in all the files are displayed grouped by the filename.
> * When a tag name is selected from the taglist window, positions the cursor at the definition of the tag in the source file.
> * Automatically highlights the current tag name.
> * Groups the tags by their type and displays them in a foldable tree.
> * Can display the prototype and scope of a tag.
> * Can optionally display the tag prototype instead of the tag name in the taglist window.
> * The tag list can be sorted either by name or by chronological order.
> * Supports the following language files:
> o Assembly, ASP, Awk, Beta, C, C++, C#, Cobol, Eiffel, Erlang, Fortran, HTML, Java, Javascript, Lisp, Lua, Make, Pascal, Perl, PHP, Python, Rexx, Ruby, Scheme, Shell, Slang, SML, Sql, TCL, Verilog, Vim and Yacc.
> * Can be easily extended to support new languages. Support for existing languages can be modified easily.
> * Provides functions to display the current tag name in the Vim status line or the window title bar.
> * The list of tags and files in the taglist can be saved and restored across Vim sessions.
> * Provides commands to get the name and prototype of the current tag.
> * Runs in both console/terminal and GUI versions of Vim.
> * Works with the winmanager plugin. Using the winmanager plugin, you can use Vim plugins like the file explorer, buffer explorer and the taglist plugin at the same time like an IDE.
> * Can be used in both Unix and MS-Windows systems.

You'll need to have ctags installed as well for Tag List to work, but
it's very much worth it, IMHO.

--
John O'Shea
Wordbank Limited
33 Charlotte Street, London W1T 1RR
Direct line: +44 (0) 20 7903 8829
Fax: +44 (0) 20 7903 8888
<http://www.wordbank.com/>

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: syntax highlight :g/pattern/p in separate buffer?

2009-12-19T05:22:36Z

Reckoner wrote:
> Hi,
>
> I use :g/pattern/p frequently to see where functions are used in a
> very large program. It would be very helpful to be able to see the
> output of this in a separate buffer with corresponding syntax
> highlighting.
>
> Is this possible? Is there a plug-in for this?

You could use Vim's builtin grep to perform the search and the quickfix
window to view the highlighted results...

:vim /pattern/ %
:copen

:help vimgrep
:help copen

Hope this helps...
Brett Stahlman

>
> Thanks in advance
>

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

syntax highlight :g/pattern/p in separate buffer?

2009-12-19T04:05:48Z

Hi,

I use :g/pattern/p frequently to see where functions are used in a
very large program. It would be very helpful to be able to see the
output of this in a separate buffer with corresponding syntax
highlighting.

Is this possible? Is there a plug-in for this?

Thanks in advance

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

automatic lines setting?

2009-12-18T17:14:37Z

Here the first few lines of my .gvimrc:

$ head .gvimrc
set lines=500 " over zelous numbers of lines
let &lines = ((float2nr(0.85*&lines)>52)?float2nr(0.85*&lines):52)

set columns=85
" double the size of window if running diff
if &diff
let &columns = ((&columns * 2 > 160)? 160: &columns*2)
endif

I wanted gvim to use 85% of the height of the screen or 52 lines,
whichever is greater. If I issue the first two commands by hand after
gvim has open. It will do what I want it to do. Why don't it work as
part of .gvimrc?

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: Weird behaviour with the manpage view plugin

2009-12-18T11:09:16Z

andrewashbacher wrote:

> Dr Chip,
>
> Thanks for a great plugin. I also am having this problem.
>
> Here is how I replicate the issue (CLI or GUI):
>
> 1. Open a php file.
> 2. Type <?php ltrim('__abc', '_'); ?>
> 3. Move cursor anywhere on top of 'ltrim'.
> 4. Press K -- this should work bringing up the PHP manual entry for
> ltrim in links.
> 5. :q to close the manual
> 6. Press K again -- this returns "E129: Function name required".
>
> Note that :Man ltrim continues to work. Hope this helps.
>

Please try manpageview v23d; I haven't finished working with it, but at
least it works for your example.
(http://mysite.verizon.net/astronaut/vim/index.html#MANPAGEVIEW)

Regards,
Chip Campbell

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: [patch] in virtual replace when line above is shorter

2009-12-18T10:38:18Z

Lech Lorens wrote:

> Vim erroneously re-indents the current line if in virtual replace mode
> <C-Y> or <C-E> is pressed while the line above or below respectively is
> not long enough.
>
> To reproduce the problem execute:
>
> $ vim -u NONE -U NONE -i NONE -c 'set nocp noet ts=8 inde=0 indk=<:>' \
> -c 'call feedkeys("2G$gR\<C-Y>\<C-Y>")' \
> file.txt
>
> where file.txt is:
> #v+
> abcdefghijklmnopqrstuvwxyz
> 1 2 3 4 5
> #v-
>
> The result should be:
> #v+
> abcdefghijklmnopqrstuvwxyz
> 1 2 3 4 z
> #v-
>
> but it is:
> #v+
> abcdefghijklmnopqrstuvwxyz
> 1 2 3 4 z 1 2 3 4 5
> #v-
>
>
> The problem is caused by 0 passed to in_cinkeys() as the typed key.
> Function in_cinkeys() is then unable to recognise the "not found" return
> value from get_special_key_code().
>
> The attached patch fixes the problem.

Thanks!

--
You have the right to remain silent. Anything you say will be
misquoted, then used against you.

/// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - Dev

Re: To print module's name

2009-12-18T07:18:28Z

Am 18.12.2009 15:51, schrieb Bu Rak:
> While browsing in verilog or vhdl code, there is a need to get which
> "module" or "entity" (these are the required keywords) the line is.
>
> My solution is maybe writing a function and map a key to call this function.
>
> Any example code for the function would be very well...

> The case is
> --------------------------------------
> module aaa
> ...
> <the cursor here somewhere>
> ...
> endmodule
> --------------------------------------
> Just press a key (or key combination) to get (or print) aaa

map command in vim to match module/instance names in verilog
(from Jan 2009)

http://groups.google.de/group/vim_use/browse_thread/thread/cb8428efdb5b550b/574000345d69f35?q=#0574000345d69f35

--
Andy

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: To print module's name

2009-12-18T06:58:14Z

2009/12/18 Bu Rak <lokumcu@...>:
> Hi,
>
> While browsing in verilog or vhdl code, there is a need to get which
> "module" or "entity" (these are the required keywords) the line is.
>
> My solution is maybe writing a function and map a key to call this function.
>
> Any example code for the function would be very well...

This isn't a direct answer to your question, but there's some code
below that handles this for C/C++ etc. It may even work for VHDL if
you indent in a similar way. If you change the line starting echo
getline(search... to have a slightly different regular expression in
the first set of double quotes, you should be able to make it do what
you want. At the moment it searches for a line that starts with at
least two non-(space/tab/#/slash) characters that doesn't end in a
colon (this works quite well for a lot of indented languages).

Al

" Show the name of the current function
nmap ,f :call ShowFuncName()<CR>

" Show the name of the current function (designed for C/C++, Perl, Java etc)
fun! ShowFuncName()
let lnum = line(".")
let col = col(".")
echohl ModeMsg
echo getline(search("^[^ \t#/]\\{2}.*[^:]\s*$", 'bW'))
echohl None
call search("\\%" . lnum . "l" . "\\%" . col . "c")
endfun

--
http://sites.google.com/site/abudden

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

To print module's name

2009-12-18T06:51:24Z

Hi,

While browsing in verilog or vhdl code, there is a need to get which "module" or "entity" (these are the required keywords) the line is.

My solution is maybe writing a function and map a key to call this function.

Any example code for the function would be very well...

Thanks,

Burak

PS:

The case is
--------------------------------------
module aaa
...
<the cursor here somewhere>
...
endmodule
--------------------------------------
Just press a key (or key combination) to get (or print) aaa

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: vim syntax file patch

2009-12-18T05:59:25Z

c9s wrote:

> any comment ?
>
> On Dec 15, 9:11 pm, Cornelius <cornelius.h...@...> wrote:
>
>> Hi folks,
>>
>> I found that VimL syntax doesnt fold for something like:
>>
>> fun! g:Test()
>>
>> endf
>>
>> it folds for :
>>
>> fun! g:Test.ok()
>>
>> endf
>>
>> so this is a patch of fixing the global function folding and my test code.
>>

Try using vim 7.2-95, available at my website since Nov 18 -- I didn't
see any problem with its folding with the example you gave above.

http://mysite.verizon.net/astronaut/vim/index.html#vimlinks_syntax

Regards,
Chip Campbell

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - Dev

Re: gvim start-up geometry

2009-12-18T05:05:16Z

On Dec 16, 11:54 pm, MK <halfcountp...@...> wrote:
> Fvwm will do that -- which is how I've had it for long time -- fullscreen terminal with no frame. But I've been feeling the need for mouse funtionality and tabs. Maybe I have to go back, because get this: it does the same thing when you open a new tab (resizes!).

I don't know whether this is relevant to your setup or the resizing
issue, but you can use non-graphical tabs within gvim. Just remove "e"
from :set guioptions. Then tabs will display as they do in plain vim.
(they're much nicer looking this way, imo) I'm not noticing the
resizing behavior with the graphical tabs on Windows though.

-BC

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: Vim client-server communication

2009-12-18T02:05:47Z

On Tue, Dec 15, 2009 at 08:59:45AM EST, MBro wrote:

[..]

> Not sure how relevant this is to your situation, but I use the client-
> server for a few things in my day-to-day
> work environment:

> 1. all MAN pages all show up under one gvim [I'm not an expert BASH
> writer]:
> function man() {
> gvim_server="MANPAGES1"
> title=+"set titlestring="Man_Page"
> silent="--remote-silent"
> oldIFS=$IFS
> IFS=
>
> # Keep track of previously run 'man pages'
> # this speeds up the process of looking at the same MAN pages over
> and over again...
> if [ ! -e /tmp/man.$* ]; then
> /bin/man $* | col -b cat >/tmp/man.$*
> fi
> gvim --servername $gvim_server -R $title $silent /tmp/man.$* >/dev/
> null &
> IFS=$oldIFS
> }

I like the idea..!

I often end up with a bunch of vim instances on various terminals one
for each of the man pages I looked at over the last 24 hours or so, and
that's clutter.

Hence, having them all in one dedicated vim instance, sounds like a
great idea.

I'm thinking that the best way to speed this up would possibly be to
have a directory such as ~/manvim with formatted vim pages from previous
runs and check it for the existence of a given man page, and if it
exists, skip the /usr/bin/man | col -b > /wherever sequence.

Since I use terminal vim in GNU/screen, I added a 'screen -X select 16'
which takes me automatically to screen window #16.. looks like this
setup will suit me better than the :Man plugin, or the vman bash
function that I already have.

I have to play with it a couple of days before I can make an informed
decision.

> 2. In a perl script I open a desired file in a remote gvim and goto
> the specified line number:
> # This is a stripped-down version of my code
> my $file = "path/to/file-name.ext";
> my $viewer = "/bin/gvim";
> my $editor_options = '--servername PDU_VIM -R --remote-silent +
> \"set filetype=MIB|LINE_NUM\"';
> $editor_options =~ s/LINE_NUM/$requested_line_number/;
> system "$viewer $editor_options $file";
>
> It appears to work reasonable for my needs :-)

I'll take a closer look at this one tomorrow.

But how come your executables are in /bin/ rather /usr/bin/..?

Is this personal customization, or the distro you are running?

Thanks much for your comments.

CJ

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: Vim script support of socket access or IPC (inter-process communication) ?

2009-12-17T20:31:30Z

Sergey Khorev 写道:
> Vim is single-threaded application. If you want to implement proper
> IPC, for instance, Vim waiting on some event, you will need to rewrite
> much of its core I'm afraid.

What if I can expect my communication to respond immediately?

Anyway, we can define a timeout, for single-direction or non-blocking IPC .

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: vim syntax file patch

2009-12-17T19:13:01Z

any comment ?

On Dec 15, 9:11 pm, Cornelius <cornelius.h...@...> wrote:

> Hi folks,
>
> I found that VimL syntax doesnt fold for something like:
>
> fun! g:Test()
>
> endf
>
> it folds for :
>
> fun! g:Test.ok()
>
> endf
>
> so this is a patch of fixing the global function folding and my test code.
>
> --
> Best Regards.
>
> Cornelius ( Yo-An Lin )
> E-mail: cornelius.h...@...://c9s.blogspot.com/
>
> vim-syntax.patch
> 1KViewDownload
>
> test.vim
> < 1KViewDownload

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - Dev

Vim k&r fold

2009-12-17T19:08:51Z

Hello all:
When i use syntax fold in C file with K&R style.
if () {
}else{
}
the if else fold in one block. how can i break it?

I want to use matchit.vim to match if else.
I don't know how to set the b:match_word.

Thanks.

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

Re: mvim and 'wait'

2009-12-17T18:48:55Z

Yes indeed - now all is good again in my world.

Thanks for the help Björn.

--
Richard

--
You received this message from the "vim_mac" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - Mac

Re: Vim client-server communication

2009-12-17T16:48:07Z

On Thu, Dec 17, 2009 at 03:18:33PM EST, Sven Brueggemann wrote:
> Hello Chris,

> > That's what I meant by 'amazing your friends' since though it has
> > its merits, I don't see this particular example as being very
> > useful, probably not enough to justify the overhead and added
> > complexity.

> i didn't follow the thread closely. You might like to watch this video
> http://www.derekwyatt.org/vim/vim-tutorial-videos/vim-intermediate-tutorial-videos/#onevim
> (about 4:30 min).

Thanks, I have something else streaming right now but I will watch it
asap.

> > I want to better understand the feature and find out if it might
> > provide useful editing strategies

> The strategy or paradigm or whatever is to use just one instance of
> vim. If you end your work day with closing lots of vim instances like
> I once did, it's worth a try...

I tend to do everything in one permanent Vim instance that initializes
when I bring up my desktop.. and have it remember what I was doing via
:mksession.

But since I do this to avoid the clutter of spawning instances all over
the place, I may yet switch to the client-server paradigm in order to
give my working model a bit more flexibility.

Since I run pretty much everything I need in one instance of GNU/screen
over xterm, it would be nice if I could also have screen switch focus to
the particular region where the server vim instance currently lives -
would make things more convenient/transparent.

Another possible use is that you might use several server instances to
address different needs, such as featuring a more capable font when
I occasion have to deal with exotic scripts, maths symbols, etc.

This is especially true, when other layers are involved, such as a
mailer for instance, since this approach might turn out to be more
effective than using the xterm mechanism to switch to a different font,
resizing the terminal, switching back to the default font, resizing the
terminal.. etc.

Certainly worth a try as you indicated.

Thanks,

CJ

--
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php

From forum: Vim - General

[patch] in virtual replace when line above is shorter

2009-12-17T15:24:46Z

Vim erroneously re-indents the current line if in virtual replace mode
<C-Y> or <C-E> is pressed while the line above or below respectively is
not long enough.

To reproduce the problem execute:

$ vim -u NONE -U NONE -i NONE -c 'set nocp noet ts=8 inde=0 indk=<:>' \
-c 'call feedkeys("2G$gR\<C-Y>\<C-Y>")' \
file.txt

where file.txt is:
#v+
abcdefghijklmnopqrstuvwxyz
1 2 3 4 5
#v-

The result should be:
#v+
abcdefghijklmnopqrstuvwxyz
1 2 3 4 z
#v-

but it is:
#v+
abcdefghijklmnopqrstuvwxyz
1 2 3 4 z 1 2 3 4 5
#v-

The problem is caused by 0 passed to in_cinkeys() as the typed key.
Function in_cinkeys() is then unable to recognise the "not found" return
value from get_special_key_code().

The attached patch fixes the problem.

--
Cheers,
Lech

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

diff --git a/src/edit.c b/src/edit.c index 19e5b8d..2c5cc48 100644 --- a/src/edit.c +++ b/src/edit.c @@ -1419,7 +1419,7 @@ normalchar: inserted_space = FALSE; #ifdef FEAT_CINDENT - if (can_cindent && cindent_on() + if (c != NUL && can_cindent && cindent_on() # ifdef FEAT_INS_EXPAND && ctrl_x_mode == 0 # endif @@ -7397,6 +7397,11 @@ in_cinkeys(keytyped, when, line_is_empty) int icase; int i; + if (NUL == keytyped) + { + EMSG2(_(e_intern2), "in_cinkeys()"); + return FALSE; + } #ifdef FEAT_EVAL if (*curbuf->b_p_inde != NUL) look = curbuf->b_p_indk; /* 'indentexpr' set: use 'indentkeys' */

From forum: Vim - Dev