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
From: Bram Moolenaar [mailto:b...@moolenaar.net]
Thanks. Perhaps Vince knows how to fix this more efficiently?
I'll have a look at the patch and see if there is a simpler way.
Vince
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
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
Hi All,
I encrypted a file using the blowfish option 'cryptmethod=1' prior to
'salt' being added. I've updated my source repository this morning
and have recompiled vim (with the 'salt' addition) and now the file
won't unencrypt. Is there a way to recover the file, or is the
contents lost?
On Mon, Jun 14, 2010 at 7:34 PM, Chris Sutcliffe I encrypted a file
using the blowfish option 'cryptmethod=1' prior to
'salt' being added. I've updated my source repository this morning
and have recompiled vim (with the 'salt' addition) and now the file
won't unencrypt. Is there a way to
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
I don't think this is the right solution. Any key typed with CTRL would
be affected.
That's exactly as it supposed to work in the patch.
I think you need to find a way to produce Esc in your russian layout.
Yes, but not only Esc.
All the keybindings with Ctrl key don't work, such as
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
On Jun 6, 3:26 pm, Bram Moolenaar b...@moolenaar.net wrote:
James Vega wrote:
On Sat, Jun 05, 2010 at 10:37:39PM +0200, Patrick Texier wrote:
Le Sat, 05 Jun 2010 16:16:06 +0200, Bram Moolenaar a écrit dans le
message 201006051416.o55eg6to002...@masaka.moolenaar.net :
Patch
Chris Sutcliffe wrote:
I encrypted a file using the blowfish option 'cryptmethod=1' prior to
'salt' being added. I've updated my source repository this morning
and have recompiled vim (with the 'salt' addition) and now the file
won't unencrypt. Is there a way to recover the file, or is
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
12 matches
Mail list logo
