Hello,
I have a function which compiles documents (LaTeX). It actually calls a python
script which then calls back vim using --remote-expr switch. It works fine on
Linux (and MacOS) though on Windows, every call to 'vim --remote-expr ...'
returns a window with error code (which is the return code
Hi Marcin Szamotulski,
a) vim-addon-async (receives callback datab but delays action until user
is not disturbed (insert mode, command line window))
b) vim-addon-background-cmd (implements what you describe, however goal
is always show error list)
c) don't call back into vim, make vim poll
On 01/10/2012 11:02 AM, Boyko Bantchev wrote:
1. I strongly believe that, in general, a dark background
reduces the eye strain.
When they get older, many people (myself included) find it more
difficult to read light text on a dark background. I don't know if it's
eye strain, or if it's
Am 11.01.2012 02:56, schrieb Gary Johnson:
I started vim as
vim -N -u NONE a
and executed
:set tw?
I saw the result textwidth=0 as expected. Then I did the
following:
:set tw=50
:split b
:set tw?
textwidth=50
Again, as expected.
:set tw=60
On 03:04 Wed 11 Jan , Charlie Kester wrote:
On 01/10/2012 11:02 AM, Boyko Bantchev wrote:
1. I strongly believe that, in general, a dark background
reduces the eye strain.
When they get older, many people (myself included) find it more
difficult to read light text on a dark
On 10:05 Wed 11 Jan , Marc Weber wrote:
Hi Marcin Szamotulski,
a) vim-addon-async (receives callback datab but delays action until user
is not disturbed (insert mode, command line window))
b) vim-addon-background-cmd (implements what you describe, however goal
is always show error
On 11/1/12 11:04, Charlie Kester corky1...@comcast.net wrote:
On 01/10/2012 11:02 AM, Boyko Bantchev wrote:
1. I strongly believe that, in general, a dark background
reduces the eye strain.
When they get older, many people (myself included) find it more
difficult to read light text
when opening too many tab pages, it will be hard to identify a file by
the name on the tab bar
how can make the tab bar split into two lines automaticlly ?
--
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 Wed, Jan 11, 2012 at 12:04 PM, Charlie Kester corky1...@comcast.net wrote:
There doesn't seem to be any settled science on this topic, and therefore
there is room for disagreement. Vim allows its users to use whatever
colorscheme they like, and that's something we should all appreciate.
I
On 11/01/12 13:03, gaoqiang wrote:
when opening too many tab pages, it will be hard to identify a file by
the name on the tab bar
how can make the tab bar split into two lines automaticlly ?
AFAIK, you can't.
But you can use fewer tab pages and more windows per tab. With the
following
* J.Z. bosto...@gmail.com [120110 19:43]:
thanks, set ft=sh did the trick. I cannot use.sh extension for files
for ksh funtions, and cannot have #! in them also.
(Please do not top-post.)
I'm curious why you can't use a shebang line (#!) in ksh. I haven't
used ksh since the early '90s,
El 10/01/2012 12:36, Paul Isambert escribió:
Hello there,
Given the mapping:
mapTab fXa
where X stands for any character, if X appears on the line,Tab
goes to Insert mode after that character, as expected; but if the
character doesn't appear on the line, the cursor shouldn't move but it
This new script looks rather 'fishy' to me:
http://www.vim.org/scripts/script.php?script_id=3876
The information about the user who submitted it isn't very convincing
either:
user name IBCBETagent
first name IBC-BET
last name Agent
email asianbookmaker@yahoode
homepage
Marvin Renich, Wed 2012-01-11 @ 08:43:06-0500:
* J.Z. bosto...@gmail.com [120110 19:43]:
thanks, set ft=sh did the trick. I cannot use.sh extension for files
for ksh funtions, and cannot have #! in them also.
I'm curious why you can't use a shebang line (#!) in ksh. I haven't
used
On 2012-01-11, Andy Wokula wrote:
Am 11.01.2012 02:56, schrieb Gary Johnson:
I started vim as
vim -N -u NONE a
and executed
:set tw?
I saw the result textwidth=0 as expected. Then I did the
following:
:set tw=50
:split b
:set tw?
textwidth=50
* Taylor Hedberg tmhedb...@gmail.com [120111 10:03]:
This is a bit of a digression, but shebang lines are not a feature of
the shell, but a feature of the operating system. So if it works in one
shell, it should (theoretically) work in any shell on the same system.
You are right, this is
Excerpts from Marcin Szamotulski's message of Wed Jan 11 12:19:04 +0100 2012:
Thanks. My call back function is just setting some variables, issues :cgetfile
command (at most), is it possible to do that without delays?
I can only repeat myself. Goto vim-addon-async and have a look at its
Hello all,
is it possible to define a syntax match only used once inside a syntax region
definition?
When I define the following using the contains option, each line with bar is
matched:
Syntax definitions:
syntax region start=START end=END contains=synmatch
syntax match synmatch /^bar/
On Jan 11, 11:46 am, Edwin Miller edwin.mil...@web.de wrote:
Hello all,
is it possible to define a syntax match only used once inside a syntax region
definition?
When I define the following using the contains option, each line with bar is
matched:
Syntax definitions:
syntax region
On Jan 11, 12:47 pm, Ben Fritz fritzophre...@gmail.com wrote:
On Jan 11, 11:46 am, Edwin Miller edwin.mil...@web.de wrote:
Hello all,
is it possible to define a syntax match only used once inside a syntax
region
definition?
When I define the following using the contains
Am 11.01.2012 17:40, schrieb Gary Johnson:
On 2012-01-11, Andy Wokula wrote:
Am 11.01.2012 02:56, schrieb Gary Johnson:
I started vim as
vim -N -u NONE a
and executed
:set tw?
I saw the result textwidth=0 as expected. Then I did the
following:
:set tw=50
:split b
TeRanEX wrote:
This new script looks rather 'fishy' to me:
http://www.vim.org/scripts/script.php?script_id=3876
Thanks. Script, download and user all deleted.
John
--
You received this message from the vim_use maillist.
Do not top-post! Type your reply below the text you are replying to.
For
This may have something to do with my settings, or is some endemic
problem in
language based indenting.
For my indent settings, I have 'si' set, but not 'ai',
However, in 2 different languages, perl and javascript,
having a backslash in a line will automatically cause indenting on the
On 2012-01-11, Andy Wokula wrote:
Am 11.01.2012 17:40, schrieb Gary Johnson:
On 2012-01-11, Andy Wokula wrote:
Am 11.01.2012 02:56, schrieb Gary Johnson:
I started vim as
vim -N -u NONE a
and executed
:set tw?
I saw the result textwidth=0 as expected. Then I did the
On 2012-01-11, Linda W wrote:
This may have something to do with my settings, or is some endemic problem in
language based indenting.
For my indent settings, I have 'si' set, but not 'ai',
However, in 2 different languages, perl and javascript,
having a backslash in a line will
So your request can be rewritten as
1) please ship perl with Windows version of Vim
2) find a fast way to prefix each line with its own line position as %
value? Thus if you have 4 lines it should be:
0 %
50 %
100 %
In those cases I tend to write a stupid .vim file and source it:
fun!
On 01/11/12 19:38, Marc Weber wrote:
2) find a fast way to prefix each line with its own line position as %
value? Thus if you have 4 lines it should be:
0 %
50 %
100 %
In those cases I tend to write a stupid .vim file and source it:
fun! Prefix()
let max = line('$')
for i in
When working with vim especially on windows creating a new file can be
a bit of a pain as I have to navigate the directory structure to do
this.
I found this http://vim.wikia.com/wiki/Set_working_directory_to_the_current_file
which is good if there is already a file open I guess.
But I was
On 2012-01-11, flebber wrote:
When working with vim especially on windows creating a new file can be
a bit of a pain as I have to navigate the directory structure to do
this.
I found this
http://vim.wikia.com/wiki/Set_working_directory_to_the_current_file
which is good if there is already
On Jan 12, 2:02 am, Albin Olsson albin.ols...@gmail.com wrote:
If anybody is interested here is how you inverse the colours
everywhere (you need a HW accelerated video driver):
Linux: Use Compiz window manager (works fine with both Gnome and KDE)
and press Meta+M or Meta+N (you also might
On Jan 12, 12:04 am, Charlie Kester corky1...@comcast.net wrote:
On 01/10/2012 11:02 AM, Boyko Bantchev wrote:
1. I strongly believe that, in general, a dark background
reduces the eye strain.
I agree strongly.
When they get older, many people (myself included) find it more
Am Mittwoch, 11. Januar 2012 19:50:18 schrieb Ben Fritz:
On Jan 11, 12:47 pm, Ben Fritz fritzophre...@gmail.com wrote:
On Jan 11, 11:46 am, Edwin Miller edwin.mil...@web.de wrote:
Hello all,
is it possible to define a syntax match only used once inside a syntax
region definition?
32 matches
Mail list logo
