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

[Vim-latex-devel] [ vim-latex-Bugs-3540930 ] Inserting environments such as "equation" leaves leftovers

[SourceForge.net <no...@so...>]

Bugs item #3540930, was opened at 2012-07-06 10:41
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3540930&group_id=52322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Inserting environments such as "equation" leaves leftovers

Initial Comment:
Extra symbols are inserted when inserting an equation environment: Press F5, type "3" to insert equation, then this happens:

\begin{equation}
    
    \label{<++>}
\end{equation}<++>

I'm not sure if the <++> is intentional, but I think it may be a bug.

I'm running Ubuntu 12.04x64, and have vim-latex suite loaded through pathogen.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3540930&group_id=52322

Re: [Vim-latex-devel] Compiling with latexmk does not work as expected

[Ted P. <te...@te...>]

> Googled a bit more. Since I am using zsh and MacVim won't read my
> .zshrc, I have to set up the path in .zprofile. Now it works.
> Thanks a lot for the hint.

I'm glad it worked out. Hopefully you can just move (as opposed to copy)
your path information from .zshrc to .zprofile so you don't have to
maintain both files (and so you don't accidentally double your path when
your zshrc runs and augments it). The profile file will be read on a
login shell (which is what Vim invokes) and then the zshrc is read if
zsh is being run in interactive mode (so that's why you were having the
trouble).

Best --
Ted


> Niels
> 
> On 5 Jul 2012, at 21:23, Ted Pavlic wrote:
> 
>> Niels --
>>
>>>> Or could you at least attach
>>>> the log file generated by TeX?
>>>
>>> Just tried to compile the file from a clean directory. There is nothing
>>> generated. There's just in vim the message "Ran latex 1 time(s)".
>>> Therefore I think that nothing gets really called.
>>
>>     That's very interesting. I notice that you're using a Mac. Are you
>> using vim from the Terminal, or are you using something like MacVim? If
>> I recall correctly, MacVim had a setting (off by default?) that would
>> run the internal instance of vim through a login shell. That would
>> ensure your PATH was set correctly. If you didn't have the setting set,
>> then you wouldn't have access to everything you might expect to have
>> access to.
>>
>>     From your Vim, can you try and test your PATH? For example, try
>> something like:
>>
>> :!echo $PATH
>>
>> or, perhaps better, try:
>>
>> :!latex
>>
>> In the latter case, LaTeX should start and give you a prompt. You can
>> hit Cntrl+D to exit from LaTeX if it pops up. If it doesn't pop up, then
>> Vim cannot find it.
>>
>>     --Ted
>>
>>
>>>> Thanks -
>>>
>>> I have to thank that you take the time and think about my problem :)
>>>
>>> Niels
>>>
>>>>> Hi,
>>>>>
>>>>> I am trying to get something compiled with latexmk and the
>>>>> vim-latex-suite. When I invoke latexmk on the file in the command line
>>>>> it work w/out any problems. When I invoke the compile in vim I just
>>>>> get:
>>>>> "Runnning bibtex…
>>>>> Ran latex 1 time(s)"
>>>>> Even when the bib-file or references changed.
>>>>>
>>>>> commands for compilation in my .vimrc:
>>>>> let g:Tex_MultipleCompileFormats = 'pdf'
>>>>> let g:Tex_CompileRule_pdf = 'latexmk -pdf -pvc $*'
>>>>> let g:Tex_DefaultTargetFormat='pdf'
>>>>>
>>>>> I also tried "let g:Tex_CompileRule_pdf = 'latexmk $*'"
>>>>>
>>>>> My .latexmkrc looks like that:
>>>>> $pdflatex = "xelatex -synctex=1 -interaction=nonstopmode %O %S";
>>>>> $bibtex_use = 2;
>>>>> $print_type = 'pdf';
>>>>> $pdf_mode = 1;
>>>>> $pdf_previewer = "open -a /Applications/Skim.app";
>>>>> $pdf_update_method = 0;
>>>>> $clean_ext = "paux lox pdfsync out";
>>>>> $force_mode = 1;
>>>>>
>>>>> As written before: invoking latexmk on the file in the command line
>>>>> "latexmk file.tex" works as it should, only in vim it doesn't.
>>>>>
>>>>> Any ideas?
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> 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...>

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

Re: [Vim-latex-devel] Compiling with latexmk does not work as expected

[Niels K. <ni...@ko...>]

Hi,

thanks for the hint with MacVim. If I run vim from the command line it 
works. Running latexmk directly in MacVim (:!latexmk file) it gives me a 
path-error.
Googled a bit more. Since I am using zsh and MacVim won't read my 
.zshrc, I have to set up the path in .zprofile. Now it works.
Thanks a lot for the hint.

Niels

On 5 Jul 2012, at 21:23, Ted Pavlic wrote:

> Niels --
>
>>> Or could you at least attach
>>> the log file generated by TeX?
>>
>> Just tried to compile the file from a clean directory. There is 
>> nothing
>> generated. There's just in vim the message "Ran latex 1 time(s)".
>> Therefore I think that nothing gets really called.
>
> 	That's very interesting. I notice that you're using a Mac. Are you
> using vim from the Terminal, or are you using something like MacVim? 
> If
> I recall correctly, MacVim had a setting (off by default?) that would
> run the internal instance of vim through a login shell. That would
> ensure your PATH was set correctly. If you didn't have the setting 
> set,
> then you wouldn't have access to everything you might expect to have
> access to.
>
> 	From your Vim, can you try and test your PATH? For example, try
> something like:
>
> :!echo $PATH
>
> or, perhaps better, try:
>
> :!latex
>
> In the latter case, LaTeX should start and give you a prompt. You can
> hit Cntrl+D to exit from LaTeX if it pops up. If it doesn't pop up, 
> then
> Vim cannot find it.
>
> 	--Ted
>
>
>>> Thanks -
>>
>> I have to thank that you take the time and think about my problem :)
>>
>> Niels
>>
>>>> Hi,
>>>>
>>>> I am trying to get something compiled with latexmk and the
>>>> vim-latex-suite. When I invoke latexmk on the file in the command 
>>>> line
>>>> it work w/out any problems. When I invoke the compile in vim I just 
>>>> get:
>>>> "Runnning bibtex…
>>>> Ran latex 1 time(s)"
>>>> Even when the bib-file or references changed.
>>>>
>>>> commands for compilation in my .vimrc:
>>>> let g:Tex_MultipleCompileFormats = 'pdf'
>>>> let g:Tex_CompileRule_pdf = 'latexmk -pdf -pvc $*'
>>>> let g:Tex_DefaultTargetFormat='pdf'
>>>>
>>>> I also tried "let g:Tex_CompileRule_pdf = 'latexmk $*'"
>>>>
>>>> My .latexmkrc looks like that:
>>>> $pdflatex = "xelatex -synctex=1 -interaction=nonstopmode %O %S";
>>>> $bibtex_use = 2;
>>>> $print_type = 'pdf';
>>>> $pdf_mode = 1;
>>>> $pdf_previewer = "open -a /Applications/Skim.app";
>>>> $pdf_update_method = 0;
>>>> $clean_ext = "paux lox pdfsync out";
>>>> $force_mode = 1;
>>>>
>>>> As written before: invoking latexmk on the file in the command line
>>>> "latexmk file.tex" works as it should, only in vim it doesn't.
>>>>
>>>> Any ideas?
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>>
>>>> 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...>

Re: [Vim-latex-devel] Compiling with latexmk does not work as expected

[Ted P. <te...@te...>]

Niels --

>> Or could you at least attach
>> the log file generated by TeX?
> 
> Just tried to compile the file from a clean directory. There is nothing
> generated. There's just in vim the message "Ran latex 1 time(s)".
> Therefore I think that nothing gets really called.

	That's very interesting. I notice that you're using a Mac. Are you
using vim from the Terminal, or are you using something like MacVim? If
I recall correctly, MacVim had a setting (off by default?) that would
run the internal instance of vim through a login shell. That would
ensure your PATH was set correctly. If you didn't have the setting set,
then you wouldn't have access to everything you might expect to have
access to.

	From your Vim, can you try and test your PATH? For example, try
something like:

:!echo $PATH

or, perhaps better, try:

:!latex

In the latter case, LaTeX should start and give you a prompt. You can
hit Cntrl+D to exit from LaTeX if it pops up. If it doesn't pop up, then
Vim cannot find it.

	--Ted


>> Thanks -
> 
> I have to thank that you take the time and think about my problem :)
> 
> Niels
> 
>>> Hi,
>>>
>>> I am trying to get something compiled with latexmk and the
>>> vim-latex-suite. When I invoke latexmk on the file in the command line
>>> it work w/out any problems. When I invoke the compile in vim I just get:
>>> "Runnning bibtex…
>>> Ran latex 1 time(s)"
>>> Even when the bib-file or references changed.
>>>
>>> commands for compilation in my .vimrc:
>>> let g:Tex_MultipleCompileFormats = 'pdf'
>>> let g:Tex_CompileRule_pdf = 'latexmk -pdf -pvc $*'
>>> let g:Tex_DefaultTargetFormat='pdf'
>>>
>>> I also tried "let g:Tex_CompileRule_pdf = 'latexmk $*'"
>>>
>>> My .latexmkrc looks like that:
>>> $pdflatex = "xelatex -synctex=1 -interaction=nonstopmode %O %S";
>>> $bibtex_use = 2;
>>> $print_type = 'pdf';
>>> $pdf_mode = 1;
>>> $pdf_previewer = "open -a /Applications/Skim.app";
>>> $pdf_update_method = 0;
>>> $clean_ext = "paux lox pdfsync out";
>>> $force_mode = 1;
>>>
>>> As written before: invoking latexmk on the file in the command line
>>> "latexmk file.tex" works as it should, only in vim it doesn't.
>>>
>>> Any ideas?
>>>
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> 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...>

Re: [Vim-latex-devel] which github repository is more official?

[Ted P. <te...@te...>]

>> Yes, I read that, but I don't understand it. The Vim-LaTeX sourceforge
>> page is at:
>>
>> http://vim-latex.sourceforge.net/
> 
> You can always configure the above page to make it better. What I
> don't like is the default sf pages.
> 
> http://sourceforge.net/projects/vim-latex/
> 
> The organization of this default sf page is not friendly to a
> developer. A developer usually want to see the code directory directly
> just as in https://github.com/jcf/vim-latex. On the default sf page,
> some less important things are shown on the main page, developers have
> to do a few more clicks.

FYI, you're looking for:

http://vim-latex.git.sourceforge.net/git/gitweb.cgi?p=vim-latex/vim-latex;a=summary

which is linked directly from the Vim-LaTeX web page on the left-hand
bar near the bottom:

http://vim-latex.sourceforge.net/

Once you find that link and clone the corresponding repo on your
machine, you don't even need the website. I guess that's why I don't
understand all the commotion.

--Ted

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

Re: [Vim-latex-devel] Compiling with latexmk does not work as expected

[Peter V. <mai...@pe...>]

I use latexmk too and it works for me.

I also have an addition -bibtex option set

let g:Tex_CompileRule_pdf = "/usr/local/bin/latexmk -bibtex -pdf $*"

Peter


On Thu, Jul 5, 2012 at 12:57 AM, Ted Pavlic <te...@te...> wrote:
> Niels -
>
> That usually means an error or untrapped warning is being generated. Do you
> have the same problem with other files? Is there any way you could send a
> minimal "working" (i.e., failing) example TeX? Or could you at least attach
> the log file generated by TeX?
>
> Thanks -
>
> --Ted
>
> --
> Sent from the mobile device of Ted Pavlic
> Please excuse typos, swypos, or very brief responses
>
> On Jul 4, 2012 1:06 PM, "Niels Kobschätzki" <ni...@ko...> wrote:
>>
>> Hi,
>>
>> I am trying to get something compiled with latexmk and the
>> vim-latex-suite. When I invoke latexmk on the file in the command line
>> it work w/out any problems. When I invoke the compile in vim I just get:
>> "Runnning bibtex…
>> Ran latex 1 time(s)"
>> Even when the bib-file or references changed.
>>
>> commands for compilation in my .vimrc:
>> let g:Tex_MultipleCompileFormats = 'pdf'
>> let g:Tex_CompileRule_pdf = 'latexmk -pdf -pvc $*'
>> let g:Tex_DefaultTargetFormat='pdf'
>>
>> I also tried "let g:Tex_CompileRule_pdf = 'latexmk $*'"
>>
>> My .latexmkrc looks like that:
>> $pdflatex = "xelatex -synctex=1 -interaction=nonstopmode %O %S";
>> $bibtex_use = 2;
>> $print_type = 'pdf';
>> $pdf_mode = 1;
>> $pdf_previewer = "open -a /Applications/Skim.app";
>> $pdf_update_method = 0;
>> $clean_ext = "paux lox pdfsync out";
>> $force_mode = 1;
>>
>> As written before: invoking latexmk on the file in the command line
>> "latexmk file.tex" works as it should, only in vim it doesn't.
>>
>> Any ideas?
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>
>
> ------------------------------------------------------------------------------
> 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
>

Re: [Vim-latex-devel] Compiling with latexmk does not work as expected

[Ted P. <te...@te...>]

Niels -

That usually means an error or untrapped warning is being generated. Do you
have the same problem with other files? Is there any way you could send a
minimal "working" (i.e., failing) example TeX? Or could you at least attach
the log file generated by TeX?

Thanks -

--Ted

--
Sent from the mobile device of Ted Pavlic
Please excuse typos, swypos, or very brief responses
On Jul 4, 2012 1:06 PM, "Niels Kobschätzki" <ni...@ko...> wrote:

> Hi,
>
> I am trying to get something compiled with latexmk and the
> vim-latex-suite. When I invoke latexmk on the file in the command line
> it work w/out any problems. When I invoke the compile in vim I just get:
> "Runnning bibtex…
> Ran latex 1 time(s)"
> Even when the bib-file or references changed.
>
> commands for compilation in my .vimrc:
> let g:Tex_MultipleCompileFormats = 'pdf'
> let g:Tex_CompileRule_pdf = 'latexmk -pdf -pvc $*'
> let g:Tex_DefaultTargetFormat='pdf'
>
> I also tried "let g:Tex_CompileRule_pdf = 'latexmk $*'"
>
> My .latexmkrc looks like that:
> $pdflatex = "xelatex -synctex=1 -interaction=nonstopmode %O %S";
> $bibtex_use = 2;
> $print_type = 'pdf';
> $pdf_mode = 1;
> $pdf_previewer = "open -a /Applications/Skim.app";
> $pdf_update_method = 0;
> $clean_ext = "paux lox pdfsync out";
> $force_mode = 1;
>
> As written before: invoking latexmk on the file in the command line
> "latexmk file.tex" works as it should, only in vim it doesn't.
>
> Any ideas?
>
>
> ------------------------------------------------------------------------------
> 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
>

[Vim-latex-devel] Compiling with latexmk does not work as expected

[Niels K. <ni...@ko...>]

Hi,

I am trying to get something compiled with latexmk and the 
vim-latex-suite. When I invoke latexmk on the file in the command line 
it work w/out any problems. When I invoke the compile in vim I just get:
"Runnning bibtex…
Ran latex 1 time(s)"
Even when the bib-file or references changed.

commands for compilation in my .vimrc:
let g:Tex_MultipleCompileFormats = 'pdf'
let g:Tex_CompileRule_pdf = 'latexmk -pdf -pvc $*'
let g:Tex_DefaultTargetFormat='pdf'

I also tried "let g:Tex_CompileRule_pdf = 'latexmk $*'"

My .latexmkrc looks like that:
$pdflatex = "xelatex -synctex=1 -interaction=nonstopmode %O %S";
$bibtex_use = 2;
$print_type = 'pdf';
$pdf_mode = 1;
$pdf_previewer = "open -a /Applications/Skim.app";
$pdf_update_method = 0;
$clean_ext = "paux lox pdfsync out";
$force_mode = 1;

As written before: invoking latexmk on the file in the command line 
"latexmk file.tex" works as it should, only in vim it doesn't.

Any ideas?

Re: [Vim-latex-devel] which github repository is more official?

[Peng Yu <pen...@gm...>]

On Tue, Jul 3, 2012 at 11:36 AM, Ted Pavlic <te...@te...> wrote:
>> As I said in the previous email, "sf is a badly designed website. I
>> have a much harder time to find the things that I need on sf than on
>> github."
>
> Yes, I read that, but I don't understand it. The Vim-LaTeX sourceforge
> page is at:
>
> http://vim-latex.sourceforge.net/

You can always configure the above page to make it better. What I
don't like is the default sf pages.

http://sourceforge.net/projects/vim-latex/

The organization of this default sf page is not friendly to a
developer. A developer usually want to see the code directory directly
just as in https://github.com/jcf/vim-latex. On the default sf page,
some less important things are shown on the main page, developers have
to do a few more clicks.

-- 
Regards,
Peng

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

[Ted P. <te...@te...>]

> 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...>

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

[Peng Yu <pen...@gm...>]

> :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

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

[Peng Yu <pen...@gm...>]

> 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

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

[Ted P. <te...@te...>]

> 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...>

Re: [Vim-latex-devel] which github repository is more official?

[Ted P. <te...@te...>]

> As I said in the previous email, "sf is a badly designed website. I
> have a much harder time to find the things that I need on sf than on
> github."

Yes, I read that, but I don't understand it. The Vim-LaTeX sourceforge
page is at:

http://vim-latex.sourceforge.net/

What problem do you have with this page *that is related to SF* and
*that could be fixed by migrating to github*? There is nothing
particularly sourceforge-y about this page, and so any trouble you're
having finding the information you want here would be replicated on a
github site. So it seems like your gripe is more with the layout of the
Vim-LaTeX page than with SF itself.

If I am not understanding you correctly, then please explain what aspect
of the LaTeX-suite SF page is causing you the most trouble in finding
the information you want, and how would github improve things?

--Ted

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

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

[Peng Yu <pen...@gm...>]

> :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

Re: [Vim-latex-devel] which github repository is more official?

[Peng Yu <pen...@gm...>]

> How do *you* feel that github is more convenient? Cloning is cloning,
> regardless of where you are cloning from. At the level of distributing
> source via a git repository, the two are equivalent. They differ in
> the additional services provided to collaborating developers, but in
> both cases developers can collaborate effectively without using any of
> those features.

As I said in the previous email, "sf is a badly designed website. I
have a much harder time to find the things that I need on sf than on
github."

-- 
Regards,
Peng

Re: [Vim-latex-devel] Disable short cut for things like ::

[Ted P. <te...@te...>]

See

:help Imap_FreezeImap

Set g:Imap_FreezeImap to 0 in your .vimrc.

:let g:Imap_FreezeImap = 0

That should disable the macro expansion.

--Ted

On Sat, Jun 30, 2012 at 6:48 AM, Peng Yu <pen...@gm...> wrote:
> Hi,
>
> I feel that the short cut defined in vim latex is in convenient. I'd
> like to disable all keyboard shortcut like :: (which is changed to
> \ldots). Is there a way to do?
>
> --
> 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...>

Re: [Vim-latex-devel] which github repository is more official?

[Ted P. <te...@te...>]

> sf is a badly designed website. I have a much harder time to find the
> things that I need on sf than on github.

sf and github have two completely different purposes. github is
primarily meant for hosting git repositories and provides some limited
ability to distribute documentation. Cloning a repo from github is
equivalent to cloning a repo from SF (unless you are using a software
package put together by the github folks).

> I haven't serious compared sf with github. But I've seen more people
> start using github rather than sf (some people also quit google code
> for github), but I have not seen a single example that quit sf for
> github. So I feel that github is the trend. Its pull request feature
> is also very convenient.

Again, I really think that github is not meant to be a substitute for
SF. If anything, it's complementary.

Google Code, however, is much more like an SF alternative. It provides
a mechanism for distributing documentation, gathering bug requests,
scrutinizing patches, and other SF-like features. Although github has
some ability to do these things, github is primarily meant to enable
developer collaboration on particular projects. It is not meant to be
the end-user front end.

> Why these people start cloning into github? My interpretation is that
> github is much more convenient and more people are using github. In
> this case, why not just host the main repository in github and stop
> using sf.

How do *you* feel that github is more convenient? Cloning is cloning,
regardless of where you are cloning from. At the level of distributing
source via a git repository, the two are equivalent. They differ in
the additional services provided to collaborating developers, but in
both cases developers can collaborate effectively without using any of
those features.

--Ted

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

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

[Ted P. <te...@te...>]

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...>

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

[Peng Yu <pen...@gm...>]

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

Re: [Vim-latex-devel] How to disable menus generated by vim-latex?

[Peter V. <mai...@pe...>]

Correction,
set this to disable menus:

let g:Tex_Menus = 0
let g:Tex_PackagesMenu = 0

Peter

On Mon, Jul 2, 2012 at 11:53 AM, Peter Vasil
<mai...@pe...> wrote:
> Hi,
>
> thre is an entry in the manual for menu option,
> http://vim-latex.sourceforge.net/documentation/latex-suite.html#customizing-menus
>
> To dsable Tex menus, set this in your vimrc :
>
> let g:Tex_Menus = 0
> let g:Tex_MathMenus = 0
>
>
> Peter
>
>
> On Sun, Jul 1, 2012 at 6:53 PM, Alessandro Pezzoni
> <ale...@la...> wrote:
>> On Sun, Jul 01, 2012 at 10:22:41AM -0500, Peng Yu wrote:
>>> I never use the menus. It is a waste of time to load them up for me.
>>> Is there a way to disable them?
>>
>> I don't know if there is a way to disable only the vim-latex menus, but
>> you can put "set guioptions-=m" in your .gvimrc to disable menus tout
>> court.
>>
>> Alessandro
>>
>>
>> ------------------------------------------------------------------------------
>> 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

Re: [Vim-latex-devel] How to disable menus generated by vim-latex?

[Peter V. <mai...@pe...>]

Hi,

thre is an entry in the manual for menu option,
http://vim-latex.sourceforge.net/documentation/latex-suite.html#customizing-menus

To dsable Tex menus, set this in your vimrc :

let g:Tex_Menus = 0
let g:Tex_MathMenus = 0


Peter


On Sun, Jul 1, 2012 at 6:53 PM, Alessandro Pezzoni
<ale...@la...> wrote:
> On Sun, Jul 01, 2012 at 10:22:41AM -0500, Peng Yu wrote:
>> I never use the menus. It is a waste of time to load them up for me.
>> Is there a way to disable them?
>
> I don't know if there is a way to disable only the vim-latex menus, but
> you can put "set guioptions-=m" in your .gvimrc to disable menus tout
> court.
>
> Alessandro
>
>
> ------------------------------------------------------------------------------
> 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

Re: [Vim-latex-devel] How to disable menus generated by vim-latex?

[Alessandro P. <ale...@la...>]

On Sun, Jul 01, 2012 at 10:22:41AM -0500, Peng Yu wrote:
> I never use the menus. It is a waste of time to load them up for me.
> Is there a way to disable them?

I don't know if there is a way to disable only the vim-latex menus, but
you can put "set guioptions-=m" in your .gvimrc to disable menus tout
court.

Alessandro

[Vim-latex-devel] How to disable menus generated by vim-latex?

[Peng Yu <pen...@gm...>]

Hi,

I never use the menus. It is a waste of time to load them up for me.
Is there a way to disable them?

-- 
Regards,
Peng

Re: [Vim-latex-devel] which github repository is more official?

[Peng Yu <pen...@gm...>]

On Sat, Jun 30, 2012 at 8:48 PM, Ted Pavlic <te...@te...> wrote:
> Peng -
>
> git is git regardless of the host. Moreover, sf provides much more than just
> a repo to the latex suite. How has sf caused you trouble using the official
> git repo hosted there?

sf is a badly designed website. I have a much harder time to find the
things that I need on sf than on github.

> Or are you just saying it would be easier for you to submit pull requests
> rather than patches? Note that git itself is maintained via patches posted
> to a mailing list rather than pull requests via github. Or do you just like
> that LinkedIn provides a module for showing off your latex suite
> contributions?

I haven't serious compared sf with github. But I've seen more people
start using github rather than sf (some people also quit google code
for github), but I have not seen a single example that quit sf for
github. So I feel that github is the trend. Its pull request feature
is also very convenient.

> Why don't you just setup a clone on github that automatically pulls from the
> sf git repo?
>
> Or are you saying that there are already so many clones by people not
> accustomed to anything but pull requests that the latex suite is getting
> fragmented? (despite all the documentation hooks back to sf)

Why these people start cloning into github? My interpretation is that
github is much more convenient and more people are using github. In
this case, why not just host the main repository in github and stop
using sf.

-- 
Regards,
Peng