On 4 August 2013, Tony Mechelynck wrote:
> On 03/08/13 14:11, Bram Moolenaar wrote:
> >
> >Patch 7.4b.012
> >Problem:Output from a shell command is truncated at a NUL. (lcd 47)
> >Solution: Change every NUL into an SOH.
> >Files: src/misc1.c
>
> Why into an SOH, and not into a (no
On 03/08/13 21:57, Bram Moolenaar wrote:
Ron Aaron wrote:
On Friday, August 2, 2013 9:16:41 PM UTC+3, Bram Moolenaar wrote:
Ron Aaron wrote:
:lmap is only for typed characters. From the help:
No, that's not my problem. I'm attaching a file which demonstrates
the exact problem, if you
On Saturday, August 3, 2013 10:57:29 PM UTC+3, Bram Moolenaar wrote:
> It appears you expect lmap's to be remappable. If you look at the output of
> ":lmap" you can see they are listed with a star, which means they are not
> remappable.
No, I expect that if I map "'" to something, then that map
> It appears you expect lmap's to be remappable. If you look at the
> output of ":lmap" you can see they are listed with a star, which means
> they are not remappable.
It is related to my old question, which is listed in todo.txt
> When a mapping exists both for insert mode and lang-insert mode,
On Sunday, August 4, 2013 8:34:05 AM UTC+8, Andrei Olsen wrote:
> On Sunday, August 4, 2013 2:12:28 AM UTC+2, Bohr Shaw wrote:
> > This is a the left and bottom part of the whole screen picture.
>
> This is probably related to this discussion:
> https://groups.google.com/d/topic/vim_dev/ODi7rQPQdT
On 08/03/2013 08:59 PM, James McCoy wrote:
> Notice how the version number here doesn't match the version number in
> the previous command? RbConfig::CONFIG['ruby_version'] reports the API
> version, while VERSION/RUBY_VERSION report the release version.
>
> $ ruby --version
> ruby 1.9.3p194 (2012
On 03/08/13 14:11, Bram Moolenaar wrote:
Patch 7.4b.012
Problem:Output from a shell command is truncated at a NUL. (lcd 47)
Solution: Change every NUL into an SOH.
Files: src/misc1.c
Why into an SOH, and not into a (non-line-breaking) LF like everywhere
else in Vim?
Best regards
On Sat, Aug 03, 2013 at 08:29:06PM -0400, Michael Henry wrote:
> Empirically, I can verify that the behavior has changed. On
> Fedora 17, the query works:
>
> $ ruby -r rbconfig -e "puts RbConfig::CONFIG['ruby_version']"
> 1.9.1
>
> On Fedora 19, this same query prints the empty string.
>
>
On Sunday, August 4, 2013 2:12:28 AM UTC+2, Bohr Shaw wrote:
> This is a the left and bottom part of the whole screen picture.
This is probably related to this discussion:
https://groups.google.com/d/topic/vim_dev/ODi7rQPQdTw/discussion
--
--
You received this message from the "vim_dev" maillis
All,
On Fedora 19, Vim's configure script no longer correctly detects
the version of Ruby. Vim's current algorithm involves the Ruby
expression ``RbConfig::CONFIG['ruby_version']``, which returns a
string such as "1.9.1" on Fedora 17. On Fedora 19, the above
Ruby expression returns an empty stri
This is a the left and bottom part of the whole screen picture.
--
--
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 message because yo
I updated Cygwin on my machine a week or two ago, which included new
gcc-mingw packages, and suddenly I could no longer include Strawberry
Perl in my native Vim builds. I do not believe this is the fault of
Vim, but I am looking for tips on how to correct this problem since my
own investigat
Ron Aaron wrote:
> On Friday, August 2, 2013 9:16:41 PM UTC+3, Bram Moolenaar wrote:
> > Ron Aaron wrote:
>
> >
> > :lmap is only for typed characters. From the help:
>
> No, that's not my problem. I'm attaching a file which demonstrates
> the exact problem, if you do "gvim -u test.vim", and
On Friday, August 2, 2013 9:16:41 PM UTC+3, Bram Moolenaar wrote:
> Ron Aaron wrote:
>
> :lmap is only for typed characters. From the help:
No, that's not my problem. I'm attaching a file which demonstrates the exact
problem, if you do "gvim -u test.vim", and then in insert mode type the "'"
Hi Bram!
If my understanding is correct,
The reply doesn't seem to be the answer for the problem I posted?
How about that? Is it a bug? or the behavior is supposed to work?
On Sat, Aug 3, 2013 at 3:16 AM, Bram Moolenaar wrote:
>
> Ron Aaron wrote:
>
>> Perhaps this is related to the bug I repor
Nazri Ramliy wrote:
> On Sat, Aug 3, 2013 at 8:11 PM, Bram Moolenaar wrote:
> > + /* Change NUL into SOH, otherwise the string is truncated. */
> > + for (i = 0; i < len; ++i)
> > + if (buffer[len] == NUL)
> > + buffer[len] = 1;
>
> The loop above doesn't loo
Patch 7.4b.014 (after 7.4b.012)
Problem:Stupid mistake.
Solution: Changle "len" to "i".
Files: src/misc1.c
*** ../vim-7.4b.013/src/misc1.c 2013-08-03 14:10:45.0 +0200
--- src/misc1.c 2013-08-03 17:29:33.0 +0200
***
*** 10890,10897
{
/* Ch
Patch 7.4b.013
Problem:Install dir for JP man pages is wrong.
Solution: Remove ".UTF-8" from the directory name. (Ken Takata)
Files: src/Makefile
*** ../vim-7.4b.012/src/Makefile2013-07-28 18:00:18.0 +0200
--- src/Makefile2013-08-03 17:19:33.0 +0200
***
On 3 August 2013, David Szotten wrote:
> Hi,
>
> the help for extend (`:help extend`) includes the following paragraph
>
> < When {expr1} is the same List as {expr2} then the number of
> items copied is equal to the original length of the List.
> E.g., whe
Hi,
the help for extend (`:help extend`) includes the following paragraph
< When {expr1} is the same List as {expr2} then the number of
items copied is equal to the original length of the List.
E.g., when {expr3} is 1 you get N new copies of the first
> I suppose truncation is never useful. How about changing the NUL (0x00)
> into SOH (0x01)? SOH hardly ever appears, thus it can still be
> recognized as probably having been a NUL.
I would like to see readsystem() function in addition to system() one in order
to cope with the problem in the p
On 3 August 2013, Nazri Ramliy wrote:
> On Sat, Aug 3, 2013 at 8:11 PM, Bram Moolenaar wrote:
> > + /* Change NUL into SOH, otherwise the string is truncated. */
> > + for (i = 0; i < len; ++i)
> > + if (buffer[len] == NUL)
> > + buffer[len] = 1;
>
> The loop
On Sat, Aug 3, 2013 at 8:11 PM, Bram Moolenaar wrote:
> + /* Change NUL into SOH, otherwise the string is truncated. */
> + for (i = 0; i < len; ++i)
> + if (buffer[len] == NUL)
> + buffer[len] = 1;
The loop above doesn't look right to. Shouldn't it be like thi
On 3 August 2013, Bram Moolenaar wrote:
>
> lcd wrote:
>
> > The easy way to describe this is by an example:
> >
> > :echo system('printf "a\0b\n"')
> >
> > prints "a". The output of "system(command)" is truncated at the first
> > NUL character in command's output.
> >
> > Th
Tony Mechelynck wrote:
> On 27/07/13 18:47, Zdenek Sekera wrote:
> > On 07/19/2013 10:51 PM, tux- wrote:
> >> Zdenek Sekera schrob am Freitag, 19. Juli 2013 um 22:40 Zeit:
> >>
> >>> Has the probable release date for 7.4 been set already?
> >> When it's done.
> >>
> > Thanks for useful reply, I r
Dominique wrote:
> Vim doxygen syntax file does not highlight the \tparam doxygen
> command, which is almost the same as \param but used for type
> arguments in c++ templates, see:
>
> http://www.stack.nl/~dimitri/doxygen/manual/commands.html#cmdtparam
>
> The \tparam doxygen command is used in
Patch 7.4b.012
Problem:Output from a shell command is truncated at a NUL. (lcd 47)
Solution: Change every NUL into an SOH.
Files: src/misc1.c
*** ../vim-7.4b.011/src/misc1.c 2013-07-05 19:44:45.0 +0200
--- src/misc1.c 2013-08-03 13:59:15.0 +0200
***
*** 10887
lcd wrote:
> The easy way to describe this is by an example:
>
> :echo system('printf "a\0b\n"')
>
> prints "a". The output of "system(command)" is truncated at the first
> NUL character in command's output.
>
> This affects all functions calling get_cmd_output(), including
>
ZyX wrote:
> Steps to reproduce:
>
> vim -u NONE -N -c ':h /\%(\)'
>
> . This will produce two “E55: Unmatched \)” messages and one
> “E149: Sorry, no help for /\%(\)”. Note that there is such tag.
> Trying to use “:h /\%(” works.
>
> According to “:h {subject}” ({subject} should be typed
Patch 7.4b.011
Problem:":he \%(\)" does not work. (ZyX)
Solution: Add an exception to the list.
Files: src/ex_cmds.c
*** ../vim-7.4b.010/src/ex_cmds.c 2013-08-02 14:15:06.0 +0200
--- src/ex_cmds.c 2013-08-03 13:36:44.0 +0200
***
*** 5924,5937 **
Steps to reproduce:
vim -u NONE -N -c ':h /\%(\)'
. This will produce two “E55: Unmatched \)” messages and one “E149: Sorry, no
help for /\%(\)”. Note that there is such tag. Trying to use “:h /\%(” works.
According to “:h {subject}” ({subject} should be typed literally) (which points
to t
Hi
Vim doxygen syntax file does not highlight the \tparam doxygen
command, which is almost the same as \param but used for type
arguments in c++ templates, see:
http://www.stack.nl/~dimitri/doxygen/manual/commands.html#cmdtparam
The \tparam doxygen command is used in stl or boost for example:
32 matches
Mail list logo
