headers
Cesar Romani | 1 Feb 2011 04:59
Picon

MkVimball doesn't work on windows

I'm using gvim 7.3.107 on Win XP with vimball v32c

If I have the following file:
--------------------
autoload\dbext.vim
autoload\dbext_dbi.vim
doc\dbext.txt
doc\dbext_gpl.dat
plugin\dbext.vim
--------------------

and do %MkVimball! dbext
I'm getting:

***vimball*** unable to read file<autoload\dbext.vim>

but if I do gf I can read the file!

I changed \ to / but the result is the same.

Many thanks in advance,

-- 
Cesar

--

-- 
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
(Continue reading)

Permalink | Reply | 2 comments |
headers
Christian Brabandt | 1 Feb 2011 08:29

Re: 'list', :list, and 'listchars'

On Sat, January 29, 2011 10:59 am, Andy Wokula wrote:
> Am 26.01.2011 18:41, schrieb Ben Fritz:
>>> From looking at :list, it seems like it's basically supposed to print
>> the line as it would show with 'list' turned on. However, I have a few
>> questions:
>>
>> :help :list says it will use '^' for unprintable characters, and
>> additionally says "This can be changed with the 'listchars' option.
>> However, there does not seem to be any 'listchars' option controlling
>> the display of unprintable characters. What does setting 'list' do for
>> unprintable characters? Anything?
>>
>> :help :list only mentions EOL and unprintable behavior, but
>> experimentation shows that "trail", "extends", and "tab" also apply
>> from 'listchars'. "precedes" and "extends" certainly would not make
>> sense in this context, but what about "nbsp" and "conceal"?
>> Experimentation shows that these two options do not have any effect.
>> Should they? I could understand "conceal" having no effect, but I
>> would certainly expect "nbsp" to apply, since "trail", etc. all apply.
>
> Unprintable characters basically are control characters
>      :h 'isprint
> Tab is a control character - when 'listchars' does not include
> 'tab:xy', then tab will be printed as '^I'.
>
> "nbsp" was added recently, maybe just forgotten to be implemented for
> :list ...
> :list is such a rarely used command ...

Here is a patch, that adds nbsp support to :list command. I leave out
(Continue reading)

Permalink | Reply | 5 comments |
headers
Christian Brabandt | 1 Feb 2011 08:39

Re: MkVimball doesn't work on windows

On Tue, February 1, 2011 4:59 am, Cesar Romani wrote:
> I'm using gvim 7.3.107 on Win XP with vimball v32c
>
> If I have the following file:
> --------------------
> autoload\dbext.vim
> autoload\dbext_dbi.vim
> doc\dbext.txt
> doc\dbext_gpl.dat
> plugin\dbext.vim
> --------------------
>
> and do %MkVimball! dbext
> I'm getting:
>
> ***vimball*** unable to read file<autoload\dbext.vim>
>
> but if I do gf I can read the file!
>
> I changed \ to / but the result is the same.
>
> Many thanks in advance,

What is the working directory when you edit the vimball file?
And where are your files located?

I assume, that your autoload\dbext.vim file does not exist inside your
.vim directory (as the documentation says)?

In that case, try explicitly mentioning the path where the autoload/
(Continue reading)

Permalink | Reply | 1 comment |
headers
Christian Brabandt | 1 Feb 2011 08:50

Re: vimscript syntax problem

On Mon, January 31, 2011 6:20 pm, H Xu wrote:
> Hello everybody,
>
> In a vimscript file, parentheses across multi lines is highlighted as
> errors, which is shown in the attachment. Is there any way to fix this?
>
> Thanks.

This was recently discussed here. See the thread starting at
http://groups.google.com/group/vim_use/browse_frm/thread/b7a3187fee6932e8/c1d090858eaaea64?#c1d090858eaaea64

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
Permalink | Reply | 2 comments |
headers
Steve Laurie | 1 Feb 2011 10:23
Picon

Determining if Vim is running in text-console mode or X Windows

Hi,

I've searched Vim help and Google as well as done lots of 
experimentation with no luck.

Basically, what I'm trying to do is put something in my .vimrc file that 
can determine if I'm starting Vim in text-console mode or in gnome-terminal.

The reason I need to do this is because I log into FreeBSD in 
text-console. If I go into Xorg, I use startx and I use gnome-terminal 
in Window Maker.

I need to determine if I'm in text-console mode so I can set the term 
setting in my .vimrc file to cons25 and if I startx, I need to set 
t_Co=256, term to xterm-256color and set the theme to a nice 256 color 
theme.
If I try to use the color settings in console mode, the screen turns red 
and the text flashes.

I've tried the following:

if has("x11")
     set term=xterm-256color
     set t_Co=256
     colorscheme calmar256-dark
else
     set term=cons25
     colorscheme myvim
endif
(Continue reading)

Permalink | Reply | 14 comments |
headers
Karthick Gururaj | 1 Feb 2011 10:58
Picon

Re: Determining if Vim is running in text-console mode or X Windows

On Tue, Feb 1, 2011 at 2:53 PM, Steve Laurie <mr.steven.laurie <at> gmail.com> wrote:
> Hi,
>
> I've searched Vim help and Google as well as done lots of experimentation
> with no luck.
>
> Basically, what I'm trying to do is put something in my .vimrc file that can
> determine if I'm starting Vim in text-console mode or in gnome-terminal.

> The reason I need to do this is because I log into FreeBSD in text-console.
> If I go into Xorg, I use startx and I use gnome-terminal in Window Maker.
Why not keep GUI specific settings .gvimrc? Let .vimrc have only the
settings that are common to both GUI/text versions..

>
> I need to determine if I'm in text-console mode so I can set the term
> setting in my .vimrc file to cons25 and if I startx, I need to set t_Co=256,
> term to xterm-256color and set the theme to a nice 256 color theme.
> If I try to use the color settings in console mode, the screen turns red and
> the text flashes.
>
>
> I've tried the following:
>
> if has("x11")
>    set term=xterm-256color
>    set t_Co=256
>    colorscheme calmar256-dark
> else
>    set term=cons25
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christian Brabandt | 1 Feb 2011 11:00

Re: Determining if Vim is running in text-console mode or X Windows

On Tue, February 1, 2011 10:23 am, Steve Laurie wrote:
> Hi,
>
> I've searched Vim help and Google as well as done lots of
> experimentation with no luck.
>
> Basically, what I'm trying to do is put something in my .vimrc file that
> can determine if I'm starting Vim in text-console mode or in
> gnome-terminal.
>
> The reason I need to do this is because I log into FreeBSD in
> text-console. If I go into Xorg, I use startx and I use gnome-terminal
> in Window Maker.
>
> I need to determine if I'm in text-console mode so I can set the term
> setting in my .vimrc file to cons25 and if I startx, I need to set
> t_Co=256, term to xterm-256color and set the theme to a nice 256 color
> theme.
> If I try to use the color settings in console mode, the screen turns red
> and the text flashes.
>
>
> I've tried the following:
>
> if has("x11")
>      set term=xterm-256color
>      set t_Co=256
>      colorscheme calmar256-dark
> else
>      set term=cons25
(Continue reading)

Permalink | Reply | 10 comments |
headers
Karthick Gururaj | 1 Feb 2011 11:07
Picon

Re: Determining if Vim is running in text-console mode or X Windows

On Tue, Feb 1, 2011 at 3:30 PM, Christian Brabandt <cblists <at> 256bit.org> wrote:
   [snip]

> So you basically distinguish it by inspecting your $TERM variable. First
> determine in both situations what your $TERM is set to, then put something
> like this in your .vimrc

Ah, I mis-read the post. Clearer now :)

--

-- 
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
Permalink | Reply | 9 comments |
headers
Erik Christiansen | 1 Feb 2011 11:49
Favicon

Re: Remapping CTRL-I to <Esc>

On Fri, Jan 28, 2011 at 07:37:17AM +0100, Christophe-Marie Duquesne wrote:
> On Fri, Jan 28, 2011 at 6:52 AM, Ben Schmidt
> <mail_ben_schmidt <at> yahoo.com.au> wrote:
> > On 28/01/11 3:56 PM, Chris Jones wrote:
> >>
> >> Is it possible to remap CTRL-I to ‘Escape’ in insert mode without
> >> remapping<Tab>  at the same time?
> 
> I think using an external tool such as xmodmap, you could remap <c-i>
> to <esc>, but this solution would affect the whole system.

Originally to compensate for a uselessly small laptop ESC key, I long
ago remapped "Caps Lock" to ESC:

To change CAPS_LOCK to ESCAPE, put into ~/.Xmodmap:
   keycode 0x42 =  Escape
   clear Lock                             # Disable Caps-Lock

Now I use it on desktops as well, because I've never found a use for
"Caps Lock" [1]. Since ESC is used so much in vim, it seems useful to have
it on a single key. Consistent behaviour across all applications is an
advantage, I find.

YMMV (by a large margin ;-)

Erik

[1] If ever a long shouting heading were needed, there are several vim
    ways to convert after input.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Bram Moolenaar | 1 Feb 2011 11:53
Picon

Re: Present For You


Note: this is spam, don't click on the link (which I obfuscated).

> I really like this http://ilovSPAMon.com/inSPAMtml Hope u too!

-- 
hundred-and-one symptoms of being an internet addict:
169. You hire a housekeeper for your home page.

 /// Bram Moolenaar -- Bram <at> 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
Permalink | Reply | 0 comments |

Gmane