Hi,
at least for me, there is one problem with the folding of %%fakesection:
They are nested in sections (see attached test.tex). Imho they should be
at the same level as section.
The attached patch automatically adds %%fakepart, %%fakechapter,... as
folded sections and they are folded at th
. s
>
> ...why do you leave the first part of the branch there? Doesn't your addition
> mitigate the need for special "fake" cases? Can't we just use your addition
> exclusively?
>
> Thanks --
> Ted
>
> On 08/10/2010 04:50 AM, Gerd Wachsmuth w
Hi all,
I attached two small patches:
- the first will correct the behavior of < , there was one "\"
missing.
- the other one will correct the behaviour with bib-files with capital
entries.
Best Regards
Gerddiff -ur '--exclude=.svn' ./ftplugin/latex-suite/brackets.vim
/HOME1/users/persona
Hi,
recently, I customized the EnvMacros in my latex suite. If anyone is
interested, I could provide the following customizations:
- I like to have a carriage return after most of the envmacros => add some
variable like Tex_Env_AddCarriageReturn
- I like to have the \label{} right after the be
Hi,
after vim-latex changed to git, I want to put my vim configuration in a
local git repo located at ~/conf. I would like to link ~/.vim to
~/conf/vim.
Therefore, I have to merge the commits at vim-latex/master:vimfiles/ into
my local repo at the point master:vim/.
I fiddled arround with git
Hi,
I'm looking forward when Till will put vimfiles/ in a separate repo (or
branch). Then I can use the method described in
http://vimcasts.org/episodes/synchronizing-plugins-with-git-submodules-and-pathogen/
This sounds very handy. I think I will also publish my configuration at
github.
Best
>> The only potential issue I see is that after the splitting of the
>> repository, they will have different commit ids than the original
>> repository had. Since the repository is not published that long, I tend
>> to think that this is not important.
>
> That probably won't be much of an issue...
Hi,
I use the F9-completion very often and feel to make some advertising ;)
I patched the outline.py, such that it offers a greater gain for me. But
first I will take up Ted's arguments.
> > Additionally \citep, \citet, \citeauthor, etc... Not sure if they
would
> > match whatever pattern trigg
On Tue, 22 Feb 2011, Ng Oon-Ee wrote:
> On Tue, Feb 22, 2011 at 3:23 PM, Gerd Wachsmuth
> wrote:
>> Hi,
>>
>> I use the F9-completion very often and feel to make some advertising ;)
>> I patched the outline.py, such that it offers a greater gain for me. But
On Tue, 22 Feb 2011, Ng Oon-Ee wrote:
> In a previous thread I mentioned that using main.latexmain breaks
> completion, where main.tex.latexmain fixes it.
>
> Having used this more in actual writing, I've come across buggy
> behaviour while editing subfiles (chap1/chap1.tex for example), where
>
Hi,
with this patch, envmacros.vim allows more customizations.
1.
let g:Tex_EnvLabelprefix_equation = "eq:"
=> labels in equations have the prefix eq:
this works for:
figure,table,theorem,definition,lemma,proposition,corollary,assumption,remark,equation,eqnarray,align,multline
2.
let g:Tex_En
> I can see how someone editing a single
> document would often want to complete both ways.
In which situation you need to stick to the old tex-based completion? I
used my aux-based completion since one or two months and I never missed
the tex-based completion.
The only advantage of the tex-base
> INSTRUCTIONS:-
>
> Test 1-
> 1. edit chap1/chap1.tex
> 2. Type \cite{ then press F9
> 3. Should show up as 0 results.
> 4. Run :edit ../main.tex
> 5. Type \cite{ then press F9
> 6. Results show. Undo everything, then :edit chap1/chap1.tex
> 7. Typing \cite{ then pressing F9 now shows results.
>
>
Hi,
On Tue, 22 Feb 2011, Simon Quittek wrote:
> Hello Gerd,
>
> I think, your ideas are very good, and since I use/would like to use F9
> much more often, I welcome improvement!
> Just to make sure to understand from the users view: instead of typing
> "\eqref{eq" and then looking through the lis
> I noticed that Till has been reviewing a lot of patches on the Patch tracker
> on the Vim-LaTeX website at Sourceforge. It might be a nice idea to post this
> there too (it's too bad that tracker doesn't post to the list -- to give the
> best of both worlds).
I was not aware of this possibilit
Hi Martin,
the problem is, that Vim does not distinguish between "é" and (alt
+ i) and is mapped by the latex-suite (insert \item in
itemize/enumerate).
Your solution would be: Insert "iunmap é" (or "iunmap ") in
ftplugin/tex.vim.
Best regards
Gerd
On 03/01/2011 11:03 PM, Martin Pulec wrote:
The file
ftplugin/tex.vim
is not overwritten by latex-suite (vimlatex). It is intended to use this
file for customizations of the latex-suite and for settings which
belongs to tex-files only.
Regards
On 03/02/2011 05:58 PM, Gianluca Meneghello wrote:
> I had the same problem, so thanks for redir
Hi,
you have actually two possibilities:
- map "IMAP_JumpForward" to any other key (see plugins/imap.vim,
line 489) in your .vimrc
- remove the mapping in ".vim/after/plugin/imaps.vim"
Regards
Gerd
On 10/18/2011 07:05 PM, Charles LeDoux wrote:
> Hello,
>
> How can I remove or remap the ma
Hi,
what command do you use to set Tex_IgnoredWarnings in you
ftplugin/tex.vim? You have to use "let" and not "TexLet", see also the
comments at the beginning of texrc:
" 2. Just set values of each setting individually in your
"$VIMFILES/ftplugin/tex.vim file. (See above for w
It's also possible to use
\begin{frame}
\frametitle{Frame name}
\end{frame}
with LaTeX Beamer.
Regards
Gerd
On 10/27/2011 06:38 PM, Ted Pavlic wrote:
> Of course, another option is to include a comment after each
> \begin{frame} that is descriptive:
>
> \begin{frame}{Frame name}
> % Frame
:
> --
>
> Comment By: Gerd Wachsmuth (gerw)
> Date: 2011-10-15 12:40
>
> Message:
> I can't upload the patch here. (Why?)
>
> I send it on the mailinglist.
>
> -
I would suggest the following:
- Read the manual, in particular:
http://vim-latex.sourceforge.net/documentation/latex-suite.html#customizing-compiling
- Add something like "LaTeX Warning: Label `%.%#' multiply defined.".
Regards
Gerd
On 11/18/2011 06:38 PM, David Karapetyan wrote:
> Yes, this
Try
call IMAP('DEF', '\begin{definition}\<++>\\end{definition}<++>',
'tex')
Regards
Gerd
On 01/18/2012 07:58 PM, abstractd wrote:
> How do I change the following
> call IMAP('DEF', '\begin{definition}<++>\end{definition}<++>', 'tex')
> (in my tex.vim) such that it adds an empty line between begi
Please read the FAQ:
http://vim-latex.sourceforge.net/index.php?subject=faq&title=FAQ
On 02/03/2012 01:46 PM, EEva wrote:
> Hi vim-latex list,
>
> I come to you since I encountered a strange behaviour from both vim and gvim
> while using the vim-latexsuite extension. I just can't type 'é' (in In
Hi Guido,
Vim cannot distinguish between "ì" and (meta/alt + l). Hence,
typing ì is superseeded by the mapping to Tex_LeftRight in the
file "ftplugin/latex-suite/brackets.vim".
A workaround would be the mapping similar
imap lr Tex_LeftRight
in "~/.vim/ftplugin/tex.vim".
@all: Is there a tab
I've put
augroup filetypedetect
" Some LaTeX types
au! BufRead,BufNewFile *.cls setfiletype tex
au! BufRead,BufNewFile *.lco setfiletype tex
augroup END
in my ".vim/filetype.vim" and
syntax on
filetype plugin on
in my ".vimrc".
Best Regards
Gerd
On 04/11/2012 10:47
In my personal copy of the latex-suite
(https://github.com/gerw/vim-latex-suite) I used the following change in
ftplugin/latex-suite/texviewer.vim to avoid those empty buffers.
Regards
Gerd
@@ -855,7 +856,8 @@ function! Tex_FindBibFiles()
call Tex_Debug(":Tex_FindBibFiles: ", "view")
Hi,
try (maybe with some quotes)
iskeyword+=-_
By the way, pressing after "\ref{eq:" should also work!?
Regards
Gerd
On 06/18/2012 11:27 PM, Tohiko Looka wrote:
> Greetings,
>
> I included the following line in my tex.vim file
> set iskeyword+=:
> And now I can type "\ref{eqn:" and then pr
On 07/09/2012 09:25 AM, Ted Pavlic wrote:
>>> for shortcite (and do something similar for your other options).
>>
>> I actually do not want to go this way. When tex.vim gets updated, I have
>> to copy it over again, patch in my stuff again etc. Thus I hope for
>> finding a way to do it locally as i
On 07/17/2012 09:01 PM, Ted Pavlic wrote:
>> Is that means I donot need to modify ~.vim/ftplugin/latex-suite/texrc, and
>> just overwrite it by putting setting in .vimrc file?
>
> That's correct. You should not edit the texrc file. For one, if you ever
> update your LaTeX-suite to add new bug fixe
> So
> 1. Why latex-suite behaves differently on my computer other than the
> "default" behavior?
Because the documentation is not up to date.
> 2. Is there any way to let the \label<++> be placed ALWAYS at the first
> line of an environment? I know I can
> customize them one by one, but I have no
For me this works as expected. Which version of latex-suite do you use?
On 11/16/2012 01:44 PM, Alan Grossfield wrote:
> When I write longish latex documents, I often break them into pieces
> (using \input) and keep multiple files open using gvim's vsplit
> command. I've noticed that if I do this
ion?
>
> Raniere
>
> On Fri, Nov 16, 2012 at 10:57 AM, Gerd Wachsmuth
> wrote:
>> For me this works as expected. Which version of latex-suite do you use?
>>
>> On 11/16/2012 01:44 PM, Alan Grossfield wrote:
>>> When I write longish latex documents, I often b
, Alessandro Pezzoni wrote:
> 2012/11/16 Gerd Wachsmuth :
>> latex-suite does not have a version number (any more). So the question
>> reduces to "Where (and possibly when) did you get latex-suite from?".
>
> Well, he did say "as distributed under Fedora"...
&
Hi,
I can confirm that this issue remains fer the current official version
of latex-suite, but is fixed in my repo
https://github.com/gerw/vim-latex-suite
See in particular the commits
https://github.com/gerw/vim-latex-suite/commit/ae303c1f0df77583d685cf4b81cb6f8914ee070c
https://github.com/ge
Hi,
I can't reproduce this behaviour. All registers ("", "*, "+) are not
affected by opening a new (g)vim session (with or without latex-suite).
I'm using my own version of latex-suite
(https://github.com/gerw/vim-latex-suite).
Regards
Gerd
On 02/09/2013 09:18 PM, David Woodfall wrote:
> On
I cannot reproduce this behaviour. You might want to set
let g:Tex_Debug = 1
let g:Tex_DebugLog = "vim-latex-suite.log"
in .vim/ftplugin/tex.vim
and watch the debug file while loading your tex file.
Regards
Gerd
On 02/25/2013 10:34 AM, André Gaul wrote:
> Am 22.02.2013 16:15, schrieb Mirko H
Dear Marc,
this is not a problem of vim-latexsuite, but of the syntax file of vim
for tex. It is typically located in a location like
/usr/share/vim/vim73/syntax/tex.vim
However, the best solution would be to create a file
.vim/syntax/tex/breqn.vim
which contains the highlighting information
Hi,
try something like
call IMAP ('()', '(<++>)<++>', '')
in your ~/.texrc, see also .vim/ftplugin/latex-suite/main.vim for the
other bracket-mappings.
On 04/07/2013 02:27 PM, Ivan Diaz wrote:
> Hi there!
>
> I just came across vim-latex recently, and I love it! Thanks for all the
> hard work
One should rather define Tex_Env_figure or add the code
if !exists("g:Tex_package_detected")
let g:Tex_package_detected = 'graphicx'
elseif g:Tex_package_detected !~ '\'
let g:Tex_package_detected = g:Tex_package_detected.',graphicx'
endif
to .vim/after/ftplugin/tex.vim.
Read the
Hi,
this may come from the folding of your file. Try to disable folding
http://stackoverflow.com/questions/3322453/how-can-i-disable-code-folding-in-vim-with-vim-latex
and try again. If this helps, the folding is the bad guy.
Another possibility is to disable the menus. Add
" no Tex-Menus
let
I have no problem with the spell checking, even if I use the
standard tex.syntax (which is versioned with 57):
gerw:~/head -n 6 /usr/share/vim/current/syntax/tex.vim
" Vim syntax file
" Language: TeX
" Maintainer: Dr. Charles E. Campbell, Jr.
" Last Change: Aug 12, 2010
" Version: 57
Hi,
s:figure_graphicx is invoked, if the graphicx package is detected. If
the automatic detection does not work for you (and you always use the
graphicx package), you could put
"" Add graphicx to the detected packages (such that EFI uses
\includegraphics)
if !exists("g:Tex_package_detected")
Hi,
this seems to be a strange interaction with the IMAP-features of the
latex-suite.
I tried
:iab a (m)
:iab m [a]
Now,
a => (m)
a => ([a])
Here, first a is expanded to (m) and the inner m is expanded to [a].
If one uses
let Imap_FreezeImap=1
triggers no expansions, but works correctly
Hi,
you can file a pull-request on github
(https://github.com/vim-latex/vim-latex) or you can send the patch to
the mailing list.
Best Regards,
Gerd
On 2015-07-06 02:41, Carlos Eduardo de Andrade wrote:
> Hi all,
>
> I usually use a lot of bibfiles such as:
>
> \bibliography{./bibfiles/agt,%
Thank you for reporting. This bug is already fixed in the current
version of latex-suite, see
https://github.com/vim-latex/vim-latex/commit/0c766a7ecf9eda8f616ad2db5741fca98c7181c8
Best Regards,
Gerd
On 2016-05-05 01:42, Enrique Escalante wrote:
> Hello everybody,
>
> I'm using the LaTeX-Suite
Hi,
I cannot reproduce your behaviour. Which settings concerning
cite-completion do you use? In particular, what is
Tex_UseCiteCompletionVer2
Tex_RememberCiteSearch
Which version of latex-suite do you use?
Best Regards,
Gerd
On 05/26/2016 01:35 AM, Rosas, Alexandre wrote:
> Dear all,
> is
Hi Alexandre,
> Latex suite version: 1.8.23
Unfortunately, this does not say very much - the version number is
1.8.23 since May 2006...
Where did you download latex-suite? Can you try the most recent version from
https://github.com/vim-latex/vim-latex/archive/master.zip
?
Best Regards,
Gerd
Thank you for your reply - glad that it worked.
Best regards,
Gerd
On 2016-05-27 23:00, Rosas, Alexandre wrote:
> Hi Gerd,
> I download and installed the newest version and the problem went away.
> Thank you for your help.
> Alexandre
>
> From: gerd.wachsm
Dear George,
yes, indeed, vim-latex greps through the tex-file for \labels, see
ftplugin/latex-suite/outline.py. You could also try to change the logic
to cope with tcolorbox's theorems.
Or, you try my version of vim-latex at
https://github.com/gerw/vim-latex-suite. There, I changed the logic
Hi George,
> Before I install your version, is there any small change that I can do
> to implement this feature in my existing installation? I tried replacing
> my /ftplugin/latex-suite/outline.py/ with yours from github, but this
> didn't change anything with the issue I described.
You have to us
Hi,
did you read
http://vim-latex.sourceforge.net/documentation/latex-suite/latex-project.html
? In particular, did you have a file like "main.tex.latexmain"?
Best regards,
Gerd
On 08/11/2016 03:26 PM, Guido Milanese wrote:
> Hello! I am writing a manual and, given the complexity of the proje
> Additional question: is there a system to list all the labels not as
> they are in the document structure, bu alfabetically? I tried an
> internal/external "sort" but 'modifiable' is off and so it does not work.
No, this is not possible. You could just do ":set modifiable!", or you
could try to
Hi,
what about
http://vim-latex.sourceforge.net/documentation/latex-suite/recommended-settings.html
?
I agree that the download instructions at
http://vim-latex.sourceforge.net/index.php?subject=download
could be enhanced by mentioning:
- the direct cloning of the github repository
- usage of
Hi,
this was not possible up to now. I have pushed a fix to this problem to
the upstream git repository (https://github.com/vim-latex/vim-latex).
However, this will not help you, since there will be some lag until this
is included in package managers.
So you could also try to convince/force yo
Hi,
I think this is an issue with the compatibility mode of vim. What does
:set compatible?
:set cpoptions?
say? You may want to add
set nocompatible
at the beginning of your vimrc file.
Best regards,
Gerd
On 2016-10-20 11:44, Christoffer Østfeldt wrote:
> Hi there
>
> I am experiencing wha
Hi,
latex-suite does not deal with the spell checking. Which part of the
tex-file is spell-checked depends on the syntax file (syntax/tex.vim),
which is not provided by the latex-suite.
Best regards,
Gerd
On 2016-10-20 19:32, Le Cocq wrote:
> Hello.
>
> Although I have activated spell in frenc
Hi,
in my version of latex-suite (https://github.com/gerw/vim-latex-suite),
I have changed the mechanism of \ref-completions. The current version of
latex-suite greps through the tex-file for \labels. My version greps
through the aux-file. This has the advantage, that one does not have to
memo
latex-devel@lists.sourceforge.net"
>>
>> Subject: Re: [Vim-latex-devel] Aux completion
>>
>> Please do not remove the current functionality. I think it would be very
>> annoying to rely on the aux file being up-to-date.
>>
>> Well-chosen keys are
Hi,
> - F9 works only after the first compilation (not too restrictive)
> - F9 completes based on either labels or current reference numbers. -
> The labels method works almost as before, except that the outline window
> does not show a preview of the relevant part of the .tex file.
Yes.
> For t
Hi,
> 1) When I type eqnarray, hit it does create the environment but
> with different placeholders than the ones in the tutorial and it doesn't
> have the \label there. Can you please update the tutorial so it matches
> the current state?
Yes, this should be preferable. The current version of la
> After setting the winaltkeys to 'no' it no longer triggers the menu
> but it prints characters like éě and such instead.
Yes, this is intended behavior of newer versions of the latex-suite. Vim
is not able to distinguish between, e.g., and é (see :help
map-alt-keys). Therefore, these alt-mapping
Hi,
there is currently no possibility to disable this feature globally.
However, you can set
:let b:Tex_MainFileExpression = expand('%:p')
in the buffers belonging to your tikzfig*.tex files to explicitly set
the main file for compilation.
Hope this helps,
Gerd
On 03/22/2017 02:12 PM, Ch
Hi Daryl,
this is weird. In fact, `:help creating-menus` states:
>
Special characters in a menu name:
Separates the menu name from right-aligned text. This can be
used to show the equivalent typed command. The text ""
can be used here for convenience. If you are u
o, there is nothing after the word Compile (or any of its siblings)
in the TeX-Suite menu. So, feeling brave, I opened texmenuconf.vim and
on line 56 deleted the after the word "Compile" and got the -ll.
When I added a space after "Compile", the -ll disappeared.
So, reco
Dear Kevin,
what you describe is currently not possible, i.e., you cannot remove the
"" after "\begin{someenv}" directly by some configuration variable.
However, you can define
let g:Tex_Env_someenv =
"\\begin{someenv}[<+optional+>]{<+mandatory+>}\<++>\\\end{someenv}"
in your `.vim/ftplugi
Hi,
what do you mean by 'tikz commutative diagrams do not work'? Does the
code not compile? Is the syntax highlighting wrong? Please provide some
more details!
Best regards,
Gerd
On 17/04/2019 17:19, Daniel Ricardo Barrero wrote:
Hello dear latex-suite development team. I've been using the
tion,
Daniel R. Barrero R.
El vie., 26 abr. 2019 a las 1:19, Gerd Wachsmuth
(<mailto:gerd.wachsm...@mathematik.tu-chemnitz.de>>) escribió:
Hi,
what do you mean by 'tikz commutative diagrams do not work'? Does the
code not compile? Is the syntax highlighting wrong
]<++>{<++>a<++>r<++>t<++>i<++>c<++>l<++>e<++>}<++>
<++>\<++>p<++>a<++>g<++>e<++>s<++>t<++>y<++>l<++>e<++>{<++>e<++>m<++>p<++>t<++>y<++>}&
69 matches
Mail list logo
