vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project

Re: [Vim-latex-devel] some questions about main.vim

[Srinath A. <sr...@fa...>]

> Why is silent used only in has('gui')?
>
When I try to execute a <silent> command like ":silent !latex %" or such
from within a console vim, my vim display gets overwritten by the
display of the commanad. (I tested this using the console vim which
ships with cygwin) I then have to press <C-l> to get back... A newbie
might get into a total panic if something like that happens... With gvim
ofcourse, a seperate window is spawned... Doesn't this problem occur
with console vim's in *nix?

On Thu, 9 Jan 2003, Benji Fisher wrote:

> 2. Does the comment about compiler/tex.vim mean that ":compiler tex" was
> tried and did not work?

I haven't tried this in a long while... Let me see... No ":compiler tex"
doesn't seem to work. I haven't looked into this in a while. Maybe our
compiler/tex.vim needs to set some global variable so vim's compiler
doesn't overwrite ours... It looks like ":compiler tex" does source our
compiler/tex.vim but also vim's compiler/tex.vim...

Srinath

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

[Charles B. <bon...@ma...>]

Thanks for your prompt responses. 

I believe the \ll and \lv problems were due to an interaction
with auctex.vim that I had in my /.vim/ but had forgotten
about.  Since removing auctex.vim, the problem is gone.

One bug: The documentation says that "SPG" gives a \paragraph,
but "SPR" does.

Two suggestions:
1) add the following line to main.vim to give \sum (which I
use a lot and a macro can save lots of typing)

call IMAP (g:Tex_Leader.'M', "\\sum_{<++>}^{<++>}<++>", 'tex')

(an "M" is a rotated sigma).

2) add the reformat paragraph macro from auctex.vim (lines 604-625).

One comment: The output of \ll is confusing.  It took me awhile to
figure out how to continue editing without exiting the editor. I would
prefer to continue to see my file in a window (\ll was opening up my
.bbl file which it thought was in error--and it wasn't). This problem
may be unavoidable due to complexities within vim, but it is confusing
when first presented.

Thanks again.  If I find any more bugs or suggestions, I'll let
you know.

	Charlie Boncelet


On Wed, 2003-01-08 at 16:30, Benji Fisher wrote:
> Charles Boncelet wrote:
> > As for your suggestion:
> > 
> > :map \ll
> > No mapping found.
> > 
> > I'm using gvim 6.1.  Yes, I was unclear.  I can type
> > the letters :-), but nothing happens when I do.  
> > 
> > I did what I thought was a correct install.  Now
> > I have some idea what's wrong (no mapping found).
> > 
> > Thanks,
> > 	Charlie Boncelet
> 
>       Maybe you have set mapleader?
> 
> :echo mapleader
> 
> (If it is undefined, you will get an error message.  If it is defined, 
> try using its value instead of "\".)  Maybe you have a terminal-only vim?
> 
> :echo has("gui")
> 
> (I do not know why, but these maps are only defined if this returns 1, 
> true.  We should probably change this...)  Maybe the right files are not 
> being sourced?  (Unlikely, since you said the menu works.)
> 
> :scriptnames
> 
> and look for something line .../ftplugin/latex-suite/main.vim .
> 
> HTH					--Benji Fisher
-- 
Charles Boncelet <bon...@ec...>
University of Delaware

[Vim-latex-devel] some questions about main.vim

[Benji F. <be...@me...>]

      Near the end of latex-suite/main.vim we have the following lines:

" viewing/searching
if !hasmapto('RunLaTeX')
	if has("gui")
	nnoremap <buffer> <Leader>ll :silent! call RunLaTeX()<cr>
	nnoremap <buffer> <Leader>lv :silent! call ViewLaTeX()<cr>
	nnoremap <buffer> <Leader>ls :silent! call ForwardSearchLaTeX()<cr>
	else
		nnoremap <buffer> <Leader>ll :call RunLaTeX()<cr>
		nnoremap <buffer> <Leader>lv :call ViewLaTeX()<cr>
	nnoremap <buffer> <Leader>ls :call ForwardSearchLaTeX()<cr>
	end
end
" This line seems to be necessary to source our compiler/tex.vim file.
" The docs are unclear why this needs to be done even though this file
" is the first compiler plugin in 'runtimepath'.
	runtime compiler/tex.vim

(I changed the indent for e-mail readability.)

1. Why do we use :silent! only under :if has("gui")?
2. Does the comment about compiler/tex.vim mean that ":compiler tex" was 
tried and did not work?

					--Benji

Re: [Vim-latex-devel] Screw up!

[Srinath A. <sr...@fa...>]

Releif sweeps over me in waves :) (Is that a cheesy dialogue or what?!)

Thank $DIETY for small (in this case HUGE) mercies!

Here's an amusing story I will bore you with... Well, the latest commit
on the imaps.vim branch was an attempt to put a cvs 'keyword'.
Unfortunateley, I screwed up and put $Header: $ instead of $Header$.
Therefore, I got the bright idea of outdating the latest version and
recommiting the correct one so that the version history of imaps.vim
doesn't contain this faulty commit.

Now most cvs commands use ':' as an abbreviation for 'the latest
revision'. For example,

cvs admin -m :"`cat /tmp/log.txt`" imaps.vim

changes the log message of the last revision of imaps.vim...

I assumed 'cvs admin -o' also performed the same way. BIG MISTAKE!!! BIG
BIG MISTAKE!!! For 'admin -o', ':' is the same as "1:last" ARGH!!!

So as soon as I gave that command, I saw this:

~/testing/latex-suite/vimfiles/plugin > cvs admin -o : imaps.vim
RCS file: /cvsroot/vim-latex/vimfiles/plugin/imaps.vim,v
deleting revision 1.26
deleting revision 1.25
deleting revision 1.24
deleting revision 1.23
deleting revision 1.22
deleting revision 1.21
deleting revision 1.20
deleting revision 1.19
deleting revision 1.18
deleting revision 1.17
deleting revision 1.16
deleting revision 1.15
deleting revision 1.14
deleting revision 1.13
deleting revision 1.12
deleting revision 1.11
deleting revision 1.10
cvs server: /cvsroot/vim-latex/vimfiles/plugin/imaps.vim,v: can't remove branch point 1.9
cvs server: RCS file for `imaps.vim' not modified.

Well, after a minute or 2 of hectic pacing, I saw the last line...
Imagine my releif!!!!

So well, it looks like I learnt the lesson the easy way... Just a big
scare thats all....

More later!

Srinath

On Wed, 8 Jan 2003, Srinath Avadhanula wrote:

>
> I did a huge mistake while doing an admin job on the repository. I have
> just deleted versions 1.10 - 1.26 of imaps.vim!!! :(((
>
> Please wait for a while I go through the cvs logs and restore imaps.vim
> to the latest value.
>
> I also promise that I will _NEVER_ do a 'cvs admin' again. A lesson
> really badly learnt.
>
> Sorry,
>
> Srinath
>
>
>
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>

[Vim-latex-devel] Screw up!

[Srinath A. <sr...@ee...>]

I did a huge mistake while doing an admin job on the repository. I have
just deleted versions 1.10 - 1.26 of imaps.vim!!! :(((

Please wait for a while I go through the cvs logs and restore imaps.vim
to the latest value.

I also promise that I will _NEVER_ do a 'cvs admin' again. A lesson
really badly learnt.

Sorry,

Srinath

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

[Benji F. <be...@me...>]

Charles Boncelet wrote:
> As for your suggestion:
> 
> :map \ll
> No mapping found.
> 
> I'm using gvim 6.1.  Yes, I was unclear.  I can type
> the letters :-), but nothing happens when I do.  
> 
> I did what I thought was a correct install.  Now
> I have some idea what's wrong (no mapping found).
> 
> Thanks,
> 	Charlie Boncelet

      Maybe you have set mapleader?

:echo mapleader

(If it is undefined, you will get an error message.  If it is defined, 
try using its value instead of "\".)  Maybe you have a terminal-only vim?

:echo has("gui")

(I do not know why, but these maps are only defined if this returns 1, 
true.  We should probably change this...)  Maybe the right files are not 
being sourced?  (Unlikely, since you said the menu works.)

:scriptnames

and look for something line .../ftplugin/latex-suite/main.vim .

HTH					--Benji Fisher

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

[Srinath A. <sr...@fa...>]

On Wed, 8 Jan 2003, Charles Boncelet wrote:

> As for your suggestion:
>
> :map \ll
> No mapping found.
>

Okay then, what does

:echo mapleader

say? If it echoes some character other than \, then you will need to use
that. For example, if it says `, then use `ll and `lv. But its very
strange that you would have mapleader set to something else without
knowing about it...

HTH

Srinath

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

[Charles B. <bon...@ma...>]

As for your suggestion:

:map \ll
No mapping found.

I'm using gvim 6.1.  Yes, I was unclear.  I can type
the letters :-), but nothing happens when I do.  

I did what I thought was a correct install.  Now
I have some idea what's wrong (no mapping found).

Thanks,
	Charlie Boncelet

On Wed, 2003-01-08 at 15:44, Benji Fisher wrote:
> Charles Boncelet wrote:
> > I just downloaded and installed latex-suite.  Very impressive,
> > thanks.
> > 
> > For the life of me, however, I can't figure out how to input
> > the "\ll" and "\lv" commands to compile and view.  The menu
> > works, just not the keystrokes.
> > 
> > Thanks,
> > 	Charlie
> 
>       If you are in Normal mode (not Insert mode), just tyoe the three 
> characters.  If you use TeX, you must know where the find the "\" 
> character on your keyboard!
> 
>       Are you using eVim ("easy" vim, or with 'insertmode' set)?  If so, 
> you can use <C-L> or <C-\><C-N> to get to Normal mode, or <C-O> to do so 
> for just one command.  If not, what does vim tell you when you type
> 
> :map \ll
> 
> ?
> 
> HTH					--Benji Fisher
-- 
Charles Boncelet <bon...@ec...>
University of Delaware

Re: [Vim-latex-devel] help needed with \ll and \lv shortcuts

[Benji F. <be...@me...>]

Charles Boncelet wrote:
> I just downloaded and installed latex-suite.  Very impressive,
> thanks.
> 
> For the life of me, however, I can't figure out how to input
> the "\ll" and "\lv" commands to compile and view.  The menu
> works, just not the keystrokes.
> 
> Thanks,
> 	Charlie

      If you are in Normal mode (not Insert mode), just tyoe the three 
characters.  If you use TeX, you must know where the find the "\" 
character on your keyboard!

      Are you using eVim ("easy" vim, or with 'insertmode' set)?  If so, 
you can use <C-L> or <C-\><C-N> to get to Normal mode, or <C-O> to do so 
for just one command.  If not, what does vim tell you when you type

:map \ll

?

HTH					--Benji Fisher

[Vim-latex-devel] help needed with \ll and \lv shortcuts

[Charles B. <bon...@ma...>]

I just downloaded and installed latex-suite.  Very impressive,
thanks.

For the life of me, however, I can't figure out how to input
the "\ll" and "\lv" commands to compile and view.  The menu
works, just not the keystrokes.

Thanks,
	Charlie
-- 
Charles Boncelet <bon...@ec...>
University of Delaware

[Vim-latex-devel] Re: imaps, version of 3rd jan 2003

[Luc H. <her...@fr...>]

* On Tue, Jan 07, 2003 at 06:42:42PM -0800, Srinath Avadhanula <sr...@fa...> wrote:
> > I will check it. Does it works even when the cursor is within a
> > placeholder boundaries ? [my last conclusions was that I need to
> > call searchpair twice]
> It does work... If you are in the middle of a placeholder and press
> <C-j> it will goto the next placeholder. <C-K> selects the placeholder
> you are current in...

I like your idea of using "'<" with visual mappings. And regarding the
fact the backward-search jumps to the current PH instead of the previous
one is not completly illogical. I will eventually simplify my code to
adopt your way.

> > [not silent mapping]
> > Set 'cmdheight' to 2 or more to see the echoing.
> Hmm... I dont see anything on the commandline even with cmdheight = 2.
> Dunno... Maybe I'll randomly add a <silent> next time...

That's odd. Things have changed since the 3rd january version and the
1.24. Now, it is all right. 


> > What makes the inclusive search so different and required ?
> Well, here's the comment in the latest imaps.vim
> [...]

I see. Thanks.

> > I will eventually have to make many experiments in order to be able to:
> > - let ftplugins change the values of opening and closing string
> > - let ftplugins encoded in latin1, utf-8, etc
> > - be compatible with any encoding of fileencoding for the current
> >   buffer/file.
> Benji has spent time on this and I think we have a working system right
> now to do all of this. We have even thought of things like "what if the
> placeholder setting was done in a file with 'fenc' different from the
> tex file which the user is editing?" So if you want, you might want to
> see whats done here.

I've seen his function just after I've written an equivalent one. Now,
I'd curious to have some input from people using encodings other that
latin1 or utf-8.

> [multi-line PH]
> > I'm skeptical about their usefulness (English ?). When we need long
> > tags/comments, I'd rather use a templates plugin like the one
> > written by Robert "Feral" Kelly.
> Well, even if we have some other ways of generating templates, I would
> be very reluctant to have another function do the actual jumping between
> placeholders.  Code duplication! 
>
> Does this templates plugin offer something different?  

FTE (the plugin) serves a different purpose ; it has nothing to do with
jumping.

I see multi-line PH as an helper to the end-user who has just inserted a
template (from a file or from IMAP(), or ...). If the text is really
long and explain many things, I'm not sure PHs are the best things to
use. I see them more as markers where we will jump to and we will
eventually replace by some other text.


FTE permit to insert lines like (don't remember the exact format):

FTE: -------------------- begin -------------------
FTE: some introduction to the template that has been inserted
FTE: this comment may be very, very long.
FTE:
FTE: Next: the name of the environment
FTE:a:    %%%(environment name ; this is a PH)
FTE:b[ ]: Do you wish to center it ?
FTE:
    \begin{@a}
FTE: IF(@b, \begin{center})
       <+insert your code here+>
FTE: IF(@b, \end{center})
    \end{@a}
    <++>
FTE: some last comments
FTE: -------------------- end -------------------

Then, we can assign some value to @a and @b (by replacing the %%%()
placeholders), interpret the corresponding code (with <F6> for
instance). The result displayed could be:
    \begin{itemize}
       .... cursor here ....
    \end{itemize}
    <++>

I see his plugin as a multipasses templates plugin. One interresting use
is to insert the signature of some functions and an excerpt of their
man.


A solution made of PHs only would have contain a several lines-long PH
introducing the template. IMHO, this is a mis-use of PHs.

> Also, latex-suite does support templates in custommacros.vim
... and in templates.vim

But so far, I'm not sure it is as evolved as FTE or my unofficial
version of µTemplate.

-- 
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] Re: imaps, version of 3rd jan 2003

[Srinath A. <sr...@fa...>]

On Wed, 8 Jan 2003, Luc Hermitte wrote:
> > This was a bug. I have fixed it. Actually, fixing this bug made me
> > realize that I was making some other stuff needlessly complex. Things
> > are nice and simple after this bug fix. Thanks! See the latest version
> > in the cvs tree...
>
> I will check it. Does it works even when the cursor is within a
> placeholder boundaries ? [my last conclusions was that I need to call
> searchpair twice]

It does work... If you are in the middle of a placeholder and press
<C-j> it will goto the next placeholder. <C-K> selects the placeholder
you are current in...

> The guilty code is:
>     ':call histdel("/", -1)|let @/=histget("/", -1)'
> I think it is due to the fact it is returned as a string passed to
> '<c-r>='. Set 'cmdheight' to 2 or more to see the echoing.

Hmm... I dont see anything on the commandline even with cmdheight = 2.
Dunno... Maybe I'll randomly add a <silent> next time...

> In fact, I was wondering why a
>     :normal <Plug>IMAP_JumpForward
> wasn't enough ? Or may be directly a:
>     :call IMAP_JumpFunc(0)
>
> What makes the inclusive search so different and required ?
>
Well, here's the comment in the latest imaps.vim

" IMAP_Jumpfunc: takes user to next <+place-holder+> {{{
" Author: Luc Hermitte
" Arguments:
" direction: flag for the search() function. If set to '', search forwards,
"            if 'b', then search backwards. See the {flags} argument of the
"            |search()| function for valid values.
" inclusive: In vim, the search() function is 'exclusive', i.e we always goto
"            next cursor match even if there is a match starting from the
"            current cursor position. Setting this argument to 1 makes
"            IMAP_Jumpfunc() also respect a match at the current cursor
"            position. 'inclusive'ness is necessary for IMAP() because a
"            placeholder string can occur at the very beginning of a map which
"            we want to select.
"            We use a non-zero value only in special conditions. Most mappings
"            should use a zero value.

In short, if we didn't take care of inclusion, then if we did

call IMAP('foo', '<+one+> <+two+>', '')

then on pressing foo we would be taken to <+two+>. This was something
from a while ago... I'll have to check whether we still need this
because it looks like /something/e has the effect of including a match
at the current position.

> I will eventually have to make many experiments in order to be able to:
> - let ftplugins change the values of opening and closing string
> - let ftplugins encoded in latin1, utf-8, etc
> - be compatible with any encoding of fileencoding for the current
>   buffer/file.
>
Benji has spent time on this and I think we have a working system right
now to do all of this. We have even thought of things like "what if the
placeholder setting was done in a file with 'fenc' different from the
tex file which the user is editing?" So if you want, you might want to
see whats done here.

> The important advantage: it wraps the call to iconv(). Neither the
> end-user nor the .texrc writter have to worry about calling iconv() for
> funky strings.
>
Yes. Benji wrote s:Iconv(), a wrapper for iconv() which does these
things

> I'm skeptical about their usefulness (English ?). When we need long
> tags/comments, I'd rather use a templates plugin like the one written by
> Robert "Feral" Kelly.

Well, even if we have some other ways of generating templates, I would
be very reluctant to have another function do the actual jumping between
placeholders. Code duplication! Besides, multi line placeholders were a
snap to support. Does this templates plugin offer something different?
Also, latex-suite does support templates in custommacros.vim

Srinath

[Vim-latex-devel] Re: Alt mappings

[Luc H. <her...@fr...>]

* On Tue, Jan 07, 2003 at 11:36:20PM +0100, Mikolaj Machowski <mi...@wp...> wrote:
> On Tue, Jan 07, 2003 at 12:02:31PM +0100, Luc Hermitte wrote:
> > the {key}/{sequence_of_keys}. For instance, I like ']em' to insert
> > '\emph{}', but what do you prefer ? 'FEM', ']FEM', ']EM' ?
> 
> I like FEM because:
> ]FEM it too long
> ]EM can lead to inconsistence. 

I didn't wanted to propose new mappings. My point is that we all have
different preferences. Having an option to define the leading key is
really easy, contrary to the following keys.

For instance, we could write a function like:
    function s:DefMappings()
	call IMAP( b:TeXleader.'EM', '\emph{', '}')
	call IMAP( b:TeXleader.'BF', '\textbf{', '}')
	...
    endfunction

Everyone have good reason to prefer one keybinding to another.
For instance, 
- i'd rather the mapleader does not belong to '\c[a-z]'. I may have to
  use an accronym like FEM someday.
- FEM implies I hold the <shift> key
- I quite never use ']' ; because I use a bracketing system and because
  I rarely write intervals. However ']' requires me to press <AltGr>.
- the backquote (`) is a dead key on my keyboard
- I often write tables (&)
- '#', 'µ', '£', or '€' may be nice for me, but most of them are funky
  characters you may not have on your keyboard.

Anyway, the leading character is not a problem at all with a function
like s:DefMappings() -- BTW, I recall my advice to use commands that
defines mappings and menus in one call: that eases the maintenance of
the list of mappings supported.

> [...]
> what about EIT (\begin{itemize})?
    ']ul' in my environment ;-)
I have exactly the same mappings for common LaTeX and HTML constructs.


Benji added:
> This is what <Plug> is for.  We already use this in imaps.vim.
> Just search for "<Plug>" to see the examples.

Indeed. But I don't find the '<Plug>' thing as handy with ftplugins
having hundred of mappings as it is with plugins.
Moreover:
- it does not solve the problem that the menus can't be synchronized
  with mappings that the end-user tuned with the '<Plug>mappings'.
- many mappings are based on IMAP() that calls :imap itself instead of
  returning a string.

So, I agree with Srinath's opinion:
S> Well, latex-suite provides <plug>s for things like IMAP_Jumpfunc(),
S> not for things like EFI in insert mode which generates the figure
S> micro template... Doing it the <plug> way for those will be, I think
S> needlessly complex.

---- context dependant mappings ----
> > BTW, it would be nice if we could define mappings aware of the TeX
> > mode.  For instace, an same mapping would insert '\textbf{}' or
> > '\mathbf{}' according to the current TeX mode.
> 
> This is possible with checking of current syntax. Benji did it for
> inserting cdots, and I used it in 'polski' file.
> 
> if synIDattr(synID(line('.'),col('.')-1,0),"name") =~ '^texMath\|^texZone'

As I remember, the test is more tricky than that. But yes it is the
idea. Except that ... IMAP() is not handy to define such things.

The easiest approach should be:
    imap what-ever-bf <c-r>=BF()<cr>
With BF() returning '\textbf{<+cursor-pos+>}<++>' or
'\mathbf{<+cursor-pos+>}<++>'.

Today, the trick imposing the less changes will be a BF() function
returning the correct (according to user's preferences) FBF or MBF
string.

-- 
Luc Hermitte
http://hermitte.free.fr/vim/

[Vim-latex-devel] Re: imaps, version of 3rd jan 2003

[Luc H. <her...@fr...>]

* On Tue, Jan 07, 2003 at 12:02:57PM -0800, Srinath Avadhanula <sr...@fa...> wrote:
> > - The jumpBack does not work correclty. Try for instance:
> >   :vmap <C-k> <Plug>IMAP_JumpBack
> >   i<+foo+> <+bar+> <+three+>
> >   <esc>gg
> >   ^J^J^K
> 
> This was a bug. I have fixed it. Actually, fixing this bug made me
> realize that I was making some other stuff needlessly complex. Things
> are nice and simple after this bug fix. Thanks! See the latest version
> in the cvs tree...

I will check it. Does it works even when the cursor is within a
placeholder boundaries ? [my last conclusions was that I need to call
searchpair twice]

> > - the mappings are not silent.
> Oh? I have done something like:
> 
> imap <silent> <Plug>IMAP_JumpForward    <c-r>=IMAP_Jumpfunc('', 0)<CR>
> if !hasmapto('<Plug>IMAP_JumpForward', 'i')
>     imap <C-J> <Plug>IMAP_JumpForward
> endif
> 
> Doesn't this make the maps silent? Do I need

The guilty code is:
    ':call histdel("/", -1)|let @/=histget("/", -1)'
I think it is due to the fact it is returned as a string passed to
'<c-r>='. Set 'cmdheight' to 2 or more to see the echoing.
At first I defined an intermediary (and silent) mapping.

My last version does not use v/phe/e anymore. But:
    " cursor is at the beginning of a marker.
    let select = 'v'.virtcol('.').'|o'
    call search('\V'.escape(phe,'\'))
    return select. gv_or_c

Unfortunatelly, unless I mess vim-marks, I can't go to another line
(than the current one) while in visual mode.

> > - why do you need a specific jump function to use with IMAP() ? I
> >   haven't looked in the mecanics, but I find this odd ; I didn't
> >   need such a thing with µTemplate.
> 
> Well, I am kind of unsure what you mean by this question... But this
> was done mostly on purpose, since we did not want to duplicate code in
> IMAP() and IMAP_Jumpfunc(). If you are asking about why
> IMAP_Jumpfunc() now takes 2 arguments, well, ... I didn't give it much
> thought. 

In fact, I was wondering why a 
    :normal <Plug>IMAP_JumpForward
wasn't enough ? Or may be directly a:
    :call IMAP_JumpFunc(0)

What makes the inclusive search so different and required ?

> > - I don't mess with @" anymore
> So you use @_ like in IMAP_Jumpfunc()?

'"_c' actually. So yes.


> > There is also a new command:
> >     :SetMarker {open} {close}
> > that sets the two strings used to define the marker -- no need to
> > know the name of the two options.
> 
> Interesting, but I dont think end users will use this. Also, variables
> are nicer because nothing needs to be source'd apriori, so they can be
> set in .vimrc (the most natural place).

I wasn't thinking to end-user but to ftplugins writers.
I will eventually have to make many experiments in order to be able to:
- let ftplugins change the values of opening and closing string
- let ftplugins encoded in latin1, utf-8, etc
- be compatible with any encoding of fileencoding for the current
  buffer/file.

The important advantage: it wraps the call to iconv(). Neither the
end-user nor the .texrc writter have to worry about calling iconv() for
funky strings.

> > - and to test the echoing approach (as opposed to the
> >   marker-selection).
> 
> I tried the echoing approach, but it didn't work, because the command
> line is taken up with -- INSERT --, overwriting whatever is echoed.
> Have you found a way around it?

    :set cmdheight=2

It is unusable otherwise. I have to comment/document this.



> Per Benji's request, I've also commented IMAP_Jumpfunc() and taken
> care of <+placeholders
> withlinebreaks+>

I'm skeptical about their usefulness (English ?). When we need long
tags/comments, I'd rather use a templates plugin like the one written by
Robert "Feral" Kelly.



-- 
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] Re: Alt mappings

[Srinath A. <sr...@fa...>]

On Tue, 7 Jan 2003, Benji Fisher wrote:

> Mikolaj Machowski wrote:
> > create his own mappings by doing :map ]em FEM (in another words: create
> > latexSuite API). But I do not know how to do this.
>
Well, Mikolaj's idea works OOTB for me... for example, if I do:

imap ]em FEM

Then when I press ]em, I do use latex-suite's FEM macro. Unfortunately,
doing

call IMAP(']em', 'FEM', 'tex')

doesn't work (I just get 'FEM')...

>       This is what <Plug> is for.  We already use this in imaps.vim .
> Just search for "<Plug>" to see the examples.

Well, latex-suite provides <plug>s for things like IMAP_Jumpfunc(), not
for things like EFI in insert mode which generates the figure micro
template... Doing it the <plug> way for those will be, I think
needlessly complex.

If we had a way of modifying s:LookupCharacter() in imaps.vim so that
its public, then we could have done something like:

call IMAP(']em', "\<C-r>=IMAP_LookupMap('FEM')\<CR>", 'tex')

(Ofcourse, this is not the way IMAP_LookupMap works right now...)

and then ]em will expand to what FEM did previously... Maybe we can even
provide a function,

IMAP_Remap('FEM', ']em', 'tex')

which well, does what Mikolaj wants... For some time, I have been
thinking of providing a IMAP_UnMap() function... If we implement that,
IMAP_Remap() will be implemented almost the same way...

In short, I do not think doing what Mikolaj wants is very complex, and
in fact, instead of going about it changing all the places where the
maps are created, providing a IMAP_Remap() might be the way to go.

Ofcourse, this a new feature, so maybe we should wait for a little
while. I am thinking of making another vim.sf.net sometime soon, because
we seem to be decently stable and bug-free...

Srinath

Re: [Vim-latex-devel] Re: Alt mappings

[Benji F. <be...@me...>]

Mikolaj Machowski wrote:
> On Tue, Jan 07, 2003 at 12:02:31PM +0100, Luc Hermitte wrote:
> 
>>the {key}/{sequence_of_keys}. For instance, I like ']em' to insert
>>'\emph{}', but what do you prefer ? 'FEM', ']FEM', ']EM' ?
> 
> 
> I like FEM because:
> ]FEM it too long
> ]EM can lead to inconsistence. Are we getting rid of F only for \emph{}
> or for all font commands? Look for FIT. It is \itshape{}. You can change
> it for ]IT but what about EIT (\begin{itemize})?
> Existing system of shortcuts is slightly awkward bu at least (I hope)
> internally consistent.
> Really nice would be something quite different. Possibility for user to
> create his own mappings by doing :map ]em FEM (in another words: create
> latexSuite API). But I do not know how to do this.

      This is what <Plug> is for.  We already use this in imaps.vim . 
Just search for "<Plug>" to see the examples.

>>Don't worry. 
>>BTW, it would be nice if we could define mappings aware of the TeX mode.
>>For instace, an same mapping would insert '\textbf{}' or '\mathbf{}'
>>according to the current TeX mode.
> 
> 
> This is possible with checking of current syntax. Benji did it for
> inserting cdots, and I used it in 'polski' file.
> 
> if synIDattr(synID(line('.'),col('.')-1,0),"name") =~ '^texMath\|^texZone'

      I am familiar with this idea, but I cannot take credit for the ... 
map.  When I met Bram last summer, I suggested that the next Big Thing 
for vim should be a better way to deal with regions (math in TeX 
documents, comments in many languages, script languages in HTML-like 
languages, etc.)  We'll see what happens.

					--Benji

Re: [Vim-latex-devel] Re: Alt mappings

[Mikolaj M. <mi...@wp...>]

On Tue, Jan 07, 2003 at 12:02:31PM +0100, Luc Hermitte wrote:
> the {key}/{sequence_of_keys}. For instance, I like ']em' to insert
> '\emph{}', but what do you prefer ? 'FEM', ']FEM', ']EM' ?

I like FEM because:
]FEM it too long
]EM can lead to inconsistence. Are we getting rid of F only for \emph{}
or for all font commands? Look for FIT. It is \itshape{}. You can change
it for ]IT but what about EIT (\begin{itemize})?
Existing system of shortcuts is slightly awkward bu at least (I hope)
internally consistent.
Really nice would be something quite different. Possibility for user to
create his own mappings by doing :map ]em FEM (in another words: create
latexSuite API). But I do not know how to do this.

> Don't worry. 
> BTW, it would be nice if we could define mappings aware of the TeX mode.
> For instace, an same mapping would insert '\textbf{}' or '\mathbf{}'
> according to the current TeX mode.

This is possible with checking of current syntax. Benji did it for
inserting cdots, and I used it in 'polski' file.

if synIDattr(synID(line('.'),col('.')-1,0),"name") =~ '^texMath\|^texZone'

Mikolaj

Re: [Vim-latex-devel] Alt mappings

[Mikolaj M. <mi...@wp...>]

On Mon, Jan 06, 2003 at 06:16:22PM -0800, Srinath Avadhanula wrote:
> Should we just document all the maps created by latex-suite in
> latex-suite.txt and then put "Read the docs about how to override
> mappings" somewhere in the install instructions?
> Luc, Mikolaj, Fabio any suggestions? The rest of us AFAIK do not use
> the meta key anyway...
> I just thought about this? Are things like ']b' etc going to cause the
> same kind of problems diacritics caused? Do strings like ']b' occur
> often in latex?

IMO such mappings should be normal, without using IMAP mechanisms (it is
possible to wait until they "expire").

m.

Re: [Vim-latex-devel] imaps, version of 3rd jan 2003

[Srinath A. <sr...@fa...>]

Hello,

On Tue, 7 Jan 2003, Luc Hermitte wrote:

> Hello,
>
> - we don't have to test 'wrapscan', |search()| does it implicitly for us

Thanks for the tip. I removed the extra code.

> - The jumpBack does not work correclty. Try for instance:
>   :vmap <C-k> <Plug>IMAP_JumpBack
>   i<+foo+> <+bar+> <+three+>
>   <esc>gg
>   ^J^J^K

This was a bug. I have fixed it. Actually, fixing this bug made me
realize that I was making some other stuff needlessly complex. Things
are nice and simple after this bug fix. Thanks! See the latest version
in the cvs tree...

> - the mappings are not silent.

Oh? I have done something like:

imap <silent> <Plug>IMAP_JumpForward    <c-r>=3DIMAP_Jumpfunc('', 0)<CR>
if !hasmapto('<Plug>IMAP_JumpForward', 'i')
    imap <C-J> <Plug>IMAP_JumpForward
endif

Doesn't this make the maps silent? Do I need

imap <silent> <C-J> <Plug>IMAP_JumpForward

also?

> - why do you need a specific jump function to use with IMAP() ? I
>   haven't looked in the mecanics, but I find this odd ; I didn't need
>   such a thing with =B5Template.

Well, I am kind of unsure what you mean by this question... But this was
done mostly on purpose, since we did not want to duplicate code in
IMAP() and IMAP_Jumpfunc(). If you are asking about why IMAP_Jumpfunc()
now takes 2 arguments, well, ... I didn't give it much thought. I guess
the arguments could be optional and default to ('', 0)... Again, I dont
see any advantages/disadvantages either way.

> Otherwise, I've integrated in bracketing.base.vim some of the things you
> use [thanks!]:
> - the 'nomagic' stuff ; BTW, the psh and phe strings need to have their
>   '\' escaped -- I haven't checked if it is needed for other characters.

Forgot to do this in the latest commit. Will fix this next time.

> - I don't mess with @" anymore

So you use @_ like in IMAP_Jumpfunc()?

> - I've managed the visual selection in another way that does not mess
>   with the search-history at all-- way that expext the
>   marker/placeholder to hold on a single line.

Well, the latest imaps.vim is able to handle <+placeholders
withlinebreaks+> (or without linebreaks) without messing up @/. This is
simply done by appending

':call histdel("/", -1)|let @/=3Dhistget("/", -1)'

to normal commands. Works quite well so far...

> There is also a new command:
>     :SetMarker {open} {close}
> that sets the two strings used to define the marker -- no need to know
> the name of the two options.

Interesting, but I dont think end users will use this. Also, variables
are nicer because nothing needs to be source'd apriori, so they can be
set in .vimrc (the most natural place).

> - and to test the echoing approach (as opposed to the marker-selection).

I tried the echoing approach, but it didn't work, because the command
line is taken up with -- INSERT --, overwriting whatever
is echoed. Have you found a way around it?

Per Benji's request, I've also commented IMAP_Jumpfunc() and taken care
of <+placeholders
withlinebreaks+>

Thanks,
Srinath

[Vim-latex-devel] IMAP_Jumpfunc()

[Benji F. <be...@me...>]

      I have already exeeded my time quota for vim coding today, so 
maybe someone else can have a loko at this.  I have a few requests for 
IMAP_Jumpfunc():

1. Document the arguments:  I think one is passes to search() and the 
other is some sort of inclusive/exclusive flag.

2. Think about what happens when the <+place
holders+> include a line break.  I think that '<+.\{-}+>' works well for 
strings variables, but when searching in the buffer, we should use 
'<+\_.\{-}+>'.

					--Benji

Re: [Vim-latex-devel] Alt mappings

[Carl M. <cm...@ma...>]

On Mon, Jan 06, 2003 at 06:16:22PM -0800, Srinath Avadhanula wrote:
> Hmm... Lets see... What about moving away from "special" keys altogether
> and using ']l' ']b' ']c' etc in insert mode (as Luc suggests) and
> <M-[lbc]> in normal mode (or maybe even ']b' etc in normal mode as
> well)? 

I know that some people use the ']b' map, and it does seem
very convenient.  But isn't there a danger that someone will
type

a[x]b[x]

and get garbage?  (Of course, not if they use automatic
bracket insertion, but they might not want to).  There are
lots of mathematical situations where functions have square
brackets.  I would not create a mapping like that for my own
typing.  

'?' seems like a reasonable mapleader, but it's harder to
type than ']', since you have to hold down the shift key,
and maybe it's wierd to use it as a mapleader.  

Would the apersand '&' be good?  That is not used in
mathematics, as far as I know.

Perhaps, since the backtick ` is already a mapleader, double
backtick `` should be the second mapleader?  

<Insert> might still be worth considering.

In any case, ther problem needs careful consideration.

Best wishes,
Carl

Re: [Vim-latex-devel] imaps, version of 3rd jan 2003

[Luc H. <her...@fr...>]

Hello,

I have looked at imaps.vim, the version shipped with the archive made on
the 3rd January. To be more precise, I've focused on the jumping
function.

So, I have several questions and remarks:
- we don't have to test 'wrapscan', |search()| does it implicitly for us
- The jumpBack does not work correclty. Try for instance:
  :vmap <C-k> <Plug>IMAP_JumpBack
  i<+foo+> <+bar+> <+three+>
  <esc>gg
  ^J^J^K
- the mappings are not silent.
- why do you need a specific jump function to use with IMAP() ? I
  haven't looked in the mecanics, but I find this odd ; I didn't need
  such a thing with µTemplate. 

Otherwise, I've integrated in bracketing.base.vim some of the things you
use [thanks!]:
- the 'nomagic' stuff ; BTW, the psh and phe strings need to have their
  '\' escaped -- I haven't checked if it is needed for other characters.
- I don't mess with @" anymore
- less screen flashes (s/<esc><c-l>/<c-\><c-n>)
And:
- I've managed the visual selection in another way that does not mess
  with the search-history at all-- way that expext the
  marker/placeholder to hold on a single line.

There is also a new command: 
    :SetMarker {open} {close} 
that sets the two strings used to define the marker -- no need to know
the name of the two options.

I've also tried to automatically manage the value of the 'encoding'. But
I'm not sure it is really useful.

So, I still have:
- to tune/change some little things regarding iconv -- but so far it
  works fine on my win32 version of Vim. I can insert (<M-Insert> [1])
  and jump to markers in latin1 and utf-8, the markers beeing defined
  with:
     :SetMarker « »
  or :SetMarker \foo \bar
  or :SetMarker <+ +>
  or :SetMarker «+ +»
- and to test the echoing approach (as opposed to the marker-selection).


[1] I must confess: I use some meta-mappings in insert mode.
-- 
Luc Hermitte
The latest version of the file should be available at:
http://hermitte.free.fr/vim/ressources/vimfiles/plugin/bracketing.base.vim

[Vim-latex-devel] Re: Alt mappings

[Luc H. <her...@fr...>]

* On Mon, Jan 06, 2003 at 10:55:15PM -0500, Benji Fisher <be...@me...> wrote:
> Srinath Avadhanula wrote:
> >Hmm... Lets see... What about moving away from "special" keys
> >altogether and using ']l' ']b' ']c' etc in insert mode (as Luc
> >suggests) 

This is an idea I've stolen from Sven scripts. Now, I'm used to it and
like it.

> >and <M-[lbc]> in normal mode (or maybe even ']b' etc in normal mode
> >as well)? 

> >This way people who want to use <M-c> etc for national characters can
> >continue to do so... Ofcourse this makes the users of latex-suite
> >learn yet another "leader" character...  

May be, may be not. What about two options:
- [bg]:meta_or_mapleader
- [bg]:insert_mapleader

If the first is true, mappings are defined as '<M-{key}>', otherwise the
mappings are defined with '{[bg]:insert_mapleader}{key}'.

The configuration step is a little more complex, but still quite simple.
What is really hard to propose to the end user is a simple way to change
the {key}/{sequence_of_keys}. For instance, I like ']em' to insert
'\emph{}', but what do you prefer ? 'FEM', ']FEM', ']EM' ?

> >Maybe ']' can be reserved for beginning maps which change the text
> >before them in some way...

What do you mean by 'before them' ?

> [...]
> >" Pressing <F5> will prompt you for which environment to insert.
> >" Change <F5> to change the ``hotkey''.
> >nmap <silent> <F5> <Plug>Tex_FastEnvironmentInsert
> >
> >etc. The user needs to change the lhs in these lines to customize...
> >But texrc or the user's copy of texrc is sourced only once when
> >latex-suite initializes, not for every BufEnter event... So that
> >might not be a good place...

Why don't you put it in a {rtp}/ftplugin/tex/ directory ?
Or do something like:
#### {rtp}/ftplugin/tex/tex_options-commands.vim ####
    " excerpt from a similar file from my C++ ftplugins
    let s:esc_pwd = ''
    " Function: s:CheckOptions() {{{ 
    " Role: Checks whether we must reload the options file to match the
    " current project.
    function! s:CheckOptions()
      if s:esc_pwd != escape(getcwd(), '\')
	let s:pwd = getcwd()
	let s:esc_pwd = escape(s:pwd, '\')
	let g:do_load_tex_options = 1
	if filereadable("./tex_options.vim")
	  so ./tex_options.vim
	else 
	  runtime ftplugin/tex/tex_options.vim
	endif
      endif
    endfunction
    " }}}

    call s:CheckOptions()
    " + definition of a Vim-command if needed.
####
But, that supposes:
- the mappings in .texrc (I really don't like this name) are buffer
  mappings, not global mappings

And I wonder if we really need to reload the options every time we enter
a new buffer. I think the end-user will likely have the same mappings
for all his (La)TeX buffers.


> Actually, I was suggesting something more radical.  Something like
> this:
> 
> let Tex_FastEnvironmentInsert = ''	" '<F5>' is popular.
> " Either default to empty string as above or else comment it out:
> " let Tex_FastEnvironmentInsert = '<F5>'
> 
> Then the TexSetOptions() function (called on each FileType tex event,
> I think) can test whether g:Tex_FastEnvironmentInsert exists (or is
> not the empty string) and use it to define a map if so.  This is the
> way I did it way back in texmacros.vim (for vim 5.3+).

I like this approach: let's take advantage of the ftplugin mecanism.

> >Luc, Mikolaj, Fabio any suggestions? The rest of us AFAIK do not use
> >the meta key anyway...

I use (ie: define to mappings binded to ...) the meta keys only for
NORMAL mode now. While they overlap with accentuated character (Vim does
not make any difference when I hit 'é' or '<M-i>'). 



> >I just thought about this? Are things like ']b' etc going to cause
> >the same kind of problems diacritics caused? Do strings like ']b'
> >occur often in latex?
> Closed intervals are pretty common:  $[a,b]$.  Some authors like to
> reverse the brackets for open intervals:  $]a,b[$  instead of $(a,b)$.  

That's true. I completly forgot. As finding non funky keys not used in a
way or in other is nearly impossible (except if you like ^X), I think
the easiest for us is to have the end-user to define his preferences on
this topic -- cf. the 2 options in the beginning of this message. Then,
he will use ']', '#', 'µ', ... what ever he want and can to use.

> (I have to restrain myself:  let's not disparage anyone's
> nationality!)  

In France, we do use ']a,b[' for open intervals, is it used elsewhere ?

> Of course, we could make ']b' do something special in text mode, but
> not in math mode.
> 
> Vim modes: [...]
> TeX modes: [...]
> 
> Why do I mention this?  Mostly because it is late, but also because I
> was a little worried that mentioning a TeX mode might lead to
> confusion because Vim had modes, too.

Don't worry. 
BTW, it would be nice if we could define mappings aware of the TeX mode.
For instace, an same mapping would insert '\textbf{}' or '\mathbf{}'
according to the current TeX mode.

-- 
Luc Hermitte
http://hermitte.free.fr/vim/

Re: [Vim-latex-devel] Alt mappings

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> Hmm... Lets see... What about moving away from "special" keys altogether
> and using ']l' ']b' ']c' etc in insert mode (as Luc suggests) and
> <M-[lbc]> in normal mode (or maybe even ']b' etc in normal mode as
> well)? This way people who want to use <M-c> etc for national characters
> can continue to do so... Ofcourse this makes the users of latex-suite
> learn yet another "leader" character...  Maybe ']' can be reserved for
> beginning maps which change the text before them in some way... In the
> future, we could have more of such maps...
> 
> Ofcourse, I have still not gotten around to creating a good way to let
> the end user over-ride the maps. Benji suggested that a section of texrc
> can have things like
> 
> " Pressing <F5> will prompt you for which environment to insert.
> " Change <F5> to change the ``hotkey''.
> nmap <silent> <F5> <Plug>Tex_FastEnvironmentInsert
> 
> etc. The user needs to change the lhs in these lines to customize...
> But texrc or the user's copy of texrc is sourced only once when
> latex-suite initializes, not for every BufEnter event... So that might
> not be a good place...

      Actually, I was suggesting something more radical.  Something like 
this:

" We do not need much of a comment because we use long, descriptive
" variable names.
" Key for inserting a TeX environment (duh).
" See :help latex-environment for details.
" Usually, these :help pointers in the comments will apply to several
" options at once.
let Tex_FastEnvironmentInsert = ''	" '<F5>' is popular.
" Either default to empty string as above or else comment it out:
" let Tex_FastEnvironmentInsert = '<F5>'

Then the TexSetOptions() function (called on each FileType tex event, I 
think) can test whether g:Tex_FastEnvironmentInsert exists (or is not 
the empty string) and use it to define a map if so.  This is the way I 
did it way back in texmacros.vim (for vim 5.3+).

> Should we just document all the maps created by latex-suite in
> latex-suite.txt and then put "Read the docs about how to override
> mappings" somewhere in the install instructions?

      Yes.  Each group of related options in texrc should have a comment 
pointing to the appropriate tag in doc/latex-suite.txt .

> Luc, Mikolaj, Fabio any suggestions? The rest of us AFAIK do not use
> the meta key anyway...
> 
> I just thought about this? Are things like ']b' etc going to cause the
> same kind of problems diacritics caused? Do strings like ']b' occur
> often in latex?

      Closed intervals are pretty common:  $[a,b]$.  Some authors like 
to reverse the brackets for open intervals:  $]a,b[$  instead of 
$(a,b)$.  (I have to restrain myself:  let's not disparage anyone's 
nationality!)  Of course, we could make ']b' do something special in 
text mode, but not in math mode.

Vim modes:	Insert (and Replace)
		Normal (a.k.a. Beep or Escape mode)
		Command (a.k.a. : or Ex mode)
		Visual (and Select)

TeX modes:	Horizontal (a.k.a text or paragraph mode)
			(and Restricted Horizontal, a.k.a. LR, mode)
		Vertical (and Internal Vertical)
		Math
		Display Math

Why do I mention this?  Mostly because it is late, but also because I 
was a little worried that mentioning a TeX mode might lead to confusion 
because Vim had modes, too.

					--Benji

Re: [Vim-latex-devel] Alt mappings

[Srinath A. <sr...@fa...>]

On Mon, 6 Jan 2003, Benji Fisher wrote:

> Carl Mueller wrote:
> > About the Alt macros, how about the following?
> >
> > 1.  As an option, the user can turn on the <Alt> mappings.
> >     (This was mentioned by others.)

I think having an option g:Tex_UseMetaMappings (defaults to 0, i.e 'no')
is a good thing...

> > 2.  As a default, use the <Insert> key for the <Alt> mappings.
> >     The <Insert> key isn't used for anything else, is it?
> >     It could be a right handed version of the "`" mappings.
> >     Besides the <Alt> mappings that I wrote, one could use the
> >     <Insert> key for mappings that control fonts, such as
> >     {\em ...} and so on.
> >
>       The <Insert> key is used to toggle between Insert and Replace
> modes.  I almost never use Replace mode, and I often hit the <Insert>
> key when I am aiming for the <Del> key, so I have :imap'ed it to <Nop>.
>
>       In other words, it is not quite true that the <Insert> key is
> unused, but it is pretty close.
>

Hmm... Lets see... What about moving away from "special" keys altogether
and using ']l' ']b' ']c' etc in insert mode (as Luc suggests) and
<M-[lbc]> in normal mode (or maybe even ']b' etc in normal mode as
well)? This way people who want to use <M-c> etc for national characters
can continue to do so... Ofcourse this makes the users of latex-suite
learn yet another "leader" character...  Maybe ']' can be reserved for
beginning maps which change the text before them in some way... In the
future, we could have more of such maps...

Ofcourse, I have still not gotten around to creating a good way to let
the end user over-ride the maps. Benji suggested that a section of texrc
can have things like

" Pressing <F5> will prompt you for which environment to insert.
" Change <F5> to change the ``hotkey''.
nmap <silent> <F5> <Plug>Tex_FastEnvironmentInsert

etc. The user needs to change the lhs in these lines to customize...
But texrc or the user's copy of texrc is sourced only once when
latex-suite initializes, not for every BufEnter event... So that might
not be a good place...

Should we just document all the maps created by latex-suite in
latex-suite.txt and then put "Read the docs about how to override
mappings" somewhere in the install instructions?

Luc, Mikolaj, Fabio any suggestions? The rest of us AFAIK do not use
the meta key anyway...

I just thought about this? Are things like ']b' etc going to cause the
same kind of problems diacritics caused? Do strings like ']b' occur
often in latex?

Srinath