On Jul 14, 6:09 am, Peter Odding pe...@peterodding.com wrote:
There is some info in the following:
http://vim.wikia.com/wiki/Execute_external_programs_asynchronously_un...
Thanks for your suggestion John. When I initially followed the link
above I didn't realize that :!start ... is a
Ben Fritz wrote:
Hence, the use of :!start /min in the tip John linked you to :-)
It appears I didn't read the linked web page carefully enough, thanks
for correcting me Ben. After receiving your message I was still
concerned that the /min option would open a minimized command prompt
window
Tom Link wrote:
In my experience the major problem with running external apps like
those listed above is filenames -- e.g. when I use cygwin tools from
windows gvim or when I want to use the same code to run an executable
on linux and windows etc. I don't consider the cmd window a major
problem
I haven't had much trouble with filenames personally, as long as I stick
to forward slashes (which work on Windows) instead of backslashes (which
don't work on anything but Windows) and don't mangle user-provided
pathnames starting with drive letters on Windows. Could you be more
specific in
On Jun 16, 3:41 am, Peter Odding pe...@peterodding.com wrote:
I haven't had much trouble with filenames personally, as long as I stick
to forward slashes (which work on Windows) instead of backslashes (which
don't work on anything but Windows) and don't mangle user-provided
pathnames
Peter Odding wrote:
I've asked myself why Vim's system() function on Windows uses
vimrun.exe and shows a command prompt window. The only reason
I can think of is so that the user has a chance to quit the
external command using Ctrl-C.
Sorry if the following is not relevant (I have not
Hello,
Tom Link wrote :
Which executable do you intend to execute in a cross-plattform
portable way?
(c)make/(b)jam/aap, gcc, doxygen, ctags, latex, ...
As far as I'm concerned, the need exists. I'd rather not require an external
executable/DLL though.
--
Luc Hermitte
On 6/14/2010 10:24 PM, Peter Odding wrote:
Ernie Rael wrote:
I wonder what the chances are of getting a new command in vim that
does what you want (or perhaps some options for no-window and
no-wait). Then the DLL on windows would not be needed.
[...]on UNIX it's dead easy to make
Which executable do you intend to execute in a cross-plattform
portable way?
(c)make/(b)jam/aap, gcc, doxygen, ctags, latex, ...
In my experience the major problem with running external apps like
those listed above is filenames -- e.g. when I use cygwin tools from
windows gvim or when I
Re execution background processes, what's wrong with :call system(cmd
/c start notepad)?
On Windows when you create a child process running a command-line program
(such as Exuberant Ctags) a command prompt window automatically pops up. If
One question, have you _actually_ seen console window
Unless you mean why it is necessary to have a DLL to perform these
operations on Windows.
Exactly
--
Sergey Khorev
http://sites.google.com/site/khorser
Can anybody think of a good tagline I can steal?
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
Sergey Khorev wrote:
One question, have you _actually_ seen console window when system()
function is used?
Yes I did, which is why I said as much:
The reason those command prompts windows bother me is that my easytags.vim** plug-in runs Exuberant Ctags every time the CursorHold autocmd fires
llor...@neo ~ $ which cmd
llor...@neo ~ $ type cmd
-bash: type: cmd: not found
This seems to answer the question of portability of using cmd ;-)
Which executable do you intend to execute in a cross-plattform
portable way?
--
You received this message from the vim_dev maillist.
Do not
On 14-Jun-2010 Tom Link micat...@gmail.com wrote:
llor...@neo ~ $ which cmd
llor...@neo ~ $ type cmd
-bash: type: cmd: not found
This seems to answer the question of portability of using cmd ;-)
Which executable do you intend to execute in a cross-plattform
portable way?
What's the
Ernie Rael wrote:
I wonder what the chances are of getting a new command in vim that does
what you want (or perhaps some options for no-window and no-wait). Then
the DLL on windows would not be needed.
I've asked myself why Vim's system() function on Windows uses vimrun.exe
and shows a
Hi list!
I wrote a plug-in that aims to improve the integration between Vim and
its environment by providing functions to switch to full-screen, open
URLs in the user's default web browser and execute external commands in
the background without opening a command prompt window. A DLL is
I wrote a plug-in that aims to improve integration between Vim and its
environment by providing functions to switch to full-screen, open URLs in
the user's default web browser and execute external commands in the
background without opening a command prompt window.
Re execution background
On 13-Jun-2010 Sergey Khorev sergey.kho...@gmail.com wrote:
I wrote a plug-in that aims to improve integration between Vim and its
environment by providing functions to switch to full-screen, open URLs in
the user's default web browser and execute external commands in the
background
Hi Sergey,
Re execution background processes, what's wrong with :call system(cmd
/c start notepad)?
On Windows when you create a child process running a command-line
program (such as Exuberant Ctags) a command prompt window automatically
pops up. If you don't want this you have to
Hi again.
Before I published the shell.vim plug-in I tested my execute()
implementation by comparing the results of executing the interactive,
graphical program Notepad using Vim's system() function and my execute()
implementation, simply as a demonstration of a child process blocking
20 matches
Mail list logo