On Thu, 25 Jan 2007 10:10:18 +0100, A.J.Mechelynck wrote:
> Spencer Collyer wrote:
> > Hi,
> >
> > When I'm writing C++ code, if I have a long comma-separated list of
> > items (like initializer parameters or function arguments) I like to
> > lay them out so that the comma is the first non-whitesp
DervishD schrieb:
Hi all :))
I'm trying to fully understand the syntax commands, and when doing
tests a question popped up in my mind: let's say I have a region which
starts with something like "\I\i*{" and ends with "}". For example, the
example below will match:
strange{contents}
Hi all :)
* DervishD <[EMAIL PROTECTED]> dixit:
> That is, the contained item is "swallowing" part of the "start"
> match!. I thought that when the match for "start" was performed, the
> matched test wasn't tried for any other match, including "contained"
> items. Obviously, I was wrong (
Hi all :))
I'm trying to fully understand the syntax commands, and when doing
tests a question popped up in my mind: let's say I have a region which
starts with something like "\I\i*{" and ends with "}". For example, the
example below will match:
strange{contents}
BUT, the belo
jose isaias cabrera wrote:
Greetings!
When I execute a command on the vim shell, ie.,
:!build -I..;c:\dmd\import -version=gui OpenJobs.d
a DOS command screen pops up and there is some data there. I have two
questions:
1. Can the info provided by the execution of the command be placed
right
Tim Chase wrote:
print("This is 1.\n");print("This is 2.");
print("This is 3.\n");
I would like the above to be formated like (which is just adding in
the newline a print that may not have it, but only if it does not
have it):
print("This is 1.\n");print("This is 2.");
print("This is 3.\n")
On Thu 25-Jan-07 1:08pm -0600, jose isaias cabrera wrote:
> When I execute a command on the vim shell, ie.,
>
> :!build -I..;c:\dmd\import -version=gui OpenJobs.d
>
> a DOS command screen pops up and there is some data there. I have two
> questions:
> 1. Can the info provided by the execution of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25-Jan-07, at 1:07 PM, Greg Dunn wrote:
On 1/25/07, Brian McKee <[EMAIL PROTECTED]> wrote:
Control-A to increment numbers is really handy sometimes. How about
adding logical opposites?
i.e. control-a while the cursor is over the word TRUE wou
print("This is 1.\n");print("This is 2.");
print("This is 3.\n");
I would like the above to be formated like (which is just adding in the
newline a print that may not have it, but only if it does not have it):
print("This is 1.\n");print("This is 2.");
print("This is 3.\n");
I presume you
Greetings!
When I execute a command on the vim shell, ie.,
:!build -I..;c:\dmd\import -version=gui OpenJobs.d
a DOS command screen pops up and there is some data there. I have two
questions:
1. Can the info provided by the execution of the command be placed right
below the command, ie.
:!
Hello,
I have the following question. Given several lines in a file that look
like the following:
print("This is 1.\n");print("This is 2.");
print("This is 3.\n");
I would like the above to be formated like (which is just adding in the
newline a print that may not have it, but only if it
On 1/25/07, Brian McKee <[EMAIL PROTECTED]> wrote:
Control-A to increment numbers is really handy sometimes. How about
adding logical opposites?
i.e. control-a while the cursor is over the word TRUE would make it
flip to FALSE,
on to off, yes to no and vice versa - case preserving of course.
Brian McKee wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
Please correct me if I've missed something.
I see where sponsorship allows you to vote on new features.
What's the appropriate proceedure for suggesting a feature?
I'm including my suggestion here because somebody's likel
Robert Hicks wrote:
A.J.Mechelynck wrote:
Robert Hicks wrote:
[...]
I only use a .vimrc and for the things that are gui specific I wrap in:
if has("gui_running")
" stuff for gvim
endif
Is there any reason NOT to do that if I only want to maintain one
config file?
Robert
I do that t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
Please correct me if I've missed something.
I see where sponsorship allows you to vote on new features.
What's the appropriate proceedure for suggesting a feature?
I'm including my suggestion here because somebody's likely to point
out why
A.J.Mechelynck wrote:
Robert Hicks wrote:
[...]
I only use a .vimrc and for the things that are gui specific I wrap in:
if has("gui_running")
" stuff for gvim
endif
Is there any reason NOT to do that if I only want to maintain one
config file?
Robert
I do that too. For the settings
Robert Hicks wrote:
[...]
I only use a .vimrc and for the things that are gui specific I wrap in:
if has("gui_running")
" stuff for gvim
endif
Is there any reason NOT to do that if I only want to maintain one config
file?
Robert
I do that too. For the settings which must wait until t
Hi again, and thanks for your quick responses.
I am using the addition of an extra filter on the makeprg, as
suggested. Here's what I use (I'm setting it buffer local, for other
reasons):
let &l:makeprg = &makeprg . ' $* \| sed -e "{
s/\(\w\)\:\\\/\/cygdrive\/\1\//;s/\\\/\//g }"'
which converts
Bill McCarthy wrote:
On Wed 24-Jan-07 1:41am -0600, Robert Cussons wrote:
I'm sorry, I know this should be a problem that I can
resolve for myself, but I have searched the vim help under
"bells" and "visualbell" and tried what it says and it
doesn't seem to work, so your help would be greatly
a
Hello,
Tom Whittock <[EMAIL PROTECTED]> wrote:
> I'm running the vim under cygwin, and have set up my build process to
> execute via :make. This is great, but the build process reports
> filenames in DOS format, not the cygwin /cygdrive/* way. This means
> that when a quickfix command runs, vim w
Tom Whittock schrieb:
Hi.
I'm running the vim under cygwin, and have set up my build process to
execute via :make. This is great, but the build process reports
filenames in DOS format, not the cygwin /cygdrive/* way. This means
that when a quickfix command runs, vim will be asked to open
"C:\dev
Hi.
I'm running the vim under cygwin, and have set up my build process to
execute via :make. This is great, but the build process reports
filenames in DOS format, not the cygwin /cygdrive/* way. This means
that when a quickfix command runs, vim will be asked to open
"C:\dev\test.cpp", when I alre
Spencer Collyer wrote:
> Hi,
>
> When I'm writing C++ code, if I have a long comma-separated list of
> items (like initializer parameters or function arguments) I like to lay
> them out so that the comma is the first non-whitespace character on the
> line, like so:
>
> foo( param1
>
23 matches
Mail list logo
