On 2012-09-11, Timothy Madden wrote:
Hello
I would like to execute a Vim script from the command line, for
example to build a vimball archive from a Makefile.
But when I do that the Vim window always pops up and then immediately
disappears (as the script completes). Even if there are
On 10/09/12 04:14, Tim Johnson wrote:
[...]
Well, I as the OP quit following this thread until now and am
playing catchup.
I have the following code at lines 21 to 24 in
/Applications/MacVim-snapshot-62/MacVim.app/Contents/Resources/vim/runtime/ftplugin/python.vim
[code]
nnoremap silent
On 11/09/12 08:49, eNG1Ne wrote:
I'd like to be able to include a couple of variables in my mup source files, so
that when they're compiled the output shows the system date and the filename.
What's the simplest way to approach that?
Thanks in advance!
Are you sure you're on the right
On Tuesday, September 11, 2012 4:03:30 AM UTC+1, 葛布林 wrote:
I see, and I am starting trying. Very thanks! It is much better than the
original plsql.vim.
It is very handy that the color will change from white to blue after I close
a quotation. But in my codes there are some occasions like
* ChLange [2012-09-10 11:50 AM +0200]:
Another question: My Cursor is hidden when moving (for example,
holding down on of the arrow keys). It's visible again when the
movement stops. But again, this seems only to be a with HTML/Mason. In
pure Perl scripts, this is not a problem.
You should
On 09/11/2012 10:14 AM, Gary Johnson wrote:
On 2012-09-11, Timothy Madden wrote:
Hello
I would like to execute a Vim script from the command line, for
example to build a vimball archive from a Makefile.
But when I do that the Vim window always pops up and then immediately
disappears (as the
On 09/11/2012 08:02 AM, lith wrote:
I would like to execute a Vim script from the command line, for example
to build a vimball archive from a Makefile.
You can use the -c command line option, e.g.:
gvim -u NONE -U NONE -c YOUR COMMANDS HERE
With respect to vimball: There are also (at least)
I am trying to create a 1,000,000 byte file with VIM. The following
has VIM using 100% of _both_ my CPUs (Intel DuoCore) for almost two
hours before I killed it:
iaesc100.
/i assume that the holdup is not that 100 'a' characters are being
written, but rather that insert mode is being
Just to be clear, of course I am aware of bult-in Linux utilities such
as dd, ut I am trying to figure out what is wrong with VIM to
understand how to use that tool better in the future.
Thanks.
--
Dotan Cohen
http://gibberish.co.il
http://what-is-what.com
--
You received this message from
Hi,
Why not just:
iaesc - insert 'a'
yl- copy one character
100p- paste it 100 times
Regards,
Karol Samborski
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
On Tue, Sep 11, 2012 at 2:29 PM, Karol Samborski edv.ka...@gmail.com wrote:
Hi,
Why not just:
iaesc - insert 'a'
yl- copy one character
100p- paste it 100 times
Because that would give me a 101 byte file!
Seriously, though, thanks. This is
Dotan Cohen wrote:
I am trying to create a 1,000,000 byte file with VIM. The
following has VIM using 100% of _both_ my CPUs (Intel
DuoCore) for almost two hours before I killed it:
iaesc100.
Vim is for editing text, not performing arbitrary operations.
One problem with the above (on a
On Tue, Sep 11, 2012 at 2:34 PM, John Beckett johnb.beck...@gmail.com wrote:
Dotan Cohen wrote:
I am trying to create a 1,000,000 byte file with VIM. The
following has VIM using 100% of _both_ my CPUs (Intel
DuoCore) for almost two hours before I killed it:
iaesc100.
Vim is for editing
2012/9/11 Dotan Cohen dotanco...@gmail.com:
Because that would give me a 101 byte file!
My mistake. Please use 'x' instead of 'yl' :)
Karol Samborski
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For more
On 11.09.12 14:34, Dotan Cohen wrote:
I had to have only 99 characters to get a 100 file, in other
words there is an extra byte in there somewhere.
If ff is unix, then a '\n' is appended to the line. (It's what I had
expected, and od -c shows that that is what vim does.)
Erik
--
You
On Tue, Sep 11, 2012 at 2:50 PM, Erik Christiansen
dva...@internode.on.net wrote:
On 11.09.12 14:34, Dotan Cohen wrote:
I had to have only 99 characters to get a 100 file, in other
words there is an extra byte in there somewhere.
If ff is unix, then a '\n' is appended to the line.
On 11/09/12 13:12, Dotan Cohen wrote:
I am trying to create a 1,000,000 byte file with VIM. The following
has VIM using 100% of _both_ my CPUs (Intel DuoCore) for almost two
hours before I killed it:
iaesc100.
/i assume that the holdup is not that 100 'a' characters are being
written,
On 11/09/12 12:03, Timothy Madden wrote:
On 09/11/2012 10:14 AM, Gary Johnson wrote:
On 2012-09-11, Timothy Madden wrote:
Hello
I would like to execute a Vim script from the command line, for
example to build a vimball archive from a Makefile.
But when I do that the Vim window always pops up
Original Message
Subject:Re: system and user variables
Date: Tue, 11 Sep 2012 10:45:35 +0200
From: Niels Grundtvig Nielsen communicator@gmail.com
To: Tony Mechelynck antoine.mechely...@gmail.com
OK, pretend I didn't mention mup source. The question is
Both MacVim and Mac terminal vim use the PATH I have set.
vim-app, a gui version of terminal vim compiled from MacPorts vim-app
@7.3.646_0, does NOT use my PATH.
I found it did not work when trying
:r !gcal
(/bin/bash: line 1: gcal: command not found)
How would I get vim-app to start with my
On Tue, Sep 11, 2012 at 5:25 PM, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
I think that the following will create a file containing one million spaces
(and *no* carriage-return after them). I haven't tested it. It mixes
ex-commands and normal-mode commands. It assumes that the current
On 2012-09-11, Bee wrote:
Both MacVim and Mac terminal vim use the PATH I have set.
vim-app, a gui version of terminal vim compiled from MacPorts vim-app
@7.3.646_0, does NOT use my PATH.
I found it did not work when trying
:r !gcal
(/bin/bash: line 1: gcal: command not found)
How
Gary Johnson wrote:
On 2012-09-11, Bee wrote:
Both MacVim and Mac terminal vim use the PATH I have set.
vim-app, a gui version of terminal vim compiled from MacPorts vim-app
@7.3.646_0, does NOT use my PATH.
I found it did not work when trying
:r !gcal
(/bin/bash: line 1: gcal:
On Tue, Sep 11, 2012 at 3:32 PM, William Robertson
will...@williamrobertson.net wrote:
I didn't touch the quoting rules - they are still the original. I'll have
a look but I doubt I can improve on them.
I assigned VARCHAR and CHAR to the TODO highlighting group so that you can
easily
After performing a :vimgrep across a variety of files, I'm really
only interested in jumping to the next *file*, not the next match.
I can repeatedly do :cn until I get to the next file (exploiting
@: and @@ lazily), but I was hoping there might be some sort of
ignore the rest of this file and go
On Tuesday, September 11, 2012 6:29:35 PM UTC+1, 葛布林 wrote:
On Tue, Sep 11, 2012 at 3:32 PM, William Robertson
wil...@williamrobertson.net wrote:
I didn't touch the quoting rules - they are still the original. I'll have a
look but I doubt I can improve on them.
I assigned
Dotan Cohen dotanco...@gmail.com wrote:
I am trying to create a 1,000,000 byte file with VIM. The following
has VIM using 100% of _both_ my CPUs (Intel DuoCore) for almost two
hours before I killed it:
iaesc100.
/i assume that the holdup is not that 100 'a' characters are being
On 2012-09-11, Tim Chase wrote:
After performing a :vimgrep across a variety of files, I'm really
only interested in jumping to the next *file*, not the next match.
I can repeatedly do :cn until I get to the next file (exploiting
@: and @@ lazily), but I was hoping there might be some sort of
On 09/11/12 13:24, Gary Johnson wrote:
:help :cnf
Perfect. Just my overlooking. Thanks!
-tim
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
Hi,
try this
if has(gui_macvim)
let $PATH = /opt/local/bin:/opt/local/sbin:.$PATH
endif
I added something quite similar to my vimrc
-Derek
On Wed, Sep 12, 2012 at 1:37 AM, Bee fo...@calcentral.com wrote:
Both MacVim and Mac terminal vim use the PATH I have set.
vim-app, a gui version
On Tuesday, September 11, 2012 9:49:50 AM UTC-5, Tony Mechelynck wrote:
Original Message
Subject: Re: system and user variables
Date: Tue, 11 Sep 2012 10:45:35 +0200
From: Niels Grundtvig Nielsen communicator@gmail.com
To: Tony Mechelynck
On Sep 11, 9:40 am, Derek Ashley Thomas derekatho...@gmail.com
wrote:
Hi,
try this
if has(gui_macvim)
let $PATH = /opt/local/bin:/opt/local/sbin:.$PATH
endif
I added something quite similar to my vimrc
-Derek
On Wed, Sep 12, 2012 at 1:37 AM, Bee fo...@calcentral.com wrote:
On 2012-09-11, Bee wrote:
It is for vim-app, not MacVim, so this is what I used in my .gvimrc:
if has(mac)
if has(gui_macvim)
if has(patch260) Snow Leopard, previously bottom left
The preceding line should be:
if v:version 703 || v:version == 703 has(patch260) Snow Leopard,
On Sep 11, 1:24 pm, Gary Johnson garyj...@spocom.com wrote:
On 2012-09-11, Bee wrote:
It is for vim-app, not MacVim, so this is what I used in my .gvimrc:
if has(mac)
if has(gui_macvim)
if has(patch260) Snow Leopard, previously bottom left
The preceding line should be:
Oh, sorry I was not aware of vim-app on macports. The only additional
comment I have is that you may want to have if has('gui') before changing
the $PATH variable since you probably don't need to change it in
terminal-vim.
Also, my MacVim does not seem to load any environment variables for the
On Sep 11, 4:07 pm, Derek Ashley Thomas derekatho...@gmail.com
wrote:
Oh, sorry I was not aware of vim-app on macports. The only additional
comment I have is that you may want to have if has('gui') before changing
the $PATH variable since you probably don't need to change it in
terminal-vim.
On 09/11/2012 05:37 PM, Tony Mechelynck wrote:
[...]
That build script consists only of ex-commands, so you can omit the
leading colons and run Vim in batch mode as follows:
vim -esS build.vim
see
:help -e
:help -s-ex
:help -S
If you want your vimrc to be used, you will
On 2012-09-12, Timothy Madden wrote:
On 09/11/2012 05:37 PM, Tony Mechelynck wrote:
[...]
That build script consists only of ex-commands, so you can omit the
leading colons and run Vim in batch mode as follows:
vim -esS build.vim
see
:help -e
:help -s-ex
:help -S
On Wed, Sep 12, 2012 at 1:59 AM, William Robertson
will...@williamrobertson.net wrote:
Interesting - the quoting issue goes away if you set filetype=sqloracle.
My plsql.vim just sources that so I can't think any reason for it to have
its own parsing rules for quoted text. It seems fixed if
Fair point ... and bam ... yanked and put right into gvimrc for simplicity.
Thanks for correcting me :)
On Wed, Sep 12, 2012 at 8:49 AM, Bee fo...@calcentral.com wrote:
On Sep 11, 4:07 pm, Derek Ashley Thomas derekatho...@gmail.com
wrote:
Oh, sorry I was not aware of vim-app on macports.
40 matches
Mail list logo
