On Sat, Feb 17, 2024 at 8:31 PM Colin Kennedy wrote:
> Does :cc still honor the switchbuf=vsplit setting after this change?
>
> It’s nested in the PR replies currently but I think I asked whether we
> need this now in this PR and the consensus was to handle it as a horizontal
> split. If people
Hello Vim developers; there's a set of parentheses in src/drawline.c
unbalanced around the preprocessor conditional for FEAT_DIFF that
prevent compilation with the feature disabled. A patch is attached.
--
Tom Ryder <https://sanctum.geek.nz/>
--
--
You received this message from the &q
s probably meant to check if "throw_exception() == FAIL" instead of
"!= FAIL", wasn't it?
Tom
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www
> That "*" should be "s" then. I'll include that.
Yes. Sure. This is a copy-paste error where I would expect some
21st-century-AI-check to automatically kick in. ;-)
Tom M
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! T
Hi,
:menu listing sometimes contains items with an "s" in the first column.
Here is an example which can be seen after sourcing the standard menu.vim:
:menu Edit.Select\ All--- Menus ---
400 All^IggVG
n :call 11_SelectAll()
v :call 11_SelectAll()
s :call 11_SelectAll()
o
maparg('v')
>
The change to use the name "menu_info" instead of "maparg" seems to be
forgotten here.
Tom
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, vis
the timeout in 100
> msec parts, then check for CTRL-C typed, then back to waiting.
I am not sure how portable it would be but can't the signal handler be
configured in such a way that it lets the select() fail with EINTR after it
catches the SIGINT for CTRL-C?
That way it wouldn't be necessary
ncealed line after window
scroll (#5215)"
https://groups.google.com/forum/#!topic/vim_dev/cFeSIxAsnSc
*Travis CI* - "Build #10297 - vim/vim - Travis CI"
https://travis-ci.org/vim/vim/builds/610985079?utm_source=github_status_medium=notification
Tom
--
--
You received this messag
+ using |:split| but having the same contents as window
> {nr}, and
> + then closing {nr}.
> +
> + Both {nr} and {target} can be window numbers or
> |window-ID|s.
> +
> + Returns zero for success, non-zero
. All US users would benefit from it.
What do you think?
Tom
--
--
You received this message from the "vim_dev" 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
---
You received this messa
utput is horked
After the fix, the number of columns with features will be uniform once again.
It might even help to get rid of the hang. Though I am not sure I run vim in
the same way as toothpik as this is depends on
Tom M
--
--
You received this message from the "vim_dev" mailli
> ! #if defined(FEAT_BEVAL) || defined(FEAT_TEXT_PROP) || defined(PROT)
This was meant to check "PROTO" instead of "PROT", wasn't it?
Tom
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are
s, and the title string is never loaded up for me when I start vim.
>
> Let me know if you can repro!
FWIW, I am currently at Vim version 8.1.885 and I can reproduce it.
Tom
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the
Hello Vim developers; attached is a patch for an issue that cropped up
for me when rebuilding Vim without +diff (FEAT_DIFF) since the recent
work on 'signcolumn'.
--
Tom Ryder <https://sanctum.geek.nz/>
--
--
You received this message from the "vim_dev" maillist.
Do not top
On Mon, Jun 17, 2019 at 09:47:35AM +1200, Tom Ryder wrote:
On Sun, Jun 16, 2019 at 03:32:30PM +0200, Bram Moolenaar wrote:
Just add it as a global function, without "static". Then update the
prototype in src/proto/evalfunc.pro. You can do it automatically if
you have cproto, but
ry you had to update all those files when adding a new source file,
that's why I don't like adding many smaller files. Well, and it makes
building slower.
That's OK; it was interesting to figure out. Might be handy for me in
future too.
--
Tom Ryder <https://sanctum.geek.nz/>
--
there are so few existing ones already in there,
although a few of the ones towards the end of the file are time-related.
I don't think we should do this. This is only useful for debugging,
not really for users.
OK, agreed. Thanks.
--
Tom Ryder <https://sanctum.geek.nz/>
--
--
You re
On Fri, Jun 14, 2019 at 12:43:32PM +1200, Tom Ryder via vim_dev wrote:
On Thu, Jun 13, 2019 at 08:40:27PM +0200, Bram Moolenaar wrote:
Can you make a patch that adds a function to call localtime_r() and
keeps the current value of $TZ, and calls tzset() only when it
changes?
Yes, I think so
On Thu, Jun 13, 2019 at 08:40:27PM +0200, Bram Moolenaar wrote:
Can you make a patch that adds a function to call localtime_r() and
keeps the current value of $TZ, and calls tzset() only when it changes?
Yes, I think so. I'll attempt that later today. Thanks.
--
Tom Ryder <ht
those calls, per my patch, it works again.
Perhaps tzset() should only be called once, or perhaps only when the
$TZ variable was changed?
The latter idea seems good to me. Perhaps even a new function
settimezone() could be added, or a new optional parameter for
strftime()?
--
Tom Ryder
the problem on my Debian
GNU/Linux system at least points you in the right direction for
correcting the issue.
--
Tom Ryder <https://sanctum.geek.nz/>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For
Hello Vim developers; attached is a patch to apply the P_NODUP flag to
the 'backupskip' option to prevent duplicate paths being added to it,
and a test for the same.
--
Tom Ryder <https://sanctum.geek.nz/>
--
--
You received this message from the "vim_dev" maillist.
Do not top
and floating point numbers.
> !
> ! expr7 * expr7 Number multiplication
> *expr-star*
> ! expr7 / expr7 Number division *expr-/*
> ! expr7 % expr7 Number modulo*expr-%*
>
> For all, exc
> + while lnum < 10
> + call append( 1, string( lnum ) )
> + let lnum = lnum + 1
> + endwhile
> + normal G
> +
> + call assert_equal( line( '.' ), 11 )
> + endfunc
> +
> + func Test_Write_To_HiddenBuffer_Does_Not_Fix_Cursor_Clear()
> + call _SetUpHidd
P("ols", pp + 2, 3))
> ! cols = (int)strtol(pp + 2, NULL, 0);
> ! else if (pp[2] && STRNCMP("apitalize", pp + 2, 9))
> capitalize = 1;
> else
> {
> if (!argv[2])
> --- 508,517
> }
> else if
noticed two small typos:
> +The |:for| loop executes commands for each byte a Blob. A variable is set
byte of a Blob.
> + When {object} is a |Blob|, Vim stores and increment the
and increments the
Best Regards,
Tom
--
--
You received this message from the "vi
)| function. Using
[:] also
> + ! works, as explained above.
Wasn't this meant to say "copy of a blob" instead of "copy of a list"?
Thanks.
Tom
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you
On Tue, Jan 1, 2019 at 9:52 PM Tom M <7to...@gmail.com> wrote:
>
> for a zero-width property it's not enough to have {col} equal to "end_col
> ", "end_lnum" (if given) should be equal to {lnum} too.
>
>
I am not saying that it's coded wron
> !end_col column just after the text; not used when "length"
> ! is present; when {col} and "end_col" are equal
> ! this is a zero-width text property
for a zero-width property it's not enough to have {col} equal to "end_col",
"end_lnum" (if
so
added, with an example.
--
Tom Ryder <https://sanctum.geek.nz/>
--
--
You received this message from the "vim_dev" 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
---
You receiv
fine FOR_ALL_SIGNS_IN_BUF(buf) \
for (sign = buf-b_signlist; sign != NULL; sign = sign-next)
Perhaps 'sign' should be an argument of the macro, shouldn't it?
Otherwise there might be some unwanted effects on the code where the
macro is used.
Tom
--
--
You received this message from the "vim_
On Mon, Dec 24, 2018 at 9:36 AM Christian Brabandt wrote:
> I'll have a look.
>
> Tom, can you provide a simple test case?
It's about the issue reported by John Little and Tony Mechelynck on
Wed, Oct 24, 2018: "linebreak, showbreak, and visual block yank
problem". See: https:
e. If I ever happen to get it right I'll get back to you.
Tom
On Sat, Dec 22, 2018 at 4:56 PM Bram Moolenaar wrote:
>
>
> Tomm wrote:
>
> > On Tuesday, November 27, 2018 at 9:46:48 PM UTC+1, Christian Brabandt wrote:
> > > Hi,
> > > as somebody who has contrib
quite often tried to fix various bugs around the block editing and
> display of characters in combination of various settings that influence
> the display.
>
> On Di, 27 Nov 2018, Tom M wrote:
>
> [...]
> > Currently (as the test case suggests), the buffer ends up with l
nd the *whole*
length of the tab char is highlighted, not only the firs (or last) space?
The most important thing for me is to be able to programatically figure when
(in general) a space should be deleted together with it's lbr-padding and
when the corresponding external part od padding should stay
half of its width is to be
deleted. Let me know what you think.
Thanks.
Tom
func! Test_lbr_visual_block_space() " SCREEN: " with nolbr: "
|12345678901234567890| " 1|_0_a___d| " |_e
| " 2|_x suffix_too_wide_f| (space) " |or_window |
On Thu, Nov 15, 2018 at 7:46 AM Christian Brabandt wrote:
>
>
> On Mi, 14 Nov 2018, Tom M wrote:
>
> > On Wednesday, November 14, 2018 at 10:23:52 PM UTC+1, Tom M wrote:
> > >
> > > Hi,
> > >
> > > I propose the following patch (please see
On Wednesday, November 14, 2018 at 10:23:52 PM UTC+1, Tom M wrote:
>
> Hi,
>
> I propose the following patch (please see the attachment) to fix issues of
> John and Tony. It ads handling of 'showbreak' and 'linebreak' in visual block
> operations.
>
> Tom
Oooops, wron
> lines=68
> columns=174
> guifont=Bitstream Vera Sans Mono 8
> linebreak
> showbreak=---|
> ).
>
> Try it, it is easier to see than to explain.
>
> Best regards,
> Tony.
Hi,
I propose the following patch (please see the attachment) to fix issues o
, such as php.vim's square
bracket maps. I'm willing to fix some of those up too, if appropriate.
--
Tom Ryder <https://sanctum.geek.nz/>
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more informa
back to a value from 'tabstop'.
--
Tom Ryder <https://sanctum.geek.nz/>
--
--
You received this message from the "vim_dev" 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
---
You recei
On Tue, Apr 3, 2018 at 7:14 PM, Bram Moolenaar <b...@moolenaar.net> wrote:
>
> Tom M wrote:
>
>> > On Thu, Mar 29, 2018 at 2:06 PM, Bram Moolenaar <b...@moolenaar.net>
>> > wrote:
>> >
>> >>
>> >> Tom M wrote:
>>
On Tue, Apr 3, 2018 at 7:14 PM, Bram Moolenaar <b...@moolenaar.net> wrote:
>
> Tom M wrote:
>
> > > On Thu, Mar 29, 2018 at 2:06 PM, Bram Moolenaar <b...@moolenaar.net>
> > > wrote:
> > >
> > >>
> > >> Tom M wrote:
> >
On Mon, Apr 2, 2018 at 1:33 AM, Tom M <7to...@gmail.com> wrote:
>
>
> On Thu, Mar 29, 2018 at 2:06 PM, Bram Moolenaar <b...@moolenaar.net>
> wrote:
>
>>
>> Tom M wrote:
>>
>> > First of all, thank you for VIM. Now, I'd like to share an example
On Thu, Mar 29, 2018 at 2:06 PM, Bram Moolenaar <b...@moolenaar.net> wrote:
>
> Tom M wrote:
>
> > First of all, thank you for VIM. Now, I'd like to share an example of
> > a rather confusing behaviour. It's the ':file' ex command when used in
> > combination
after E23.
3) Or at least some notification that the file was not changed to 'b.txt'.
This is VIM 8.0.1648 on a Linux machine. VIM 7.4 is affected too.
Thanks in advance for all responses.
Best regards,
Tom
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type y
> Tom Lebreux wrote:
>
>> the source code doesn't appear in the source buffer
>> when using :Termdebug. I can use gdb fine to step,continue,break,etc
>> but I cannot see the source code (unless I `list` manually in the gdb
>> window. Also, the buttons in the tabbar d
program compiled with `-g` for debug info. I also
tried doing exactly what is described in the scenario shown in
:help Termdebug.
I tried with `vim -u NONE` just to be sure no plugins or configs messed
with this functionality. My vim version patch 1176.
Tom Lebreux
--
--
You received this message
Hi,
when I use :Termdebug to debug with gdb, my cpu hits 100%.
The only way to stop it is to exit completely or kill vim.
I am running vim 8.0 with included patch: 1-1159.
I tried both with my vimrc loaded and with `vim --clean`.
Tom Lebreux
--
--
You received this message from the "vi
You need :execute 'grep' join(map(files, 'shellescape(v:val, 1)'))
Thanks for pointing out the optional special argument to me.
Regards,
Tom
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information
On Friday, January 31, 2014 2:52:38 PM UTC-5, Daniel paradigm Thau wrote:
On Wednesday, January 29, 2014 7:40:10 PM UTC-5, Daniel paradigm Thau wrote:
Apologies for the delay.
Review for those who have forgotten and/or don't care to backread:
With this patch, if the user attempts to
On Saturday, June 14, 2014 10:21:30 AM UTC-4, Christian Wellenbrock wrote:
On Friday, June 13, 2014 4:39:37 PM UTC+2, Tom McDonald wrote:
Here's a recording of a demonstration of the current behaviour:
https://asciinema.org/a/10129
I agree that this change is useful and more consistent
Here's a recording of a demonstration of the current behaviour:
https://asciinema.org/a/10129
--
--
You received this message from the vim_dev 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
---
You
There's an exception to the i{ text object that ignores ignores leading
whitespace before the final } character. I think it would be useful if this
extended to the i( and i[ text objects as well. In particular, as a PHP
developer, I run into code like this a lot:
$foo = array(
(it's probably just one), you should be able to determine if it's hard-coded,
in a resources file somewhere, or both, and then set up a resources file to
override with something more appropriate, or edit the resources file.
TOM
PS Most of the time Meta is now a reference to the Alt key
at all because not all terminals can
display more than two.
Tom Sorensen
--
You received this message from the vim_dev 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
from :help design-multi-platform,
Support all the keys on the keyboard for mapping.
It would be great to get closer to that.
Tom Sorensen
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http
affected.
Tom
--
You received this message from the vim_dev 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
--
this is a bigger issue for those using the same config on Windows and
other platforms. You have to change rtp near the top of your .vimrc.
And, of course, if .vimrc was inside of .vim then it would be an
impossible situation.
Tom
--
You received this message from the vim_dev maillist.
Do not top
deals with that. You
still have 9 numbered groups but you can use any number of named
groups (see here for an example:
http://pragdave.blogs.pragprog.com/pragdave/2008/10/fun-with-ruby-19-regular-expressions.html).
Regards,
Tom.
--
You received this message from the vim_dev maillist.
Do not top
As you can see, the autoload script is loaded, even so vim shouldn't
need to. Is that the way autoloading is supposed to work or is this a
bug?
The line has to be parsed because how would you know if it isn't
an :endif. Maybe that's when the autoload function is loaded?
Anyway, you still can
a remark to the todo list.
For what it's worth, I can confirm that this is present in 7.2.000 as well
Tom
--
You received this message from the vim_dev 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
g:plugin_foo_cmd = 'rm -rf ~/*'
:protect g:plugin_foo_cmd
:function OmnipotentFunction()
: !rm -rf ~/*
:endf
:protect OmnipotentFunction
With the increased use of plugins, enhancing the sandbox this way IMHO
seems necessary, if vim doesn't already provide it. Just a thought.
Regard,
Tom
--
You
undo difficulties for users.
Tom
--
You received this message from the vim_dev 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
or Windows gvim
7.2.
Regards,
Tom
--
You received this message from the vim_dev 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,
I can't reproduce it. Perhaps something in your environment causes this?
You're right. LANG is de_DE.uft8. If I set LANG=C, the problem disappears.
Regards,
Tom
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
LC_MEASUREMENT=de_DE.utf8
LC_IDENTIFICATION=de_DE.utf8
LC_ALL=
Export LC_NUMERIC=C makes the problem disappear too. I assume the
default period character for locale de (unfortunately) is , not ..
This often causes troubles when parsing/exporting/importing data that
contain floats.
Regards,
Tom
--
You
Is anyone working on one yet? would love to take a peek at the code :p
--
You received this message from the vim_dev 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
do too. So I think it would be
good to include it in mainline.
Tom
--
You received this message from the vim_dev 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
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
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
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
/wiki/Special:Following and on the
settings page I can only change certain parameters.
Regards,
Tom
--
You received this message from the vim_dev 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
part, from the vim
community. It would be a great feature for v8. And I'm quite sure
there would be plenty of beta testers on numerous platforms (I'll
personally volunteer for XP, AIX 5.3, Solaris 9, RHEL5, and RHEL6).
Tom
--
You received this message from the vim_dev maillist.
Do not top-post
On Tue, Apr 20, 2010 at 6:09 PM, Christian Brabandt cbli...@256bit.org wrote:
Hi Tom!
On Sa, 17 Apr 2010, Tom Sorensen wrote:
It also works differently on different platforms. I played around with
a similar plugin (SwapExists.vim) that James wrote (iirc) about 6
months ago and could not get
vim-gnome, ubuntu 10.04.
BTW I have just recently started using the gnome version of gvim --
otherwise I mostly use the windows version. It seems to me that the
gnome version is rather sluggish in comparison and that the screen
gets updated more often. Is this a common observation?
Regards,
Tom
and on linux.
Regards,
Tom
--
You received this message from the vim_dev 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
Subscription settings: http://groups.google.com/group/vim_dev/subscribe?hl=en
to check whether
the current instance is the first one.
Regards,
Tom
--
You received this message from the vim_dev 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
Subscription settings: http
from a content perspective.
Tom
--
You received this message from the vim_dev 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
Subscription settings: http://groups.google.com/group/vim_dev/subscribe?hl=en
Hi,
I have just noticed that vim allows to use ** as regular expression.
Shouldn't this throw a Nested * exception like .** does?
Examples:
echo match(abc, **)
= 0
echo match(abc, .**)
= E61: Nested *
Regards
Tom
--
You received this message from the vim_dev maillist.
Do not top-post! Type
number.
Regards,
Tom
diff -r 6c3c2e464a96 src/Make_cyg.mak
--- a/src/Make_cyg.mak Wed Mar 10 16:12:48 2010 +0100
+++ b/src/Make_cyg.mak Sat Mar 13 14:16:16 2010 +0100
@@ -179,7 +179,9 @@
RUBY_INSTALL_NAME = mswin32-ruby$(RUBY_VER)
endif
else
-ifndef RUBY_PLATFORM
+ifneq (X$(wildcard, $(RUBY)/lib
I am not sure I understood you correctly. Compiler detects Ruby
version at compile time already (see numerous #ifdefs in if_ruby.c).
And I do not think there is a point in detecting version at run-time:
it looks Ruby developers do not care of C code compatibility.
I currently use has('ruby')
Maybe it /would/ make GVim more attractive if it had, let's say, a
more modern toolbar.
Maybe MS Office like ribbons would help to improve vim's popularity.
I've been told that a future version of OpenOffice will have similar
gui elements. Hence, they have to be useful.
--
You received this
to happen unless people like
Marc can easily and readily provide help where they can.
Tom
--
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
But what about spammers? I rememember there was an issue with comments
on 'Tips' on vim.sf.net.
IIRC you were able to post a tip or commment on a tip as anonymous
user without being logged in.
Since there already are several vim-related collaborative media in use
(vim-use, vim.wikia) I wonder
On the vim homepage/community, there is a link to http://vi-improved.com/wiki
The domain seems no longer to be active and is now redirected to a
GoDaddy page.
Regards,
Tom
--
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
It should be http://vi-improved.org/
This isn't the wiki though it once referred to. It seems to be rather
related to the #vim IRC channel, isn't it?
--
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
to reproduce those
problems.
Regard,
Tom
--
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
are likely to quickly become unusable since the development of vim
continues.
Regards,
Tom
--
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
of a deal.
In general, removing context menu clutter is a Good Thing. I like the
way TortoiseCVS/SVN do things (although they have far more options to
deal with).
Tom
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information
of the
options should be moved into a submenu.
Tom
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
. A lot of macro usage presumes that vim
will stop when the macro fails.
10...@q-- I have absolutely no idea how many times I need to run
this macro, so just run it until it fails.
Doing otherwise could result in some REALLY bad things happening at
the failure position.
Tom
-compliant.
Tom
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
1) All standard plugins supplied by vim should have a common method of
suppressing their loading. That is, they should all have a common
variable name to suppress them. For example, to suppress plugin x,
a variable g:plugin_x_loaded should be set or something.
How would this be different
for Windows. But
slower and using more memory, since you've added a translation layer.
Tom
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
xxFxxxExx
yyD
zzCz
The problem is caused by setting the 'lazyredraw' option, it causes the
cursor column to be computed.
This leads to a related question. Given the cursor is at position D,
is there a way to determine that the
BTW, tAssert provides convenience functions that my script don't (yet?).
At first, I wondered if both plugins should be merged.
This is also the reason why I'd rather prefer to
strip down my tassert plugin and to leave only the TAssert command and
some utility functions in it.
Just in
However I've made a different design choice: my plugin acts as a
preprocessor. Thanks to that, I'm able to know the line where an
assertion failure occurred
Cool.
BTW, tAssert provides convenience functions that my script don't (yet?).
At first, I wondered if both plugins should be merged.
WinZip (for instance) can uncompress .gz files as an easy preliminary step.
7zip[1], which is GPL licensed, handles all formats well.
The point was though that vimballs cannot readily include binary data
which isn't all wrong I think.
[1] http://www.7-zip.org
Right. For the near term, supporting unzipping using a pure-vimscript
solution isn't terribly likely, but it's definitely possible OOTB in
vims built with +python, for example.
installing zip-based plugins basically is a matter of
exec '!unzip '. shellescape(expand('%')) .' -d ~/vimfiles'
1 - 100 din 108 matches
Mail list logo
