Re: vim question
- On 3/1/06, Luis A. Florit <vim@...> wrote:
> I see. Perhaps if I replace the syntax/tex.vim in vim6.3...That should certainly work, I think.
> I installed vim6.4 in a Sun, and see how that works.
> Strange. Comments would be the very first thing I would fold.Well, I think it depends on what you're doing and on your tastes. In
most of my longer report-style documents I have no folding, but lots
of sections, subsections, etc deeply nested. I don't like the
multiple file approach (much easier to just / from within Vim when I
need to see something), which means that section folding works very
nicely for me and makes the document much easier to navigate. I don't
tend to have any comments at all.
In documents where formatting is much more of an issue I do have
comments, and lots of complicated trickery. I find it useful to fold
using markers on the start of the comment and extend it throughout the
whole following section of trickery. Makes things look much tidier.
- * El 05/03/06 a las 13:08, Gerald Lai chamullaba:
> On Sun, 5 Mar 2006, Luis A. Florit wrote:Yep, now you do. ;)
> >* El 05/03/06 a las 17:39, Luis A. Florit chamullaba:
> >>>>nmap OA <Up>
> >>>>that works fine, EXCEPT because now the O command in normal
> >>>>mode waits for a second for a 2nd key, as you said...
> >>>>So, I had to make another setting:
> >>>>set timeout timeoutlen=1000 ttimeoutlen=100
> >>>>for the O to not wait that long (1/10 sec).
> >>>A correction:
> >>>set timeout timeoutlen=1000 ttimeoutlen=100
> >>>works fine if, instead of :nmap OA <Up>
> >>>we make
> >>>set <xF2>=OA
> >>>nmap <xF2> <Up>
> Sorry, I forgot to include one detail that was 'ttimeoutlen'. The
> advantage of "encapsulating" the keycode in <xFn> like:
> set timeout timeoutlen=1000 ttimeoutlen=100
> set <xF2>=^[[a
> map <xF2> <S-Up>
> as opposed to only:
> map <Esc>[a <S-Up>
> is that <xF2> can be treated as a keycode of a single keystroke
> (within a mapping context) as opposed to a mapping of multiple
> Then setting 'ttimeoutlen' to a really small value ensures that the
> keycodes cannot (be humanly-possible but shell-possible to) be
> entered manually.
> Hope I'm making sense :)