Thread: [Vim-latex-devel] improved texviewer.vim
Brought to you by:
srinathava,
tmaas
Menu
▾
▴
vim-latex-devel
|
From: Mikolaj M. <mi...@wp...> - 2003-04-10 22:27:02
|
Hello, I'am commiting texviewer.vim with improved searching for bibfiles - use of \bibliography command, taking care about main file. But I think that with limited possibilities[1] of using external programs like grep it is not possible to make much better "engine". Ultimate solution would be project file with data about all files - *tex, *bib, whatever, project settings (for this article I want make ps for another pdf is better) and so on. Here is at least one hard issue: managing data about files (we have full explorer.vim to hack) The only easy thing is name and location: This is just our *.latexmain file. m. |
|
From: Luc H. <her...@fr...> - 2003-04-10 23:24:23
|
* On Fri, Apr 11, 2003 at 12:00:34AM +0200, Mikolaj Machowski <mi...@wp...> wrote: > The only easy thing is name and location: This is just our *.latexmain > file. Well. Actually, I'd prefer you improve this method to the one I use into my tex-tools.vim. If a variable like g:TeXName exists, it is used; otherwise, if a file named *.latexmain exists it is used; otherwise : we ask for the name of the main file to the end-user. See the function s:CheckMainFile() in: http://hermitte.free.fr/vim/ressources/vimfiles/ftplugin/tex/tex-tools.vim Hum ... looking at the code, I see it needs some improvments, but that's the idea. -- Luc Hermitte http://hermitte.free.fr/vim/ |
|
From: Alan S. <ala...@po...> - 2003-04-11 09:48:32
|
* Luc Hermitte (her...@fr...) wrote: > * On Fri, Apr 11, 2003 at 12:00:34AM +0200, Mikolaj Machowski <mi...@wp...> wrote: > > The only easy thing is name and location: This is just our *.latexmain > > file. > > Well. Actually, I'd prefer you improve this method to the one I use into > my tex-tools.vim. If a variable like g:TeXName exists, it is used; > otherwise, if a file named *.latexmain exists it is used; otherwise : we > ask for the name of the main file to the end-user. > > See the function s:CheckMainFile() in: > http://hermitte.free.fr/vim/ressources/vimfiles/ftplugin/tex/tex-tools.vim > > Hum ... looking at the code, I see it needs some improvments, but that's > the idea. By the way, did my compiler patch make it in the repository (the one that overrides a Makefile if .latexmain is present) ? Alan -- The hacker: someone who figured things out and made something cool happen. |
|
From: Alan S. <ala...@po...> - 2003-04-11 10:24:47
|
* Alan Schmitt (ala...@po...) wrote:
> By the way, did my compiler patch make it in the repository (the one
> that overrides a Makefile if .latexmain is present) ?
I just looked at the latest cvs, and there is still a problem, I think.
At the moment, the following logic is used to choose how to compile:
if there is a makefile
do make
else if g:partcomp is set
do partial compilation
else
call the latex compiler on
the current file if there is not .latexmain
.latexmain if there is one
Several things bother me:
- if there is a Makefile, the presence of .latexmain does not change
anything
- if there is a Makefile, partial compilation cannot be used
I'd rather have something like:
if g:partcomp is set
do partial compilation
else if there is a makefile and no .latexmain
do make
else
call the latex compiler on
the current file if there is not .latexmain
.latexmain if there is one
I'm ready to send a patch that does this, but I want to make sure it'd
be considered for inclusion (I've already sent to patches addressing
this before g:partcomp got in, and both silently disappeared).
Alan
--
The hacker: someone who figured things out and made something cool happen.
|
|
From: Mikolaj M. <mi...@wp...> - 2003-04-11 16:39:15
|
On Fri, Apr 11, 2003 at 06:24:03AM -0400, Alan Schmitt wrote: > Several things bother me: > - if there is a Makefile, the presence of .latexmain does not change > anything > - if there is a Makefile, partial compilation cannot be used > I'd rather have something like: > if g:partcomp is set > do partial compilation > else if there is a makefile and no .latexmain > do make > else > call the latex compiler on > the current file if there is not .latexmain > .latexmain if there is one > > I'm ready to send a patch that does this, but I want to make sure it'd > be considered for inclusion (I've already sent to patches addressing > this before g:partcomp got in, and both silently disappeared). I will be considered now :) m. |
|
From: Alan S. <ala...@po...> - 2003-04-12 10:03:21
Attachments:
compiler.vim.patch
compiler.vim.context.patch
|
* Mikolaj Machowski (mi...@wp...) wrote: > On Fri, Apr 11, 2003 at 06:24:03AM -0400, Alan Schmitt wrote: > > Several things bother me: > > - if there is a Makefile, the presence of .latexmain does not change > > anything > > - if there is a Makefile, partial compilation cannot be used > > I'd rather have something like: > > if g:partcomp is set > > do partial compilation > > else if there is a makefile and no .latexmain > > do make > > else > > call the latex compiler on > > the current file if there is not .latexmain > > .latexmain if there is one > > > > I'm ready to send a patch that does this, but I want to make sure it'd > > be considered for inclusion (I've already sent to patches addressing > > this before g:partcomp got in, and both silently disappeared). > > I will be considered now :) Here it is then, in attachment (one is simple diff, the other one is contextual diff). Alan -- The hacker: someone who figured things out and made something cool happen. |
|
From: Mikolaj M. <mi...@wp...> - 2003-04-11 09:50:35
|
On Fri, Apr 11, 2003 at 12:43:40AM +0200, Luc Hermitte wrote: > * On Fri, Apr 11, 2003 at 12:00:34AM +0200, Mikolaj Machowski <mi...@wp...> wrote: > > The only easy thing is name and location: This is just our *.latexmain > > file. > Well. Actually, I'd prefer you improve this method to the one I use into > my tex-tools.vim. If a variable like g:TeXName exists, it is used; > otherwise, if a file named *.latexmain exists it is used; otherwise : we > ask for the name of the main file to the end-user. > See the function s:CheckMainFile() in: > http://hermitte.free.fr/vim/ressources/vimfiles/ftplugin/tex/tex-tools.vim > Hum ... looking at the code, I see it needs some improvments, but that's > the idea. You are saying about your code or my code here? I don't want to introduce new function to do the same thing. If you want to improve GetMainFileName or replace it ask Srinath. m. |
|
From: Luc H. <her...@fr...> - 2003-04-11 10:16:27
|
Hello, * On Fri, Apr 11, 2003 at 11:14:39AM +0200, Mikolaj Machowski <mi...@wp...> wrote: > > Hum ... looking at the code, I see it needs some improvments, but > > that's the idea. > > You are saying about your code or my code here? Mine. Definitively! The function is quite complex and lacks of comments. > I don't want to introduce new function to do the same thing. If you > want to improve GetMainFileName or replace it ask Srinath. That's the method I should have used: a function like GetMainFileName(). But before, I have two big piece of plugins I want to finish. Then I'll look at the vim-latex what will be soon released and get to Srinath. -- Luc Hermitte http://hermitte.free.fr/vim/ |
|
From: Srinath A. <sr...@fa...> - 2003-04-11 00:25:49
|
Well, what about requiring that *.latexmain be a vim script file which
defines various project specific things like:
g:Tex_DefaultTargetFormat
g:Tex_CompileRule_{g:Tex_DefaultTargetFormat}
etc... I have not taken a look at the kind of customization which your
texviewer needs, but maybe each individual .latexmain file can contain
such stuff...
BTW, explorer.vim is not ideally suited to such things. Maybe
project.vim which is another highly rated vim script. Infact, I think
project.vim can handle such things by itself, i.e it checks for scripts
to run on entering each project etc. (Again, I haven't tried it much,
but thats what it says in the description)
Srinath
On Fri, 11 Apr 2003, Mikolaj Machowski wrote:
> Hello,
>
> I'am commiting texviewer.vim with improved searching for bibfiles - use
> of \bibliography command, taking care about main file.
>
> But I think that with limited possibilities[1] of using external programs
> like grep it is not possible to make much better "engine". Ultimate
> solution would be project file with data about all files - *tex, *bib,
> whatever, project settings (for this article I want make ps for another
> pdf is better) and so on. Here is at least one hard issue:
>
> managing data about files (we have full explorer.vim to hack)
>
> The only easy thing is name and location: This is just our *.latexmain
> file.
>
> m.
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
> for complex code. Debugging C/C++ programs can leave you feeling lost and
> disoriented. TotalView can help you find your way. Available on major UNIX
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>
>
|
|
From: Mikolaj M. <mi...@wp...> - 2003-04-11 09:41:56
|
On Thu, Apr 10, 2003 at 05:25:42PM -0700, Srinath Avadhanula wrote:
> Well, what about requiring that *.latexmain be a vim script file which
> defines various project specific things like:
> g:Tex_DefaultTargetFormat
> g:Tex_CompileRule_{g:Tex_DefaultTargetFormat}
> etc... I have not taken a look at the kind of customization which your
> texviewer needs, but maybe each individual .latexmain file can contain
> such stuff...
This would be not only for texviewer.vim. Although most suitable here:
eg. no need for scan many files - just check g:Tex_ProjectBibFiles and
grep files from this variable - now doesn't exist perfect method to get
info about all files involved in project. Of course you can scan file,
main file, included files, files included in included files but this is
ineffective and time/resource expensive.
> BTW, explorer.vim is not ideally suited to such things. Maybe
> project.vim which is another highly rated vim script. Infact, I think
> project.vim can handle such things by itself, i.e it checks for scripts
> to run on entering each project etc. (Again, I haven't tried it much,
> but thats what it says in the description)
OK. I will look into it. Writing about explorer.vim I was thinking
rather about switching from normal explorer view into project view.
m.
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X