Hello,
Could someone help me with the following issue,
please?
autoindent in Vim works great for most of the
source-code. However, when I try it on the following,
for example,
string
GetHelloWorld()
{
return string("Hello, world!");
}
, the indentation becomes
string
GetHelloWorld()
{
...
On 1/31/07, Jack Tucker <[EMAIL PROTECTED]> wrote:
Christopher Hever <[EMAIL PROTECTED]> replied:
> Well, it seems you're making it a bit to difficult. All you have to do
> is :set textwidth=n in your .vimrc, and then you can use facilities
> like gq to break lines; e.g., gq} will wrap to the
>
Christopher Hever <[EMAIL PROTECTED]> replied:
> Well, it seems you're making it a bit to difficult. All you have to do
> is :set textwidth=n in your .vimrc, and then you can use facilities
> like gq to break lines; e.g., gq} will wrap to the
> end of the paragraph.
Thank you sir ... works on all
Hello:
I'm an old Unix user that converted to SuSE Linux five or six
years ago. I have a rather simple problem that's giving me
trouble so I joined the mailing list hoping to find some help.
I moved many vi .exrc set and map commands onto my SuSE 6.4 system
unchanged and they worked fine, VIM ve
[DervishD]
[Bram Moolenaar]
Only a few things might need to be spread to other directories, using
symlinks when possible (binary in /usr/local/bin, libs in
/usr/local/lib, header files in /usr/local/include).
Well, I know about a packaging system that does exactly that (I don't
remember it
Is there any possibility of editing during compiling like in Visual
Studio, also seeing the errorlist growing during compiling?
Hi Peter.
I'd like this too. I started looking into it, but the partial solution
I have is ugly, and can't find a way around not being able to
programmatically update
"Tim Chase" wrote,
Using a simple change to Tim Chase' original substitution response, you
have:
[snip]
if you don't want to type it in every time,
:vmap :s/\d\+/\=line('.')-line("'<")
which adds ctrl-i as a key in visual mode to do the job.
Ok, one last question on this. :-)
Is there a w
Using a simple change to Tim Chase' original substitution response, you
have:
[snip]
if you don't want to type it in every time,
:vmap :s/\d\+/\=line('.')-line("'<")
which adds ctrl-i as a key in visual mode to do the job.
Ok, one last question on this. :-)
Is there a way to start this from
"Tom Whittock" wrote,
but it kept going to the same spot as before. I will not change the [#].
Where is the match for (? I can't figure it out.
Using a simple change to Tim Chase' original substitution response, you
have:
:'<,'>s/\d\+/\=line('.')-line("'<")
which replaces the *first nu
On 2007-01-29, Evan Klitzke <[EMAIL PROTECTED]> wrote:
> Hi everyone,
>
> I have the F2 key mapped as a "compile" function for the programs I
> write, e.g. if I am editing a .tex file I have an autocmd to execute
> pdflatex, if I am editing a .py file I have an autocmd to execute
> python. The cas
Hi,
if I compile something in vim (WinXP), vim is blocked during the compile
process. If compiling is finished, I can edit my files again.
Is there any possibility of editing during compiling like in Visual
Studio, also seeing the errorlist growing during compiling?
thanks a lot!
Peter
but it kept going to the same spot as before. I will not change the [#].
Where is the match for (? I can't figure it out.
Using a simple change to Tim Chase' original substitution response, you have:
:'<,'>s/\d\+/\=line('.')-line("'<")
which replaces the *first number* on every line in the v
Hi,
I am getting two errors in two Dr. Chip VIM plugins.
1) This error when editting via scp:
Error detected while processing function
netrw#NetRead..42_NetOptionRestore:
line 43:
E354: Invalid register name: '*'
line 44:
E354: Invalid register name: '*'
I have the last netrw.vim (6577)
"Mark Woodward" wrote,
On Mon, 2007-01-29 at 21:57 +1300, John Little wrote:
Hi
IMHO simpler and more flexible (works if there are lines not matching
the pattern) is:
:let n=0 | g/opIndex(\zs\d\+/s//\=n/|let n+=1
A useful idiom I learned here. Usually I muck around with ordinary
search
On Mon, 2007-01-29 at 21:57 +1300, John Little wrote:
> Hi
>
> IMHO simpler and more flexible (works if there are lines not matching
> the pattern) is:
>
> :let n=0 | g/opIndex(\zs\d\+/s//\=n/|let n+=1
>
> A useful idiom I learned here. Usually I muck around with ordinary
> searches until t
Hi Tony :)
* A.J.Mechelynck <[EMAIL PROTECTED]> dixit:
> Bram Moolenaar wrote:
> [...]
> >>I don't see how getting rid of hardcoded directories in the source
> >>code is going to cause problems for users ;) In fact, hardcoded
> >>directories may cause problems: if you modify "src/Makefile
Hi Bram :)
* Bram Moolenaar <[EMAIL PROTECTED]> dixit:
> DervishD wrote:
>
> > I mean, that's not the point. The point is that the source code is
> > using hardcoded directories, and that is not a good practice, even if
> > you force to have all runtime files under the same directory, be
Hi Bram :)
* Bram Moolenaar <[EMAIL PROTECTED]> dixit:
> DervishD wrote:
>
> > > Generally I find it quite strange to order application-specific files
> > > by their type instead of by the application.
> >
> > But that's a very sensible thing to do. This way you can partition
> > the hi
18 matches
Mail list logo
