Hi Arn :)
* Arn [EMAIL PROTECTED] dixit:
Any suggestions on keys/key combos that are good candidates for custom
mappings etc?
Maybe a dumb question but I hate having to unlearn something, I'd like
to create a fair number of mappings that use a consistent convention and
won't
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
But I'd say the F keys are the safest in general, especially when
taking portability into account.
Of course: if you plan to use more than one vim or more than one
keyboard type, the F keys are the best choice. In fact, for complex
Hi Tim :)
* Tim Chase [EMAIL PROTECTED] dixit:
Well, a year or so later, somehow that combination of my name and
Bram as a business found their way together and I just got a
magazine addressed to me at my company, Bram Moolenaar.
Holy *... That's just incredible XDDD
Hi all :)
This is not a bug report, it's just I'm curious about a behaviour
I've observed in vim, and I would like to know if this is the correct
behaviour or if some of my mappings may be causing the effect.
Let's say I have these two lines in a file:
this is one line
this
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
Is this normal? Is it caused by 'virtualedit'? I've observed this
behaviour in my own compiled version of Vim and in the packaged one
in Debian, at least, and I'm just curious.
It is normal and it has nothing to do
Hi all :)
Probably you've noticed that I'm used to indent the first line of
the paragraphs I write. I'm sooo used to do this that I'm not doing it
conciously, so I do it on comments, too.
The thing is that I've set 'fo+=2' to use the intentation from the
second line of a para, not
Hi Laurent :)
* vim [EMAIL PROTECTED] dixit:
About the wrist movement that's just as bad when you hit ESC as when
you use the arrow keys: just do the movement in slow motion for
yourself:
Yes, I've done it: the distance (in my keyboard at least) from touch
typing position to ESC and
Hi Yakov :)
* Yakov Lerner [EMAIL PROTECTED] dixit:
On 2/20/07, DervishD [EMAIL PROTECTED] wrote:
I suspect that the main reason behind the hjkl (which is very
unnatural for me, the arrows have a much better design with the
inverted T at least IMHO) was that the first keyboards used
Hi Pavel :)
* Pavel Shevaev [EMAIL PROTECTED] dixit:
On 2/21/07, DervishD [EMAIL PROTECTED] wrote:
Unfortunately, I still have problems using 'h' :(
That's my biggest problem at the moment as well, as a blind typer i
can't get used to it...oh, i think i just should stop whining
Hi Laurent :)
* vim [EMAIL PROTECTED] dixit:
The idea behind using h/j/k/l is to avoid moving your hand/wrist too
often while going back and forth between your keyboard and the arrow set
(although the use of h/j/k/l might have originated for other reasons
back in the old 'vi' days).
Hi Gene :)
* Gene Kwiecinski [EMAIL PROTECTED] dixit:
I suspect that the main reason behind the hjkl (which is very
unnatural for me, the arrows have a much better design with the
inverted
T at least IMHO) was that the first keyboards used to develop/use vi
probably hadn't arrow keys,
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
to hit the ESC and change modes fast, but I hadn't and now hitting ESC
is very unnatural to me, even though I use it in my shell to clean the
command line!.
If the Esc key is too far, you may try using Ctrl-[ instead -- Vim
sees it as
Hi all :)
I'm having a problem that I know how to solve, but I wonder if I'm
doing the right thing...
Some weeks ago I asked a couple of things about encodings on the
list, and based on the answers, I finally did a proper setup to edit
UTF-8 files from time to time in my latin1
Hi Kib :)
* kib2 [EMAIL PROTECTED] dixit:
I wonder if I can highlight more things in Python, I would like to
highlight functions call , i.e in a Python source, in the following line:
os.popen(...)
be able to highlight the word popen.
is it possible ?
Yes, it is. First, check
Hi Eric :)
* Eric Leenman [EMAIL PROTECTED] dixit:
When using vim on Linux these don't work anymore because of linux windows
managers.
Well, that's not exact: the window manager may have its key mappings
for internal use, but it's X which is managing the keyboard. If the
window
Hi Sean :)
* Sean Hubbell [EMAIL PROTECTED] dixit:
I would like to be able to shade (use the same background color, but
make it lighter) the text between two braces (spanning multiple lines
and possibly nested). What is the best way to accomplish this?
If you're already using a
Hi François :)
* François Pinard [EMAIL PROTECTED] dixit:
[DervishD]
[Bram Moolenaar]
Only a few things might need to be spread to other directories, using
symlinks when possible (binary in /usr/local/bin, libs in
/usr/local/lib, header files in /usr/local/include).
Well, I know
Hi Jiang :)
* Jiang Ting [EMAIL PROTECTED] dixit:
I am a plain vim user, mostly working on latex, C++ and fortran
programming. I began to use vim for 4 months and there are always some
technical problems around. The suggestions from the mail group may be
very helpful for me.
Given
Hi Bram :)
* Bram Moolenaar [EMAIL PROTECTED] dixit:
DervishD wrote:
I mean, that's not the point. The point is that the source code is
using hardcoded directories, and that is not a good practice, even if
you force to have all runtime files under the same directory, because
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
Bram Moolenaar wrote:
[...]
I don't see how getting rid of hardcoded directories in the source
code is going to cause problems for users ;) In fact, hardcoded
directories may cause problems: if you modify src/Makefile and don't
Hi Bram :)
* Bram Moolenaar [EMAIL PROTECTED] dixit:
DervishD wrote:
Given that /usr/doc or /usr/share/doc are pretty standard when
it comes to install documentation, shouldn't ex_helpgrep use the
directory from helpfile too, just like :help does?
Vim documentation must
Hi Bram :)
* Bram Moolenaar [EMAIL PROTECTED] dixit:
DervishD wrote:
Don't take me wrong: I'm not critisizing Bram's amazing work with
Vim, and I'm not asking for this to be fixed. What I really mean is
that Vim will be more flexible if it doesn't have that hardcoded paths
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
I've discovered that :helpgrep pattern doesn't work for me, always
returning E480 (BTW, :help E480 shows help about argdelete, as if
E numbers in source code and docs weren't synchronized).
But that's
Hi all, specially Bram :)
The source code for vim is full of hardcoded directories,
rendering useless the constants defined in src/Makefile. Moreover, it
doesn't use configure values to establish locations, but that's a
minor problem. The major problem is that this scheme breaks LSB for
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
That won't work, because docs are not in /usr/doc/vim/doc, but in
/usr/doc/vim. Otherwise it would work. On my system, documentation is
under /usr/share/doc/packagename (the share part is variable, since
I maintain
Hi all :)
I've discovered that :helpgrep pattern doesn't work for me, always
returning E480 (BTW, :help E480 shows help about argdelete, as if
E numbers in source code and docs weren't synchronized).
But that's not the weird part. If I search for a very common word
(let's say most,
Hi Andy :)
* Andy Wokula [EMAIL PROTECTED] dixit:
DervishD schrieb:
That is, the contained item is swallowing part of the start
match!. I thought that when the match for start was performed, the
matched test wasn't tried for any other match, including contained
items. Obviously, I
Hi all :)
Another weird question O:)
Let's suppose that I search frequently for a very complex pattern.
This is easy to do using a keymap, for example. But let's assume that I
also search frequently using the same pattern preceded by an arbitrary
char *AND* followed by the same char.
Hi Tony :)
Once more, Antoine came to the rescue :)) You're great, dude :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
In Perl I would store the complex pattern in some scalar, but I
don't know how to do it in VimL. Probably it can be done with let
and eval
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
[...]
Tony, again you've not only solved my doubt, but gave me an
important lesson about VimL. I owe you yet another one. I just hope
someday I will be able to return at least part of your kindness with me.
I
Hi all :))
I'm trying to fully understand the syntax commands, and when doing
tests a question popped up in my mind: let's say I have a region which
starts with something like \I\i*{ and ends with }. For example, the
example below will match:
strange{contents}
BUT, the below
Hi all :)
* DervishD [EMAIL PROTECTED] dixit:
That is, the contained item is swallowing part of the start
match!. I thought that when the match for start was performed, the
matched test wasn't tried for any other match, including contained
items. Obviously, I was wrong (or I
Hi Ralf :)
* Ralf Schmitt [EMAIL PROTECTED] dixit:
I'm a bit confused about the hlsearch feature of v7.
In my .vimrc I set set nohlsearch to disable highlighting
of search results on startup.
This way, you've effectively turned off search highlighting, no
matter of :nohl command.
Hi all :))
I've noticed something weird regarding IncSearch and I don't know if
the problem is that I've set up my colors badly or that just I don't
understand how the highlight command works. My terminal is 8 colors.
If I set my IncSearch highlight group to something like this:
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
I don't want such cluttering, either. My idea is to have the
following:
- A 'vimrc' that just sources 'modules' (right now my vimrc does
little except sourcing 'options.vim', 'mappings.vim' and a couple more
Hi Tony :)))
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
I would like to have configuration data, syntax rules and indent
functions for a filetype together in just one file because this way is
much more easy to maintain for me (long story). Apart from the obvious
Hi all :))
I've found a bug in Vim 7.0 (doesn't seem to be mentioned in any
patch up and including 188.
When I issue syntax spell default, it results in the following
error: E390: Illegal argument: default. I've took a look at the help
for E390 and it seems to be an error for syntax
Hi all :)
I would like to have configuration data, syntax rules and indent
functions for a filetype together in just one file because this way is
much more easy to maintain for me (long story). Apart from the obvious
disadvantage that having all together in a file makes impossible to
Hi Guido :)
* Guido Van Hoecke [EMAIL PROTECTED] dixit:
I think I'll follow the advices from Salman Halim and Kim Schulz and
I'll subscribe to vim tips using the RSS feed and will report the number
I have no problems to add the vim scripts rss feed to my firefox live
bookmarks by
Hi Salman :)
* Halim, Salman [EMAIL PROTECTED] dixit:
Spam in comments can also be addressed by moderators as of fairly
recently. When you come across such a comment, you can mark the
comment as spam, leaving the rest of the tip and comments alone.
While you are correct that you may not
Hi Yongwei :)
* Yongwei Wu [EMAIL PROTECTED] dixit:
On 1/18/07, DervishD [EMAIL PROTECTED] wrote:
Did you set 'fileencodings' to an empty string? Otherwise this would
not work.
Apart from fixing the above (including the last version I posted
here, which has a catch, yes, I have
Hi Yongwei :)
* Yongwei Wu [EMAIL PROTECTED] dixit:
* Yongwei Wu [EMAIL PROTECTED] dixit:
On 1/18/07, DervishD [EMAIL PROTECTED] wrote:
Did you set 'fileencodings' to an empty string? Otherwise this would
not work.
Apart from fixing the above (including the last version I
Hi Bram :)
* Bram Moolenaar [EMAIL PROTECTED] dixit:
utf-8 is a superset of latin1, thus using utf-8 for 'encoding'
should nearly always work.
Except that then I have to encode my 'showbreak' option as utf8 and
not latin1 :( I prefer to have it encoded as latin1 (as the rest
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
If I change 'enc', I see 'á', correctly.
You should do :edit ++enc=utf-8 filename or include utf-8 in
'fileencodings' before editing the file. Then it will work no matter
what 'encoding' is set to.
But then my
Hi all, and sorry for self-replying...
* DervishD [EMAIL PROTECTED] dixit:
I want to edit/view utf8 files *and* I don't want new files or
US-ASCII files to be considered utf8, my best bet is to use
BufReadPre to detect utf8 files using file -i or something
similar, thus forcing
Hi Stavros :)
* Stavros Tsolakos [EMAIL PROTECTED] dixit:
I am editing a text file with vim7. I set tw=80 and it works for any
text I write AFTER setting it. But how could I force vim reformat my
whole text file so that all lines obey to the new textwidth?
There is probably a
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
Notice the dash between utf and 8.
My bad, I typed carelessly. It succeeded on my system because I did
my first test with a file *named* 'utf8'. I've noticed the problem a
moment ago, and it's already fixed.
Hoho... Then maybe
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
Notice the dash between utf and 8.
My bad, I typed carelessly. It succeeded on my system because I did
my first test with a file *named* 'utf8'. I've noticed the problem
Hi all :)
I've noticed that there are still spam in the Tips comments at the
vim website. Bram, do you need help with that? If you want, I can take a
look at the comments and delete any spam I catch. I don't know how much
spare time I'll have, but even with ~1500 tips, it shouldn't take
Hi Bram :)
* Bram Moolenaar [EMAIL PROTECTED] dixit:
DervishD wrote:
I've done the following autocommand to perform the detection:
autocmd BufReadPre *
\ if system(file -i . expand(amatch)) =~ utf8 |
\ setlocal fenc=utf8 |
\ endif
I'm sure
Hi Bram :)
* Bram Moolenaar [EMAIL PROTECTED] dixit:
DervishD wrote:
I've noticed that there are still spam in the Tips comments at the
vim website. Bram, do you need help with that? If you want, I can take a
look at the comments and delete any spam I catch. I don't know how
Hi Salman :)
* Halim, Salman [EMAIL PROTECTED] dixit:
While I'm not in a position to determine who gets to moderate tips, I
would like to request that if anybody sees spam while looking through
a tip and decides to mention it, please include the tip number(s) so a
moderator can go in and
Hi Kim :)
* Kim Schulz [EMAIL PROTECTED] dixit:
On Wed, 17 Jan 2007 20:46:30 +0100
DervishD [EMAIL PROTECTED] wrote:
I've noticed that there are still spam in the Tips comments at the
vim website. Bram, do you need help with that? If you want, I can
take a look at the comments
Hi all :))
So far I've picked:
1473,1471,1461,1460,1459,1457,1452. At least some of them have been
already deleted.
About the spam in tips' comments, that's another issue.
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
It's my PC
Hi Bram :)
* Bram Moolenaar [EMAIL PROTECTED] dixit:
DervishD wrote:
After that, I've set up this mappings to switch manually from
one encoding to other:
noremap silent Leader+ :setlocal fenc=utf8 enc=utf8CR
noremap silent Leader- :setlocal fenc=latin1 enc=latin1CR
Hi Bram :)
* Bram Moolenaar [EMAIL PROTECTED] dixit:
DervishD wrote:
Keep in mind that when you change 'encoding' in a running Vim then all
text in loaded buffers, registers, variables, etc. will become
invalid. It's better to only set 'encoding' when starting up and then
leave
Hi Klaus :)
* Klaus Ethgen [EMAIL PROTECTED] dixit:
I think that question was asked many time before but with differed
direction but maybe there is someone having a answer. (I found some for
the other direction not for mine.)
I asked more or less the same a few days ago, you can see
Hi Jean Rene :)
* Jean-Rene David [EMAIL PROTECTED] dixit:
* DervishD [2007.01.12 07:45]:
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
[...]
Beware of ' and ` though: they are used in
Normal mode for mark movements.
Yes, but both keys do the same, so I'm on
the safe side
Hi Tim :)
* Tim Chase [EMAIL PROTECTED] dixit:
Yes, ñ or ç would be good. Beware of ' and ` though: they are used in
Normal mode for mark movements.
Yes, but both keys do the same, so I'm on the safe side if I choose
only one of them, am I wrong?
They do similar, but not
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
:scriptencoding applies no farther than the end of the current script.
And does it affect sourced scripts or should I put that line in all
scripts?
It doesn't affect sourced scripts. Each script should include or not
include
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
[...]
As long as your vimrc includes only 7-bit ASCII, there's no problem. But
in the particular case of your vimrc, you could add the following lines
at top, do :setlocal
Hi Tim :)
* Tim Chase [EMAIL PROTECTED] dixit:
\ is hard to type in my keyboard (spanish) because I'm forced to
press Alt-Gr plus the top left key in the keyboard (just below ESC), so
I'm looking for a good substitute for the leader: do you know where
could I find free characters to
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
* Matthew Winn [EMAIL PROTECTED] dixit:
The Leader defaults to \ on some installations, I believe.
\ is the default value, and that's the value used if mapleader is
empty. It's a bad idea to set mapleader to , unless you have a
Hi Scot :)
* Scot Becker [EMAIL PROTECTED] dixit:
Try removing both the
set encoding and
set fileencoding lines.
And see if it does what you want.
It should do latin1 still by default (based on your system settings),
and still let you see utf files. If that fails, leave the 'set
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
My system is latin-1, so I want my files written using latin-1
encoding. But sometimes I get files in utf8 encoding, so I set up my vim
like this:
set encoding =latin1
set fileencoding =latin1
set
Hi Matthew :)
* Matthew Winn [EMAIL PROTECTED] dixit:
The Leader defaults to \ on some installations, I believe.
\ is the default value, and that's the value used if mapleader is
empty. It's a bad idea to set mapleader to , unless you have a
keyboard where \ is hard to type, as , is
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
Your problem lies in the relation between UTF-8, Latin1 and US-ASCII.
Characters 0x00 to 0x7F are represented identically in all three,
therefore if a file contains only 7-bit ASCII characters, it won't make
any difference whether
Hi all :)
My system is latin-1, so I want my files written using latin-1
encoding. But sometimes I get files in utf8 encoding, so I set up my vim
like this:
set encoding =latin1
set fileencoding =latin1
set fileencodings =ucs-bom,utf-8,latin1
This last line is causing
Hi Redoute :)
* Redoute [EMAIL PROTECTED] dixit:
DervishD wrote:
Any way of working around this problem?
%{char2nr(getline('.')[col('.')-1])}
works for me.
Thanks! I've modified it a bit, because I wanted the number as hexa
and always with the same width, using printf:
set
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
Hi Tony :)
:-) Olá Raúl
It's Hola, but thanks for the nice gesture :)
So really it is a bug and not a feature. Again, thanks :)
IMHO, I said. Bram has the final say, not me.
Of course
Hi Viktor :)
* Viktor Kojouharov [EMAIL PROTECTED] dixit:
With the upgrade to vim 7, I am no longer able to navigate in insert
mode with the arrow keys. This happens in any terminal. In gvim, they
work fine. Instead of moving the cursor, the arrow keys do something
like pressing O in
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
Of course, but given that even in the GUI version the problem
happens (I thought that the bar was in between characters, and not at
the 25% leftmost position), I'm inclined to think it is a bug and not a
feature
Hi Viktor :)
* Viktor Kojouharov [EMAIL PROTECTED] dixit:
On 1/3/07, DervishD [EMAIL PROTECTED] wrote:
* Viktor Kojouharov [EMAIL PROTECTED] dixit:
With the upgrade to vim 7, I am no longer able to navigate in insert
mode with the arrow keys. This happens in any terminal. In gvim
Hi all, and happy new year!
I have %B in my status line, but it doesn't work in insert mode,
only on normal and visual mode. At first I thought that the status line
wasn't being evaluated while in insert mode, but the line and column
numbers change correctly, so it *is* being evaluated,
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
I have %B in my status line, but it doesn't work in insert mode,
only on normal and visual mode. At first I thought that the status line
wasn't being evaluated while in insert mode, but the line and column
numbers
Hi Manu :)
* Manu Hack [EMAIL PROTECTED] dixit:
It works in Vim7 on WinXP but not on *nix (I tried solaris and linux).
On *nix, it just stopped until I press c-q. Why was it happened?
Usually, under UNIX, the c-s combination stops the TTY and c-q
resumes it. For example, under Linux
Hi Bill :))
* Bill McCarthy [EMAIL PROTECTED] dixit:
On Thu 30-Nov-06 2:26pm -0600, DervishD wrote:
I want to be able to NOT load the plugins in my system-wide runtime
directory, and instead loading my own set of plugins, and only
those. So far, I know that set noloadplugins will do
Hi all :)
I would like to share the same .vimrc for vim and view, so I can
use view as a pager without having to use -u in the command line. So
far, I've thought that the only way of knowing if I'm under vim or
view mode is to check the value of readonly. Not perfect, but it
will do.
Sorry for resending, I have had problems with email and I'm not sure
if this message made its way into the list. If it is repeated, please
ignore O:
Hi all :)
I want to be able to NOT load the plugins in my system-wide runtime
directory, and instead loading my own set of plugins,
Hi Tony :)
* A.J.Mechelynck [EMAIL PROTECTED] dixit:
DervishD wrote:
[...]
I'm pretty sure that my keyboard driver will feed keys faster
than 1 per 100 milliseconds (that's my ttimeoutlen setting right
now), and although I'm a fast typer, probably 100 will be too fast
for me
Hi all :)
First of all, please excuse if what I'm going to ask sounds
stupid, but I have been using vim for less than a week, so I'm afraid
I'm not very proficient with it ;)
Well, I've done this mapping to be able to jump to the next tag
in the help file using TAB:
:nnoremap
Hi Benji :)
* Benji Fisher [EMAIL PROTECTED] dixit:
On Wed, Nov 22, 2006 at 02:04:29PM +0100, A.J.Mechelynck wrote:
DervishD wrote:
[snip]
I want to do something like that in my vimrc.
delete_all_keys if at all possible
map i i yes, I want to go to insert
82 matches
Mail list logo
