Rebbe Malachi: June 2013

Sunday, June 30, 2013

Don't fold C++ namespaces.

I've got foldmethod set to syntax. How can I tell vim not to fold C++ namespace blocks?

I was able to do it actually, by editing the cBlock sytanx region in the default c.vim syntax file like this:

syn region cBlock start="$namespace .* $\@<!{" end="}" transparent fold

But it just doesn't look right to do it like that, plus I'd like to have a "local" solution (i.e. one I can just put in my .vimrc or somewhere in .vim/).

Any ideas?

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: how do i remap dd so that it becomes context-dependent?

Check whether virtcol('$') is greater then winwidth(0): something like this:

nnoremap <expr> dd (virtcol('$') > winwidth(0)) ? 'g0dg$' : 'dd'

On Jun 30, 2013 10:32 PM, "leo" <barbosa.leonardo@gmail.com> wrote:
>
>
> Hello all,
>
> I'm using "set wrap". I'd like to come up with a remap of dd that would does the follwing:
> If the current line is wrapped, it then performs g0dg$
> Else, it performs the conventional dd.
>
> The problem is this. if i just use:
> vnoremap dd g0dg$
> nnoremap dd g0dg$
> whenever i have non wrapped lines, such as:
> a
> b
> c
> And I "dd" line two, it will end up with sth like:
> a
> (blank line)
> c
> Instead of this expecting result:
> a
> c
>
> Thanks in advance
>
>
>
> --
> --
> You received this message from the "vim_use" 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_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

how do i remap dd so that it becomes context-dependent?

Hello all,

I'm using "set wrap". I'd like to come up with a remap of dd that would does the follwing:
If the current line is wrapped, it then performs g0dg$
Else, it performs the conventional dd.

The problem is this. if i just use:
vnoremap dd g0dg$
nnoremap dd g0dg$
whenever i have non wrapped lines, such as:
a
b
c
And I "dd" line two, it will end up with sth like:
a
(blank line)
c
Instead of this expecting result:
a
c

Thanks in advance

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Friday, June 28, 2013

Re: Terminal escape sequence ^[[A

See terminfo / termcap also make sure you're using, exporting, and that the emulator knows what terminal it should be emulating. Another hint, the search path for terminfo (iirc) is: $TERMPATH, ~/.terminfo, /etc/terminfo, /usr/share/terminfo - if you don't have a compiled terminfo file with the right name in one of those places, don't try setting the terminal to the name as it won't work.

It might also help to subscribe to some Unix related lists (or one for cygwin or putty) or get on IRC. There's a technical reason for this - when I Google (or search my email) for info related to this subject, if I see a link or email related to vim in my search, I'm probably going to pass it by thinking the question was misplaced and the responses probably a waste of time. Ie, don't keep your questions on topic because the people reading that forum might not care about or be ignorant of the topic, but because, when you forget the answer and go to search for it again, it'll be way off here in this forum you'd never think to look for it.

On Jun 28, 2013 8:44 PM, "David Fishburn" <dfishburn.vim@gmail.com> wrote:

Sorry to ask this here, it is just a terminal question, unrelated to Vim. I don't subscribe to anything Linux related.

On most of my machines that I ssh into (usually from either a Cygwin Terminal or Putty) and I type a command and hit the up arrow, I get my command back.

When I launch a console application where I can type a command, think an Interactive SQL console application where I would type:
SELECT * FROM T1

Though 2 different servers I connect to which always show ^[[A instead of the previous command and I have to re-type my command.

Yet on other servers, the same program, the up arrow shows the previous command.

Most of my Google searches say TERM is responsible, but xterm and screen I assume are Ok. Other says to use bash, which I am.

Not really sure what to check for.

If I exit the application and hit the up arrow I get back my command which launched the program.

Anyway, I grab the ENV output hoping this might be enough for someone to give me suggestions.

One of the server is running SUSE Enterprise.

ENV in a Cygwin Terminal

TERM=xterm

SHELL=/bin/bash
HISTSIZE=1000
SSH_TTY=/dev/pts/1
LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:

EC2_HOME=/home/ec2
INPUTRC=/etc/inputrc
PWD=/home/dfishbur
JAVA_HOME=/usr/java/default
LANG=en_US.UTF-8
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass

SHLVL=1
HOME=/home/dfishbur
LOGNAME=dfishbur
CVS_RSH=ssh
LESSOPEN=|/usr/bin/lesspipe.sh %s
G_BROKEN_FILENAMES=1
_=/bin/env

ENV from within SCREEN

TERM=screen
SHELL=/bin/bash
HISTSIZE=1000
SSH_TTY=/dev/pts/3
USER=dfishbur
LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:

EC2_HOME=/home/ec2
TERMCAP=SC|screen|VT 100/ANSI X3.64 virtual terminal:\
:DO=\E[%dB:LE=\E[%dD:RI=\E[%dC:UP=\E[%dA:bs:bt=\E[Z:\
:cd=\E[J:ce=\E[K:cl=\E[H\E[J:cm=\E[%i%d;%dH:ct=\E[3g:\

:do=^J:nd=\E[C:pt:rc=\E8:rs=\Ec:sc=\E7:st=\EH:up=\EM:\
:le=^H:bl=^G:cr=^M:it#8:ho=\E[H:nw=\EE:ta=^I:is=\E)0:\
:li#60:co#146:am:xn:xv:LP:sr=\EM:al=\E[L:AL=\E[%dL:\
:cs=\E[%i%d;%dr:dl=\E[M:DL=\E[%dM:dc=\E[P:DC=\E[%dP:\
:im=\E[4h:ei=\E[4l:mi:IC=\E[%d@:ks=\E[?1h\E=:\
:ke=\E[?1l\E>:vi=\E[?25l:ve=\E[34h\E[?25h:vs=\E[34l:\
:ti=\E[?1049h:te=\E[?1049l:us=\E[4m:ue=\E[24m:so=\E[3m:\

:se=\E[23m:mb=\E[5m:md=\E[1m:mr=\E[7m:me=\E[m:ms:\
:Co#8:pa#64:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:AX:\
:vb=\Eg:G0:as=\E(0:ae=\E(B:\
:ac=\140\140aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~..--++,,hhII00:\

:po=\E[5i:pf=\E[4i:Z0=\E[?3h:Z1=\E[?3l:k0=\E[10~:\
:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:k5=\E[15~:k6=\E[17~:\
:k7=\E[18~:k8=\E[19~:k9=\E[20~:k;=\E[21~:F1=\E[23~:\
:F2=\E[24~:F3=\EO2P:F4=\EO2Q:F5=\EO2R:F6=\EO2S:\

:F7=\E[15;2~:F8=\E[17;2~:F9=\E[18;2~:FA=\E[19;2~:kb=:\
:K2=\EOE:kB=\E[Z:kF=\E[1;2B:kR=\E[1;2A:*4=\E[3;2~:\
:*7=\E[1;2F:#2=\E[1;2H:#3=\E[2;2~:#4=\E[1;2D:%c=\E[6;2~:\
:%e=\E[5;2~:%i=\E[1;2C:kh=\E[1~:@1=\E[1~:kH=\E[4~:\
:@7=\E[4~:kN=\E[6~:kP=\E[5~:kI=\E[2~:kD=\E[3~:ku=\EOA:\
:kd=\EOB:kr=\EOC:kl=\EOD:km:
STY=17204.pts-3.sapmdmsaaslabdb

INPUTRC=/etc/inputrc
PWD=/home/dfishbur
JAVA_HOME=/usr/java/default
LANG=en_US.UTF-8
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SHLVL=3
HOME=/home/dfishbur

LOGNAME=dfishbur
WINDOW=3
CVS_RSH=ssh
LESSOPEN=|/usr/bin/lesspipe.sh %s
G_BROKEN_FILENAMES=1
_=/bin/env

If you can suggest a good place to ask this and work with someone I am all ears.

Thanks,
David

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Terminal escape sequence ^[[A (followup)

On 2013-06-28 20:40, Tim Chase wrote:
> There are two possibilities that occur to me.

Okay, other possibilities occurred about 3sec after I hit <send>. I
don't know if you have either an /etc/inputrc or ~/.inputrc that is
interfering with your commands, but I know the readline libs check
those for settings, so you might try moving one or both of those out
of the way and testing again in order to get back to factory defaults.

Also, though you mention that one is running SUSE, if the other is
running some flavor of BSD, they tend to use editline rather than
readline which might introduce additional oddities.

-tim

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Terminal escape sequence ^[[A

On 2013-06-28 20:43, David Fishburn wrote:
> On most of my machines that I ssh into (usually from either a Cygwin
> Terminal or Putty) and I type a command and hit the up arrow, I get
> my command back.
>
> When I launch a console application where I can type a command,
> think an Interactive SQL console application where I would type:
> SELECT * FROM T1
>
> Though 2 different servers I connect to which always show ^[[A
> instead of the previous command and I have to re-type my command.

There are two possibilities that occur to me. One is that the arrow
keys aren't properly interpreted on the server-end; the other is that
the server-end doesn't have readline functionality (which is what
backs this functionality).

I'd start by issuing control+P to recall the previous command (a
synonym for <up> in most default shell configurations with history
recall). If it recalls successfully, then you have a shell with
readline support and need to chase down why your $TERM settings aren't
interpreting your arrow presses properly. If control+P doesn't bring
up the previous line, then it's likely that your shell doesn't have
readline support. You might check whether you're running a stripped
down shell, or you can launch an alternate shell. You might also try
opening Vim and seeing if Vim properly sees the arrow keys (which, if
it does, might confirm the shell-sans-readline situation)

Just a few shot-in-the-dark ideas,

-tim

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Terminal escape sequence ^[[A

Sorry to ask this here, it is just a terminal question, unrelated to Vim. I don't subscribe to anything Linux related.

On most of my machines that I ssh into (usually from either a Cygwin Terminal or Putty) and I type a command and hit the up arrow, I get my command back.

When I launch a console application where I can type a command, think an Interactive SQL console application where I would type:

SELECT * FROM T1

Though 2 different servers I connect to which always show ^[[A instead of the previous command and I have to re-type my command.

Yet on other servers, the same program, the up arrow shows the previous command.

Most of my Google searches say TERM is responsible, but xterm and screen I assume are Ok. Other says to use bash, which I am.

Not really sure what to check for.

If I exit the application and hit the up arrow I get back my command which launched the program.

Anyway, I grab the ENV output hoping this might be enough for someone to give me suggestions.

One of the server is running SUSE Enterprise.

ENV in a Cygwin Terminal

TERM=xterm

SHELL=/bin/bash

HISTSIZE=1000

SSH_TTY=/dev/pts/1

LS_COLORS=no=00:fi=00:di=00;34:ln=00;36:pi=40;33:so=00;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=00;32:*.cmd=00;32:*.exe=00;32:*.com=00;32:*.btm=00;32:*.bat=00;32:*.sh=00;32:*.csh=00;32:*.tar=00;31:*.tgz=00;31:*.arj=00;31:*.taz=00;31:*.lzh=00;31:*.zip=00;31:*.z=00;31:*.Z=00;31:*.gz=00;31:*.bz2=00;31:*.bz=00;31:*.tz=00;31:*.rpm=00;31:*.cpio=00;31:*.jpg=00;35:*.gif=00;35:*.bmp=00;35:*.xbm=00;35:*.xpm=00;35:*.png=00;35:*.tif=00;35:

EC2_HOME=/home/ec2

INPUTRC=/etc/inputrc

PWD=/home/dfishbur

JAVA_HOME=/usr/java/default

LANG=en_US.UTF-8

SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass

SHLVL=1

HOME=/home/dfishbur

LOGNAME=dfishbur

CVS_RSH=ssh

LESSOPEN=|/usr/bin/lesspipe.sh %s

G_BROKEN_FILENAMES=1

_=/bin/env

ENV from within SCREEN

TERM=screen

SHELL=/bin/bash

HISTSIZE=1000

SSH_TTY=/dev/pts/3

USER=dfishbur

LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:

EC2_HOME=/home/ec2

TERMCAP=SC|screen|VT 100/ANSI X3.64 virtual terminal:\

:DO=\E[%dB:LE=\E[%dD:RI=\E[%dC:UP=\E[%dA:bs:bt=\E[Z:\

:cd=\E[J:ce=\E[K:cl=\E[H\E[J:cm=\E[%i%d;%dH:ct=\E[3g:\

:do=^J:nd=\E[C:pt:rc=\E8:rs=\Ec:sc=\E7:st=\EH:up=\EM:\

:le=^H:bl=^G:cr=^M:it#8:ho=\E[H:nw=\EE:ta=^I:is=\E)0:\

:li#60:co#146:am:xn:xv:LP:sr=\EM:al=\E[L:AL=\E[%dL:\

:cs=\E[%i%d;%dr:dl=\E[M:DL=\E[%dM:dc=\E[P:DC=\E[%dP:\

:im=\E[4h:ei=\E[4l:mi:IC=\E[%d@:ks=\E[?1h\E=:\

:ke=\E[?1l\E>:vi=\E[?25l:ve=\E[34h\E[?25h:vs=\E[34l:\

:ti=\E[?1049h:te=\E[?1049l:us=\E[4m:ue=\E[24m:so=\E[3m:\

:se=\E[23m:mb=\E[5m:md=\E[1m:mr=\E[7m:me=\E[m:ms:\

:Co#8:pa#64:AF=\E[3%dm:AB=\E[4%dm:op=\E[39;49m:AX:\

:vb=\Eg:G0:as=\E(0:ae=\E(B:\

:ac=\140\140aaffggjjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~..--++,,hhII00:\

:po=\E[5i:pf=\E[4i:Z0=\E[?3h:Z1=\E[?3l:k0=\E[10~:\

:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:k5=\E[15~:k6=\E[17~:\

:k7=\E[18~:k8=\E[19~:k9=\E[20~:k;=\E[21~:F1=\E[23~:\

:F2=\E[24~:F3=\EO2P:F4=\EO2Q:F5=\EO2R:F6=\EO2S:\

:F7=\E[15;2~:F8=\E[17;2~:F9=\E[18;2~:FA=\E[19;2~:kb=:\

:K2=\EOE:kB=\E[Z:kF=\E[1;2B:kR=\E[1;2A:*4=\E[3;2~:\

:*7=\E[1;2F:#2=\E[1;2H:#3=\E[2;2~:#4=\E[1;2D:%c=\E[6;2~:\

:%e=\E[5;2~:%i=\E[1;2C:kh=\E[1~:@1=\E[1~:kH=\E[4~:\

:@7=\E[4~:kN=\E[6~:kP=\E[5~:kI=\E[2~:kD=\E[3~:ku=\EOA:\

:kd=\EOB:kr=\EOC:kl=\EOD:km:

STY=17204.pts-3.sapmdmsaaslabdb

INPUTRC=/etc/inputrc

PWD=/home/dfishbur

JAVA_HOME=/usr/java/default

LANG=en_US.UTF-8

SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass

SHLVL=3

HOME=/home/dfishbur

LOGNAME=dfishbur

WINDOW=3

CVS_RSH=ssh

LESSOPEN=|/usr/bin/lesspipe.sh %s

G_BROKEN_FILENAMES=1

_=/bin/env

If you can suggest a good place to ask this and work with someone I am all ears.

Thanks,

David

Re: Slow Syntax Highlighting with Latex

On Friday, June 28, 2013 9:47:18 AM UTC-5, Ben Fritz wrote:
> On Thursday, June 27, 2013 7:07:55 PM UTC-5, at wrote:
> > I am having problems with slow speeds when using syntax highlighting in GVim using the native latex syntax highlighting.
> >
>
> What version and patchlevel of Vim? Current work leading up to 7.4 release added and is making faster a NFA-type regex engine.

The version is from the Mint 13 repositories. Here is the info:

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 4 2012 04:22:36)
Included patches: 1-429

I will use Charles' code to disable various syntaxing features if necessary. However, I am still confused as to why syntax is so slow only on this one machine and not on my other machines which use the same version and are comparable or less powerful in terms of computing resources.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Slow Syntax Highlighting with Latex

On Thursday, June 27, 2013 7:07:55 PM UTC-5, at wrote:
> I am having problems with slow speeds when using syntax highlighting in GVim using the native latex syntax highlighting.
>

What version and patchlevel of Vim? Current work leading up to 7.4 release added and is making faster a NFA-type regex engine.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Slow Syntax Highlighting with Latex

at wrote:
> I am having problems with slow speeds when using syntax highlighting in GVim using the native latex syntax highlighting.
>
> By slow I mean the response time between keyboard and screen is lagged.
>
> I can confirm that it is due to syntax highlighting by turning off all highlighting--then the response time is quick as in other applications.
>
> I have read posts by others on this topic both in this group and elsewhere. Most suggest turning off cursor line (or column) highlighting. I do not have this on.
>
> The machine I have problems with is fairly new and fast. Moreover, I use the exact same Vim configuration files on two much slower machines and do not observe this problem with the same .tex files.
>
> Any other suggestions as to how I can fix this?
>
Hello!

With v79 of syntax/tex.vim (available at my website:
http://www.drchip.org/astronaut/vim/index.html#SYNTAX_TEX ), there's a
number of ways to speed up LaTeX highlighting. From the help (which
hasn't appeared at Merc yet, but Bram has accepted):

*tex-slow* *tex-sync*
Tex: Slow Syntax Highlighting? ~

If you have a slow computer, you may wish to reduce the values for >
:syn sync maxlines=200
:syn sync minlines=50
(especially the latter). If your computer is fast, you may wish to
increase them. This primarily affects synchronizing (i.e. just what
group,
if any, is the text at the top of the screen supposed to be in?).

Another cause of slow highlighting is due to syntax-driven folding; see
|tex-folding| for a way around this.

*g:tex_fast*

Finally, if syntax highlighting is still too slow, you may set >

:let g:tex_fast= ""

in your .vimrc. Used this way, the g:tex_fast variable causes the syntax
highlighting script to avoid defining any regions and associated
synchronization. The result will be much faster syntax highlighting; the
price: you will no longer have as much highlighting or any syntax-based
folding, and you will be missing syntax-based error checking.

You may decide that some syntax is acceptable; you may use the following
table
selectively to enable just some syntax highlighting: >

b : allow bold and italic syntax
c : allow texComment syntax
m : allow texMatcher syntax (ie. {...} and [...])
M : allow texMath syntax
p : allow parts, chapter, section, etc syntax
r : allow texRefZone syntax (nocite, bibliography, label, pageref,
eqref)
s : allow superscript/subscript regions
S : allow texStyle syntax
v : allow verbatim syntax
V : allow texNewEnv and texNewCmd syntax
<
As an example, let g:tex_fast= "M" will allow math-associated highlighting
but suppress all the other region-based syntax highlighting.

*tex-folding* *g:tex_fold_enabled*
Tex: Want Syntax Folding? ~

As of version 28 of <syntax/tex.vim>, syntax-based folding of parts,
chapters,
sections, subsections, etc are supported. Put >
let g:tex_fold_enabled=1
in your <.vimrc>, and :set fdm=syntax. I suggest doing the latter via a
modeline at the end of your LaTeX file: >
% vim: fdm=syntax
If your system becomes too slow, then you might wish to look into >
https://vimhelp.appspot.com/vim_faq.txt.html#faq-29.7

Regards,
C Campbell

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Thursday, June 27, 2013

Slow Syntax Highlighting with Latex

I am having problems with slow speeds when using syntax highlighting in GVim using the native latex syntax highlighting.

By slow I mean the response time between keyboard and screen is lagged.

I can confirm that it is due to syntax highlighting by turning off all highlighting--then the response time is quick as in other applications.

I have read posts by others on this topic both in this group and elsewhere. Most suggest turning off cursor line (or column) highlighting. I do not have this on.

The machine I have problems with is fairly new and fast. Moreover, I use the exact same Vim configuration files on two much slower machines and do not observe this problem with the same .tex files.

Any other suggestions as to how I can fix this?

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: folding output of tree command?

On 6/26/13, Oliver Rath <rath@mglug.de> wrote:
> Hi list,
>
> Im looking for some expression to fold the output of tree command, i.e.:
>
> ├── opt
> ├── run -> /run
> ├── spool
> │ ├── anacron
> │ ├── asterisk [error opening dir]
> │ ├── cron
> │ │ ├── atjobs
> │ │ ├── atspool
> │ │ └── crontabs
> │ ├── cups [error opening dir]
> │ ├── libreoffice
> │ │ └── uno_packages
> │ ├── lintian
> │ ├── mail -> ../mail
> │ ├── plymouth
> │ ├── rsyslog
> │ └── samba
> └── tmp
>
> So imho I have to find a way to count the number of "│" (including the
> following spaces), so i could define a rule to open/cloes the folds
> recursivly. Any idea for an appropriate expression doing this?
>
> Tfh!
> Oliver

The following assumes that 'encoding' is a Unicode encoding. Vim thus
uses utf-8 internally, and each drawing char in your sample is 3
bytes.

func! FoldTree(lnum)
let ind = match(getline(a:lnum),'├\|└')/4+1
let indn = match(getline(a:lnum+1),'├\|└')/4+1
return indn>ind ? '>'.ind : ind-1
endfunc
setl fen fdm=expr fde=FoldTree(v:lnum)

Regards,
Vlad

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: folding output of tree command?

On Wed, June 26, 2013 17:31, Oliver Rath wrote:
> Hi list,
>
> Im looking for some expression to fold the output of tree command, i.e.:
>
> ДеДЯДЯ opt
> ДеДЯДЯ run -> /run
> ДеДЯДЯ spool
> Да ДеДЯДЯ anacron
> Да ДеДЯДЯ asterisk [error opening dir]
> Да ДеДЯДЯ cron
> Да Да ДеДЯДЯ atjobs
> Да Да ДеДЯДЯ atspool
> Да Да ДдДЯДЯ crontabs
> Да ДеДЯДЯ cups [error opening dir]
> Да ДеДЯДЯ libreoffice
> Да Да ДдДЯДЯ uno_packages
> Да ДеДЯДЯ lintian
> Да ДеДЯДЯ mail -> ../mail
> Да ДеДЯДЯ plymouth
> Да ДеДЯДЯ rsyslog
> Да ДдДЯДЯ samba
> ДдДЯДЯ tmp
>
> So imho I have to find a way to count the number of "Да" (including the
> following spaces), so i could define a rule to open/cloes the folds
> recursivly. Any idea for an appropriate expression doing this?

From your sample, I came up with this expression:

fu! FoldTree(lnum)
return len(split(matchstr(getline(a:lnum),
'^\%([ДаДеДд]\s*\)\+\%(\%([ДдДе]\?ДЯ\)\+\)')))
endfu
setl fen fdm=expr fde=FoldTree(v:lnum)

This seems to work for me. Make sure you have utf8 encoding, so the
characters are correct.

(Please note, the mail may get mangled because either of my Webmailer
sucks or Google mangles it (or even both)). So I attach a copy of this
to this mail.

Regards,
Christian

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Wednesday, June 26, 2013

Re: autocmd useage

On Jun 26, 2013 7:43 PM, "Charles Campbell" <Charles.E.Campbell@nasa.gov> wrote:
>
> wangjun850725 wrote:
>>
>> au VimEnter * call feedkeys('\ca', 't')
>>
> Please bottom post! That's the consensus vim list policy.
>
> I believe your problem is that you're trying to execute a mapping, '\ca', that has not been defined at the time the VimEnter event fires.
>
> What you want is for the mapping to execute -after- its been defined. It just so happens that vim supports that sort of thing.
>
> (untested) Try putting
>
> norm \ca
>
> in $HOME/.vim/after/plugin/NERDcomment.vim . You may have to create a directory or two.
>
> C Campbell

By the time of VimEnter all plugins should have been already loaded. It would not load though with something like yours AsNeeded (though mapping should still work as it will trigger autoload, right?) or with VAM activating plugins *not from vimrc* (additions to runtimepath are not handled correctly if they are done after vim started to load plugins from runtimepath; we have a workaround, but it uses VimEnter too and is likely to be launched after event from the vimrc).

>
> --
> --
> You received this message from the "vim_use" 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_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Re: How to change just 1 color of the default colorscheme

On Wed, Jun 26, 2013 at 2:16 PM, Bram Moolenaar <Bram@moolenaar.net> wrote:

Ben Fritz wrote:

> On Wednesday, June 26, 2013 12:20:52 PM UTC-5, Charles Campbell wrote:
> >
> > * Second, change the color. You can put overrides into
> >
> > $HOME/.vim/after/colors/TheColorschemeNameHere.vim .
> >
>
> This doesn't actually work.
>
> Bram, is there a reason it doesn't? I've wanted an after/colors
> directory on several occasions.

Well, it's always been that way...

You can setup an autocommand for the ColorScheme event to make changes
afterwards.

Continuing to find more matching files after the first one has been
found would require changes in existing files, to avoid loading two
complete color schemes. I don't think this is common enough to risk
breaking something.

I get around this by having a colorscheme called "mySolarized" or "myOriginalName" and starting by sourcing the original and then changing whatever I want to change. (Usually, setting up user colours on the status line.)

Hope this helps,

Salman

Re: How to change just 1 color of the default colorscheme

Ben Fritz wrote:

> On Wednesday, June 26, 2013 12:20:52 PM UTC-5, Charles Campbell wrote:
> >
> > * Second, change the color. You can put overrides into
> >
> > $HOME/.vim/after/colors/TheColorschemeNameHere.vim .
> >
>
> This doesn't actually work.
>
> Bram, is there a reason it doesn't? I've wanted an after/colors
> directory on several occasions.

Well, it's always been that way...

You can setup an autocommand for the ColorScheme event to make changes
afterwards.

Continuing to find more matching files after the first one has been
found would require changes in existing files, to avoid loading two
complete color schemes. I don't think this is common enough to risk
breaking something.

--
"To whoever finds this note -
I have been imprisoned by my father who wishes me to marry
against my will. Please please please please come and rescue me.
I am in the tall tower of Swamp Castle."
SIR LAUNCELOT's eyes light up with holy inspiration.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to change just 1 color of the default colorscheme

On Wednesday, June 26, 2013 12:20:52 PM UTC-5, Charles Campbell wrote:
>
> * Second, change the color. You can put overrides into
>
> $HOME/.vim/after/colors/TheColorschemeNameHere.vim .
>

This doesn't actually work.

Bram, is there a reason it doesn't? I've wanted an after/colors directory on several occasions.

To prove it doesn't work on Windows (from your $HOME\vimfiles directory):

echo echomsg "normal colors sourced"> colors\tester.vim
mkdir after\colors
echo echomsg "after colors sourced"> after\colors\tester.vim
gvim
:colors tester

I only see one message, "normal colors sourced".

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to change just 1 color of the default colorscheme

Todd Dickinson wrote:
> I'm using vim to edit Asterisk configuration files. The syntax checking makes vim an absolutely invaluable tool but the dark blue color assigned to comments is too dark to be easily discernible/readable against the black background.
>
> I don't mind the default colorscheme used with asterisk.vim syntax file.
>
> How can I modify just the COMMENT color setting within an Asterisk configuration file?
>
> I would have even considered copying the /colors/default.vim over and use as a template but the default color file doesn't contain any color settings.
>
> Any help appreciated.
>
* First, identify the color. I have a plugin, hilinks.vim, which you
can use :HLT! and then, as you move the cursor about, the syntax and
highlighting groups involved show upon the bottom of the display. You
can get it from http://www.drchip.org/astronaut/vim/index.html#HILINKS .

* Second, change the color. You can put overrides into
$HOME/.vim/after/colors/TheColorschemeNameHere.vim .

* Third, you could use hicolors, available at
http://www.drchip.org/astronaut/vim/index.html#HICOLORS, to both create
your own modified colorscheme and to check on what your colorscheme is
setting your highlighting groups to.
+ to check on your colorscheme with hicolor: :help hicolors
+ to then edit your colorscheme, creating your own: click with the
rightmouse button on whatever highlighting group you wish to change.
When done, click on the [WriteColorscheme] button on the colorscheme
editor window. You'll be prompted for a new colorscheme name to use.

Regards,
C Campbell

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to change just 1 color of the default colorscheme

On Wednesday, June 26, 2013 11:19:24 AM UTC-5, Todd Dickinson wrote:
> I'm using vim to edit Asterisk configuration files. The syntax checking makes vim an absolutely invaluable tool but the dark blue color assigned to comments is too dark to be easily discernible/readable against the black background.
>
> I don't mind the default colorscheme used with asterisk.vim syntax file.
>
> How can I modify just the COMMENT color setting within an Asterisk configuration file?
>
> I would have even considered copying the /colors/default.vim over and use as a template but the default color file doesn't contain any color settings.
>
> Any help appreciated.

See http://vim.wikia.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor to get the specific group name being used for that comment.

Then you can define a specific highlight command for that group, either in your own copy of the colorscheme, in a ColorScheme autocmd, or just in your .vimrc.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: How to change just 1 color of the default colorscheme

On Wednesday, 26 June 2013 17:19:24 UTC+1, Todd Dickinson wrote:
> I'm using vim to edit Asterisk configuration files. The syntax checking makes vim an absolutely invaluable tool but the dark blue color assigned to comments is too dark to be easily discernible/readable against the black background.
>
> I don't mind the default colorscheme used with asterisk.vim syntax file.
>
> How can I modify just the COMMENT color setting within an Asterisk configuration file?
>
> I would have even considered copying the /colors/default.vim over and use as a template but the default color file doesn't contain any color settings.
>
> Any help appreciated.

(If you're using actual console vim as opposed to gvim, this might not be relevant.) My approach was to modify the dark blue colour to one I can see properly, this has the advantage of fixing the colour everywhere it is used. I did it by defining a different blue and using that in my colourscheme, but you might be able to modify the existing colour - these lines in rgb.txt:

0 0 139 dark blue
0 0 139 DarkBlue

To test you could just modify them manually and restart gvim.

If you're using Windows such changes can be lost when vim is upgraded. This thread [1] described how I made sure the rgb.txt changes aren't lost. I think (from reading the help files, haven't tried it) that under *nix this isn't a problem since the rgb.txt file is part of the general system files.

See :help rgb.txt

regards,
Geoff

[1] http://vim.1045645.n5.nabble.com/change-display-colors-which-rule-causes-which-color-td5711079.html

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

How to change just 1 color of the default colorscheme

I'm using vim to edit Asterisk configuration files. The syntax checking makes vim an absolutely invaluable tool but the dark blue color assigned to comments is too dark to be easily discernible/readable against the black background.

I don't mind the default colorscheme used with asterisk.vim syntax file.

How can I modify just the COMMENT color setting within an Asterisk configuration file?

I would have even considered copying the /colors/default.vim over and use as a template but the default color file doesn't contain any color settings.

Any help appreciated.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: autocmd useage

wangjun850725 wrote:
> au VimEnter * call feedkeys('\ca', 't')
>
Please bottom post! That's the consensus vim list policy.

I believe your problem is that you're trying to execute a mapping,
'\ca', that has not been defined at the time the VimEnter event fires.

What you want is for the mapping to execute -after- its been defined.
It just so happens that vim supports that sort of thing.

(untested) Try putting

norm \ca

in $HOME/.vim/after/plugin/NERDcomment.vim . You may have to create a
directory or two.

C Campbell

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

folding output of tree command?

Hi list,

Im looking for some expression to fold the output of tree command, i.e.:

├── opt
├── run -> /run
├── spool
│ ├── anacron
│ ├── asterisk [error opening dir]
│ ├── cron
│ │ ├── atjobs
│ │ ├── atspool
│ │ └── crontabs
│ ├── cups [error opening dir]
│ ├── libreoffice
│ │ └── uno_packages
│ ├── lintian
│ ├── mail -> ../mail
│ ├── plymouth
│ ├── rsyslog
│ └── samba
└── tmp

So imho I have to find a way to count the number of "│" (including the
following spaces), so i could define a rule to open/cloes the folds
recursivly. Any idea for an appropriate expression doing this?

Tfh!
Oliver

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Re: autocmd useage

au VimEnter * call feedkeys('\ca', 't')

it is failed too!

From: Nikolay Pavlov

Date: 2013-06-26 23:14

To: vim_use

Subject: Re: autocmd useage

On Jun 26, 2013 6:57 PM, "Xell Liu" <xell.liu@gmail.com> wrote:
>
> On Wed, Jun 26, 2013 at 10:36 PM, wangjun850725 <wangjun850725@gmail.com> wrote:
> > Hi :
> > I want to execute "\ca" when I opened gvim.
> > I set:
> > autocmd VimEnter * exe "normal \\ca"
> > or
> > autocmd VimEnter * normal \ca
> > that are all failed.
> >
> > How to write this command?
>
> Maybe feedkeys() would help here, e.g. au VimEnter * call
> feedkeys('\ca', 'n') or something like that. Good luck.

Wondering how feedkeys(, *'n'*) is supposed to execute a *mapping*. You should have suggested feedkeys(, 't').

> > "
> > 3.2.11 Use alternate delims map
> > *NERDComAltDelim*
> > Default mapping: <leader>ca
> > Mapped to: <plug>NERDCommenterAltDelims
> > Applicable modes: normal.
> >
> > Changes to the alternative commenting style if one is available. For
> > example,
> > if the user is editing a c++ file using // comments and they hit <leader>ca
> > then they will be switched over to /**/ comments.
> >
> > the plugin is NERDcomment
> > "
> >
> > --
> > --
> > You received this message from the "vim_use" 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_use" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to vim_use+unsubscribe@googlegroups.com.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
>
> --
> --
> You received this message from the "vim_use" 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_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Re: autocmd useage

Wondering how feedkeys(, *'n'*) is supposed to execute a *mapping*. You should have suggested feedkeys(, 't').

Re: Re: autocmd useage

au VimEnter * call feedkeys('\ca', 'n')

it is failed too!

From: Xell Liu

Date: 2013-06-26 22:56

To: vim_use

Subject: Re: autocmd useage

On Wed, Jun 26, 2013 at 10:36 PM, wangjun850725 <wangjun850725@gmail.com> wrote:

> Hi :

> I want to execute "\ca" when I opened gvim.

> I set:

> autocmd VimEnter * exe "normal \\ca"

> or

> autocmd VimEnter * normal \ca

> that are all failed.

> How to write this command?

Maybe feedkeys() would help here, e.g. au VimEnter * call

feedkeys('\ca', 'n') or something like that. Good luck.

> "

> 3.2.11 Use alternate delims map

> *NERDComAltDelim*

> Default mapping: <leader>ca

> Mapped to: <plug>NERDCommenterAltDelims

> Applicable modes: normal.

> Changes to the alternative commenting style if one is available. For

> example,

> if the user is editing a c++ file using // comments and they hit <leader>ca

> then they will be switched over to /**/ comments.

> the plugin is NERDcomment

> "

> --

> You received this message from the "vim_use" 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_use" group.

> To unsubscribe from this group and stop receiving emails from it, send an

> email to vim_use+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/groups/opt_out.

You received this message from the "vim_use" 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_use" group.

To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/groups/opt_out.

Re: autocmd useage

On Wed, Jun 26, 2013 at 10:36 PM, wangjun850725 <wangjun850725@gmail.com> wrote:
> Hi :
> I want to execute "\ca" when I opened gvim.
> I set:
> autocmd VimEnter * exe "normal \\ca"
> or
> autocmd VimEnter * normal \ca
> that are all failed.
>
> How to write this command?

Maybe feedkeys() would help here, e.g. au VimEnter * call
feedkeys('\ca', 'n') or something like that. Good luck.

> "
> 3.2.11 Use alternate delims map
> *NERDComAltDelim*
> Default mapping: <leader>ca
> Mapped to: <plug>NERDCommenterAltDelims
> Applicable modes: normal.
>
> Changes to the alternative commenting style if one is available. For
> example,
> if the user is editing a c++ file using // comments and they hit <leader>ca
> then they will be switched over to /**/ comments.
>
> the plugin is NERDcomment
> "
>
> --
> --
> You received this message from the "vim_use" 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_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

autocmd useage

Hi :

I want to execute "\ca" when I opened gvim.

I set:

autocmd VimEnter * exe "normal \\ca"

autocmd VimEnter * normal \ca

that are all failed.

How to write this command?

3.2.11 Use alternate delims map *NERDComAltDelim*

Default mapping: <leader>ca

Mapped to: <plug>NERDCommenterAltDelims

Applicable modes: normal.

Changes to the alternative commenting style if one is available. For example,

if the user is editing a c++ file using // comments and they hit <leader>ca

then they will be switched over to /**/ comments.

the plugin is NERDcomment

Re: translation of "Vim explained in 6 Kbyte"

Rudra Banerjee wrote:

> Hi,
> I am writing a bengali(bn_IN) translation of http://www.vim.org/6k/features.en.txt
>
> Can I add it in that page?
> or should I contact vim_dev?

You can send it to me. A copy to the maillist would be good, so that
others can check for any mistakes.

--
"My particular problem is with registry entries, which seem to just
accumulate like plastic coffee cups..." -- Paul Moore

/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: translation of "Vim explained in 6 Kbyte"

rudrab wrote:
> I am writing a bengali(bn_IN) translation of
> http://www.vim.org/6k/features.en.txt
>
> Can I add it in that page?
> or should I contact vim_dev?

BRAM:

Would translations of the above work at vim.org?

I could put it at /6k/features.bn.text if wanted.

John

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

translation of "Vim explained in 6 Kbyte"

Hi,
I am writing a bengali(bn_IN) translation of http://www.vim.org/6k/features.en.txt

Can I add it in that page?
or should I contact vim_dev?

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Question: syntax/c.vim: cNumbers -> cNumber containment

Hi,
I am looking into .vim/syntax/c.vim and especially on cNumbers match rules.
This c syntax rules states that
cNumbers matches only the first single digit of integer number (\>\d),
while it "contains" cNumber which can contain multiple digits ( /\d\+/ ).

What is the purpose of 'cNumbers' rule here??

Thanks in advance.
----------------------------------------------------------------------------

"integer number, or floating point number without a dot and with "f".
syn case ignore
syn match cNumbers display transparent "\<\d\|\.\d" contains=cNumber,cFloat,cOctalError,cOctal
" Same, but without octal error (for comments)
syn match cNumbersCom display contained transparent "\<\d\|\.\d" contains=cNumber,cFloat,cOctal
syn match cNumber display contained "\d\+$u\=l\{0,2}\|ll\=u$\>"

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

AW: compatibility with Sun's original vi for command :su

Bram wrote:
> The POSIX spec has a bug: it says that :s means :substitute, which means
> anything starting with :s means :substitute, including :su. But then
> :suspend can be abbreviated to :su, that's a conflict.

The compatibility mode tries to emulate the behaviour of original Sun's vi,
even if it is a bug there. Vim does this at several places.

With a new cpo flag, the user would have a choice to configure vim to personal
habits. (I have been using original Sun vi for 10 years, typing :su, not
considering that I am using a bug. Now I am used to it.)

Tony wrote:
> cnoreabbrev <expr> su
> \ ((getcmdtype() == ':' && getcmdpos() <= 3)? 'suspend' : 'su')

Thanks Tony, this works 100% great!

In case you developer guys don't want a new cpo flag, maybe you want to add
Tony's line to the help page.
(see :help Y for an example of such a line in the help)

Regards,
Paul

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Tuesday, June 25, 2013

Re: compatibility with Sun's original vi for command :su

Christian Brabandt wrote:

> On Mon, June 24, 2013 23:54, Paul Maier wrote:
> > Hi,
> >
> > the original vi on Sun took :su as :suspend,
> > whereas vim takes :su as :substitute.
> >
> > I am very used to typing :su.
> >
> > Would it be possible for VIM 7.4 to add a new compatibility flag to
> > cpoptions
> > about the meaning of :su ?
> >
> > suggested compatible flag: :su = :suspend, :s = :substitute
> > without the flag: :su = :substitute
> >
>
> Looks like a bug to me. POSIX also requires :su to be used for
> :suspend (http://pubs.opengroup.org/onlinepubs/007908799/xcu/ex.html)
>
> Do we need a new cpo setting here, or should it be enough to
> patch vim to take :su as :suspend?

The POSIX spec has a bug: it says that :s means :substitute, which means
anything starting with :s means :substitute, including :su. But then
:suspend can be abbreviated to :su, that's a conflict.

Relevant quotes:

For each of the commands listed below, the command can be
entered as the abbreviation (those characters in the Synopsis
command word preceding the [), the full command (all characters
shown for the command word, omitting the [ and ]), or any subset
of the characters of the full command down to the abbreviation.
For example, the args command (shown as ar[gs] in the Synopsis)
can be entered as ar, arg or args.

[...]

Substitute

Synopsis: [range] s[ubstitute] [/pattern/repl/[options] [count] [flags]]

[...]

Suspend

Synopsis: su[spend][!]

Making an exception for :su to mean :suspend instead of :substitute
would be weird.

--
GALAHAD: No. Look, I can tackle this lot single-handed!
GIRLS: Yes, yes, let him Tackle us single-handed!
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

/// Bram Moolenaar -- Bram@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_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Building Vim on Windows

On Mon, Jun 24, 2013 at 1:21 PM, Salman Halim <salmanhalim@gmail.com> wrote:

I was able to fix the "prototype not found" warnings easily enough myself; will post the Python ones when I'm back at the home computer.

I concede that BCC might be an unpopular choice, but as long as Vim continues to include a make file for it, I assume it's because someone (besides me; my use of it wasn't public knowledge until I just admitted it on this email list!) uses it. If not, why bother?

After fiddling a bit with the MinGW paths (I also have Cygwin installed), I got a clean build with MinGW, which is great: thanks again, Ben, for the pointer. As for the BCC warnings, the list is large, so I'm including it here in as an attachment. However, to summarize, here are a few sample lines from the output (again, the addition of a function prototype earlier in the file got rid of this warning, but it's not there when I build with MinGW at all):

Warning W8065 .\regexp_nfa.c 2625: Call to function 'nfa_max_width' with no prototype in function nfa_max_width

Warning W8066 .\regexp_nfa.c 2814: Unreachable code in function nfa_max_width

Also, there are about 100 of these (on steadily increasing line numbers):

Warning W8060 if_python.c 772: Possibly incorrect assignment in function py_memsave

These seem rather suspicious:

Warning W8053 .\os_win32.c 2681: '_chmod(const signed char *,int,...)' is obsolete in function mch_setperm
Warning W8070 .\os_win32.c 3614: Function should return a value in function sub_process_writer

There are no actual errors, just a bunch of warnings. The final build, however, corrupts every file it touches absolutely.

This is no longer pressing for me, personally, but I do feel that we should either renege on support for BCC or fix it. It would help if we knew if anybody still uses BCC...

Salman

Re: Indentation issue

Hi,

Just for the record, maybe someone will need this one day. For the
fo+=2 option to work well, one needs to turn autoindenting off. I tried
putting 'set noautoindent' in several files but it didn't work
(something somewhere just activated it back on). So I finally found how
to do it properly. Create a file called ~/.vim/indent/mail.vim (if you
don't want this for writing emails, for html, it would be html.vim for
ex.) with this one line:

let b:did_indent = 1

and you're done. The reason it works is given here:

http://vim.wikia.com/wiki/How_to_stop_auto_indenting

Have a nice day,
steve

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: compatibility with Sun's original vi for command :su

On Mon, June 24, 2013 23:54, Paul Maier wrote:
> Hi,
>
> the original vi on Sun took :su as :suspend,
> whereas vim takes :su as :substitute.
>
> I am very used to typing :su.
>
> Would it be possible for VIM 7.4 to add a new compatibility flag to
> cpoptions
> about the meaning of :su ?
>
> suggested compatible flag: :su = :suspend, :s = :substitute
> without the flag: :su = :substitute
>

Looks like a bug to me. POSIX also requires :su to be used for
:suspend (http://pubs.opengroup.org/onlinepubs/007908799/xcu/ex.html)

Do we need a new cpo setting here, or should it be enough to
patch vim to take :su as :suspend?

regards,
Christian

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: compatibility with Sun's original vi for command :su

On 25/06/13 10:01, Matteo Cavalleri wrote:
> Il giorno lunedì 24 giugno 2013 23:54:43 UTC+2, Paul Maier ha scritto:
>
>> the original vi on Sun took :su as :suspend,
>>
>> whereas vim takes :su as :substitute.
>
> what does ":su" do? it's the same as pressing CTRL-z or typing ":sh"?
>
Matteo: see :help :suspend

Paul: Either use Salman's cabbrev trick (more later) or use :st instead
(for :stop which in Vim is a synonym for :suspend).

A more involved cabbrev trick for your vimrc:

if version < 700
cnoreabbrev su suspend
else
cnoreabbrev <expr> su
\ ((getcmdtype() == ':' && getcmdpos() <= 3)? 'suspend' : 'su')
endif

The above assumes 'nocompatible' (otherwise, you can still use it, but
the long cnoreabbrev <expr> line must be typed all on one line with no
line continuation) and determines at run-time whether the "finer"
version of the mapping (with getcmdtype() and getcmdpos()) can be used
or not.

I intentionally use "version" rather than "v:version" because it is more
backward-compatible.

Best regards,
Tony.
--
Without ice cream life and fame are meaningless.

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: compatibility with Sun's original vi for command :su

Il giorno lunedì 24 giugno 2013 23:54:43 UTC+2, Paul Maier ha scritto:

> the original vi on Sun took :su as :suspend,
>
> whereas vim takes :su as :substitute.

what does ":su" do? it's the same as pressing CTRL-z or typing ":sh"?

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Monday, June 24, 2013

Re: compatibility with Sun's original vi for command :su

On Monday, June 24, 2013, Paul Maier wrote:

Hi,

the original vi on Sun took :su as :suspend,
whereas vim takes :su as :substitute.

I am very used to typing :su.

Would it be possible for VIM 7.4 to add a new compatibility flag to cpoptions
about the meaning of :su ?

suggested compatible flag: :su = :suspend, :s = :substitute
without the flag: :su = :substitute

Thanks for responding!
Paul

Why not just do something like:

:cab su substitute

Or, if you want to make sure it's only after a colon (and not after every occurrence of "su"), look up getcmdpos() and only act if it's at the beginning of the command-line.

Hope this helps,

Salman

سلمان حلیم

compatibility with Sun's original vi for command :su

Hi,

the original vi on Sun took :su as :suspend,
whereas vim takes :su as :substitute.

I am very used to typing :su.

Would it be possible for VIM 7.4 to add a new compatibility flag to cpoptions
about the meaning of :su ?

suggested compatible flag: :su = :suspend, :s = :substitute
without the flag: :su = :substitute

Thanks for responding!
Paul

--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Building Vim on Windows

On Mon, Jun 24, 2013 at 1:14 PM, Nikolay Pavlov <zyx.vim@gmail.com> wrote:

On Jun 24, 2013 8:53 PM, "Salman Halim" <salmanhalim@gmail.com> wrote:

> Now, I wonder what can be done about the Borland compiler's issues.

Nothing until you post them. Most developers here are on linux like me (with gcc or clang or both) or on windows, but with mingw. With warnings posted we may be able to guess a fix, but without you will have to wait for someone with Windows and bcc which is a very unpopular choice.

Makes sense; will do as soon as am able.

Note that at least some problems (I would expect one or two, but I do not know how verbose is bcc with macros error) in if_py_both.h may be fixed by one of the patches posted here.

I've posted them in a previous post, but the only response I got was from Bram and he just said to try the next patch, which didn't help at all (as I was already well past the 944 in my Mercurial pull of the code base), after which he said to just post here again.

I was able to fix the "prototype not found" warnings easily enough myself; will post the Python ones when I'm back at the home computer.

I concede that BCC might be an unpopular choice, but as long as Vim continues to include a make file for it, I assume it's because someone (besides me; my use of it wasn't public knowledge until I just admitted it on this email list!) uses it. If not, why bother?

Thank you,

Salman

Re: Building Vim on Windows

On Jun 24, 2013 8:53 PM, "Salman Halim" <salmanhalim@gmail.com> wrote:
>
> On Mon, Jun 24, 2013 at 12:28 PM, Ben Fritz <fritzophrenic@gmail.com> wrote:
>>
>> On Monday, June 24, 2013 11:03:50 AM UTC-5, Salman Halim wrote:
>> >
>> > Thank you for this; I was wondering: does building with MinGW change GVim into a GNU-ish application? Can I still use paths like "c:\test\some\file.txt"? While I use the forward slash almost exclusively, it is nice to occasionally be able to take a file path someone else gave me and just :e or :sp it.
>> >
>>
>> Nope, MinGW just uses unix-like tools to build a native Windows application. I actually can't use cygwin paths from my MinGW Vim build, it's all native Windows paths.
>>
>> You can use the forward slash on Windows, though, like :e c:/test/some/file.txt. This doesn't depend on what you used to compile.
>>
>
> Ben,
>
> Thank you, again; I'll make the switch and see how it works out. I really appreciate your suggestions and responses.
>
> Now, I wonder what can be done about the Borland compiler's issues.

Nothing until you post them. Most developers here are on linux like me (with gcc or clang or both) or on windows, but with mingw. With warnings posted we may be able to guess a fix, but without you will have to wait for someone with Windows and bcc which is a very unpopular choice.

Note that at least some problems (I would expect one or two, but I do not know how verbose is bcc with macros error) in if_py_both.h may be fixed by one of the patches posted here.

> Salman
>
> --
> --
> You received this message from the "vim_use" 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_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Sunday, June 30, 2013

Friday, June 28, 2013

Thursday, June 27, 2013

Wednesday, June 26, 2013

Tuesday, June 25, 2013

Monday, June 24, 2013

Blog Archive

About Me