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, because
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 and don't
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 the
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
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..SNR42_NetOptionRestore:
line 43:
E354: Invalid register name: '*'
line 44:
E354: Invalid register name: '*'
I have the last netrw.vim
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
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
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 case of .c
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 number*
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 C-I :s/\d\+/\=line('.')-line(')CR
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
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 C-I :s/\d\+/\=line('.')-line(')CR
which adds ctrl-i as a key in visual mode to do the job.
Ok, one last question on this. :-)
Is there a
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
[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
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
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 gqmotion operator to break lines; e.g., gq} will wrap to the
end of the paragraph.
Thank you sir ...
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 gqmotion operator to break lines; e.g., gq} will wrap
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()
{
There appears to be an error in one of the tag names given to the
help entry for let-option:
:let {option-name} = {expr1} *:let-option* *:let-star*
The second tag should be *:let-* rather than :let-star*. This
is in the 2006 May 06 version of doc/eval.txt. A patch follows.
Rene de Zwart wrote:
I would like it if vim could integrate more into a graphical application
for instances an ide.
The integration would allow application builders to use vim as a component.
relief them of the burden of maintaining an editor
Give them access to 20+ years matured editor code
Now that there are many new - good, or not - ideas coming up. I think it
would be a great idea, if the voting page on:
http://www.vim.org/sponsor/vote_results.php
becomes updated with new ideas, and old ones get deleted/changed.
Now that we have omnicompletion, 'add intelligent,
I've noticed that the doxygen syntax highlighting incorrectly
highlights doxygen strings that look like this:
/**
* @brief Adjusts downlink frequency.
*/
It interprets link frequency as a link tag, which results in both
link and frequency being highlighted in an unexpected fashion. I
believe
21 matches
Mail list logo
