vim-latex-devel Mailing List for Vim-Latex (Page 100)
Brought to you by:
srinathava,
tmaas
Menu
▾
▴
vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(120) |
Dec
(118) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(145) |
Feb
(23) |
Mar
(30) |
Apr
(50) |
May
(88) |
Jun
(49) |
Jul
(41) |
Aug
(13) |
Sep
(51) |
Oct
(30) |
Nov
(80) |
Dec
(43) |
| 2004 |
Jan
(15) |
Feb
(25) |
Mar
(48) |
Apr
(12) |
May
(37) |
Jun
(52) |
Jul
(16) |
Aug
(10) |
Sep
(7) |
Oct
(19) |
Nov
(17) |
Dec
(19) |
| 2005 |
Jan
(15) |
Feb
(5) |
Mar
(7) |
Apr
(3) |
May
(2) |
Jun
(4) |
Jul
(3) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
(16) |
Dec
(16) |
| 2006 |
Jan
(15) |
Feb
(27) |
Mar
(49) |
Apr
(31) |
May
(24) |
Jun
(12) |
Jul
(23) |
Aug
(13) |
Sep
(22) |
Oct
(6) |
Nov
(8) |
Dec
(10) |
| 2007 |
Jan
(3) |
Feb
(13) |
Mar
(19) |
Apr
(1) |
May
(5) |
Jun
(10) |
Jul
(2) |
Aug
(13) |
Sep
(10) |
Oct
(2) |
Nov
(30) |
Dec
(15) |
| 2008 |
Jan
(11) |
Feb
(9) |
Mar
(27) |
Apr
(27) |
May
(22) |
Jun
(29) |
Jul
|
Aug
(21) |
Sep
(6) |
Oct
(4) |
Nov
(9) |
Dec
(2) |
| 2009 |
Jan
(52) |
Feb
(21) |
Mar
(9) |
Apr
(41) |
May
(13) |
Jun
(8) |
Jul
(5) |
Aug
(31) |
Sep
(14) |
Oct
(10) |
Nov
(17) |
Dec
(17) |
| 2010 |
Jan
(25) |
Feb
(22) |
Mar
(22) |
Apr
(24) |
May
(35) |
Jun
(23) |
Jul
(22) |
Aug
(10) |
Sep
(6) |
Oct
(29) |
Nov
(8) |
Dec
(6) |
| 2011 |
Jan
(12) |
Feb
(89) |
Mar
(41) |
Apr
(8) |
May
(17) |
Jun
(11) |
Jul
(3) |
Aug
(13) |
Sep
(14) |
Oct
(23) |
Nov
(8) |
Dec
(9) |
| 2012 |
Jan
(15) |
Feb
(27) |
Mar
(6) |
Apr
(17) |
May
(29) |
Jun
(9) |
Jul
(50) |
Aug
(15) |
Sep
(11) |
Oct
(12) |
Nov
(22) |
Dec
(7) |
| 2013 |
Jan
(24) |
Feb
(32) |
Mar
(6) |
Apr
(5) |
May
(2) |
Jun
(15) |
Jul
(20) |
Aug
(1) |
Sep
(3) |
Oct
(2) |
Nov
(7) |
Dec
(4) |
| 2014 |
Jan
(3) |
Feb
(7) |
Mar
(4) |
Apr
|
May
(4) |
Jun
(5) |
Jul
(4) |
Aug
(3) |
Sep
(9) |
Oct
|
Nov
(2) |
Dec
(3) |
| 2015 |
Jan
|
Feb
(4) |
Mar
(9) |
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
(6) |
Sep
(2) |
Oct
|
Nov
(6) |
Dec
|
| 2016 |
Jan
(1) |
Feb
(11) |
Mar
(4) |
Apr
(2) |
May
(8) |
Jun
(9) |
Jul
|
Aug
(9) |
Sep
(2) |
Oct
(7) |
Nov
|
Dec
|
| 2017 |
Jan
(7) |
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
| 2018 |
Jan
(1) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Mikolaj M. <mi...@wp...> - 2003-04-27 16:37:06
|
On Fri, Apr 25, 2003 at 01:42:38PM -0700, Srinath Avadhanula wrote: > Never mind... I patched up texviewer.vim for the time being... The code > in Tex_complete() for calcuating s:prefix etc seems a little hacky... > Should clean that up if someone gets more time. Hacky? s:prefix is easy - s:type is problem. But it this way we can get all info about command. About subject: Few days ago I was asked about shortcut for \item in lS. Of course there is no hardcoded and I am against placing somewhere _in_ lS: :inoremap ,i \item In AUCTeX is mapping like <Tab> (or <C-Tab>) in itemized environments it inserts \item. Technically in Vim this is possible but I don't know whick key should be shortcut: 1. <Tab> IMO is out of question. It is widely(?) used as mapping for <C-N>, <C-P> (tip #102). Of course, we could incorporate this into lS but I am not 100% sure. 2. <C-Tab> Vim users are not accustomed to such breaking fingers combinations ;). Also may be problems on various terminals. 3. <F9> or \<F9> Looks most natural choice as extension of current "magic completion" but doesn't look very intuitive for end user. My order of preference is 3b, 3a, 1 (with incorporation of #102), 2. What do you think? m. |
|
From: Mikolaj M. <mi...@wp...> - 2003-04-25 10:21:32
|
On Wed, Apr 16, 2003 at 11:15:50AM +0200, Jesus Senar wrote: > I've just installed latex-suite and I think it is great, but I have a problem > with the compile option. When I run it, the command line displays "silent! > RunLaTeX()" and nothing happens. I have the texrc file in the folder > $HOME/.vim/ftplugin/tex/, and the variables for the compiler are set, but > the command line doesn't display the correct directive. Are you sure nothing happens? Process isn't very verbose and this is normal message. m. |
|
From: Mikolaj M. <mi...@wp...> - 2003-04-25 10:21:18
|
On Sat, Apr 12, 2003 at 10:51:03PM +0200, Jess Thrysoee wrote: > Hi, > When using non-gui vim with the Vim-Latex package, I have to make a few > changes to 'ftplugin/latex-suite/compiler.vim', in order for dvi search to > work properly. I have attached the patch I use. Anyway, I'm hoping you will > include enough of it, so I don't have to patch your excellent package. > regards, Hello, I have made some changes in compiler.vim separately. Could you check it now? m. |
|
From: Quebec-Immo <que...@ca...> - 2003-04-24 03:36:29
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Untitled Document</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">
</head>
<body leftmargin=3D"0" topmargin=3D"0" marginwidth=3D"0" marginheight=3D"0=
">
<table width=3D"600" cellspacing=3D"0" cellpadding=3D"0">
<tr>
<td>
<p>Chers Internautes,</p>
<p>La fièvre immobilière continue de se faire sentir p=
artout
au Québec. <a href=3D"http://www.gouvqc.com"><strong>Quebec=
-Immo</strong></a>,
premier portail immobilier, est bien placé pour le constate=
r et
l'augmentation de notre trafic internet en fait la preuve. Pour mi=
eux
répondre à notre clientèle grandissante, nous=
avons
introduit de nouvelles sections sur le site, tel qu'un service per=
mettant
à l'acheteur de faire connaître au vendeur ce qu'il r=
echerche,
ainsi qu'une section informative immobilière.</p>
<p>Grâce à <strong><a href=3D"http://www.gouvqc.com">Qu=
ebec-Immo</a></strong>,
les acheteurs sont maintenant en mesure de faire connaître a=
ux vendeurs
ce qu'ils recherchent. Nous avons créé une nouvelle =
section
à notre site où les acheteurs peuvent publier gratui=
tement
des annonces indiquant en détail ce qu'ils recherchent d'un=
e future
propriété.</p>
<p>De plus, pour vous permettre de vous tenir à l'affût=
de
toutes les informations immobilières, nous avons éta=
bli
une nouvelle section dans laquelle divers professionels du domaine=
immobilier
publieront des textes sur tous les domaines immobiliers pour vous =
tenir
bien au fait.</p>
<p>Nous avons aussi établi un partenariat avec Vitrine .Net p=
our
vous permettre d'accéder à une tonne de ressources I=
nternet
à partir du site de <strong><a href=3D"http://www.gouvqc.co=
m">Quebec-Immo</a></strong>.</p>
<p><br>
<strong><a href=3D"http://www.gouvqc.com">Quebec-Immo</a></strong>=
est fier
d'être le premier portail immobilier au Québec. De pl=
us en
plus de Québécois(eses) utilisent notre site pour ac=
heter
ou vendre leur propriété.</p>
<p>Le volume important de visiteurs fait de notre site un endroit de=
premier
choix pour vendre votre maison. Nous sommes le media Immobilier qu=
ébécois
offrant la plus grande visibilité pour votre maison.</p>
<p>De plus, les acheteurs aiment visiter et trouver leur maison futu=
re sur
notre site car il est clair, facile à consulter et les page=
s descriptives
des maisons sont très détaillées.</p>
<p><a href=3D"http://www.gouvqc.com">Visitez Quebec-Immo dès =
maintenant.</a></p>
<p>En ce magnifique début de printemps, c'est le temps du gra=
nd ménage
printanier. Puisque nous détestons tous cette tâche, =
<strong><a href=3D"http://www.gouvqc.com">Quebec-Immo</a></strong>
fait tirer un grand ménage du printemps d'une valeur de 335=
$.
<a href=3D"http://www.gouvqc.com">Visitez notre site pour obtenir =
plus d'informations.</a></p>
<p>Quelques conseils aux vendeurs de maisons :</p>
<p>Avant de faire visiter sa maison, il est bien important de prendr=
e plusieurs
aspects en considération pour obtenir un meilleur prix et v=
endre
plus rapidement.</p>
<p>Mettez-vous dans la peau d'un acheteur, faites le tour de votre m=
aison
avec une vision critique et sévère, et notez toutes =
les
choses simples et visibles à l'oeil qui sont négativ=
es.
Cette liste vous donnera une bonne idée des points à=
corriger
sur votre maison avant de la faire vister. Investir un montant de =
1% ou
2% de la valeur peut s'avérer un investissement rentable; v=
otre
propriété sera vendue plus rapidement et à un=
meilleur
prix.</p>
<p>Faites un bon ménage, débarrassez vous des choses i=
nutiles
et accumulées au cours des ans. Portez une attention partic=
ulière
au garage, hangar et sous-sol. Ces endroits sont souvent propices =
au fouillis.<br>
Entrenez bien votre terrain et assurez-vous que le gazon est bien =
tondu.
Enlevez les mauvaisses herbes. Nettoyez patio et asphalte.</p>
<p>Assurez-vous de bien aérer avant les visites, la maison do=
it sentir
bon. Si vous en avez les talents, faites cuire un gateau à =
la vanille
ou à la lavande et pourquoi pas une tarte aux pommes, un pe=
u avant
la visite. Votre visiteur se sentira déjà plus chez =
lui.</p>
<p>Pendant la visite, laissez un peu d'air à votre visiteur. =
Trop
souvent les vendeurs veulent trop en faire et ils suivent et colle=
nt les
acheteurs et les bombardent d'informations pas toujours pertinente=
s. La
seule chose que vous devriez faire est d'encourager votre visiteur=
à
se sentir comme chez lui et à explorer. Lorsque sa visite e=
st terminée,
c'est alors le temps de répondre à ses questions; il=
sera
beaucoup plus ouvert à ce moment. Une dernière chose=
: encouragez-le
après la visite à noter les points forts de votre ma=
ison.
Lorsqu'il prendra sa décision, il aura des points de rep&eg=
rave;re
pour choisir votre propriété.</p>
<p>Bonne vente!</p>
<p>Nous espérons que vous avez apprécié ces que=
lques
informations sur l'immobilier et sur notre site. Nous avons h&acir=
c;te
de vous servir.</p>
<p><a href=3D"http://www.gouvqc.com">Visitez Quebec-Immo dès =
maintenant</a></p>
<p><br>
<br>
<br>
<br>
<br>
<br>
<font size=3D"-1">Ce bulletin d'information vous est envoyé=
par TD
promotion pour le compte de Netcom Immobilier, propriétaire=
de
Quebec-Immo. Sachez que votre adresse de courriel est utilis&eacut=
e;e
seulement pour Quebec-Immo. Votre adresse ne sera jamais partag&ea=
cute;e
avec un tiers parti. Votre adresse a été obtenue d'u=
ne base
de données disponible au grand public via Internet. Pour ne=
plus
recevoir de bulletin d'information de Quebec-Immo, suivez ce lien:=
<a href=3D"http://www.gouvqc.com/rm.html">désinscription</a></font=
></p></td>
</tr>
</table>
</body>
</html> |
|
From: Quebec-Immo <que...@ca...> - 2003-04-24 03:35:19
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Untitled Document</title>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859=
-1">
</head>
<body leftmargin=3D"0" topmargin=3D"0" marginwidth=3D"0" marginheight=3D"0=
">
<table width=3D"600" cellspacing=3D"0" cellpadding=3D"0">
<tr>
<td>
<p>Chers Internautes,</p>
<p>La fièvre immobilière continue de se faire sentir p=
artout
au Québec. <a href=3D"http://www.gouvqc.com"><strong>Quebec=
-Immo</strong></a>,
premier portail immobilier, est bien placé pour le constate=
r et
l'augmentation de notre trafic internet en fait la preuve. Pour mi=
eux
répondre à notre clientèle grandissante, nous=
avons
introduit de nouvelles sections sur le site, tel qu'un service per=
mettant
à l'acheteur de faire connaître au vendeur ce qu'il r=
echerche,
ainsi qu'une section informative immobilière.</p>
<p>Grâce à <strong><a href=3D"http://www.gouvqc.com">Qu=
ebec-Immo</a></strong>,
les acheteurs sont maintenant en mesure de faire connaître a=
ux vendeurs
ce qu'ils recherchent. Nous avons créé une nouvelle =
section
à notre site où les acheteurs peuvent publier gratui=
tement
des annonces indiquant en détail ce qu'ils recherchent d'un=
e future
propriété.</p>
<p>De plus, pour vous permettre de vous tenir à l'affût=
de
toutes les informations immobilières, nous avons éta=
bli
une nouvelle section dans laquelle divers professionels du domaine=
immobilier
publieront des textes sur tous les domaines immobiliers pour vous =
tenir
bien au fait.</p>
<p>Nous avons aussi établi un partenariat avec Vitrine .Net p=
our
vous permettre d'accéder à une tonne de ressources I=
nternet
à partir du site de <strong><a href=3D"http://www.gouvqc.co=
m">Quebec-Immo</a></strong>.</p>
<p><br>
<strong><a href=3D"http://www.gouvqc.com">Quebec-Immo</a></strong>=
est fier
d'être le premier portail immobilier au Québec. De pl=
us en
plus de Québécois(eses) utilisent notre site pour ac=
heter
ou vendre leur propriété.</p>
<p>Le volume important de visiteurs fait de notre site un endroit de=
premier
choix pour vendre votre maison. Nous sommes le media Immobilier qu=
ébécois
offrant la plus grande visibilité pour votre maison.</p>
<p>De plus, les acheteurs aiment visiter et trouver leur maison futu=
re sur
notre site car il est clair, facile à consulter et les page=
s descriptives
des maisons sont très détaillées.</p>
<p><a href=3D"http://www.gouvqc.com">Visitez Quebec-Immo dès =
maintenant.</a></p>
<p>En ce magnifique début de printemps, c'est le temps du gra=
nd ménage
printanier. Puisque nous détestons tous cette tâche, =
<strong><a href=3D"http://www.gouvqc.com">Quebec-Immo</a></strong>
fait tirer un grand ménage du printemps d'une valeur de 335=
$.
<a href=3D"http://www.gouvqc.com">Visitez notre site pour obtenir =
plus d'informations.</a></p>
<p>Quelques conseils aux vendeurs de maisons :</p>
<p>Avant de faire visiter sa maison, il est bien important de prendr=
e plusieurs
aspects en considération pour obtenir un meilleur prix et v=
endre
plus rapidement.</p>
<p>Mettez-vous dans la peau d'un acheteur, faites le tour de votre m=
aison
avec une vision critique et sévère, et notez toutes =
les
choses simples et visibles à l'oeil qui sont négativ=
es.
Cette liste vous donnera une bonne idée des points à=
corriger
sur votre maison avant de la faire vister. Investir un montant de =
1% ou
2% de la valeur peut s'avérer un investissement rentable; v=
otre
propriété sera vendue plus rapidement et à un=
meilleur
prix.</p>
<p>Faites un bon ménage, débarrassez vous des choses i=
nutiles
et accumulées au cours des ans. Portez une attention partic=
ulière
au garage, hangar et sous-sol. Ces endroits sont souvent propices =
au fouillis.<br>
Entrenez bien votre terrain et assurez-vous que le gazon est bien =
tondu.
Enlevez les mauvaisses herbes. Nettoyez patio et asphalte.</p>
<p>Assurez-vous de bien aérer avant les visites, la maison do=
it sentir
bon. Si vous en avez les talents, faites cuire un gateau à =
la vanille
ou à la lavande et pourquoi pas une tarte aux pommes, un pe=
u avant
la visite. Votre visiteur se sentira déjà plus chez =
lui.</p>
<p>Pendant la visite, laissez un peu d'air à votre visiteur. =
Trop
souvent les vendeurs veulent trop en faire et ils suivent et colle=
nt les
acheteurs et les bombardent d'informations pas toujours pertinente=
s. La
seule chose que vous devriez faire est d'encourager votre visiteur=
à
se sentir comme chez lui et à explorer. Lorsque sa visite e=
st terminée,
c'est alors le temps de répondre à ses questions; il=
sera
beaucoup plus ouvert à ce moment. Une dernière chose=
: encouragez-le
après la visite à noter les points forts de votre ma=
ison.
Lorsqu'il prendra sa décision, il aura des points de rep&eg=
rave;re
pour choisir votre propriété.</p>
<p>Bonne vente!</p>
<p>Nous espérons que vous avez apprécié ces que=
lques
informations sur l'immobilier et sur notre site. Nous avons h&acir=
c;te
de vous servir.</p>
<p><a href=3D"http://www.gouvqc.com">Visitez Quebec-Immo dès =
maintenant</a></p>
<p><br>
<br>
<br>
<br>
<br>
<br>
<font size=3D"-1">Ce bulletin d'information vous est envoyé=
par TD
promotion pour le compte de Netcom Immobilier, propriétaire=
de
Quebec-Immo. Sachez que votre adresse de courriel est utilis&eacut=
e;e
seulement pour Quebec-Immo. Votre adresse ne sera jamais partag&ea=
cute;e
avec un tiers parti. Votre adresse a été obtenue d'u=
ne base
de données disponible au grand public via Internet. Pour ne=
plus
recevoir de bulletin d'information de Quebec-Immo, suivez ce lien:=
<a href=3D"http://www.gouvqc.com/rm.html">désinscription</a></font=
></p></td>
</tr>
</table>
</body>
</html> |
|
From: Mikolaj M. <mi...@wp...> - 2003-04-21 19:34:57
|
Hello, I just commited short help about project features introduced in texproject-branch. Check if you like it. Of course there are many rough egdes, many features can be introduced but check if you like this course. Without objections I will merge it in main branch in next few days. m. |
|
From: Alan S. <ala...@po...> - 2003-04-16 16:22:33
|
* Jesus Senar (js...@li...) wrote: > Hi. > I've just installed latex-suite and I think it is great, but I have a problem > with the compile option. When I run it, the command line displays "silent! > RunLaTeX()" and nothing happens. I have the texrc file in the folder > $HOME/.vim/ftplugin/tex/, and the variables for the compiler are set, but > the command line doesn't display the correct directive. > I'm a bit new to Linux world, so I apologise if my question has a very simple > answer. > > Thanks in advance. Do you have a Makefile in this directory that does not define the target "dvi" ? Alan -- The hacker: someone who figured things out and made something cool happen. |
|
From: Mikolaj M. <mi...@wp...> - 2003-04-16 15:26:19
|
On Mon, Apr 14, 2003 at 03:32:41PM -0700, Bart Kastermans wrote: > I find the following bug: > Typing EEQ while in insert mode gives: > Error detected while processing function IMAP_Mark: > line 4: > E117: Unknown function: cursor > I use gvim version 6.0 on Windows XP. Would be happy to provide > more details about my system (except the password :-) ). I can't confirm this but I have state-of-the-art Vim (6.1.464) If you can download 4M without much hassle I'm recommending upgrade to 6.1. Yep. cursor() function was added in 6.0.234. Moment. I just grep lS code and there is no cursor() function. Which version of lS are you using? The latest version is from 25 March. m. |
|
From: Jesus S. <js...@li...> - 2003-04-16 09:17:55
|
Hi. I've just installed latex-suite and I think it is great, but I have a problem with the compile option. When I run it, the command line displays "silent! RunLaTeX()" and nothing happens. I have the texrc file in the folder $HOME/.vim/ftplugin/tex/, and the variables for the compiler are set, but the command line doesn't display the correct directive. I'm a bit new to Linux world, so I apologise if my question has a very simple answer. Thanks in advance. |
|
From: Bart K. <bka...@ya...> - 2003-04-14 22:32:51
|
I find the following bug: Typing EEQ while in insert mode gives: Error detected while processing function IMAP_Mark: line 4: E117: Unknown function: cursor I use gvim version 6.0 on Windows XP. Would be happy to provide more details about my system (except the password :-) ). Best, Bart ===== -- http://www.kastermans.nl/bart/ __________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.com |
|
From: Mikolaj M. <mi...@wp...> - 2003-04-14 17:14:45
|
Hello, I looked into but I don't know how to obtain list of files in current project :/ Also writing some kind of interface between latexSuite and project.vim would require not much less effort than writing this kind of functionality from scratch. I would rather try to do "homebrew" system. - "reinventing the wheel" + freedom of making changes, adding/removing functionality + it will be vim script. User can store there not only informations about project necessary for various lS functions but also more personal shortcuts mappings etc. needed for particular project m. |
|
From: Florent M. <ma...@ef...> - 2003-04-14 15:23:16
|
I just wrote a tips on vim.org : http://www.vim.org/tips/tip.php?tip_id=3D453 It explain how to use taglist (a plugin) with a LaTeX document. --=20 Florent Manens EFREI Promo - 2003 ma...@ef... |
|
From: Jess T. <je...@th...> - 2003-04-12 20:51:57
|
Hi, When using non-gui vim with the Vim-Latex package, I have to make a few changes to 'ftplugin/latex-suite/compiler.vim', in order for dvi search to work properly. I have attached the patch I use. Anyway, I'm hoping you will include enough of it, so I don't have to patch your excellent package. regards, ..Jess Thrysoee |
|
From: Alan S. <ala...@po...> - 2003-04-12 10:03:21
|
* 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 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: Jakub T. <ya...@ch...> - 2003-04-11 12:53:41
|
Update of the problem: in error list window there are messages like: praca.tex|| LaTeX Font Warning: Font shape `OT4/cmss/bx/it' undefined praca.tex|| LaTeX Font Warning: Some font shapes were not available, defaults substituted. ./dev/tytulowa.tex|| LaTeX Font Warning: Font shape `OT4/cmss/bx/it' undefined ./praca.bbl|3 warning| LaTeX Warning: Empty `thebibliography' environment on input line 3. ./dev/tytulowa.tex|| LaTeX Font Warning: Some font shapes were not available, defaults substituted. Regards, Maybe it is the matter of splitted tex, and files with './' at the beginning? Also, doubleclicking ond entry in error list works, it is only <up>/<down> keys that are creating erros described in previous letter. BTW, is there going to be a change in compiler.vim behaviour? I read posts on this list (via sf.net) and someone proposed ignoring Makefile if .latexmain is present. Why? In my situation, I use Makefile for compiling, and .latexmain for making sure that vim-latex "supports" various packages when I'm editing a file different from the main file (for example, when I edit introduction.tex, which is later included into main.tex). Please consider this. Q. -- __ __.--------------------------http://yacoob.dnsalias.net/cv.html---.__ (oo) | TOO MUCH EVA: You're lying in your bed and you can't help | / \/ \ | but say "Another unfamiliar ceiling" | `V__V' `--.__penguin_#128720______________________________________________.--' |
|
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: 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: 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: 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: 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.
|
|
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: 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: 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: Jakub T. <ya...@ch...> - 2003-04-09 13:15:10
|
Greetings. When I \ll a file it compiles well, but there's a bunch of warning (about fonts, or empty bibliography) in log. Error windows is created, but when I switch to it, and try to change line (j/k) following error occurs: (output of :messages afterwards) Messages maintainer: Bram Moolenaar <Br...@vi...> "praca.tex" 301 lines, 8367 characters No matching autocommands "~/workarea/qos/praca/dev/praca.sty" 170 lines, 4380 characters 4 lines yanked No matching autocommands "praca.tex" 301 lines, 8367 characters [w] (1 of 6) warning: LaTeX Font Warning: Font shape `OT4/cmss/bx/it' undefined "~/workarea/qos/praca/praca.log" 472 lines, 14203 characters "./praca.bbl" 3 lines, 49 characters "~/workarea/qos/praca/praca.log" 472 lines, 14203 characters "praca.log" 472 lines, 14203 characters search hit BOTTOM, continuing at TOP search hit BOTTOM, continuing at TOP Error detected while processing function UpdatePreviewWindow..PositionPreviewWindow: line 62: Pattern not found: ((f|[|])*. Hit ENTER or type command to continue What's wrong with that? I would greatly appreciate CCing me with answer, as I'm not on the mailing list. Regards, Q. -- __ __.--------------------------http://yacoob.dnsalias.net/cv.html---.__ (oo) | TOO MUCH EVA: You're lying in your bed and you can't help | / \/ \ | but say "Another unfamiliar ceiling" | `V__V' `--.__penguin_#128720______________________________________________.--' |
34 messages has been excluded from this view by a project administrator.
