Elliot Shank wrote:
I swear I saw something on this list about this before, but I can't find
it. If someone can point me at the prior post, I'd appreciate it.
I've got a utf-8 file with some CJK characters in it. These characters
are being displayed on the line below they are actually on.
I swear I saw something on this list about this before, but I can't find it.
If someone can point me at the prior post, I'd appreciate it.
I've got a utf-8 file with some CJK characters in it. These characters are
being displayed on the line below they are actually on.
'guifont' is set to Co
Hi all,
I have uploaded version 4.1 of the taglist plugin to the Vim online
website. You can download this version from:
http://vim.sourceforge.net/scripts/script.php?script_id=273
The taglist plugin is a source code browser plugin for Vim.
You can get more information about this plugin from:
h
":imap o o" means "add a space and delete it whenever you
insert a lowercase o in _Insert_ mode". This creates an undo point
after each lowercase o, which is probably not what you want.
See ":map-overview"
Eep! Indeed. I'm a vim newbie and I didn't RTFM properly.
Thanks!
Laurent Birtz
Laurent Birtz wrote:
Yes with these two mappings mentioned earlier in this thread,
all lines are indented after o:
:inoremap
:nnoremap o o
Got it! With these two mappings, it works correctly.
Apparently on my system (vim version 6.4, modified by Gentoo)
'
Benjamin Esham wrote:
Yakov Lerner wrote:
Laurent Birtz wrote:
When I press 'o', it starts an empty line correctly indented. If I press
'escape' immediately, the indentation is removed and the cursor moves to
column 1. If I press 'enter' instead, the indentation is removed for the
first line,
Yes with these two mappings mentioned earlier in this thread,
all lines are indented after o:
:inoremap
:nnoremap o o
Got it! With these two mappings, it works correctly.
Apparently on my system (vim version 6.4, modified by Gentoo)
':imap o o' does not wo
On 9/10/06, Benjamin Esham <[EMAIL PROTECTED]> wrote:
I get this behavior with 7.0.94, but it's done this for as long as I can
remember (I've been using Vim since 6.2, I think).
Some RedHat-8-based appliences around here have vim 6.1 :-)
Yakov
On 9/10/06, Benjamin Esham <[EMAIL PROTECTED]> wrote:
Yakov Lerner wrote:
> Laurent Birtz wrote:
>
>> When I press 'o', it starts an empty line correctly indented. If I
>> press
>> 'escape' immediately, the indentation is removed and the cursor
>> moves to
>> column 1. If I press 'enter' instead
Hi Tony,
On Sunday 10 September 2006 12:51, A.J.Mechelynck wrote:
> AFAIK both sets should be loaded. See:
>
> - BufRead and BufNewFile autocommands for the concerned file extension
> (*.c, *.cpp, *.c++, etc.)
> - FileType autocommand
> - function s:LoadFTPlugin in $VIMRUNTIME/ftplugin.vim
> - "c"
Hi Yakov,
On Sunday 10 September 2006 12:27, Yakov Lerner wrote:
> I created file ~/bat/my.dir.vim/after/ftplugin/c/xxx.vim containing line
> call input("This is after/ftplugin/c/xxx.vim>")
> and file ~/bat/my.dir.vim/after/ftplugin/cpp/cpp_xyz.vim containing line
>call input("This is after
Yakov Lerner wrote:
Laurent Birtz wrote:
When I press 'o', it starts an empty line correctly indented. If I
press
'escape' immediately, the indentation is removed and the cursor
moves to
column 1. If I press 'enter' instead, the indentation is removed
for the
first line, but the subseque
On 9/10/06, Laurent Birtz <[EMAIL PROTECTED]> wrote:
> Can you try this to see whether it does what you want ?:
> :imap
>
I get the following behavior:
When I press 'o', it starts an empty line correctly indented. If
I press 'escape' immediately, the indentation is removed and the
cur
Can you try this to see whether it does what you want ?:
:imap
I get the following behavior:
When I press 'o', it starts an empty line correctly indented. If
I press 'escape' immediately, the indentation is removed and the
cursor moves to column 1. If I press 'enter' instead, the
in
http://vim.sourceforge.net/scripts/script.php?script_id=1649
"scrollfix.vim - keep cursor at fixed visual line of window"
" This plugin, scrollfix, maintains cursor at fixed visual line of window
" (except when near beginning of file and near end of file. The
" latter is configurable. You can cho
> If you would accept using a user-command, then you could for instance define
> command -nargs=0 -count=1 -bar L call MoveByThrees()
> function MoveByThrees(count)
> let i = a:count
> while i > 0
> normal 3l
> i = i - 1
> endwhile
>
> In particular, here's a solution:
> map = :RightShift
> com! -count=1 RightShift call RightShifter()
> fun! RightShifter(cnt)
> exe "norm! ".(3*a:cnt)."l"
> endfun
That's an interesting hack, but there are a few problems with this solution:
* This only works correctly on the first line of the
Jürgen Krämer wrote:
Hi,
Yakov Lerner wrote:
How can a script test for specific patchlevel ?
For example, I have vim 7.0.86 and I need to check in the script that
patchlevel is >= 7.0.86. But v:version is 700. How ? It would be
nice if to have patchlist available through some v: variable.
you
On 9/10/06, Jürgen Krämer <[EMAIL PROTECTED]> wrote:
Hi,
Yakov Lerner wrote:
>
> How can a script test for specific patchlevel ?
> For example, I have vim 7.0.86 and I need to check in the script that
> patchlevel is >= 7.0.86. But v:version is 700. How ? It would be
> nice if to have patchlist
Hi,
Yakov Lerner wrote:
>
> How can a script test for specific patchlevel ?
> For example, I have vim 7.0.86 and I need to check in the script that
> patchlevel is >= 7.0.86. But v:version is 700. How ? It would be
> nice if to have patchlist available through some v: variable.
you can check for
On 9/10/06, A.J.Mechelynck <[EMAIL PROTECTED]> wrote:
2. This won't work if diff mode is entered after starting Vim, as
opposed to invoking it as [g]vimdiff or [g]vim -d from the command-line.
Right, but if all you use is vimdiff at shell prompt (as I do),
this is good enough and simple.
Other
On 9/10/06, A.J.Mechelynck <[EMAIL PROTECTED]> wrote:
Yakov Lerner wrote:
> On 9/10/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
>> On 9/10/06, Sven Brueggemann <[EMAIL PROTECTED]> wrote:
>> > Hello,
>> >
>> > Vim 7 combines syntax colouring and diff colouring when diffing. This
>> > often makes t
Yakov Lerner wrote:
On 9/10/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
On 9/10/06, Sven Brueggemann <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Vim 7 combines syntax colouring and diff colouring when diffing. This
> often makes the diffs hard to read.
>
> Is there a way to automagically turn syntax
Yakov Lerner wrote:
>> Vim 7 combines syntax colouring and diff colouring when diffing.
>> This often makes the diffs hard to read.
>> Is there a way to automagically turn syntax colouring off when
>> diffing?
> put this into your ~/.vimrc:
> if &diff | syntax off | endif
Now that was fast... Tha
Sven Brueggemann wrote:
Hello,
Vim 7 combines syntax colouring and diff colouring when diffing. This
often makes the diffs hard to read.
Is there a way to automagically turn syntax colouring off when diffing?
Kind regards
Sven
(Untested)
:setl syn=
:diffthis
:winc
On 9/10/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
On 9/10/06, Sven Brueggemann <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Vim 7 combines syntax colouring and diff colouring when diffing. This
> often makes the diffs hard to read.
>
> Is there a way to automagically turn syntax colouring off when d
On 9/10/06, Sven Brueggemann <[EMAIL PROTECTED]> wrote:
Hello,
Vim 7 combines syntax colouring and diff colouring when diffing. This
often makes the diffs hard to read.
Is there a way to automagically turn syntax colouring off when diffing?
put this into your ~/.vunrc:
if &diff | syntax off |
Hello,
Vim 7 combines syntax colouring and diff colouring when diffing. This
often makes the diffs hard to read.
Is there a way to automagically turn syntax colouring off when diffing?
Kind regards
Sven
On 9/10/06, Dima <[EMAIL PROTECTED]> wrote:
Hi,
I don't find a way how to make C++ indentation when all function
arguments are aligned in this way:
int TcSomeClass::SomeMethod(int arg1,
int arg2,
Meino Christian Cramer wrote:
Hi,
I often want to insert _one_ "object" only while being in normal mode
and return to normal mode as soon as possible.
My currrent edit scheme looks similiar to this:
(missing empty line in source code recognized)
either "o" or "O" pressed which throws me i
On 9/10/06, Meino Christian Cramer <[EMAIL PROTECTED]> wrote:
Hi,
I often want to insert _one_ "object" only while being in normal mode
and return to normal mode as soon as possible.
My currrent edit scheme looks similiar to this:
(missing empty line in source code recognized)
either "o"
Hi,
I don't find a way how to make C++ indentation when all function
arguments are aligned in this way:
int TcSomeClass::SomeMethod(int arg1,
int arg2,
char *arg3) {
Currenly I receive the following
Hi,
I often want to insert _one_ "object" only while being in normal mode
and return to normal mode as soon as possible.
My currrent edit scheme looks similiar to this:
(missing empty line in source code recognized)
either "o" or "O" pressed which throws me into insert mode
ESCape from ins
Marius Roets wrote:
Hi everybody,
I have a quick question regarding ftplugins. I created a directory in my
after/ftplugin directory for each filetype, with several plugins in
each. Up to now I had a directory called c, which served to hold plugins
for both c and c++ files, and this worked well.
On 9/10/06, Marius Roets <[EMAIL PROTECTED]> wrote:
Hi everybody,
I have a quick question regarding ftplugins. I created a directory in my
after/ftplugin directory for each filetype, with several plugins in
each. Up to now I had a directory called c, which served to hold plugins
for both c and c
Hi everybody,
I have a quick question regarding ftplugins. I created a directory in my
after/ftplugin directory for each filetype, with several plugins in
each. Up to now I had a directory called c, which served to hold plugins
for both c and c++ files, and this worked well. However I decided to
s
On 9/9/06, Laurent Birtz <[EMAIL PROTECTED]> wrote:
Hello,
I need help to change the default behavior of the 'autoindent' option.
The doc says:
Copy indent from current line when starting a new line (typing
in Insert mode or when using the "o" or "O" command). If you do not
type a
On 9/9/06, Laurent Birtz <[EMAIL PROTECTED]> wrote:
Hello,
I need help to change the default behavior of the 'autoindent' option.
The doc says:
Copy indent from current line when starting a new line (typing
in Insert mode or when using the "o" or "O" command). If you do not
type a
38 matches
Mail list logo
