On 19 Jan., 15:23, krzysztof cierpisz wrote:
> > $ sudo apt-get install libgtk2.0-dev
>
> had already installed -> did not help
>
> > Or maybe even better to install all packages required to build vim-gnome
> > with:
>
> > $ sudo apt-get build-dep vim-gnome
>
> > Then try to run ./configure sc
>put gui-related settings in .gvimrc solves the issue. and you don't
need
>to test for has("gui") at all. Anyway, move non-cli things into .gvimrc
>speeds up your cli vim startup slightly.
Might work for some, but for me, personally, I don't like having to
maintain *2* files across different pl
On Tue, Jan 13, 2009 at 07:09:15PM +0200, Itai Fiat wrote:
> On Tue, Jan 13, 2009 at 18:51, Itai Fiat wrote:
> >> 1. From vim, run :shell
> >> 2. Find the files I'm after
> >> 3. Open these in the vim session I ran :shell from.
> > This sound incredibly useful. This idea has never occurred to
On 20/01/09 05:02, pansz wrote:
> Tony Mechelynck 写道:
>> It is on purpose that I test has('gui') rather than has('gui_running'):
>> this way it will work even if you start a GUI-enabled Vim in Console
>> mode in an xterm and later use the ':gui' command to start GUI mode.
>
> put gui-related setti
On Jan 8, 1:19 pm, itai wrote:
> 4. The vim help files seem to recommend against using 'autuchdir'. I
> use the following:
> autocmd BufEnter * lcd %:p:h
>
> (Seehttp://vim.wikia.com/wiki/Set_working_directory_to_the_current_file
> .)
>
Regarding 'autochdir'...why is it that the help files
> I've been using autochdir...the only broken thing I've noticed is
> saving and restoring sessions
The same here. I don't think it will break too many other plugins
since without that option you cannot make any assumptions about the
current directory anyway. The autocommand is probably worse bec
On Tue, Jan 20, 2009 at 1:03 PM, Ben Fritz wrote:
>
> On Jan 8, 1:19 pm, itai wrote:
>
>> 4. The vim help files seem to recommend against using 'autuchdir'. I
>> use the following:
>> autocmd BufEnter * lcd %:p:h
>
> Regarding 'autochdir'...why is it that the help files recommend
> against usi
On Tue, Jan 20, at 10:24 Tom Link wrote:
>
> > I've been using autochdir...the only broken thing I've noticed is
> > saving and restoring sessions
>
> The same here. I don't think it will break too many other plugins
> since without that option you cannot make any assumptions about the
> current
Is there any way to stop gvim from auto-resizing itself? I'm running
Ubuntu with dual monitors, and usually have gvim sized to my
liking(full vertical space, and 140 columns) on the secondary display.
No matter what I do, I have about 100-150 pixels worth of space at
the bottom that gvim refuses
Hello,
~/.vimrc part follows:
[...]
set enc=utf-8
set tenc=utf-8
set fileencodings=ucs-bom,utf-8,iso-8859-7,ascii
[...]
I 've the following problem, I saw in the :help that when the fenc != enc
condition is satisfied vim will internally convert text (I suppose in
utf-8) for both reading and writ
On 20/01/09 23:31, Steve V wrote:
> Is there any way to stop gvim from auto-resizing itself? I'm running
> Ubuntu with dual monitors, and usually have gvim sized to my
> liking(full vertical space, and 140 columns) on the secondary display.
> No matter what I do, I have about 100-150 pixels wort
On 20/01/09 22:27, Dimitris Mandalidis wrote:
> Hello,
> ~/.vimrc part follows:
>
> [...]
> set enc=utf-8
> set tenc=utf-8
> set fileencodings=ucs-bom,utf-8,iso-8859-7,ascii
> [...]
>
> I 've the following problem, I saw in the :help that when the fenc != enc
> condition is satisfied vim will inte
Hola~
I was watching a guy using jedit, which made me appreciate the
simplicity of vim's interface. In jedit, you can draw a thin line at
80 columns. It's not obnoxious, but is in an indicator where 80
columns is. You can see it in this screenshot:
http://www.jedit.org/index.php?page=screens
Michael O'Brien wrote:
> I was watching a guy using jedit, which made me appreciate
> the simplicity of vim's interface. In jedit, you can draw a
> thin line at 80 columns. It's not obnoxious, but is in an
> indicator where 80 columns is. You can see it in this screenshot:
>
> http://www.j
On 21/01/09 02:51, Michael O'Brien wrote:
> Hola~
>
> I was watching a guy using jedit, which made me appreciate the
> simplicity of vim's interface. In jedit, you can draw a thin line at
> 80 columns. It's not obnoxious, but is in an indicator where 80
> columns is. You can see it in this screens
On Tuesday 20 January 2009 12:37 pm, Matt Wozniski wrote:
>
> On Tue, Jan 20, 2009 at 1:03 PM, Ben Fritz wrote:
> >
> > On Jan 8, 1:19 pm, itai wrote:
> >
> >> 4. The vim help files seem to recommend against using 'autuchdir'. I
> >> use the following:
> >> autocmd BufEnter * lcd %:p:h
> >
>
Gene Kwiecinski 写道:
>> put gui-related settings in .gvimrc solves the issue. and you don't
> need
>> to test for has("gui") at all. Anyway, move non-cli things into .gvimrc
>> speeds up your cli vim startup slightly.
>
> Might work for some, but for me, personally, I don't like having to
> maint
On 21/01/09 04:33, pansz wrote:
> Gene Kwiecinski 写道:
>>> put gui-related settings in .gvimrc solves the issue. and you don't
>> need
>>> to test for has("gui") at all. Anyway, move non-cli things into .gvimrc
>>> speeds up your cli vim startup slightly.
>> Might work for some, but for me, persona
18 matches
Mail list logo
