Thread: [Vim-latex-devel] Disable "->`` and "->'' in .tex and .bib files?

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi,

I want to disable all the mapping defined in vim-latex-suite, such as
"->`` and "->''? Is there a way to do so?

-- 
Regards,
Peng

Peng --

Most of your questions are addressed in:

:help latex-suite

as well as on the Vim-LaTeX project page, which would be difficult to
maintain on github. Many of your questions ask about disabling
features of latex-suite. It may be helpful to know what parts of
latex-suite you find helpful. If it's just the syntax highlighting,
you can get that without having latex-suite installed at all.

To disable just smart quotes, you can see:

:help Tex_SmartKeyQuote

You can set the g:Tex_SmartKeyQuote to 0 to turn off smart quotes entirely.

    If you want to turn off other IMAP expansion, see:

:help pausing-imaps

In particular, set g:Imap_FreezeImap to 1 in your .vimrc. That will
turn off expansions like EQE and `w and others.

    --Ted

On Mon, Jul 2, 2012 at 8:17 AM, Peng Yu <pen...@gm...> wrote:
> Hi,
>
> I want to disable all the mapping defined in vim-latex-suite, such as
> "->`` and "->''? Is there a way to do so?
>
> --
> Regards,
> Peng
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

-- 
Ted Pavlic <te...@te...>

> :help latex-suite

I didn't not know how to get the document work as I'm using pathogen.
I just figured out that I should use "helptags
~/.vim/bundle/vim-latex-suite/doc/" instead. However, when do ":help
latex-suite", I still get error message 'File
"myhome/.vim/doc/latex-suite.txt" does not exist', although I
eventually get to the help page.

> the Vim-LaTeX project page, which would be difficult to
> maintain on github.

This is not true. You can use gh-pages. http://pages.github.com/

> latex-suite you find helpful. If it's just the syntax highlighting,
> you can get that without having latex-suite installed at all.

I only need to use syntax highlighting and indentation. Anything else
offered by latex-suite is a drag to me. To get what I need, it seems
that the simplest way is just to grab the syntax file and indentation
file. But I think that this may not be a good approach in the long run
for keeping the package up-to-date.

The project webpage is better to state at the very beginning how to
just enable syntax highlight and indentation.

Just my 2 cents.

-- 
Regards,
Peng

> I didn't not know how to get the document work as I'm using pathogen.

I use pathogen as well. See pathogen's documentation:

http://www.vim.org/scripts/script.php?script_id=2332

pathogen will put each bundled plugin into your runtimepath. After that:

Use :Helptags to run :helptags on every doc/ directory in your
'runtimepath'.

Works for me.

> This is not true. You can use gh-pages. http://pages.github.com/

That's fine, but it does not justify the extra work it would take to
convert the Vim-LaTeX page into a gh-pages branch and publicize the
change in hosting site. So there is significant cost to a conversion and
very little benefit. Even at a low cost, the latex-suite is primarily in
maintenance mode at this stage in its life. Without a dedicated batch of
new developers who are willing to stick it out for the long run, there's
no way a conversion to a new hosting site could happen. Just switching
LaTeX-suite from SVN to git took a great deal of effort because it was
clear that if there were any problems with the conversion that did not
immediately show up, there might not be devs around to fix them.

> The project webpage is better to state at the very beginning how to
> just enable syntax highlight and indentation.

You get syntax highlighting for free. It comes with vim. Notice that
there is no "syntax" directory in vim-latex. Without LaTeX suite, you
would get the same highlighting so long as your file type was set correctly.

Indentation comes with Vim-LaTeX, but (IIRC) it does not depend on the
rest of the LaTeX suite. If all you want is the indentation, then all
you need is the "indent/tex.vim" file inside the repo. If your file type
is set correctly, then you'll get the TeX-specific indentation.

As you can see on the list, most of the active LaTeX-suite users use the
extended features, like completion, key mappings, smart compilation,
forward and reverse searching, and the TeX-specific code folding. These
are features that come in handy when composing very large documents
(articles, reports, and books) with many parts distributed over many
files, much like a modern-day program in Java. Those who use LaTeX for
relatively small projects are usually satisfied with the basic support
that comes built into distributions of Vim. So that's why the default
feature set is how it is and why there is not more direct documentation
for how to turn it off (because for most people, those instructions
would simply be "uninstall LaTeX suite").

--Ted

-- 
Ted Pavlic <te...@te...>

> http://www.vim.org/scripts/script.php?script_id=2332

I don't see where pathogen's document is on the above page.

> pathogen will put each bundled plugin into your runtimepath. After that:
>
> Use :Helptags to run :helptags on every doc/ directory in your
> 'runtimepath'.

help :Helptags leads me to :helptags. Where is :Helptags documented?

> Works for me.

:Helptags works for me, too. Thanks!

> That's fine, but it does not justify the extra work it would take to
> convert the Vim-LaTeX page into a gh-pages branch and publicize the
> change in hosting site. So there is significant cost to a conversion and
> very little benefit. Even at a low cost, the latex-suite is primarily in
> maintenance mode at this stage in its life. Without a dedicated batch of
> new developers who are willing to stick it out for the long run, there's
> no way a conversion to a new hosting site could happen. Just switching
> LaTeX-suite from SVN to git took a great deal of effort because it was
> clear that if there were any problems with the conversion that did not
> immediately show up, there might not be devs around to fix them.

I get your point. So the real point is that the effort that takes to migrate.

> You get syntax highlighting for free. It comes with vim. Notice that
> there is no "syntax" directory in vim-latex. Without LaTeX suite, you
> would get the same highlighting so long as your file type was set correctly.

Never check the syntax highlight file. Just checked the indentation file.

> As you can see on the list, most of the active LaTeX-suite users use the
> extended features, like completion, key mappings, smart compilation,
> forward and reverse searching, and the TeX-specific code folding. These
> are features that come in handy when composing very large documents
> (articles, reports, and books) with many parts distributed over many
> files, much like a modern-day program in Java. Those who use LaTeX for
> relatively small projects are usually satisfied with the basic support
> that comes built into distributions of Vim. So that's why the default
> feature set is how it is and why there is not more direct documentation
> for how to turn it off (because for most people, those instructions
> would simply be "uninstall LaTeX suite").

This makes sense for frequent latex users. For me, I only use it
occasionally when I need to write some papers. For my everyday
documents, I use pandoc. Long time ago, before I knew pandoc, I used
to learn the short cuts in vim-latex-plugin. But since I don't use
them everyday, I quickly forgot them. And it doesn't make sense for me
to relearn them unless I am going to use vim-latex-plugin everyday
from now, which is not going to be the case.

So your assumption of frequenter latex users may not always apply. I
think that there should other occasional latex users like me.
Therefore, it is making sense to just add one or two sentence for
describing how to just enable indentation in the initial installation
page.

-- 
Regards,
Peng

> :help pausing-imaps

I have added the following line to my .vimrc. However, I still feel
the delay from \. I tried to open even a file
xxxxxxxxxx.xxxxxxxxxxxxxxx
 which should not be related with any plugin, and I also experience
the delay. So I guess the delay is from vim itself. Are you aware a
way to disable the delay entirely.

let g:Imap_FreezeImap = 1

-- 
Regards,
Peng

> I have added the following line to my .vimrc. However, I still feel
> the delay from \. I tried to open even a file

Have you looked at:

:help mapleader

? It is backslash by default. Consequently, any maps that have been
set with <Leader> will have a backslash in them and Vim will wait
every time you issue a backslash. Try then:

:map!

to see your mappings. Do you see any that start with backslash? If so,
that may be because they were defined somewhere with <Leader>. If you
find what's setting these mappings and get rid of the mappings, then
your problem should disappear.

Alternatively, you could set mapleader to some SINGLE character you
never use. That way, unless you have mappings that use an explicit
backslash initially, the mappings won't cause vim to pause to wait.

--Ted

> xxxxxxxxxx.xxxxxxxxxxxxxxx
>  which should not be related with any plugin, and I also experience
> the delay. So I guess the delay is from vim itself. Are you aware a
> way to disable the delay entirely.
>
> let g:Imap_FreezeImap = 1
>
> --
> Regards,
> Peng

-- 
Ted Pavlic <te...@te...>