Re: Netrw doesn't work on Windows correctly. Please permit us to modify code on github.com

[mattn]

On Wednesday, November 9, 2016 at 3:58:03 AM UTC+9, DrChip wrote:
> Cesar Romani wrote:

> Netrw actually doesn't check that expand("$COMSPEC") is execuable before
> setting up g:netrw_localcopycmd; instead, it uses that if netrw reports
> has("win32") || has("win95") || has("win64") || has("win16") is true and
> that g:netrw_cygwin is false.
> 
> So, what should one use instead of expand("$COMSPEC"), and how do I
> detect that condition?  The expand("$COMSPEC") stuff used to work, so
> presumably Windows has changed things (and I'm primarily a Linux user).
> 
> Alternatively, one may provide substitutes for the various commands: 
> (ie. the command to be run as a string)
> 
>   g:netrw_localcopycmd
>   g:netrw_localcopydircmd
>   g:netrw_localmkdir
>   g:netrw_localmovecmd
>   g:netrw_localrmdir
>  
> Please let me know what those commands are.

Not different from autoload/netrw.vim is defined for. Problem is a checking 
with executable().

BTW, I want to hear the answer from you about permiting to modify your codes to 
us.

I'm thinking that current development speed is so wrong. This is NOT only 
things about netrw. Many authors of third-party plugin/files are already 
spoiled to keep development. And they doesn't know how many problems is 
remaining on vim8.
Dr Chip, for example, have you seen this?

https://github.com/vim/vim/issues?utf8=%E2%9C%93=is%3Aissue%20is%3Aopen%20netrw

Maybe, the problems occuring on users are not same that you know. I'm guessing 
that this is a reason that netvim is started. We can implement timer APIs, We 
can implement job APIs, We can implment channel APIs. But that was slowly to 
start.

We need contribute from users. And I'm thinking that we should be possible to 
modify bundled files directly. If those are personaly plugin isolated from vim, 
it won't be a problem. But those are bundled as vim runtime files. So I hope 
that vim-dev should manage latest version. My opinion may not be a correct 
answer for this problem. So if you have opinion about this, please let me known.

I'm very sorry to trouble you about my rude, but waiting your answer.

Thanks.
- mattn

-- 
-- 
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] Updated French tutorial

[Dominique Pellé]

Hi

Attached patch updates the French Vim tutorial.

Regards
Dominique

-- 
-- 
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 --git a/runtime/tutor/tutor.fr b/runtime/tutor/tutor.fr
index e5a6c45..ef2d847 100644
--- a/runtime/tutor/tutor.fr
+++ b/runtime/tutor/tutor.fr
@@ -61,8 +61,8 @@ NOTE : Les touches fl
  Ceci quitte l'éditeur SANS enregistrer les changements que vous avez
  faits.
 
-  3. Lorsque l'invite du shell vous sera présentée, tapez la commande qui
- vous a mené dans ce tutoriel. Cela pourrait être :vimtutor 
+  3. Revenez ici en tapant la commande qui vous a mené à ce tutoriel.
+ Cela pourrait être :vimtutor 
 
   4. Si vous avez mémorisé ces étapes et êtes confiant, effectuez les étapes
  1 à 3 pour sortir puis rentrer dans l'éditeur.
@@ -154,7 +154,7 @@ NOTE : En avan
 !! NOTE : Lisez toute la leçon avant d'exécuter les instructions ci-dessous !!
 
   1. Sortez de ce tutoriel comme vous l'avez fait dans la Leçon 1.2 :  :q!
- Ou, si vous avez accès à un autre terminal, exécutez y les actions
+ Ou, si vous avez accès à un autre terminal, exécutez-y les actions
  qui suivent.
 
   2. À l'invite du shell, tapez cette commande :  vim tutor 
@@ -704,7 +704,7 @@ NOTE : Si vous quittez Vim et le red
   3. Appuyez  :  . En bas de l'écran  :'<,'> va apparaître.
 
   4. Tapez   w TEST  , où TEST est un nom de fichier qui n'existe pas.
- Vérifiez que vous voyez  :'<,'>w TEST  avant de d'appuyer sur .
+ Vérifiez que vous voyez  :'<,'>w TEST  avant d'appuyer sur .
 
   5. Vim va enregistrer les lignes sélectionnées dans le fichier TEST.
  Utilisez  :!dir  ou  :!ls pour le voir. Ne l'effacez pas encore !
@@ -1034,5 +1034,5 @@ NOTE : Le compl
   Dernières mises à jour par Dominique Pellé.
 
   E-mail :  dominique.pe...@gmail.com
-  Last Change : 2016 Jul 02
+  Last Change : 2016 Nov 08
 ~~
diff --git a/runtime/tutor/tutor.fr.utf-8 b/runtime/tutor/tutor.fr.utf-8
index 9c44db1..4e42fd3 100644
--- a/runtime/tutor/tutor.fr.utf-8
+++ b/runtime/tutor/tutor.fr.utf-8
@@ -61,8 +61,8 @@ NOTE : Les touches fléchées devraient également fonctionner. Mais en utilisan
  Ceci quitte l'éditeur SANS enregistrer les changements que vous avez
  faits.
 
-  3. Lorsque l'invite du shell vous sera présentée, tapez la commande qui
- vous a mené dans ce tutoriel. Cela pourrait être :vimtutor 
+  3. Revenez ici en tapant la commande qui vous a mené à ce tutoriel.
+ Cela pourrait être :vimtutor 
 
   4. Si vous avez mémorisé ces étapes et êtes confiant, effectuez les étapes
  1 à 3 pour sortir puis rentrer dans l'éditeur.
@@ -154,7 +154,7 @@ NOTE : En avançant dans ce cours, n'essayez pas de mémoriser, apprenez par
 !! NOTE : Lisez toute la leçon avant d'exécuter les instructions ci-dessous !!
 
   1. Sortez de ce tutoriel comme vous l'avez fait dans la Leçon 1.2 :  :q!
- Ou, si vous avez accès à un autre terminal, exécutez y les actions
+ Ou, si vous avez accès à un autre terminal, exécutez-y les actions
  qui suivent.
 
   2. À l'invite du shell, tapez cette commande :  vim tutor 
@@ -704,7 +704,7 @@ NOTE : Si vous quittez Vim et le redémarrez de nouveau avec le fichier TEST,
   3. Appuyez  :  . En bas de l'écran  :'<,'> va apparaître.
 
   4. Tapez   w TEST  , où TEST est un nom de fichier qui n'existe pas.
- Vérifiez que vous voyez  :'<,'>w TEST  avant de d'appuyer sur .
+ Vérifiez que vous voyez  :'<,'>w TEST  avant d'appuyer sur .
 
   5. Vim va enregistrer les lignes sélectionnées dans le fichier TEST.
  Utilisez  :!dir  ou  :!ls pour le voir. Ne l'effacez pas encore !
@@ -1034,5 +1034,5 @@ NOTE : Le complètement fonctionne pour de nombreuses commandes. Essayez
   Dernières mises à jour par Dominique Pellé.
 
   E-mail :  dominique.pe...@gmail.com
-  Last Change : 2016 Jul 02
+  Last Change : 2016 Nov 08
 ~~

Re: [vim/vim] Popup menu does not default to below the cursor (#1241)

[h_east]

Hi Matt and list,

2016-11-9(Wed) 1:29:38 UTC+9 Matt Gardner:
> For comparison, here are the same screenshots using the commit just prior to 
> that patch:

Oh, sorry.
I wrote a patch that respects the original behavior.
Please confirming this.

Thanks for the reporting and suggestions!
--
Best regards,
Hirohito Higashi (a.k.a. h_east)

-- 
-- 
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 --git a/src/popupmnu.c b/src/popupmnu.c
index 19d215b..307dbbe 100644
--- a/src/popupmnu.c
+++ b/src/popupmnu.c
@@ -105,7 +105,8 @@ redo:
 
 /* Put the pum below "row" if possible.  If there are few lines decide on
  * where there is more room. */
-if (row - above_row >= below_row - row)
+if (row + 2 >= below_row - pum_height
+			&& row - above_row > (below_row - above_row) / 2)
 {
 	/* pum above "row" */
 

Re: Netrw doesn't work on Windows correctly. Please permit us to modify code on github.com

[Charles E Campbell]

Cesar Romani wrote:
> On 08/11/2016 04:08 a.m., mattn wrote:
> > Hi, Dr. Chip and list.
> >
> > I met some problems on netrw on Windows for  a long time. Most of
> > operations which use Windows commands of cmd.exe doesn't work because
> > netrw checks the command exists by executable(). The commands are
> > defined like:
> >
> > let g:netrw_localcopycmd= expand("$COMSPEC")." /c copy"
> >
> > So executable() always return 0 on Windows.
> >
> > And I met more bugs about netrw.
> >
> > * mz (decompress) doesn't work
> > * documentation bug about ms
> >
> > I'm sorry but I say netrw is often buggy. But I want to fix them. So I
> > hope you that put the code of netrw on github or somewhere. And please
> > permit us to modify the code of netrw for vim-dev or vim-jp.
>
> I can confirm it. It would be fine to fix netrw for Windows.
Netrw actually doesn't check that expand("$COMSPEC") is execuable before
setting up g:netrw_localcopycmd; instead, it uses that if netrw reports
has("win32") || has("win95") || has("win64") || has("win16") is true and
that g:netrw_cygwin is false.

So, what should one use instead of expand("$COMSPEC"), and how do I
detect that condition?  The expand("$COMSPEC") stuff used to work, so
presumably Windows has changed things (and I'm primarily a Linux user).

Alternatively, one may provide substitutes for the various commands: 
(ie. the command to be run as a string)

  g:netrw_localcopycmd
  g:netrw_localcopydircmd
  g:netrw_localmkdir
  g:netrw_localmovecmd
  g:netrw_localrmdir
 
Please let me know what those commands are.

Regards,
Chip Campbell

-- 
-- 
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: Usage of libiconv-2.dll (64-bit) results in false detection of file encoding

[Axel Bender]

Hi Ken,

thanks for looking into this. Changing the order helps, but now KOI8-R texts 
are displayed as Latin-1 (=> visual garbage). Obviously there's no general 
solution to this...

I've resorted to defining some commands that will read/re-read a/the file with 
a specified encoding set (via "++enc").

Your help was much appreciated.

-- 
-- 
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: Netrw doesn't work on Windows correctly. Please permit us to modify code on github.com

[Cesar Romani]

On 08/11/2016 04:08 a.m., mattn wrote:
> Hi, Dr. Chip and list.
>
> I met some problems on netrw on Windows for  a long time. Most of
> operations which use Windows commands of cmd.exe doesn't work because
> netrw checks the command exists by executable(). The commands are
> defined like:
>
> let g:netrw_localcopycmd= expand("$COMSPEC")." /c copy"
>
> So executable() always return 0 on Windows.
>
> And I met more bugs about netrw.
>
> * mz (decompress) doesn't work
> * documentation bug about ms
>
> I'm sorry but I say netrw is often buggy. But I want to fix them. So I
> hope you that put the code of netrw on github or somewhere. And please
> permit us to modify the code of netrw for vim-dev or vim-jp.

I can confirm it. It would be fine to fix netrw for Windows.

Best regards,

--
Cesar

--
--
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: Usage of libiconv-2.dll (64-bit) results in false detection of file encoding

[Ken Takata]

Hi,

2016/11/8 Tue 18:25:55 UTC+9 Axel Bender wrote:
> Hi Ken,
> 
> thanks for replying. As of your questions:
> 
> a) I can verify (procmon) that libicon-2.dll (64-bit) is loaded when 
> d:\gnu\mingw64 is in %PATH%.
> 
> b) has('iconv') prints "1" in that case.
> 
> When I remove d:\gnu\mingw64 from %PATH% (or change it to d:\gnu\mingw32), 
> has('iconv') shows "0", and the file's type is correctly identified ("latin1" 
> instead of "koi8-r").

Okay, understand.
This is because Vim cannot handle koi8-r when iconv is disabled. If 64-bit
libiconv-2.dll is not available in %PATH%, koi8-r might not be opened.
If libiconv-2.dll is available, Vim can handle koi8-r and Vim cannot
distinguish latin-1 from koi8-r, because the range of koi8-r code points
is wider than that of latin-1. 
So how about changing the order of fencs?
E.g.: set fileencodings=ucs-bom,utf-8,latin1,koi8-r

Regards,
Ken Takata

-- 
-- 
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: Usage of libiconv-2.dll (64-bit) results in false detection of file encoding

[Axel Bender]

Hi Ken,

thanks for replying. As of your questions:

a) I can verify (procmon) that libicon-2.dll (64-bit) is loaded when 
d:\gnu\mingw64 is in %PATH%.

b) has('iconv') prints "1" in that case.

When I remove d:\gnu\mingw64 from %PATH% (or change it to d:\gnu\mingw32), 
has('iconv') shows "0", and the file's type is correctly identified ("latin1" 
instead of "koi8-r").

-- 
-- 
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.

Netrw doesn't work on Windows correctly. Please permit us to modify code on github.com

[mattn]

Hi, Dr. Chip and list.

I met some problems on netrw on Windows for  a long time. Most of operations 
which use Windows commands of cmd.exe doesn't work because netrw checks the 
command exists by executable(). The commands are defined like:

let g:netrw_localcopycmd= expand("$COMSPEC")." /c copy"

So executable() always return 0 on Windows.

And I met more bugs about netrw.

* mz (decompress) doesn't work
* documentation bug about ms

I'm sorry but I say netrw is often buggy. But I want to fix them. So I hope you 
that put the code of netrw on github or somewhere. And please permit us to 
modify the code of netrw for vim-dev or vim-jp.

Best Regards.

Thanks.

- mattn

-- 
-- 
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.