On Sat, Feb 11, 2012 at 4:00 AM, tsai wrote:
> Hi everyone,
>
> After installing Cygwin, where is the default location of the .vimrc file so
> I can augment it? Kind of confusing. I know on my Linux box, it is hidden in
> the home directory and a simple ls -la will list it. That isn't happening in
In the cobol.vim file, something causes all sentences starting
with "if" to be colored red just like an error. The "if" verb is
perfectly legitimate in COBOL, I have used it since 1968.
Will someone who reads and understands vim files please tell me
which line or lines to change? The way it is n
On Mon, Feb 13, 2012 at 7:11 PM, Chris Lott wrote:
> Is there a more efficient or better way to cluster together a set of
> autocommands in my .vimrc? For instance, I have the following:
>
> au BufNewFile,BufRead *.mtxt setlocal filetype=pandoc
> au BufNewFile,BufRead *.mtxt setlocal spell
> au Bu
Is there a more efficient or better way to cluster together a set of
autocommands in my .vimrc? For instance, I have the following:
au BufNewFile,BufRead *.mtxt setlocal filetype=pandoc
au BufNewFile,BufRead *.mtxt setlocal spell
au BufNewFile,BufRead *.mtxt setlocal equalprg=pandoc\ -t\ markdown\
* Leonardo Barbosa [2012-02-13 20:21]:
> I have some mappings in my .vimrc. However, some of them only
> work if I re-source my .vimrc after I have opened the file to
> edit. What might be happening? Is there a way of automatically
> resource the .vimrc everytime I open i file with vim?
"the gl
On Mon, Feb 13, 2012 at 18:01, Jürgen Krämer wrote:
>> Thanks. Where is the set ruf line code documented? I figured out that
>> the leading %40 means forty characters' width, but I would really like
>> to see where this syntax is documented.
>
> :help ruf
>
> From there you are referred to
>
> :
On Feb 13, 9:46 am, Taylor Hedberg wrote:
> Leonardo Barbosa, Mon 2012-02-13 @ 13:32:42-0200:
>
> > I have some mappings in my .vimrc. However, some of them only work if
> > I re-source my .vimrc after I have opened the file to edit. What might
> > be happening?
>
> My guess would be that you ha
Hi,
Dotan Cohen wrote:
> On Mon, Feb 13, 2012 at 17:23, Andy Wokula wrote:
>> Not sure how useful that is, but 'ruler' can be customized with
>> 'rulerformat':
>>:set ls=0 ru
>>:set ruf=%40(%n/%{bufnr('$')}\ %f%)
>>:h 'ruf
>>
>> only useful with one window at a time, looks like above
On Mon, Feb 13, 2012 at 17:23, Andy Wokula wrote:
> Not sure how useful that is, but 'ruler' can be customized with
> 'rulerformat':
> :set ls=0 ru
> :set ruf=%40(%n/%{bufnr('$')}\ %f%)
> :h 'ruf
>
> only useful with one window at a time, looks like above ruler only shows the
> buffer num
Leonardo Barbosa, Mon 2012-02-13 @ 13:32:42-0200:
> I have some mappings in my .vimrc. However, some of them only work if
> I re-source my .vimrc after I have opened the file to edit. What might
> be happening?
My guess would be that you have an ftplugin script for the filetype
you're working with
Hi,
I have some mappings in my .vimrc. However, some of them only work if
I re-source my .vimrc after I have opened the file to edit. What might
be happening? Is there a way of automatically resource the .vimrc
everytime I open i file with vim?
Best,
Leo
--
You received this message from the
Am 13.02.2012 09:10, schrieb Dotan Cohen:
On Mon, Feb 13, 2012 at 00:12, Taylor Hedberg wrote:
I believe it's just called the "command line", and there's not that much
you can configure about it, other than controlling how many lines it
takes up and setting 'showcmd' so it shows normal-mode com
Dotan Cohen, Mon 2012-02-13 @ 10:10:21+0200:
> I want to have it always show the filename, the buffer number, and the
> amount of open buffers. I seems wasteful to me to put that info on the
> statusline and then take up another valuable vertical line.
I don't think that's possible. The job of the
Hi all,
I'm using VIM to indent a Fortran code. My problem is that VIM indent the
proprecessor directives too. This causes errors in compilation.
Do you know how can avoid to indent the lines starting with # ?
The following is my .vimrc file:
set nocompatible
set mouse=a
set hidden
set viminfo+=
Hi all,
I'm using VIM to indent a Fortran code. My problem is that VIM indent the
proprecessor directives too. This causes errors in compilation.
Do you know how can avoid to indent the lines starting with # ?
The following is my .vimrc file:
set nocompatible
set mouse=a
set hidden
set viminfo+
On Sun, Feb 12, 2012 at 11:48:43PM +0200, Dotan Cohen wrote:
> In the final line of my terminal window in VIM I have a line that
> serves several purposes:
> [...]
> How is this line called, and how is it configured? I tried to
> configure the status line, but adding laststatus=2 to .vimrc makes
>
Hi,
howardb21 wrote:
>
> On Feb 5, 11:35 pm, Jürgen Krämer wrote:
>> Hi,
>>
>> howardb21 wrote:
>>> On Feb 2, 10:26 pm, J rgen Kr mer wrote:
>>
There are also [ic]noreabbrev variants which would prevent the
right-hand-side of an abbreviation to be re-used as the left-hand-side
o
On Mon, Feb 13, 2012 at 00:12, Taylor Hedberg wrote:
> I believe it's just called the "command line", and there's not that much
> you can configure about it, other than controlling how many lines it
> takes up and setting 'showcmd' so it shows normal-mode commands as you
> type them. What did you
18 matches
Mail list logo
