Re: Vim charity: financial report 2013
Hi, > Vim users are asked to support a project in Uganda, and many have sent > money in 2013. The ICCF foundation takes care of this and the financial > report is now available: http://www.iccf.nl/jaarrekening2013en.pdf I do not see the revenue of the books. Does it go to another foundation? Could you explain? Thanks, Frédéric -- -- 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 you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [patch] doc/gui.txt: small complements
Cade Foster wrote:
> diff -r 10d35c8b50e3 runtime/doc/gui.txt
> --- a/runtime/doc/gui.txt Mon Feb 24 03:32:00 2014 +0100
> +++ b/runtime/doc/gui.txt Thu Mar 06 19:30:14 2014 +0700
> @@ -133,6 +133,7 @@
> :winp[os]
> Display current position of the top left corner of the GUI vim
> window in pixels. Does not work in all versions.
> +Also see |getwinposx()| and |getwinposy()|.
>
> :winp[os] {X} {Y}*E466*
> Put the GUI vim window at the given {X} and {Y} coordinates.
> @@ -151,8 +152,12 @@
> option.
>
> If you are running the X Window System, you can get information about the
> -window Vim is running in with this command: >
> +window Vim is running in with this commands: >
> :!xwininfo -id $WINDOWID
> + :!xprop -id $WINDOWID
> +< or >
> + :execute '!xwininfo -id ' . v:windowid
> + :execute '!xprop -id ' . v:windowid
> <
> *gui-IME* *iBus*
> Input methods for international characters in X that rely on the XIM
Thanks.
--
Q: What kind of stuff do you do?
A: I collect hobbies.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Patch 7.4.193
Patch 7.4.193
Problem:Typos in messages.
Solution: "then" -> "than". (Dominique Pelle)
Files: src/if_py_both.h, src/spell.c
*** ../vim-7.4.192/src/if_py_both.h 2014-02-15 15:58:55.081904773 +0100
--- src/if_py_both.h2014-03-08 16:10:46.015459417 +0100
***
*** 236,242
if (*result <= 0)
{
PyErr_SET_STRING(PyExc_ValueError,
! N_("number must be greater then zero"));
return -1;
}
}
--- 236,242
if (*result <= 0)
{
PyErr_SET_STRING(PyExc_ValueError,
! N_("number must be greater than zero"));
return -1;
}
}
***
*** 2405,2411
if ((item = PyIter_Next(iterator)))
{
PyErr_FORMAT(PyExc_ValueError,
! N_("attempt to assign sequence of size greater then %d "
"to extended slice"), 0);
Py_DECREF(item);
ret = -1;
--- 2405,2411
if ((item = PyIter_Next(iterator)))
{
PyErr_FORMAT(PyExc_ValueError,
! N_("attempt to assign sequence of size greater than %d "
"to extended slice"), 0);
Py_DECREF(item);
ret = -1;
***
*** 2510,2516
{
Py_DECREF(iterator);
PyErr_FORMAT(PyExc_ValueError,
! N_("attempt to assign sequence of size greater then %d "
"to extended slice"), (int) slicelen);
list_restore(numadded, numreplaced, slicelen, l, lis, lastaddedli);
PyMem_Free(lis);
--- 2510,2516
{
Py_DECREF(iterator);
PyErr_FORMAT(PyExc_ValueError,
! N_("attempt to assign sequence of size greater than %d "
"to extended slice"), (int) slicelen);
list_restore(numadded, numreplaced, slicelen, l, lis, lastaddedli);
PyMem_Free(lis);
*** ../vim-7.4.192/src/spell.c 2014-02-23 22:52:33.372764715 +0100
--- src/spell.c 2014-03-08 16:10:46.019459417 +0100
***
*** 12037,12043
/* Normal byte, go one level deeper. If it's not equal to the
* byte in the bad word adjust the score. But don't even try
* when the byte was already changed. And don't try when we
!* just deleted this byte, accepting it is always cheaper then
* delete + substitute. */
if (c == fword[sp->ts_fidx]
#ifdef FEAT_MBYTE
--- 12037,12043
/* Normal byte, go one level deeper. If it's not equal to the
* byte in the bad word adjust the score. But don't even try
* when the byte was already changed. And don't try when we
!* just deleted this byte, accepting it is always cheaper than
* delete + substitute. */
if (c == fword[sp->ts_fidx]
#ifdef FEAT_MBYTE
*** ../vim-7.4.192/src/version.c2014-02-24 03:31:55.816738026 +0100
--- src/version.c 2014-03-08 16:11:51.591460422 +0100
***
*** 740,741
--- 740,743
{ /* Add new patch number below this line */
+ /**/
+ 193,
/**/
--
BEDEVERE: How do you know so much about swallows?
ARTHUR: Well you have to know these things when you're a king, you know.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
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 you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [patch] doc/gui_x11.txt: replace broken URL
Cade Foster wrote: > Site www.yzis.org no more exists. > Replace on https://github.com/chrizel/Yzis Thanks. -- SIGFUN -- signature too funny (core dumped) /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [patch] fixed a few typos in Python messages mostly
Dominique wrote: > Attached patch fixed a few typos in Python messages mostly. Ironically one is in spell.c :-). Thanks! -- BRIDGEKEEPER: What is the air-speed velocity of an unladen swallow? ARTHUR: What do you mean? An African or European swallow? BRIDGEKEEPER: Er ... I don't know that ... Arrggghhh! BRIDGEKEEPER is cast into the gorge. "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [patch] UTF-8: mapping a multi-byte key where the second byte is 0x80 doesn't appear
Condition is good now.
I came back to take the respoisibility.
To study the Vim script a little bit.
I submit the patch and test.
I weaken the power of my shoulders.
Hello again.
Nobuhiro Takasaki
--
--
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 you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff -r 10d35c8b50e3 src/getchar.c
--- a/src/getchar.c Mon Feb 24 03:32:00 2014 +0100
+++ b/src/getchar.c Sat Mar 08 20:34:04 2014 +0900
@@ -2207,9 +2207,13 @@
/* Don't allow mapping the first byte(s) of a
* multi-byte char. Happens when mapping
* and then changing 'encoding'. */
-if (has_mbyte && MB_BYTE2LEN(c1)
- > (*mb_ptr2len)(mp->m_keys))
-mlen = 0;
+{
+char_u *p1 = mp->m_keys;
+char_u *p2 = mb_unescape(&p1);
+if (has_mbyte && p2 != NULL &&
+ MB_BYTE2LEN(c1) > MB_PTR2LEN(p2))
+mlen = 0;
+}
#endif
/*
* Check an entry whether it matches.
test106.in
Description: Binary data
test106.ok
Description: Binary data
Re: Incorrect expansion of %? (with patch)
Gary Johnson wrote: > On 2014-03-04, Gary Johnson wrote: > > On 2014-03-04, Christian Brabandt wrote: > > > Am 2014-03-04 08:15, schrieb Gary Johnson: > > > >There is a difference between the expansion of % and Ctrl-R % on the > > > >command line. > > > > > > > >I use Dropbox to keep a number of my configuration files, including > > > >my ~/.vim directory, synchronized between various machines running > > > >Linux and Windows. > > > > > > > >Today I discovered this file in the ~/Dropbox/vimfiles of a machine > > > >named toucan which is running Fedora 14: > > > > > > > >filetype (toucan's conflicted copy 2014-03-01).vim > > > > > > > >Using a GUI file manager, I opened this file with gvim. I made some > > > >changes to it, then tried comparing the changed buffer with the > > > >copy on disk with this command which I have used for years: > > > > > > > >:w !diff "%" - > > > > > > > >The result surprised me. > > > > > > > >diff: Dropbox/vimfiles/filetype \(toucan's conflicted copy > > > >2014-03-01\).vim: No such file or directory > > > > > > That indeed looks wrong. Interestingly, it seems to work for me, when > > > escaping the quote, like this: > > > > > > :w !cmd \"%\" - > > > > > > (note sure, why this works). > > > > > > For the most recent versions, I think :w !cmd %:S - should also work. > > > > I observed the problem on Linux, not Windows, so cmd is not > > involved. Vim's expansion of % may differ between Linux and > > Windows. > > Attached is a patch that fixes this on Linux. > > I think the original code was a well-intentioned but incorrect > attempt to quote characters in the expansion of % that are special > to the shell. The problem is that the quoting is inconsistent. If > one is going to quote a file name so that % expands usefully in a > shell command such as > > :!cat % > > then all characters special to the shell must be quoted. The > current Vim code quotes the characters "!&;()<>" but not space. > Consequently, any spaces in the file name are seen by the shell as > separators. > > If one attempts to fix the space problem by quoting the file name as > > :!cat "%" > > and the file name contains any of the characters "!&;()<>", then the > backslashes used by Vim to quote those characters appear to the > shell as literal backslashes. > > Since users are used to placing file names that may contain special > characters withing quotes, I think it would be least confusing for > Vim not to try to help with additional quoting. Therefore this > patch removes this extra quoting. This also preserves the current > behavior in the most common case of file names containing spaces. > It is much less common for file names to include any of "!&;()<>", > and with this bug, there is no way for the user to use % in a shell > command if % expands to a name containing any of those characters > and a space. > > The patch is based on Vim 7.4.135. Thanks. Yeah, it should either escape the spaces as well, so that % can be used without the quotes, or escape nothing, so that "%" works. Doesn't $ need escaping even inside ""? But not inside ''. Hmm, perhaps instead of a quick fix we can think of how to do this properly? -- BRIDGEKEEPER: What is your favorite colour? LAUNCELOT:Blue. BRIDGEKEEPER: Right. Off you go. "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Can't open file with gf/gF for grep result on windows.
Yasuhiro Matsumoto wrote: > Try below: > > C:\temp>grep Matsumoto c:/vim/src/*.c > list > C:\temp>vim list > > And you can see: > > c:/vim/src/gui_w48.c:1228: * forcedly redrawn. (Yasuhiro Matsumoto) */ > c:/vim/src/gui_w48.c:1925: /* added for non-MS IME (Yasuhiro Matsumoto) */ > > Then, type gf or gF on left side at first line. As you know, isfname contains > ":" on windows. So vim occur "E447: Can't find file ...". > (NOTE: don't say "you can do it with :cfile", this is a problem about gf/gF) > > This is not useful. I wrote a patch for this problem. > > https://gist.github.com/mattn/9388140 > > I tested below: > > http://www.google.com/ => HTML content(OK) > http:/ssdfsdf => E447 Can't find file "http:/ssdfsdf" (OK) > http:/ssdfsdf/ => E447 Can't find file "http:/ssdfsdf/" (OK) > p:/ssdfsdf => E447 Can't find file "p:/ssdfsdf" (OK) > p:/ssdfsdf/ => E447 Can't find file "p:/ssdfsdf/" (OK) > _:/ssdfsdf/ => E447 Can't find file "_:/ssdfsdf/" (OK) > _:ssdfsdf/ => E447 Can't find file "_:ssdfsdf/" (OK) > :ssdfsdf/ => E447 Can't find file ":ssdfsdf/" (OK) > c:/vim/src/gui_w48.c:1228: => Open the file(OK) > c:/vim/src/gui_w48.c:1925: => Open the file(OK) > ../../../vim/src/gui_w48.c:1925: => Open the file(OK) > :::foo::: => E447 Can't find file ":::foo:::" (OK) I have also been wondering if we can make "gf" a bit more clever. I sometimes end up copying a path because its end is not clear. The way you detect a ":" terminating the name looks a bit too simple. How about file://c:/path ? It would be good to add a comment to explain what it's doing at least. A crude but effective solution would be to first take the longest path, see if it exists. If not, then try removing a part at the end and try again. This would require a list of "optional file name characters". We should not have more than two or three tries to avoid this taking a long time (it's disk operations, and $PATH can contain many directories). - Bram -- To the optimist, the glass is half full. To the pessimist, the glass is half empty. To the engineer, the glass is twice as big as it needs to be. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: vim.org currently down
> At the moment there appears to be a problem with the vim.org domain. > I do not know how long it will take to fix this. > > For the time being: > - For the website use: http://vim.sourceforge.net > - For the maillists use the @googlegroups.com addresses. > Note that this uses an underscore: vim_dev instead of vim-dev. Aand we're back! Thanks to Sec for fixing it. Keep those alternatives in mind in case it ever happens again. -- Sorry, no fortune today. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
vim.org currently down
At the moment there appears to be a problem with the vim.org domain. I do not know how long it will take to fix this. For the time being: - For the website use: http://vim.sourceforge.net - For the maillists use the @googlegroups.com addresses. Note that this uses an underscore: vim_dev instead of vim-dev. -- BEDEVERE: Look! It's the old man from scene 24 - what's he Doing here? ARTHUR: He is the keeper of the Bridge. He asks each traveler five questions ... GALAHAD: Three questions. "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- 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 you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [patch] doc/gui.txt: small complements
Thanks, Manny. I fix that
--
--
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 you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
diff -r 10d35c8b50e3 runtime/doc/gui.txt
--- a/runtime/doc/gui.txt Mon Feb 24 03:32:00 2014 +0100
+++ b/runtime/doc/gui.txt Sat Mar 08 17:31:23 2014 +0700
@@ -133,6 +133,7 @@
:winp[os]
Display current position of the top left corner of the GUI vim
window in pixels. Does not work in all versions.
+Also see |getwinposx()| and |getwinposy()|.
:winp[os] {X} {Y} *E466*
Put the GUI vim window at the given {X} and {Y} coordinates.
@@ -151,8 +152,12 @@
option.
If you are running the X Window System, you can get information about the
-window Vim is running in with this command: >
+window Vim is running in with these commands: >
:!xwininfo -id $WINDOWID
+ :!xprop -id $WINDOWID
+< or >
+ :execute '!xwininfo -id ' . v:windowid
+ :execute '!xprop -id ' . v:windowid
<
*gui-IME* *iBus*
Input methods for international characters in X that rely on the XIM
