Re: [vim/vim] propose vim as manpager that syntax highlights and follows symlinks (#491)

2016-04-28 Fir de Conversatie Charles E Campbell
Murukesh Mohanan wrote:
>
> Typically man pages have bold and underlines displayed using |x\bx|
> and |_\bx|, |\b| being the backspace and |x| the letter in question
> (Thomas Dickey talks about this in this Unix & Linux post
> ). That's what makes
> using just |vim -| as the manpager annoying. The workaround I have
> seen posted in a number of places is to filter out the backspaces, and
> the characters that would have been printed over. Typically:
>
> |MANPAGER='col -b | vim -' |
>
> There's no reason to do this with |col -b|, of course. You could do
> something like:
>
> if !empty($MAN_PN)
> autocmd StdinReadPost * set ft=man | file $MAN_PN | call PrepManPager()
> endif
>
> And |PrepManPager()| defined in some suitable place:
>
> function! PrepManPager()
> setlocal modifiable
> %s/.\b\(.\)/\1/g
> 1
> setlocal nomodified
> setlocal nomodifiable
> endfunction
> 
>
> Aside:
>
> In the Unix & Linux post mentioned above, I'd posted my method, which
> involves keeping the backspaces and concealing them, instead of
> removing them. Personally, I feel the loss of functionality in
> searching is balanced by the added syntax highlighting I can do with
> the backspaces retained. There are manpages for which the standard
> |syntax/man.vim| is useless, because it has no way to know what the
> actual page would have highlighted. (Pick any C++ STL manpage, for
> example.) If anyone's interested, here's how I use conceal for this
> .
>
>
Have you tried ManPageView?  I use the kornshell, but it should work
with bash also:

# man: {{{2
function man
{
gv -c "Man $*" -c "sil! only"
}

then   man printf  brings up ManPageView in vim.  (you can get
ManPageView from
http://www.drchip.org/astronaut/vim/index.html#MANPAGEVIEW).

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.


Patch 7.4.1797

2016-04-28 Fir de Conversatie Bram Moolenaar

Patch 7.4.1797
Problem:Warning from Windows 64 bit compiler.
Solution:   Change int to size_t. (Mike Williams)
Files:  src/term.c


*** ../vim-7.4.1796/src/term.c  2016-04-27 20:36:27.456988992 +0200
--- src/term.c  2016-04-28 22:18:38.975560577 +0200
***
*** 6174,6180 
  
  while (!feof(fd))
  {
!   int len;
int pos;
  
(void)fgets(line, LINE_LEN, fd);
--- 6174,6180 
  
  while (!feof(fd))
  {
!   size_t  len;
int pos;
  
(void)fgets(line, LINE_LEN, fd);
*** ../vim-7.4.1796/src/version.c   2016-04-27 20:36:27.460988946 +0200
--- src/version.c   2016-04-28 22:19:17.151112566 +0200
***
*** 755,756 
--- 755,758 
  {   /* Add new patch number below this line */
+ /**/
+ 1797,
  /**/

-- 
ARTHUR:  What does it say?
BROTHER MAYNARD: It reads ... "Here may be found the last words of Joseph of
 Aramathea." "He who is valorous and pure of heart may find
 the Holy Grail in the arrggghhh..."
ARTHUR:  What?
BROTHER MAYNARD: "The Arrggghhh..."
 "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: [vim/vim] propose vim as manpager that syntax highlights and follows symlinks (#491)

2016-04-28 Fir de Conversatie toothpik
On Thu, Apr 28, 2016 at 02:25:36AM -0700, Konfekt wrote:

> Thanks a bunch ! Exactly, the definition of MAN_PN is the weak point.
> So after updating instructions for other shells, apparemment BSD is
> unsupported. Could you explain tha ol trick about the removal of
> backspaces that yet works around it? 

I've got a function defined in my .bashrc as follows:

vman() { man "$@" 2>&1 | col -bx | iconv -c | vim -c 'set ft=man nomod nolist 
nonu nornu' -c 'call Hideme()' -; }

(the above was sent as all one line)

it's the 'col -bx' that removes backspaces -- Hideme is a function in
my .vimrc as follows:

function! Hideme()
setlocal noswapfile
setlocal buftype=nofile
setlocal bufhidden=hide
endfunction

-- 
-- 
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: How to run a job asynchronously?

2016-04-28 Fir de Conversatie boss
On Wednesday, 27 April 2016 11:44:48 UTC+1, Andrew Stewart  wrote:
> I also implemented my job_start using an out_cb handler again instead of a 
> close_cb handler.  The occasional-missing-callback problem has disappeared 
> and it all worked perfectly.  Thanks!

I know this isn't the place for MacVim-specific discussion, but as it's related 
I thought it worth mentioning that MacVim never starts looking for messages on 
channels:

https://github.com/macvim-dev/macvim/issues/272

-- 
-- 
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] 'guicolors' option name does not intuitive.

2016-04-28 Fir de Conversatie Bram Moolenaar

Hirohito Higashi wrote:

> Hi Bram and list,
> 
> 2016-4-27(Wed) 15:57:38 UTC+9 h_east:
> > Hi Bram, Ken and list,
> > 
> > 2016-4-25(Mon) 19:04:59 UTC+9 h_east:
> > > Hi Ken!
> > > 
> > > 2016-4-25(Mon) 18:58:05 UTC+9 Ken Takata:
> > > > Hi h_east,
> > > > 
> > > > 2016/4/25 Mon 6:51:36 UTC+9 h_east wrote:
> > > > > Hi Bram and List!
> > > > > 
> > > > > 2016-4-25(Mon) 5:03:24 UTC+9 Bram Moolenaar:
> > > > > > Hirohito Higashi wrote:
> > > > > > 
> > > > > > > I think that 'guicolors' option name does not intuitive.
> > > > > > > This option for terminal, but prefix is 'gui'
> > > > > > > I think it's unnatural.
> > > > > > > 
> > > > > > > I propose to rename option name to 'termtruecolor'.  (Short name 
> > > > > > > is 'ttc')
> > > > > > > How about this?
> > > > > > > 
> > > > > > > NOTE:
> > > > > > >   This has been first proposed by Ken Takada.
> > > > > > > 
> > > > > > > Patch attached.
> > > > > > > Please check this.
> > > > > > 
> > > > > > Yes, I was wondering what users think of when seeing 'guicolors'.  
> > > > > > The
> > > > > > main thing it does is using the GUI colors for the terminal.  
> > > > > > Whether
> > > > > > it's actually true colors depends on the terminal.
> > > > > > 
> > > > > > So, how about 'termguicolors'?
> > > > > > 
> > > > > > Ah, I see Nikolai also suggested this.
> > > > > 
> > > > > Yes, patch update.
> > > > > 
> > > > >   guicolors --> termguicolors
> > > > >   gcol --> tgc
> > > > >   termtruecolor --> termguicolors
> > > > >   FEAT_TERMTRUECOLOR --> FEAT_TERMGUICOLORS
> > > > 
> > > > I think it's also better to change function names.
> > > 
> > > Nice catch! Thanks.
> > 
> > I update a patch.
> > - Ready for 7.4.1795
> > - Merge Ken's patch
> >   https://groups.google.com/d/msg/vim_dev/q2LuLFueRbE/b848hy1jAgAJ
> > 
> > Please check this.
> 
> Patch update.
> Now ready to apply the patch to Vim 7.4.1796. :-)

Thanks!  I'll include it soon (but I'm quite busy...).

-- 
A hamburger walks into a bar, and the bartender says: "I'm sorry,
but we don't serve food here."

 /// 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] 'guicolors' option name does not intuitive.

2016-04-28 Fir de Conversatie h_east
Hi Bram and list,

2016-4-27(Wed) 15:57:38 UTC+9 h_east:
> Hi Bram, Ken and list,
> 
> 2016-4-25(Mon) 19:04:59 UTC+9 h_east:
> > Hi Ken!
> > 
> > 2016-4-25(Mon) 18:58:05 UTC+9 Ken Takata:
> > > Hi h_east,
> > > 
> > > 2016/4/25 Mon 6:51:36 UTC+9 h_east wrote:
> > > > Hi Bram and List!
> > > > 
> > > > 2016-4-25(Mon) 5:03:24 UTC+9 Bram Moolenaar:
> > > > > Hirohito Higashi wrote:
> > > > > 
> > > > > > I think that 'guicolors' option name does not intuitive.
> > > > > > This option for terminal, but prefix is 'gui'
> > > > > > I think it's unnatural.
> > > > > > 
> > > > > > I propose to rename option name to 'termtruecolor'.  (Short name is 
> > > > > > 'ttc')
> > > > > > How about this?
> > > > > > 
> > > > > > NOTE:
> > > > > >   This has been first proposed by Ken Takada.
> > > > > > 
> > > > > > Patch attached.
> > > > > > Please check this.
> > > > > 
> > > > > Yes, I was wondering what users think of when seeing 'guicolors'.  The
> > > > > main thing it does is using the GUI colors for the terminal.  Whether
> > > > > it's actually true colors depends on the terminal.
> > > > > 
> > > > > So, how about 'termguicolors'?
> > > > > 
> > > > > Ah, I see Nikolai also suggested this.
> > > > 
> > > > Yes, patch update.
> > > > 
> > > >   guicolors --> termguicolors
> > > >   gcol --> tgc
> > > >   termtruecolor --> termguicolors
> > > >   FEAT_TERMTRUECOLOR --> FEAT_TERMGUICOLORS
> > > 
> > > I think it's also better to change function names.
> > 
> > Nice catch! Thanks.
> 
> I update a patch.
> - Ready for 7.4.1795
> - Merge Ken's patch
>   https://groups.google.com/d/msg/vim_dev/q2LuLFueRbE/b848hy1jAgAJ
> 
> Please check this.

Patch update.
Now ready to apply the patch to Vim 7.4.1796. :-)

--
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/runtime/doc/options.txt b/runtime/doc/options.txt
index 8310a68..e42116d 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -3477,18 +3477,6 @@ A jump table for the options with a short description can be found at |Q_op|.
 	This option cannot be set from a |modeline| or in the |sandbox|, for
 	security reasons.
 
-		*'guicolors'* *'gcol'*
-'guicolors' 'gcol'	boolean (default off)
-			global
-			{not in Vi}
-			{not available when compiled without the 
-			|+termtruecolor| feature}
-	When on, uses |highlight-guifg| and |highlight-guibg| attributes in 
-	the terminal (thus using 24-bit color). Requires a ISO-8613-3
-	compatible terminal.
-	If setting this option does not work (produces a colorless UI) 
-	reading |xterm-true-color| might help.
-
 			*'guicursor'* *'gcr'* *E545* *E546* *E548* *E549*
 'guicursor' 'gcr'	string	(default "n-v-c:block-Cursor/lCursor,
 	ve:ver35-Cursor,
@@ -7551,6 +7539,18 @@ A jump table for the options with a short description can be found at |Q_op|.
 		:set encoding=utf-8
 <	You need to do this when your system has no locale support for UTF-8.
 
+		*'termguicolors'* *'tgc'*
+'termguicolors' 'tgc'	boolean (default off)
+			global
+			{not in Vi}
+			{not available when compiled without the
+			|+termguicolors| feature}
+	When on, uses |highlight-guifg| and |highlight-guibg| attributes in
+	the terminal (thus using 24-bit color). Requires a ISO-8613-3
+	compatible terminal.
+	If setting this option does not work (produces a colorless UI)
+	reading |xterm-true-color| might help.
+
 		*'terse'* *'noterse'*
 'terse'			boolean	(default off)
 			global
diff --git a/runtime/doc/term.txt b/runtime/doc/term.txt
index 0ac5b41..69cf5f0 100644
--- a/runtime/doc/term.txt
+++ b/runtime/doc/term.txt
@@ -426,10 +426,10 @@ Vim has started, the escape sequences may not be recognized anymore.
 			*xterm-true-color*
 Vim supports using true colors in the terminal (taken from |highlight-guifg|
 and |highlight-guibg|), given that terminal supports this. To make this 
-work, 'guicolors' option needs to be set.
+work, 'termguicolors' option needs to be set.
 
-Sometimes setting 'guicolors' is not enough and one has to set the |t_8f| and
-|t_8b| options explicitly. Default values of these options are
+Sometimes setting 'termguicolors' is not enough and one has to set the |t_8f|
+and |t_8b| options explicitly. Default values of these options are
 `^[[38;2;%lu;%lu;%lum` and `^[[48;2;%lu;%lu;%lum` (replace `^[` with real
 escape) respectively, but it is only set when `$TERM` is `xterm`. Some
 terminals accept the same sequences, but with all semicolons replaced by
diff --git a/runtime/doc/various.txt b/runtime/doc/various.txt
index b73949f..8565a88