Bram
Patch
Problem:Make_mvc.mak creates an empty gvim.exe.mnf file
(or stops with an error message).
Solution: Don't use 'echo' to create files. Use inline files
instead.
Files: src/Make_mvc.mak
This has always worked just fine. When does it fail?
Mathias Michaelis wrote:
Patch
Problem:IMHO .pdb files should reside in the same directory as the
corresponding .exe files so they can be distributet along
with them.
Solution: Change one line within src/Make_mvc.mak
Files: src/Make_mvc.mak
I accidentally posted to individuals, not the list - damn Gmail!
Brad
On 16/06/06, John (Eljay) Love-Jensen [EMAIL PROTECTED] wrote:
Emacs can do everything: it's an editor, an environment, an operating system
(in the same sense that JVM is an operating system), and a religion. The only
Repost: to the actual list this time:
On 16/06/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 6/16/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Brad Beveridge wrote:
Hello all, I am involved in a project that has embedded ECL
(http://ecls.sourceforge.net/), a Lisp interpreter into Vim.
Is
Bram Moolenaar wrote:
Mathias Michaelis wrote:
Patch
Problem:Make_mvc.mak creates an empty gvim.exe.mnf file
(or stops with an error message).
Solution: Don't use 'echo' to create files. Use inline files
instead.
Files: src/Make_mvc.mak
This has always
Bram Moolenaar wrote:
Mathias Michaelis wrote:
Patch
Problem:IMHO .pdb files should reside in the same directory as the
corresponding .exe files so they can be distributet along
with them.
Solution: Change one line within src/Make_mvc.mak
Files:
Hi all
Clewn and vimGdb 1.8 have been released.
The clewn project implements full gdb support in the vim editor:
breakpoints, watch variables, gdb command completion, assembly
windows, etc.
You can get clewn and vimGdb from http://clewn.sourceforge.net.
New features:
vimGdb is ported to Vim
Tony Mechelynck wrote:
echo string1 file
echo string2 file
echo string3 file
etc.
ought to work, _except_ when the string is (ignoring case) ON OFF or
empty (in which case you will set, clear or display the echo on/off
setting instead of writing / appending to
Bram Moolenaar wrote:
Tony Mechelynck wrote:
echo string1 file
echo string2 file
echo string3 file
etc.
ought to work, _except_ when the string is (ignoring case) ON OFF or
empty (in which case you will set, clear or display the echo on/off
setting instead of
On 6/18/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 5/23/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
create a file ~/.vimtest as follows:
cat .vimtest
set nocompatible
set readonly
C-D
and execute (g)vim:
vim .vimtest -u .vimtest
try
Yakov Lerner wrote:
On 6/18/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 5/23/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
create a file ~/.vimtest as follows:
cat .vimtest
set nocompatible
set readonly
C-D
and execute (g)vim:
vim .vimtest
All,
I'm curious to know peoples' opinions on this matter, especially Bram,
since he's back.
The issue is about whether the completion popup menu should disappear
when the user hits backspace all the way back to the initial
pre-completed state. Right now, the popup window disappears.
--Matt
On
On 6/18/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 6/18/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Yakov Lerner wrote:
On 5/23/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
create a file ~/.vimtest as follows:
cat .vimtest
set nocompatible
set readonly
C-D
I will modify rubycomplete so that it doesn't load anything from the
current buffer by default. This will limit completion to the default
environment objects. rubycomplete does not seem to work with
$SAFE 3.
As a note, sorry about the lag, I missed this thread until Bram brought
it to my
vim unserstands \t and \n in [] in regexp (as tab and as newline).
But \s is not treated as blanks in []. Can you please add
treatment of \s as blanks in [] in regexp. I mean, \s is sort of
space and Tab, no more complex than that, no ?
Thanks
Yakov
My code contains multiple targets for the same tag, as explained
in the (*1).
Let's assume that 'tags' contains multiple lines for the same name.
I want to go to the *next definition of tag 'foo', so that N presses of
some key X gets me to the 1st definition of the tag, then to the second,
etc.
I found that it would be more satisfying to the user
if :match and :syn had additional attribute, 'priority=',
so that user could control what has higher prio and what
has higher prio.
I find current rules of assigning priorities ad hoc and too
user-uncontrollable. For :match, they are fixed and
Eric Arnold wrote:
Does anybody understand why trailing spaces in an echon string don't
actually show up?
echon \ngimme
let inp = getchar()
echon nr2char(inp)
It appears this is because getchar() doesn't flush the output and
position the cursor. Try this patch:
***
Dnia niedziela, 18 czerwca 2006 12:00, Yakov Lerner napisał:
vim unserstands \t and \n in [] in regexp (as tab and as newline).
But \s is not treated as blanks in []. Can you please add
treatment of \s as blanks in [] in regexp. I mean, \s is sort of
space and Tab, no more complex than that,
On 6/18/06, Mikolaj Machowski [EMAIL PROTECTED] wrote:
Dnia niedziela, 18 czerwca 2006 12:00, Yakov Lerner napisał:
vim unserstands \t and \n in [] in regexp (as tab and as newline).
But \s is not treated as blanks in []. Can you please add
treatment of \s as blanks in [] in regexp. I mean,
George V. Reilly wrote:
There were concerns about switching over to Subversion when we
first started using it a few months ago, just before Vim 7.0
released. Are those concerns still valid?
If you mean switch over completely, that's Bram's decision.
Edward L. Fox wrote:
Dennis Nezic wrote:
when i exit my wm (e16), since it doesn't (and shouldn't) close any
other programs, gvim is stuck without an x server, and doesn't handle
this loss gracefully. effectively, it's as if it was kill -9'ed ... and
thus leaves temporary files behind, which i later have to
It works. Thanks.
On 6/18/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Eric Arnold wrote:
Does anybody understand why trailing spaces in an echon string don't
actually show up?
echon \ngimme
let inp = getchar()
echon nr2char(inp)
It appears this is because getchar() doesn't flush the
Yakov Lerner wrote:
My code contains multiple targets for the same tag, as explained
in the (*1).
Let's assume that 'tags' contains multiple lines for the same name.
I want to go to the *next definition of tag 'foo', so that N presses of
some key X gets me to the 1st definition of the tag,
Maciej Kalisiak wrote:
I've created a seperate thread for this issue, even though I discussed
it briefly earlier, as I've done some testing and it seems this may be
a Vim bug.
NOTES
- using Vim 7.0, downloaded and installed about 2 days ago
- running under WinXP SP2
STEPS TO REPRODUCE
Yegappan Lakshmanan wrote:
Hi Yakov,
On 6/18/06, Yakov Lerner [EMAIL PROTECTED] wrote:
How can I determine [in vim function] that my current line
number corresponds to the definition of tag X ?
Do I need to parse tags-file for that, or I can get it using
existing vim functions ?
You need
Gerald Lai wrote:
For Netrw v98, this hack seems to make it work as requested:
Doesn't work for me :(
I installed the Decho plugin, and noticed that the 'cd' command inside
netrw works, but looks like something else is resetting the directory
back to the original value!
Is there some way I can
On 6/18/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Yegappan Lakshmanan wrote:
Hi Yakov,
On 6/18/06, Yakov Lerner [EMAIL PROTECTED] wrote:
How can I determine [in vim function] that my current line
number corresponds to the definition of tag X ?
Do I need to parse tags-file for that, or I
K.S.Sreeram wrote:
Gerald Lai wrote:
For Netrw v98, this hack seems to make it work as requested:
Doesn't work for me :(
I installed the Decho plugin, and noticed that the 'cd' command inside
netrw works, but looks like something else is resetting the directory
back to the original value!
Yakov Lerner wrote:
On 6/18/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Yegappan Lakshmanan wrote:
Hi Yakov,
On 6/18/06, Yakov Lerner [EMAIL PROTECTED] wrote:
How can I determine [in vim function] that my current line
number corresponds to the definition of tag X ?
Do I need to parse
Hi Yakov,
On 6/18/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 6/18/06, A.J.Mechelynck [EMAIL PROTECTED] wrote:
Yegappan Lakshmanan wrote:
Hi Yakov,
On 6/18/06, Yakov Lerner [EMAIL PROTECTED] wrote:
How can I determine [in vim function] that my current line
number corresponds to the
I finally managed to solve the problem!
Here's what is needed in the vimrc :
autocmd BufEnter,BufRead,BufNewFile,BufFilePost * \
execute :lcd . expand(%:p:h)
Previously, I was using only the 'BufEnter' event, that doesn't work
when changing directories from within netrw. Then Tony suggested
hi,
would it be possible to make a Commments/Additional
Notes functionallty for scripts ? Similiar to the
Additional Notes in the tips section.
with this the feedback from the user would be better. and
the developer of the script can improve the script and would
be more motivated.
regards
Jochen Baier wrote:
hi,
would it be possible to make a Commments/Additional
Notes functionallty for scripts ? Similiar to the
Additional Notes in the tips section.
with this the feedback from the user would be better. and
the developer of the script can improve the script and would
be more
Marc Weber wrote:
Suggestion: change
===
*m* *mark* *Mark*
m{a-zA-Z} Set mark {a-zA-Z} at cursor position (does not move
the cursor, this is
Hari Krishna Dara wrote:
I was just stuck by another serious bug in Vim7, again to do with insert
mode completion (i_Ctrl-P) and repeat, and it is easy to reproduce (I
apologize if this was already reported). Try this:
- Start plain vim: gvim -u NONE
- :set nocp
- Add the below two
Hari Krishna Dara wrote:
It seems like I am getting E788 error too often, without much reason.
The latest is for the :compiler command that is being executed from a
ftplugin. I narrowed it down to the command itself, not the compiler
plugin, as adding a :finish at the start of the compiler
Am running under cygwin, where they've updated to vim7.
One of the first problems I'm noticing is that when I edit a file,
then exit, then re-edit, I'm no longer placed back at the location
I was at when I had previously exited.
Is this a bug, or did some value not get properly updated when
we
Linda W wrote:
Am running under cygwin, where they've updated to vim7.
One of the first problems I'm noticing is that when I edit a file,
then exit, then re-edit, I'm no longer placed back at the location
I was at when I had previously exited.
Is this a bug, or did some value not get properly
A.J.Mechelynck wrote:
when I edit a file, then exit, then re-edit, I'm no longer placed
back at the same location
Is this a bug, or did some value not get properly updated when
we were upgraded to vim7 from vim6? I.e. do I need to change
some setting?
As has been repeatedly said this past
Linda W wrote:
A.J.Mechelynck wrote:
when I edit a file, then exit, then re-edit, I'm no longer placed
back at the same location
Is this a bug, or did some value not get properly updated when
we were upgraded to vim7 from vim6? I.e. do I need to change
some setting?
As has been repeatedly
A.J.Mechelynck wrote:
As has been repeatedly said this past week, this requires a viminfo
setting and an autocommand.
Has it been said that it didn't require these in the past? I.e. --
has this requirement changed since 64?
The autocommand is defined near line 70 of
A.J.Mechelynck wrote:
As has been repeatedly said this past week, this requires a viminfo
setting and an autocommand.
Maybe as has not been said. I have all that.
The autocommand is defined near line 70 of $VIMRUNTIME/vimrc_example.vim
so if you source the latter, you should
Linda W wrote:
A.J.Mechelynck wrote:
As has been repeatedly said this past week, this requires a viminfo
setting and an autocommand.
Has it been said that it didn't require these in the past? I.e. --
has this requirement changed since 64?
No.
The autocommand is defined near
Thanks Gerald, and others - think I might settle for
a) keeping expandtab enabled,
b) remap tab to insert a real tab, ie, imap tab ^Q^I
(^Q instead of ^V since for better and worse I use mswin.vim on windows)
c) set list to be able to see the tab characters, thus also setting listchars
like
I get almost zero emails on the scripts I've added. This means
1) They work perfectly
2) They are getting downloaded, but not used
3) There isn't enough immediacy to the feedback options, i.e. people
more likely to respond in a forum, than take the trouble to do
individual correspondance.
From
On Sun, 18 Jun 2006 16:16:01 +0200,
Bram Moolenaar [EMAIL PROTECTED] wrote:
Dennis Nezic wrote:
when i exit my wm (e16), since it doesn't (and shouldn't) close any
other programs, gvim is stuck without an x server, and doesn't
handle this loss gracefully. effectively, it's as if it
I have the following line in my ~/.vimrc
au BufWinLeave *.f90 mkview
If I open file1.f90 then do
:sp file2.f90
and close the file2.f90 then a new view is written. However if I do
:tabe file2.f90
and close the file2.f90 then the above autocommand is not executed and no new
view is
Hello all,
I have recently taken over maintainance of the PHP syntax file which was rather
neglected for around 2 years. PHP is growing quite rapidly and unfortunately
that means that by now there are well over 1700 keywords which need to be
correctly identified, and my next release of the
49 matches
Mail list logo
