Dear Ted, I am subscribed to the list--I have been receiving emails from others who are posting to the list. My patches are indeed being withheld in some queue, thanks to their size (max size for emails is 44KB or so). However, even emails with size <44KB are being withheld. Also, why is the project being moved to svn? Don't want to sound like a snob, but git (in conjunction with github) might be a better option; many useful vim scripts are already located there. As a test, I have cc'd this message to the list; unless a miracle occurs, it shouldn't go through.
-- Best, David Karapetyan http://davidkarapetyan.com University of Notre Dame Department of Mathematics 255 Hurley Hall Notre Dame, IN 46556-4618 Phone: 574-631-5706 Cell: 202-460-5173 Fax: 574-631-6579 On Oct 27, 2010, at 3:35 PM, Ted Pavlic wrote: > David -- > > You may need to be subscribed to the list. I've received messages as recently > as today from the list. Perhaps your messages are behind held in some > moderator queue somewhere... > > --Ted > > On 10/27/2010 03:28 PM, David Karapetyan wrote: >> Dear Ted, >> >> Actually, I have been sending messages >> vim-latex-de...@lists.sourceforge.net. I don't know why my messages are not >> showing up. Thank you for the workarounds as well. >> >> -- >> Best, >> David Karapetyan >> http://davidkarapetyan.com >> University of Notre Dame >> Department of Mathematics >> 255 Hurley Hall >> Notre Dame, IN 46556-4618 >> Phone: 574-631-5706 >> Cell: 202-460-5173 >> Fax: 574-631-6579 >> >> >> On Oct 27, 2010, at 2:17 PM, Ted Pavlic wrote: >> >>> David -- >>> >>> By the way, I didn't see any of your messages show up on the >>> vim-latex-devel list, which makes me think you're sending to the main >>> vim-devel list, which is the wrong list to use. That also explains why you >>> haven't seen much vim-latex-devel activity. >>> >>> You need to look into this list: >>> >>> vim-latex-devel@lists.sourceforge.net >>> >>> You also need to post your patches (with "PATCH" in the subject) to that >>> list. You can find subscription information at: >>> >>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel >>> >>> As you'll see, that list is actually moderately active. >>> >>> I also recommend that you use SVN to download the development version >>> of the vim-latex suite. Several patches have been applied since the >>> previous release. >>> >>> Best -- >>> Ted >>> >>> On 10/27/2010 11:41 AM, Ted Pavlic wrote: >>>> David -- >>>> >>>> I've taken a look, and I think that multiply defined labels are going to >>>> be a bit of a problem regardless of what approach you take. It is true >>>> that latex gives a warning in the TeX file for multiply defined labels, >>>> but it also gives a warning in the AUX. That is, gvim is arguably not >>>> screwing anything up because it is opening the file that LaTeX tells it >>>> it should be opening up (I do have a workaround; see below). >>>> >>>> On the first LaTeX pass through your TeX, it generates the AUX. On the >>>> second pass, it incorporates information accumulated in the AUX. It is >>>> on that pass through the AUX that generates the error, and that's why >>>> LaTeX reports that the AUX is the problem (as opposed to the TeX). >>>> >>>> There are three workarounds: >>>> >>>> *) Press CTRL-O to bring you back to your TeX file after TeX opens a new >>>> buffer with the AUX in it (you can also :bd to delete the AUX buffer, >>>> but then you'll be placed in the quickfix window, and you'll have to :bd >>>> that to get back to TeX). >>>> >>>> *) You can tell Vim-LaTeX to ignore these warnings entirely. Take a look >>>> at: >>>> >>>> :help Tex_IgnoredWarnings >>>> >>>> to see how you can set the configuration variable g:Tex_IgnoredWarnings. >>>> As it asys, you must also make sure you adjust g:Tex_IgnoreLevel >>>> accordingly. You can add a string that matches the multiple-label >>>> warning string, and if Vim sees that TeX is throwing that error, it will >>>> not take any action. >>>> >>>> *) To turn off the "goto error" feature of Vim-LaTeX so it doesn't try >>>> to open up the source of the first error automatically. You're supposed >>>> to be able to use: >>>> >>>> :set g:Tex_GotoError=0 >>>> >>>> but right now, it doesn't appear like that is working... at least not in >>>> the toy example I have setup. >>>> >>>> So CTRL-O might be your best bet. :-/ >>>> >>>> --Ted >>>> >>>> >>>> On 10/27/2010 12:16 AM, David Karapetyan wrote: >>>>> Dear Ted, >>>>> >>>>> Following your suggestions (regarding the .aux file being barfed onto >>>>> the screen after a multiple compilation) does not fix the problem. I >>>>> am currently on a Mac, and was curious if you were having the same >>>>> problems. I have also submitted my patch to the vim-developers list >>>>> with the "PATCH" subject line, per your suggestion. >>>>> >>>>> -- >>>>> Best, >>>>> David Karapetyan >>>>> http://davidkarapetyan.com >>>>> University of Notre Dame >>>>> Department of Mathematics >>>>> 255 Hurley Hall >>>>> Notre Dame, IN 46556-4618 >>>>> Phone: 574-631-5706 >>>>> Cell: 202-460-5173 >>>>> Fax: 574-631-6579 >>>>> >>>>> On Oct 24, 2010, at 9:30 PM, Ted Pavlic wrote: >>>>> >>>>>> David -- >>>>>> >>>>>>> I would have emailed the vim-latex developers list, but they are >>>>>>> notoriously slow at replying (even when I send patches and bug fixes >>>>>>> in). Is the vim-latex project even being maintained? >>>>>> >>>>>> Till Maas does as best as he can. Usually if you post a message to >>>>>> the list with "PATCH" or "[PATCH]" in the subject, it will get his >>>>>> attention. I know he's been wanting to convert the repo from svn to >>>>>> Mercurial to aid in the easy management of the project and inclusion >>>>>> of more developers... but he just hasn't had the time (and is a >>>>>> little worried about the process) to do the conversion. >>>>>> >>>>>>> I wanted to ask you about a bug with vim-latex compilation that I >>>>>>> cannot resolve. If the multicompile option is set for pdfs, vim-latex >>>>>>> will barf the .aux file onto my screen (displacing whatever source >>>>>>> code I am editing) whenever I have a duplicate label in my tex source >>>>>>> code. How can I disable this "feature"? >>>>>> >>>>>> I have a FEELING that the problem is the standard problem that Vim's >>>>>> compiler error code has with the default way LaTeX generates error >>>>>> messages. That is, rather than a normal compiler that would say >>>>>> something like... >>>>>> >>>>>> gcc: missing blah on line 5 in file myfile.c >>>>>> >>>>>> LaTeX does something like... >>>>>> >>>>>> (myfile.c >>>>>> # lots >>>>>> # of >>>>>> # OK >>>>>> # messages >>>>>> error: line 5: missing blah >>>>>> # other >>>>>> # messages >>>>>> ) >>>>>> >>>>>> and to make matters worse, these things get nested... and sometimes >>>>>> all of the closures happen on the same line... This really confuses >>>>>> Vim. The usual symptom is that Vim picks the wrong file to open when >>>>>> showing you an error. There is a way to get LaTeX to generate error >>>>>> messages in the conventional format, but it still breaks warning >>>>>> messages. So you have to take a different approach. >>>>>> >>>>>> See a post I put together a long time ago at: >>>>>> >>>>>> http://phaseportrait.blogspot.com/2008/03/fixing-vim-latex-compiler-error.html >>>>>> >>>>>> >>>>>> I give a description of the problem and many of the known fixes. I >>>>>> recommend you try at least one of them if not more. In most cases, >>>>>> using my "vimlatex" pipe script in front of your usual LaTeX build >>>>>> line will do its best to "sanitize" the LaTeX error messages for Vim. >>>>>> >>>>>> (however, if the "rubber" Python script is a very nice LaTeX make >>>>>> frontend, and it can also sanitize error and warning messages without >>>>>> too much effort) >>>>>> >>>>>>> I have various patch files for vim-latex that fix a number of bugs it >>>>>>> has when used on macosx (using the MacVim editor and Skim pdf >>>>>>> viewer). If you are interested, I can send them to you. >>>>>> >>>>>> I do have commit access to the SVN repo, but I just haven't had much >>>>>> time. I really strongly recommend that you post the patches to the >>>>>> vim-latex-devel list with "PATCH" or "[PATCH]" in the subject. They >>>>>> will likely get committed in a week or two when Till goes through and >>>>>> does house cleaning. I've seen several new commits in the >>>>>> not-too-distant past. >>>>>> >>>>>> I hope that helps! >>>>>> >>>>>> Best -- >>>>>> Ted >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ted Pavlic<t...@tedpavlic.com> >>>>>> >>>>>> Please visit my 2010 d'Feet ALS walk page: >>>>>> http://web.alsa.org/goto/tpavlic >>>>>> My family appreciates your support in the fight to defeat ALS. >>>>> >>>>> >>>> >>> >>> -- >>> Ted Pavlic<pavli...@osu.edu> -- NSF CPS Postdoctoral Researcher >>> Computer Science and Engineering, The Ohio State University >>> 395 Dreese Laboratories, 2015 Neil Ave., Columbus, OH 43210 >>> >>> Please visit my 2010 d'Feet ALS walk page: >>> http://web.alsa.org/goto/tpavlic >>> My family appreciates your support in the fight to defeat ALS. >> > > -- > Ted Pavlic <pavli...@osu.edu> -- NSF CPS Postdoctoral Researcher > Computer Science and Engineering, The Ohio State University > 395 Dreese Laboratories, 2015 Neil Ave., Columbus, OH 43210 > > Please visit my 2010 d'Feet ALS walk page: > http://web.alsa.org/goto/tpavlic > My family appreciates your support in the fight to defeat ALS. ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ Vim-latex-devel mailing list Vim-latex-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
