Matthew Winn wrote:
On Fri, 18 May 2007 20:24:17 -0600, Russell Bateman
[EMAIL PROTECTED] wrote:
As far as I know, Vim won't autowrap blocks of text you paste in.
Something could be written I suppose, but I don't know of something
already doing it.
It depends how you paste. If you
(Stupid plain text problem...)
Russell Bateman wrote:
Eric Leenman wrote:
Hi,
I'm used to cut, copy and paste the windows-way.
Meaning, selecting text and then press CTRL-X, CTRL-C or CTRL-V.
In VIM (and correct me if I'm wrong) you
yank (y) for copy
put (p) for paste
. for cut
The project to integrate vim and gdb usefully is called clewn and is on
clewn.sourceforge.net. I think there may be others as well.
Mathieu Malaterre wrote:
Hello,
I was looking at the ideas page for google summer of code for vim,
and I did not see integration of gdb in vim. As far as I know
While (someone) is at it, tip #1472's author and summary need to be
adjusted. Similarly, #1456's author field.
(Pardon, this may not have gone out in the correct format.)
Russell Bateman wrote:
Why are you typing : ? Unless I have misunderstood your notation here,
search is simply:
/\word\
Russ Bateman
Matthew Karas wrote:
Hello,
When I try to search for a word with the following
command
I have had inexplicable and inconsistent trouble with Windoz doing this
at least since back in version 98. It's infuriating.
Jeffrey Robertson wrote:
That's just a different way into the same dialog box I used in
the first place. It doesn't work for me. Although I can select
gvim.exe, it
What Gary says is historically true, but I would point out that it was
the fact that deep underneath vi was sitting on ed. Many full-screen
versions of line editors, like teco, suffered from having their wings
tied down close to the lowest assumptions and could not spread them and
soar.
I
I don't seem to have this problem when I code because I would tend to
code your line thus:
progname=/usr/local/txserver
Russ
Ben K. wrote:
Vimmers,
I find gf very convenient, but with shell scripts, I'd like a
different behavior:
In shell scripts, there should be no spaces around =.
As long as we're degenerating into the whimsical, it's also a homophone
for a slang term for brother-in-law (BEAUF-rère).
A.J.Mechelynck wrote:
Robert Cussons wrote:
Bill McCarthy wrote:
Hello Vim List,
I listened to Bram's BOF this past weekend. I still don't
know what BOF means.
From
I've been an ignorecaser too (for 20 years) and share the same concerns.
Greg Dunn wrote:
On 9/22/06, Yakov Lerner [EMAIL PROTECTED] wrote:
Am I, like, alone in the Universe to use/have 'set ignorecase' by
default ?
Yakov
I'm an ignorecaser too. It gets in the way a bit with C
Just in case my answer will get you going a little quicker (because I've
always found vim help useful, but it's a lot more useful to those who
already know--I've scratched my head and had to experiment a lot for
even simple things)...
You can put these modelines at the top of your file or the
I get these all the time and, as far as I can tell, they are somewhat
meaningless to me (maybe they mean something to vim list management)
since, if I ignore them, I don't seem to be subject to any adverse
consequences: I seem still to get the mail threads.
Russ
Max Dyckhoff wrote:
Has
[more way off topic comments]
...some linguists say that those silent letters are not artifacts, but
reflect __phonemes__ (is that the word?) that are still present in the
mental representation of the language...
--__morphemes__, actually, from a written point of view (you did say
letters).
As you say, warning: off-topic post. Read at your own risk.
This discussion underlines all the more strongly why I don't attempt to
produce final documents using vim: I sometimes use an actual word
processor like Open Office Writer, but mostly I write in HTML and, of
course, the best HTML
Of course, we all realize that the original difference between AZERTY
and QWERTY was the analyzed solutions to the problem of the likelihood
of two typewriter hammers striking the platen in close enough succession
that they would jam together and get stuck. Accents arose as a
distinction only
in Paris for 6 years, I'm something of an
Anglophile, but that's another story--check out my Inspector Morse site
at http://www.windofkeltia.com/morse and my Allo, Allo page at
http://www.windofkeltia.com/allo .)
Russ
A.J.Mechelynck wrote:
Russell Bateman wrote:
Of course, we all realize
I found that I got an error with
!-- vim: ts=2 sw=2: --
Error detected while processing modelines:
line 789 (the last line of my file, but I tried it also on lines 1 and 2
(after the html tag) with the same result)
E518: Unknown option: --
Hit ENTER or type command to continue
Instead, I
editors. For this reason, at my place of work at
least, it goes at the bottom where seemingly no one cares.
A.J.Mechelynck wrote:
Russell Bateman wrote:
I found that I got an error with
!-- vim: ts=2 sw=2: --
Error detected while processing modelines:
line 789 (the last line of my file
Well, if I can't get off the list, at least, please bring me my wine!
;-)
Charles E Campbell Jr wrote:
marcelo wrote:
Excuse this OT. But I can't unsubscribe to this list. When I try the
ezmlm
response says that i'm not in the mailing list. I tried the
[EMAIL PROTECTED] and got no
We keep hearing about how placing a modeline at the top of the file...
Because I work in a multitabbed environment (i.e.: there are more than
one tab standard), I have to use a modeline to sort out tabstop and
shiftwidth. I put this modeline AT THE BOTTOM of my file where it works
just fine
Formally speaking, C99 (ISO/IEC 9899:1999) still refers to ANSI C
which does not tolerate the C++ style comment operator. If you don't
believe me, just pass whatever your compiler's strict ANSI compliance
flag is and see if it doesn't croak on them. Back in 1989, ANSI had not
yet conceded the
and
that includes no C++ style comments, but truly, I haven't tested that
assertion since I'd get crucified if I did. Maybe I'll try it before
checking something in.
Russ
Yakov Lerner wrote:
On 6/20/06, Russell Bateman [EMAIL PROTECTED] wrote:
Formally speaking, C99 (ISO/IEC 9899:1999) still
to mask out your comments and
avoid all the confusion? (that was a joke, I think)
Max
-Original Message-
From: Russell Bateman [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 20, 2006 9:22 AM
To: Yakov Lerner
Cc: Vim List
Subject: Re: how to detect c99 vs c89 (//-comments vs /*-comments
I was unable to figure out how to do that. As the last line of my
Makefile.am I always put:
# vim: set tabstop=4 shiftwidth=4 noexpandtab:
since, by default, these guys around me (I'm the new guy) like expandtab
which, as you know, is problematic for makefiles.
Best,
Russ
John Orr wrote:
There is help for this as others have told you by now, but I'm sure you
just want to get going, so here's what I do. I only write in C/C++,
make, bash, HTML and Perl, etc. and not in other, assorted high-level
languages so I don't know its effect on them, but this setting, which I
have in my
http://www.satokar.com/viplugin/index.php?MMN_position=7:7
Not sure of the main page for this tool as I'm at work (where I don't
use Java), but I have it at home. This will get you there, though.
I am using this and it work fine. It's worth the paltry sum I paid for
it. It's not Vim, but
I systematically place a comment at the bottom of files that establishes
tabular format:
/* vim: set tabstop=2 shiftwidth=2: */
and even in scripts and other files:
# This enforces this script's tab settings...
# /* vim: set tabstop=2 shiftwidth=2: */
That way, the problem is solved for
Actually, a spell checker would not catch this mistake which, from a
spell checker's point of view, is one of mere usage, not spelling,
peak being a word for the top of a mountain. Any spell checker would
have let it pass without commentary. And since both words are nouns,
even Microsoft Word
Yakov,
I know how to do this, but the only example I have of it is at work and
I won't be there until tomorrow.
It involves putting something like this at the top or bottom of the file:
/*
* vim set tabstop 4:shiftwidth 3:autoindent */
Anything you can specify using set in ex will get
29 matches
Mail list logo
