RE: new text object feature request
Hi Peter,
It can (see below), but then again, the other text objects could be
implemented as vimscript as well. Extending the existing text objects to
include parameters seems like a natural fit.
David
nmap cim :call ChangeInnerParam()
function ChangeInnerParam()
call s:selectInnerParam()
normal x
startinsert
endfunction
function s:selectInnerParam()
call search('[(,]', "bW")
normal lv
call search('[(,)]', "W")
let c = getline(".")[col(".")-1]
if (c == '(')
" skip over a nested param list
normal %
call search('[,)]', "W")
endif
normal h
endfunction
-Original Message-
From: Peter Hodge [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 15, 2007 4:34 PM
To: Larson, David; vim-dev@vim.org
Subject: Re: new text object feature request
--- "Larson, David" <[EMAIL PROTECTED]> wrote:
> I often need to replace parameter text and usually try to remember the
> text object that selects the "inner parameter", only to come up short
> since that type isn't defined. It seems natural to have a "parameter"
> text object, where it would act on the text between commas or
> parentheses, i.e. from "(," to ",)".
>
> What say you? Something worthy of the todo list?
Hello,
I believe that can be done using Vimscript, so you could try that first.
regards,
Peter
___
How would you spend $50,000 to create a more sustainable environment in
Australia? Go to Yahoo!7 Answers and share your idea.
http://advision.webevents.yahoo.com/aunz/lifestyle/answers/y7ans-babp_re
g.html
new text object feature request
I often need to replace parameter text and usually try to remember the text object that selects the "inner parameter", only to come up short since that type isn't defined. It seems natural to have a "parameter" text object, where it would act on the text between commas or parentheses, i.e. from "(," to ",)". What say you? Something worthy of the todo list? David
RE: I can't change the font in vim7.1!
I wasn't aware of that feature. Thanks for the tip! :)
-Original Message-
From: A.J.Mechelynck [mailto:[EMAIL PROTECTED]
Sent: Monday, May 14, 2007 5:35 PM
To: Larson, David
Cc: vim-dev@vim.org
Subject: Re: I can't change the font in vim7.1!
Larson, David wrote:
> I just upgraded to 7.1, and now when I open up a gvim session, I get
> this huge monospaced font that I can't change. If I type:
>
> :set guifont?
>
> it returns "7x14" which is what I set it to, but it isn't what is
> displayed. If I change the setting to *any* other font that is valid
for
> my system, the display doesn't change, although the guifont setting
> shows that it is set to the new value.
>
> Help!
> David
>
> :version
> shows:
>
> VIM - Vi IMproved 7.1 (2007 May 12, compiled May 14 2007 09:50:48)
> Compiled by [EMAIL PROTECTED]
> Big version with GTK2 GUI. Features included (+) or not (-):
With a GTK2 GUI, you can set the font interactively, using
:set guifont=*
This will bring up a font chooser menu. Thereafter,
:set guifont=
will show on the command-line the exact command (with escaping
backslashes if
and where needed) that you need to write into your vimrc to set that
font.
There are (including the obsolete kvim) five different "families" of Vim
GUIs,
each of which requires a different 'guifont' format, not accepted by
other
GUIs. The following is what I use in my "portable vimrc" to "sniff" the
GUI
version:
if has("gui_running") " console Vim cannot set the font
if has("gui_gtk2")" GTK+2, not GTK+1
set gfn=Bitstream\ Vera\ Sans\ Mono\ 9
elseif has("gui_photon") " Photon GUI
set gfn=Bitstream\ Vera\ Sans\ Mono:s9
elseif has("gui_kde") " the obsolete kvim
set gfn=Bitstream\ Vera\ Sans\ Mono/9/-1/5/50/0/0/0/1/0
elseif has("x11") " other X11 GUIs including GTK+1
set
gfn=-*-lucidatypewriter-medium-r-normal-*-*-100-*-*-m-*-*
else " non-X11 GUIs including Windows
set gfn=Lucida_Console:h9:cDEFAULT
endif
endif
Best regards,
Tony.
--
... My pants just went on a wild rampage through a Long Island Bowling
Alley!!
Re: Stable Vim version 7.1 has been released
[Bram Moolenar] So how do I tell make that I want to build three targets in sequence then? For generice make, not GNU make. It was once forbidden to depend on GNU make in GNU packages. I guess the first package to blatantly break this rule has been GNU libc. So, most of our habits were developed for generic make. When one wants to build three targets in sequence, there is some reason for needing to build one before another, such needs are dependencies indeed, to be expressed explicitly as such. So, instead of: goal: a b c ACTIONS one writes, after having identified the real needs: goal: c ACTIONS c: b b: a Another approach I saw at times, but not so commendable, is: goal: $(MAKE) a $(MAKE) b $(MAKE) c ACTIONS -- François Pinard http://pinard.progiciels-bpi.ca
Re: problems with vim
Thanks, The problem was sloved by keeping these two lines in .vimrc set backspace=2 set nocompatible Thanks once again.. -- Nageshwar M
Re: Stable Vim version 7.1 has been released
Francois Pinard wrote: > [Bram Moolenar] > > >Hmm, in my POV a rule like: > > > target: one two three > > >means that "one", "two" and "three" are build in sequence, not at the > >same time. I suppose adding the "-jN" argument changes the semantics of > >the Makefile, and that causes it to break. > > In fact, so far that I know (and everything I know is debatable! :-), > the "in sequence" is not part of the semantic of Makefiles, and should > never be relied upon. Of course, if you experiment with various "make" > implementations, you may observe that dependencies are usually build in > sequence, but this should be seen as an accident, and not as a proof. So how do I tell make that I want to build three targets in sequence then? For generice make, not GNU make. -- Birthdays are healthy. The more you have them, the longer you live. /// Bram Moolenaar -- [EMAIL PROTECTED] -- 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///
Re: MSVC build option about default library MSVCRT
[redirecting to vim-dev] > I am wondering whether l. 705 of Make_mvc.mak in vim-7.1-extra.tar.gz > should be change from > > LINKARGS1 = $(linkdebug) $(conflags) /nodefaultlib:libc > > to > > LINKARGS1 = $(linkdebug) $(conflags) /nodefaultlib:libc /nodefaultlib:msvcrt > > I have been using it for maybe half a year and not found a single > problem yet. It will eliminate this message when building vim.exe: > > libcmt.lib(crt0init.obj) : warning LNK4098: defaultlib 'msvcrt.lib' > conflicts with use of other libs; use /NODEFAULTLIB:library > > Without /nodefaultlib:msvcrt vim.exe will have a dependency on > MSVCR71.DLL (I use MSVC 7.1). This added flag will not affect > gvim.exe. The command lines I used are: > > nmake -f Make_mvc.mak GUI=yes OLE=yes MBYTE=yes IME=yes GIME=yes > CSCOPE=yes PERL=C:\Perl DYNAMIC_PERL=yes PERL_VER=58 > PYTHON=C:\Python24 DYNAMIC_PYTHON=yes PYTHON_VER=24 RUBY=C:\ruby > DYNAMIC_RUBY=yes RUBY_VER=18 RUBY_VER_LONG=1.8 TCL=C:\Tcl > DYNAMIC_TCL=yes TCL_VER=84 TCL_VER_LONG=8.4 XPM=C:\xpm %* > nmake -f Make_mvc.mak MBYTE=yes CSCOPE=yes PERL=C:\Perl > DYNAMIC_PERL=yes PERL_VER=58 PYTHON=C:\Python24 DYNAMIC_PYTHON=yes > PYTHON_VER=24 RUBY=C:\ruby DYNAMIC_RUBY=yes RUBY_VER=18 > RUBY_VER_LONG=1.8 TCL=C:\Tcl DYNAMIC_TCL=yes TCL_VER=84 > TCL_VER_LONG=8.4 XPM=C:\xpm %* I'm very careful with these things. Make_mvc.mak is used for several versions of MSVC, starting at 4.1. You need to check all versions to make sure it doesn't cause any problems. I suppose the error message you get is from some of the languages Ruby/Python/Tcl/ I don't get it, thus you can probably solve it by checking your included libraries. Perhaps one has not been build by MSVC? That usually causes trouble (not just an error message, but a crash at runtime). Try actually using all the languages. -- "The sun oozed over the horizon, shoved aside darkness, crept along the greensward, and, with sickly fingers, pushed through the castle window, revealing the pillaged princess, hand at throat, crown asunder, gaping in frenzied horror at the sated, sodden amphibian lying beside her, disbelieving the magnitude of the frog's deception, screaming madly, "You lied!" - Winner of the Bulwer-Lytton contest (San Jose State University), wherein one writes only the first line of a bad novel /// Bram Moolenaar -- [EMAIL PROTECTED] -- 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///
Re: problems with vim
Nageshwar wrote: Hi, I got the same problem in gvim also (backspace problem). The backspace is working for newly entered characters as long as we are in the same line. Once we left a line and came back, backspace is not working, [...] :set backspace=indent,eol,start see ":help 'backspace'" Best regards, Tony. -- That woman speaks eight languages and can't say "no" in any of them. -- Dorothy Parker
Re: problems with vim
On Tue, May 15, 2007 at 02:38:01PM +0530, Nageshwar wrote: > I got the same problem in gvim also (backspace problem). The backspace > is working for newly entered characters as long as we are in the same > line. Once we left a line and came back, backspace is not working, This is the traditional vi behaviour. :h bs Yeti -- http://gwyddion.net/
Re: problems with vim
Hi,
I got the same problem in gvim also (backspace problem). The backspace
is working for newly entered characters as long as we are in the same
line. Once we left a line and came back, backspace is not working,
The tab problem was solved with -N option. thanks..
On 5/15/07, A.J.Mechelynck <[EMAIL PROTECTED]> wrote:
Nageshwar M wrote:
> Hello,
>
> I tried in xterm, konsole, and yakuake but got the same problem. I
> guess the problem is with compilation options... When I used :set
> esckeys arrow keys working properly but not backspace (in gvim also i
> faced the same problem). Also the command completion is not working ..
> i typed :he and pressed tab.. it didn't give me available commands
>
- Do you get the same problem in the GUI? ("vim -g" or "gvim")?
- The problem with completion may be due to 'compatible' mode: try
vim -u NONE -N
:set wildmenu
:he
Best regards,
Tony.
--
Hartley's First Law:
You can lead a horse to water, but if you can get him to float
on his back, you've got something.
--
--
Best Regards,
Nageshwar M
Re: problems with vim
Nageshwar M wrote:
Hello,
I tried in xterm, konsole, and yakuake but got the same problem. I
guess the problem is with compilation options... When I used :set
esckeys arrow keys working properly but not backspace (in gvim also i
faced the same problem). Also the command completion is not working ..
i typed :he and pressed tab.. it didn't give me available commands
- Do you get the same problem in the GUI? ("vim -g" or "gvim")?
- The problem with completion may be due to 'compatible' mode: try
vim -u NONE -N
:set wildmenu
:he
Best regards,
Tony.
--
Hartley's First Law:
You can lead a horse to water, but if you can get him to float
on his back, you've got something.
Re: patch 7.1.002
Bram Moolenaar wrote: > Patch 7.1.002 > Problem:Oracle Pro*C/C++ files are not detected. > Solution: Add the missing star. (Micah J. Cowan) Just to be clear: while I reformatted the solution in patch-form, it was Arturo Olguín Cruz who first found the bug and determined its fix: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/86916 -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ signature.asc Description: OpenPGP digital signature
Re: [Patch] proper detection of ProC files.
Micah Cowan wrote: > Fixes an apparent typo in filetype.vim. > > Per https://bugs.launchpad.net/ubuntu/+source/vim/+bug/86916. Must have been there for a while. Thanks for the fix! -- In a world without fences, who needs Gates and Windows? /// Bram Moolenaar -- [EMAIL PROTECTED] -- 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///
patch 7.1.002
Patch 7.1.002
Problem:Oracle Pro*C/C++ files are not detected.
Solution: Add the missing star. (Micah J. Cowan)
Files: runtime/filetype.vim
*** ../vim-7.1.001/runtime/filetype.vim Thu May 10 20:42:30 2007
--- runtime/filetype.vimTue May 15 09:12:06 2007
***
*** 1,7
" Vim support file to detect file types
"
" Maintainer: Bram Moolenaar <[EMAIL PROTECTED]>
! " Last Change:2007 May 10
" Listen very carefully, I will say this only once
if exists("did_load_filetypes")
--- 1,7
" Vim support file to detect file types
"
" Maintainer: Bram Moolenaar <[EMAIL PROTECTED]>
! " Last Change:2007 May 15
" Listen very carefully, I will say this only once
if exists("did_load_filetypes")
***
*** 1286,1292
au BufNewFile,BufRead *.it,*.ih setf ppwiz
" Oracle Pro*C/C++
! au BufNewFile,BufRead .pc setf proc
" Privoxy actions file
au BufNewFile,BufRead *.actionsetf privoxy
--- 1286,1292
au BufNewFile,BufRead *.it,*.ih setf ppwiz
" Oracle Pro*C/C++
! au BufNewFile,BufRead *.pcsetf proc
" Privoxy actions file
au BufNewFile,BufRead *.actionsetf privoxy
*** ../vim-7.1.001/src/version.cMon May 14 19:35:51 2007
--- src/version.c Tue May 15 09:13:11 2007
***
*** 668,669
--- 668,671
{ /* Add new patch number below this line */
+ /**/
+ 2,
/**/
--
hundred-and-one symptoms of being an internet addict:
132. You come back and check this list every half-hour.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- 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///
Re: problems with vim
Hello, I tried in xterm, konsole, and yakuake but got the same problem. I guess the problem is with compilation options... When I used :set esckeys arrow keys working properly but not backspace (in gvim also i faced the same problem). Also the command completion is not working .. i typed :he and pressed tab.. it didn't give me available commands On 5/15/07, A.J.Mechelynck <[EMAIL PROTECTED]> wrote: Nageshwar M wrote: > Hello, > > I compiled the vim 7.1 source for unix and installed it in my fedora > core 4 pc. When I pressed arrows its printing A,B,C,D's(in insert > mode) , backspace is not working and when I pressed delete > continuously the gvim is closing down. Someone please help me. > > The information that vim is showing for :version is > > Normal version with GTK2 GUI. Features included (+) or not (-): [...] This is usually due to a termcap problem. In which case(s) do you see the problem (among the following)? - in GUI mode (e.g. Alt-F2 then gvim) - in console mode in a terminal displaying through X (and which one: xterm? konsole? gnome-terminal? other[and which one]?) - in the "pure text" linux console (hit Ctrl-Alt-Fn with n in the range [1..6], log in if necessary, then invoke vim) Best regards, Tony. -- A nymph hits you and steals your virginity. -- -- Best Regards, Nageshwar M
