Hi,
I am using Vim 7.0 under Windows XP and I have installed Vim-LaTeX on
top of it. One problem that I have is not being able to view PDF
output of my tex files. I have Adobe Acrobat 7.0 (full version) and
after I compile my file to PDF target, the PDF file is generated, but
issuing \lv command d
preciate that.
Have a good time,
Hooman
On 6/11/06, Vaidotas Zemlys <[EMAIL PROTECTED]> wrote:
> Hi,
> Št, 2006 06 10 02:26 -0400, coupled cores rašė:
> > Hi,
> >
> > I am using Vim 7.0 under Windows XP and I have installed Vim-LaTeX on
> > top of it. One
Hi List,
I have installed a copy of GNU grep for in windows XP and it is
working fine. I have installed it in a directory which doesn't have
any spaces in its name and it is in the %PATH% variable. I can run
grep from command line.
The problem is that when I try to use F9 to complete my \ref and
Hi Marc,
I had exactly the same problem and it took me a long time to fix it.
Turned out that after I installed Python on my windows XP machine,
everything worked fine. That outline is a python code in LaTeX-Suite.
I wasn't sure about this, but as soon as I installed Python my f9
started to work n
Yes that's the file that you are looking for. In Win XP it is called _vimrc and in Unix it is called .vimrc. HoomanOn 7/27/06, Diego Acosta <
[EMAIL PROTECTED]> wrote:Dear developers,
I am trying to install and use VIM-Latex on a Win XP laptop per these instructions:
http://vim-latex.sourceforge.ne
Hi List,
I have upgraded my TeX implementation to MikTeX 2.5 and I have
problems when I use \lv to view the DVI file. The compilation finishes
without any error, but when I press \lv, instead of my own file (which
has the name main.dvi), YAP opens a file which has the same name, but
it is located
Hello,
I know that the F9 issue has been discussed couple of times in the
list, but unfortunately nobody has given a decisive reply to resolve
the problem.
I had to re-format my computer and I lost all my settings. Now, I have
installed gVim, Vim-LaTeX, python 2.5 and grep 2.51a on my Win XP
mach
Regarding the second scenario that I sent in my previous email, I
found what was causing it. It was basically the fact that the file
simplication.tex wasn't in that directory.
Now, I am sure that what causes the problem is the spaces in the
directory names. I had this problem once before, but I th
Hi,
When I compile a file using \ll, for each run of latex a command
window pops up and then closes. Is there a way to run latex silently
and suppress those command windows from poppin up?
Regards,
Hooman
-
Using Tomcat but
Dear All,
After days of having lots of problems with command completion in
directories which their folders have spaces in their names, I
discovered that the cause of the problem is the WinManager module. I
can't figure out whether bufexplorer causes it, or the WinManager, but
when I removed WinMan
helps.
Cheers,
Hooman
On 10/23/06, Guido Milanese <[EMAIL PROTECTED]> wrote:
> On Saturday 21 October 2006 08:23, coupled cores wrote:
> > Dear All,
> >
> > After days of having lots of problems with command completion in
> > directories which their fold
Hi Stephan
I have had this problem and I struggled with for some time. Here is my
experience with it. Some of might be irrelevant, but it is the
configuration that I come up with that works:
1. Install Vim in a directory which doesn't have a space in its name.
My choice is: C:\Vim.
2. Install Pyt
Dear All,
I have been experiencing this problem recently after I upgraded my
MikTeX from 2.4 to 2.5. After compiling with \ll to dvi, I can open
the dvi file with \lv, but if I chance something in my tex file and
compile it again I get an error message that:
I can't write on file `mythesis.dvi'.
Hi
Unfortunately, I haven't found a solution to this problem. I have
noticed that the problem happens only when the AUX files is changes
(for example a new label is added, a new reference is added,
pagination is changed, etc.). In such cases I just close the file in
YAP and then issue the \lv comm
Hi Ritesh,
I had the same problem on Win XP machine. The solution to your first
question is simple. Just put the following line in your _vimrc file
(or .vimrc if it is called that in Mac OS X):
let g:tex_flavor='latex'
This will solve the first part of your problem. As soon as you create
a new T
Hi,
I think this has been discusses in the list before. Search the list
for and I am pretty sure you find some information.
When I compile multi-file projects this feature doesn't work, but for
single file TeX files, it shows the location of the error.
Best,
Hooman
On 2/25/07, Jushan Bai <[EMAI
I certainly hope that the development is not dead. There was an email
from Srinath some time ago on the list that he is graduated and he can
spend more time on vim-latex. This is a wonderful vim plugin and I
think it shouldn't be discontinued.
On 3/7/07, Yigal Weinstein <[EMAIL PROTECTED]> wrote:
Dear Sebastian,
I have noticed this behaviour. When you use raw TeX code inside a
LaTeX document, the _(underscore) and ^ and @ are highlighted with a
red background. I think the syntax highlighting of the LaTeX files
expects these special characters to appear only inside math
environment such as
18 matches
Mail list logo
