Dear Vim Devel Mailing list,
Some suggestions for Vim IMprovement.
1. When using the % alias as the file you are editing... you are able to do
things like: :!echo % in vi to show you the path and file of what you are
currently editing. But, this will not give you the absolute path of
things. if you're in your home directory and type "vi .vimrc" then do the
echo thing, it's "full path" will be ./.vimrc instead of
/usr/home/ronnie/.vimrc or whatever. How about a fullpath alias something
other than %? Or maybe a .vimrc flag to set that % to mean its absolute
path, etc.
A quick workaround in Perl until this is maybe fixed for anyone interested:
#!/usr/bin/perl
use strict;
use Cwd qw(realpath);
my $in_path = $ARGV[0];
if ( ! $in_path) {
$in_path = '.';
}
if ( -e $in_path ) {
print realpath($in_path);
print "\n";
}
Interface that with Vim and you should be okay for a while...
2. Annoyance: When you use the % key in Vim to go to the matching bracket
on the cursor, it takes into account commented out brackets that vim
clearly knows are commented out due to the syntax highlighting. If it could
ignore these brackets then life would be grant! Perhaps it's a togglable
flag already? I don't know... On the other side of the coin, if you are
pressing % on a commented comment, maybe it would go to its other bracket
commented counterpart.
3. Perl's =cut pod comments work half the time in Vim's syntax
highlighting. You have to hit pgup and pgdown quickly to "jerk" the syntax
highligting color into shape. Usually when the problem occurs, it comments
the rest of the entire text till EOF after the start of the first =cut
comment.
4. Somehow a toggle option so that when you exit out of insert mode, it
doesn't automatically move the cursor to the left. Press i, esc, i, esc,
etc etc to see what I mean. Obviously, it was meant for a reason and it's
not a bug, but I believe I could get used to Vim much better without that
behaviour. If you could toggle it...
5. Ever used Vim in a putty window, and pasted a giant section of code
after hitting insert when you accidently left "auto-indent" on? The pasted
text is all screwed up cause of the tabs and such. Of course, you have to
hit undo, toggle the auto-indent, then repaste it. But I make this mistake
so often... that maybe it could have an intelligent input buffering system
that can tell how fast you're typing and it knows right away that you're
pasting text, and to turn off the auto-indent (if you tell your .vimrc to do
so)? This one is a long shot, but I believe this would make a lot of
programmers happy. My coworkers agree with me on this one.
Just throwing those out there. Any comments? Thanks
--
smu johnson <[EMAIL PROTECTED]>
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
