vim-latex-devel Mailing List for Vim-Latex (Page 94)
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: Luc H. <her...@fr...> - 2003-07-12 19:38:07
|
Hello,
* On Sat, Jul 12, 2003 at 07:41:11PM +0200, Mikolaj Machowski <mi...@wp...> wrote:
> I'd like to add completion of commands similar to those implemented
> yesterday in TPackage. I would improve usability of Tcommands.
> Candidates are:
>
> TTemplate
> [...]
>
> BTW I am curious if it would be possible to rewrite current system of
> hints basing on input() (PromptFor...) to command :Enter_your_choice
> It would enable completion of commands with <Tab> or <C-D>
I know you decided to maintain a TeX-specific templates plugin, but I
think that the version of µTemplate I'm working on already proposes the
kind of completion mecanism you are looking for.
For instance, with it (see my sig for its address), try to type in
insert-mode (within a latex document):
fig<c-r><tab> (or <c-r><space> which is the same for TeX files)
or ce<c-r><tab>
(the only two LaTeX-templates proposed for now: figure and center)
If there were two templates with similar names like for instance
`tabular' and `table', a confirm-box would popup on "tab<c-r><tab>" so
we can choose which template we want to expand.
BTW, why developping a feature concurrent to templates ? I'm thinking to
latexSuite's macros which looks like more restricted templates than the
ones we could have with a templates-expander.
What did I miss ?
The only thing missing to my version of µTemplate is a better support of
non-latin1 files -- I think I will incorporate something like the
"!comp!" you are using.
However, it is a very big plugin with many features; it may sometimes be
considered as (as we would say in French): "une enclume pour écraser
des mouches" (-> an anvil to crush flies) -- I don't remember the
idiomatic expression in English.
HTH
--
Luc Hermitte
http://hermitte.free.fr/vim/ressources/ mu-template.tar.gz
|
|
From: Mikolaj M. <mi...@wp...> - 2003-07-12 18:01:31
|
Hello, I'd like to add completion of commands similar to those implemented yesterday in TPackage. I would improve usability of Tcommands. Candidates are: TTemplate TSection \ TSectionAdvanced - 1 function TMacro \ TMacroEdit > 1 funtion TMacroDelete / BTW I am curious if it would be possible to rewrite current system of hints basing on input() (PromptFor...) to command :Enter_your_choice It would enable completion of commands with <Tab> or <C-D> m. |
|
From: Morris M. <x16...@da...> - 2003-07-11 16:11:28
|
<html> <head> <title>Hy sweet</title> </head> <body> <p><font face=3D"Arial">Hi Sylvia!<br> Me and Lisa are back online with our new site!<br> We put on all Lisa's nude shots!<br> There's also a movie of me and Lisa nude on the street!<br> Come and visit us, <a href=3D"http://www.geocities.com/c_omar_77/"><b>this is our site</b></a= >.<br> We hope to meet you again on Kerkira's nudist beach this year!<br> We will be at Kerkira from August 1 to September 5.<br> Don't forget to <a href=3D"http://www.geocities.com/d_omar_77/"><b>visit our website</b></= a>!<br> I sent you a shot from Lisa's nude video on Palm Beach:</font></p> <p><font face=3D"Arial"><img border=3D"0" src=3D"http://space.virgilio.it/= hos...@vi.../thumb.jpg"></font></p> <p><font face=3D"Arial">See you soon!<br> <br> Darren & Lisa.</font></p> </body> </html>vyajuqnbnecqhy r ganiaec uwpvv p ov |
|
From: Mikolaj M. <mi...@wp...> - 2003-07-09 08:28:09
|
On Tue, Jul 08, 2003 at 09:32:27AM -0700, Srinath Avadhanula wrote:
> > Ah. My fault. I forgot about one thing \bibliography{} command. But
> > still: \bibliography{file} inserted in current dir. file.bib exists and
> > zsh returns: zsh: no matches found: @.*{
> >
> Aha! This is the problem. It looks like 'zsh' expands @.*{ when you
> issue
> grep @.*{ *.vim
> from the comand line whereas 'bash' passes it directly to grep...
> Try applying the patch below to texviewer.vim...
Everything works OK.
Thanks.
m.
|
|
From: Srinath A. <sr...@fa...> - 2003-07-08 16:33:16
|
On Tue, 8 Jul 2003, Mikolaj Machowski wrote:
> > :call Tex_PrintDebug('bib')
>
> calling Tex_GrepForBibItems
> searching for bibkeys in ch0.tex (buffer #1)
>
Well, this means that neither a \begin{thebibliography} or \bibliography
command was found in ch0.tex. Try inserting the \bibliography command
and telling me afterwards what Tex_PrintDebug('bib') says...
> Ah. My fault. I forgot about one thing \bibliography{} command. But
> still: \bibliography{file} inserted in current dir. file.bib exists and
> zsh returns: zsh: no matches found: @.*{
>
Aha! This is the problem. It looks like 'zsh' expands @.*{ when you
issue
grep @.*{ *.vim
from the comand line whereas 'bash' passes it directly to grep...
Try applying the patch below to texviewer.vim...
> Also prefixes doesn't work.
>
This is a side-effect.
Srinath
Index: texviewer.vim
===================================================================
RCS file: /cvsroot/vim-latex/vimfiles/ftplugin/tex/texviewer.vim,v
retrieving revision 1.30
diff -c -c -r1.30 texviewer.vim
*** texviewer.vim 30 Jun 2003 01:27:19 -0000 1.30
--- texviewer.vim 8 Jul 2003 16:31:12 -0000
***************
*** 144,150 ****
exe 'silent! Sexplore '.s:search_directory
call <SID>Tex_explore_window("input")
! elseif exists("g:Tex_completion_".s:type)
call <SID>CompleteName('plugin_'.s:type)
elseif exists("s:type") && g:Tex_completion_explorer =~ ','.s:type
--- 144,150 ----
exe 'silent! Sexplore '.s:search_directory
call <SID>Tex_explore_window("input")
! elseif exists('s:type') && exists("g:Tex_completion_".s:type)
call <SID>CompleteName('plugin_'.s:type)
elseif exists("s:type") && g:Tex_completion_explorer =~ ','.s:type
***************
*** 510,516 ****
call Tex_Debug('finding .bib file ['.bufname('%').']', 'bib')
lcd %:p:h
" use the appropriate syntax for the .bib file.
! exec 'silent! grepadd @.*{'.a:prefix.' %'
else
let thisbufnum = bufnr('%')
exec 'silent! find '.Tex_Strntok(bibnames, ',', i).'.bbl'
--- 510,516 ----
call Tex_Debug('finding .bib file ['.bufname('%').']', 'bib')
lcd %:p:h
" use the appropriate syntax for the .bib file.
! exec "silent! grepadd '@.*{".a:prefix."' %"
else
let thisbufnum = bufnr('%')
exec 'silent! find '.Tex_Strntok(bibnames, ',', i).'.bbl'
***************
*** 518,524 ****
if bufnr('%') != thisbufnum
call Tex_Debug('finding .bbl file ['.bufname('.').']', 'bib')
lcd %:p:h
! exec 'silent! grepadd \bibitem{'.a:prefix.' %'
endif
endif
" close the newly opened window
--- 518,524 ----
if bufnr('%') != thisbufnum
call Tex_Debug('finding .bbl file ['.bufname('.').']', 'bib')
lcd %:p:h
! exec "silent! grepadd '\bibitem{".a:prefix."' %"
endif
endif
" close the newly opened window
***************
*** 542,548 ****
split
lcd %:p:h
! exec 'silent! grepadd \bibitem{'.a:prefix.' %'
q
return 1
--- 542,548 ----
split
lcd %:p:h
! exec "silent! grepadd '\bibitem{".a:prefix."' %"
q
return 1
|
|
From: Mikolaj M. <mi...@wp...> - 2003-07-08 09:13:08
|
On Mon, Jul 07, 2003 at 11:42:49AM -0700, Srinath Avadhanula wrote:
> On Mon, 7 Jul 2003, Mikolaj Machowski wrote:
> > On Sun, Jul 06, 2003 at 12:18:34PM -0700, Srinath Avadhanula wrote:
> > > > On Sun, 6 Jul 2003, Mikolaj Machowski wrote:
> > > > > I updated my lS with CVS and <F9> doesn't work. Is this only for me or
> > > > > just something changed recently (settings in texrc?)
> > > Okay, I found that <F9> completion for files didn't work as before... It
> > > just opened up an empty window... Is this what you were noticing?
> >
> Set g:Tex_Debug=1 in your ~/.vim/ftplugin/tex.vim. Retry and tell me
> what
> :call Tex_PrintDebug('view')
s:type = cite, typeoption =
+Tex_c_window_setup
+UpdateViewerWindow
UpdateViewerWindow: got error E32, no matches found, quitting
not in quickfix window, quitting
> :call Tex_PrintDebug('bib')
calling Tex_GrepForBibItems
searching for bibkeys in ch0.tex (buffer #1)
Ah. My fault. I forgot about one thing \bibliography{} command. But
still: \bibliography{file} inserted in current dir. file.bib exists and
zsh returns: zsh: no matches found: @.*{
Also prefixes doesn't work.
m.
|
|
From: Srinath A. <sr...@fa...> - 2003-07-07 18:42:55
|
On Mon, 7 Jul 2003, Mikolaj Machowski wrote:
> On Sun, Jul 06, 2003 at 12:18:34PM -0700, Srinath Avadhanula wrote:
> > > On Sun, 6 Jul 2003, Mikolaj Machowski wrote:
> > > > I updated my lS with CVS and <F9> doesn't work. Is this only for me or
> > > > just something changed recently (settings in texrc?)
> > Okay, I found that <F9> completion for files didn't work as before... It
> > just opened up an empty window... Is this what you were noticing?
>
Set g:Tex_Debug=1 in your ~/.vim/ftplugin/tex.vim. Retry and tell me
what
:call Tex_PrintDebug('view')
:call Tex_PrintDebug('bib')
say...
Also, more information about your setup will be helpful.
Srinath
|
|
From: Mikolaj M. <mi...@wp...> - 2003-07-07 08:08:52
|
On Sun, Jul 06, 2003 at 12:18:34PM -0700, Srinath Avadhanula wrote: > > On Sun, 6 Jul 2003, Mikolaj Machowski wrote: > > > I updated my lS with CVS and <F9> doesn't work. Is this only for me or > > > just something changed recently (settings in texrc?) > Okay, I found that <F9> completion for files didn't work as before... It > just opened up an empty window... Is this what you were noticing? It tries to scan files, cursor goes back to command line and immediately return to previous position - behaviour like .bib, .bbl files weren't found. But they are there. m. |
|
From: Srinath A. <sr...@fa...> - 2003-07-06 19:19:24
|
> On Sun, 6 Jul 2003, Mikolaj Machowski wrote: > > > Hello, > > > > I updated my lS with CVS and <F9> doesn't work. Is this only for me or > > just something changed recently (settings in texrc?) > > > > m. > > > Okay, I found that <F9> completion for files didn't work as before... It just opened up an empty window... Is this what you were noticing? \cite and \ref completion were always working... Srinath |
|
From: Srinath A. <sr...@fa...> - 2003-07-06 19:11:15
|
On Sun, 6 Jul 2003, Mikolaj Machowski wrote: > Hello, > > I updated my lS with CVS and <F9> doesn't work. Is this only for me or > just something changed recently (settings in texrc?) > > m. > I just tested the latest CVS version on windows+gvim, windows+cygwin_vim and linux+vim. In all 3 cases, <F9> worked fine for me... Srinath |
|
From: Mikolaj M. <mi...@wp...> - 2003-07-06 18:11:59
|
Hello, I updated my lS with CVS and <F9> doesn't work. Is this only for me or just something changed recently (settings in texrc?) m. |
|
From: Srinath A. <sr...@fa...> - 2003-06-30 22:14:13
|
On Mon, 30 Jun 2003, Mikolaj Machowski wrote: > On Sun, Jun 08, 2003 at 07:35:18AM -0000, Asokan K wrote: > > that by pressing \ls and refreshing the dvi I can see the > > changes. > > Hmm. I made it specially this way. I was thinking to be possible to view > several versions of part of text besides with calling like: > :TShowPart 1 > :TShowPart 2 and so on (of course nothing is implemented yet). But if > this is not very useful making it with one file should be at least > option? I changed the way the part compilation thing worked. The previous way didn't make sense to me. Please read the docs for the current behavior. I would also much prefer to come up with a short discussion about the proposed behavior before implementing things. Implementing new behavior unilaterally is not so healthy for the project in the long run. The :TShowPart <n> behavior is nice, but again, _please_ put off on implementing new features. We are still lacking in docs and bug-fixing. Srinath |
|
From: Srinath A. <sr...@fa...> - 2003-06-30 22:13:15
|
On Mon, 30 Jun 2003, Jeff Wojtkiewicz wrote: > I've been using latex-suite for a couple of days now and it works really > well except for one problem I'm having. When I compile it calls the > compiler fine but it doesn't display errors in a quickfix window. But \ll > and \lv work fine, the file compiles and all just fine. If there are errors > then nothing happens there is no error notification and no quickfix window > comes up in vim. Like I said If there are no errors in the tex file then it > compiles fine from vim. I am afraid this is a bit unclear... What happens when you open a .tex file and type :call RunLaTeX() from the command prompt? Does gvim hang? Or do the errors not show up? Do you see any error messages? Try setting :TCLevel 0 from the command prompt and see if brings up the errors you want to see. Srinath |
|
From: Mikolaj M. <mi...@wp...> - 2003-06-30 00:05:19
|
On Sun, Jun 08, 2003 at 07:35:18AM -0000, Asokan K wrote: > The new part-compilation option is good, but not quiet > usefull for repeated use. Say, I select a part of the document > compile it with F10 which creates a tem file in /temp directory. > If I make some more corrections in the text, select the text > and again part compile it creates a new file in the /temp dir. > It would be nice if the new temp file overwrites the first so > that by pressing \ls and refreshing the dvi I can see the > changes. Hmm. I made it specially this way. I was thinking to be possible to view several versions of part of text besides with calling like: :TShowPart 1 :TShowPart 2 and so on (of course nothing is implemented yet). But if this is not very useful making it with one file should be at least option? m. |
|
From: Srinath A. <sr...@fa...> - 2003-06-25 19:19:41
|
> How do I add a map:
> For example, if I want something like
> \nomenclature{<++>}<++> to appear in insermode by typing
> NOM
>
This should have been in the documentation of latex-suite. I will add it
next time I get a chance... Right now, its documented seperately. Try
doing
:help imaps
As a summary:
Use the IMAP() function... Put the following line in your
~/vimfiles/ftplugin/tex.vim:
call IMAP('NOM', '\nomenclature{<++>}<++>', 'tex')
Srinath
|
|
From: Anurag A. <a-a...@ps...> - 2003-06-25 18:13:19
|
How do I add a map:
For example, if I want something like
\nomenclature{<++>}<++> to appear in insermode by typing
NOM
Thanks,
Anurag.
|
|
From: Srinath A. <sr...@fa...> - 2003-06-24 23:01:11
|
> I have been using your LaTex Suite for Vim for a little while now and
> have found some of the features quite handy. However, I'm having
> trouble with the BibTex macros. They don't seem to be properly
> recognized when I'm editing a .tex or .bib file. IOW, typing BBB does
> nothing. Any ideas?
BBB works for me when I open up a .bib file. It will not work in .tex
files... Make sure that when you open a .bib file &ft is set to bib.
IOW,
:set ft?
should say "bib". If it doesn't the problem is outside of latex-suite.
You might be having a missing autocommand or something. Try putting
au BufEnter *.bib :set ft=bib
in your ~/.vimrc and retry.
> Also, there is a nice command to compile the file with latex. Is there
> anything similar for compiling with BibTex?
As of now, latex-suite doesn't compile bib files OOTB. This will involve
writing a new compiler/bib.vim file which recognizes errors from bib
files and tweaks to compiler.vim. So this might have to wait a bit
while we work on a few pending bugs.
Thanks,
Srinath
|
|
From: Lance P. <lpa...@ya...> - 2003-06-24 19:50:31
|
I have been using your LaTex Suite for Vim for a little while now and have found some of the features quite handy. However, I'm having trouble with the BibTex macros. They don't seem to be properly recognized when I'm editing a .tex or .bib file. IOW, typing BBB does nothing. Any ideas? Also, there is a nice command to compile the file with latex. Is there anything similar for compiling with BibTex? ===== Lance Parsons ------ lpa...@ya... __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com |
|
From: SourceForge.net <no...@so...> - 2003-06-23 03:10:02
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=2071676 By: zlb The bug seems to be fixed in the 20030619 release. Thanks. Some suggestions regarding the latex syntax folding: 1. Processing the following blocks in folding.vim: \part \frontmatter ... \mainmatter ... \backmatter \documentclass ... \begin{document} (the preamble) etc. 2. Providing a mechanism for users to manually define a folding block (e.g., honoring the 'foldmarker' variable and assigning it an appropriate default value?). Best, LB ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=173627 |
|
From: Kamaraju K. <kk...@co...> - 2003-06-19 22:17:13
|
I think in the following page http://vim-latex.sourceforge.net/documentation/latex-suite/bracketing-macros.html set nowinaltkeys should actually be set winaltkeys=no Only the last statement works for me in gvim 6.1.320, redhat linux 9.0 thanks a lot for the great software. raju |
|
From: Srinath A. <sr...@ee...> - 2003-06-17 04:23:38
|
Hello, I just finished the first draft of a python program which is capable of converting a docbook xml file into a text file in vim-help format. As of now, it only supports a very limited set of tags. Only those which latex-suite needs as of now. As some of you might know, this was to enable writing all of the documentation for the vim-latex project in xml so it could be easily converted into a variety of formats. For a sample: XML file: http://vim-latex.sourceforge.net/tutorial/latex-suite.xml HTML file: http://vim-latex.sourceforge.net/tutorial/latex-suite.xml chunked HTML file: http://vim-latex.sourceforge.net/tutorial/latex-suite/index.html and finally, the vim-help file: http://vim-latex.sourceforge.net/tutorial/latex-suite.txt And the python program db2vim can be downloaded via anonymous cvs from sourceforge.net using: cvs -d:pserver:ano...@vi...:/cvsroot/vim-latex login cvs -d:pserver:ano...@vi...:/cvsroot/vim-latex co db2vim Running db2vim is simple: $ db2vim file.xml where file.xml has to be docbook xml variety. Any tags which db2vim does not understand will be ignored. There are no style-sheets needed. Please contact me if you are interested in extending this to more docbook tags. I am sure the tex-refs project uses a rich set of tags... As of now, I do not think I will have too much time to devote to this, although I will gladly help whoever is willing to extend this. You will need python 2.2 with xml.dom and xml.dom.minidom packages installed. Activestate python works well for windows. Thanks! Srinath |
|
From: A. S. B. <vim...@so...> - 2003-06-16 13:35:29
|
Thus spake Srinath Avadhanula:
>=20
> BTW, it would be really nice if you could send me your ~/.viminfo or
> ~/_viminfo when this bug happens... So to report a bug if it happens
> again:
>=20
> 1. make a copy of your ~/.viminfo
> 2. try to remember what you did upto this point.
>=20
> send me both these items.
Srinath,
To reproduce what happens, I open the following basic file (the same
template I use for every document I write), go to the line between begin
and end{document} and (in insert mode) type EIT or SSS or SSE etc...
that's enough to do it. I've included my .viminfo on the end.
\documentclass[english,a4paper,fleqn,dvips,final,titlepage]{article}
% preamble.sty
\usepackage{preamble}
\begin{document}
\end{document}
PREAMBLE.STY is as follows (comments removed to reduce the size of the
post)...
\usepackage{babel,graphicx, amsmath, amssymb, textcomp, pslatex, acronym, l=
istings}
\usepackage[center]{caption2}
\usepackage[dvips]{color}
\makeatletter
\def\NAT@parse{\typeout{This is a fake Natbib command to fool Hyperref}}
\makeatother
\usepackage[dvips,
pdftitle=3D{},
pdfauthor=3D{A. S. Budden},
pdfsubject=3D{},
pdfkeywords=3D{},
pdfpagemode=3D{UseOutlines},
bookmarks,bookmarksopen,
pdfstartview=3D{FitH},
colorlinks,linkcolor=3D{black},
urlcolor=3D{black}]{hyperref}
\usepackage[amssymb]{SIunits}
\usepackage[sort]{cite}
\definecolor{darkgreen}{rgb}{0,0.5,0}
\lstset{%
basicstyle=3D\footnotesize, % print whole listing small
keywordstyle=3D\color{blue}\bfseries, % bold blue keywords
identifierstyle=3D, % nothing happens
commentstyle=3D\color{darkgreen}, % green comments
stringstyle=3D\ttfamily, % typewriter type for strings
tabsize=3D4, % sensible tabstops
stringspaces=3Dfalse} % no special string spaces
\newenvironment{centre}{\begin{center}}{\end{center}}
\newenvironment{itemise}{\begin{itemize}}{\end{itemize}}
\newcommand{\comment}[1]{\textcolor{red}{[#1]}}
\newcommand{\commenthash}{\comment{\#\#\#}}
\newcommand{\figwidth}{0.8\columnwidth}
\setlength{\parindent}{0in} % indent of first line of paragraph
\setlength{\parskip}{3ex} % distance between paragraphs
\pagestyle{plain}
\pagenumbering{arabic}
\bibliographystyle{unsrt} % References sorted by usage in text and numbered
=2EVIMINFO:
# This viminfo file was generated by Vim 6.2.
# You may edit it if you're careful!
# Value of 'encoding' when this file was written
*encoding=3Dutf-8
# hlsearch on (H) or off (h):
~h
# Last Search Pattern:
~MSle0~/{
# Last Substitute Search Pattern:
~MSle0&\s\+$
# Last Substitute String:
$\1
# Command Line History (newest to oldest):
:q!
:noh
:wq
:e
:w
:W
:q
:qa
:hardcopy > ~/test.ps
:set pfn=3DMiscFixed:h8
:set printfont=3DMiscFixed\ 8
:e /mnt/dspcode/bldc/bldc.c
:u
:r /mnt/dspcode/bldc/bldc.c=20
:set printfont=3DMiscFixed\ 10
:set guifont?
:set pfn?
:help hardcopy
:bn
:bp
:hardcopy
:e ../sinemod/firstpwm.c
:harcopy
:qa!
:'<,'>!sort
:r /sbin/nomadic
:Spell
:'<,'>|sort
:'<,'>sort
:sp cvectors.asm
:buffers
:help buffers
:previous
:next
:e ../bldc/bldc.c
:set hidden?
:help buffer
:sp ../bldc/bldc.c
:E
:help fullscreen
:Wq
:new <cfile>
:sp cooked_cheesecake.tex
:%s/STDERR/#STDERR/
:sp
:S
:set wrap
:w ctkey
:'<,'>q
:sp .muttrc
# Search String History (newest to oldest):
?{
?\\begin\s*{\s*document\s*}
?^"=3D
?\s\+$
?=20
?for the balanced set
?next
?charset
?urlview
?STDERR
?\<touch\>
?^<img
?secmem
?gpg
?status_form
?auto_view
?dvips
?pgp
?print
?\<Tex_itemise\>
?enumerate
?itemi[sz]e
?s:ingredients
?Tex_description
?Tex_list
?s:description
?s:lists
?Tex_Special
?s:list
?\(<BODY BGCOLOR.*\n\)\_.*\(Quiptic Crossword\|Cryptic Crossword\|Prize Cro=
ssword\|Quick Crossword\)
?cross1.htm
?subscri
?zR
?'
?--
?\r
?sensorless_
?fitzgibb`
?\\subsection
?\\section
?open all
?bold
?viewing
?pdf
?Yann
?A-A-P
?\.\*\.vim\.org
?set hei
?lists
?ADR;WORK:Default;;
# Expression History (newest to oldest):
# Input Line History (newest to oldest):
@pdf
# Input Line History (newest to oldest):
# Registers:
"0 LINE 0
image/*; mutt_bgrun /usr/bin/display %s; copiousoutput; test=3DRunningX
""1 LINE 0
\section{}<++>
"2 LINE 0
\subsection{}<++>
"3 LINE 0
\makeatother
"4 LINE 0
\newcommand\tabcaption{\def\@captype{table}\caption}
"5 LINE 0
\newcommand\figcaption{\def\@captype{figure}\caption}
"6 LINE 0
\makeatletter
"7 LINE 0
\bibliography{citations}
"8 LINE 0
=09
"9 LINE 0
=09
"a CHAR 0
=09
"f CHAR 0
=09
"p CHAR 0
=80kd=1B=80kb
"q CHAR 0
=09
"w CHAR 0
w=1B=1B=0D
"- CHAR 0
,titlepage
# File marks:
'A 356 1 /mnt/dspcode/bldc/bldc.c
'0 4 8 ~/current_work/dspwork/tmp/tmp.tex
'1 5 6 ~/current_work/dspwork/tmp/tmp.tex
'3 7 6 ~/current_work/dspwork/tmp/tmp.tex
'4 9 0 ~/current_work/dspwork/tmp/tmp.tex
'5 15 9 ~/documents/latex/university/dsp_change_log/dsp_change_log.tex
'6 8 6 ~/current_work/dspwork/newfile.tex
'7 10 0 ~/current_work/dspwork/newfile.tex
'8 18 12 ~/current_work/dspwork/newfile.tex
'9 22 12 ~/current_work/dspwork/newfile.tex
# Jumplist (newest first):
-' 4 8 ~/current_work/dspwork/tmp/tmp.tex
-' 5 9 ~/current_work/dspwork/tmp/tmp.tex
-' 1 0 ~/current_work/dspwork/tmp/tmp.tex
-' 2 11 ~/current_work/dspwork/tmp/tmp.tex
-' 3 0 ~/current_work/dspwork/tmp/tmp.tex
-' 7 6 ~/current_work/dspwork/tmp/tmp.tex
-' 9 0 ~/current_work/dspwork/tmp/tmp.tex
-' 15 9 ~/documents/latex/university/dsp_change_log/dsp_change_log.tex
-' 18 13 ~/documents/latex/university/dsp_change_log/dsp_change_log.tex
-' 1 0 ~/documents/latex/university/dsp_change_log/dsp_change_log.tex
-' 7 11 ~/documents/latex/university/dsp_change_log/dsp_change_log.tex
-' 10 0 ~/documents/latex/university/dsp_change_log/dsp_change_log.tex
-' 8 6 ~/current_work/dspwork/newfile.tex
-' 6 18 ~/current_work/dspwork/newfile.tex
-' 5 18 ~/current_work/dspwork/newfile.tex
-' 1 0 ~/current_work/dspwork/newfile.tex
-' 10 0 ~/current_work/dspwork/newfile.tex
-' 4 0 ~/current_work/dspwork/newfile.tex
-' 18 12 ~/current_work/dspwork/newfile.tex
-' 17 7 ~/current_work/dspwork/newfile.tex
-' 15 18 ~/current_work/dspwork/newfile.tex
-' 14 26 ~/current_work/dspwork/newfile.tex
-' 22 12 ~/current_work/dspwork/newfile.tex
-' 21 7 ~/current_work/dspwork/newfile.tex
-' 12 0 ~/.viminfo
-' 1 0 ~/.viminfo
-' 77 0 ~/.viminfo
-' 6 4 ~/documents/latex/university/dsp_change_log/dsp_change_log.tex
-' 4 0 ~/documents/latex/university/phd_notes/eqns/eqn.hamming.window.fu=
nction.tex
-' 1 0 ~/documents/latex/university/phd_notes/eqns/eqn.hamming.window.fu=
nction.tex
-' 122 0 ~/.procmailrc
-' 1 0 ~/.procmailrc
-' 9 0 /tmp/mutt-zakalwe-17972-3
-' 12 3 /tmp/mutt-zakalwe-17972-3
-' 1 0 /tmp/mutt-zakalwe-17972-3
-' 4 0 /mnt/dspcode/sinemod
-' 1 0 /mnt/dspcode/sinemod
-' 39 0 /mnt/dspcode/sinemod
-' 40 0 /mnt/dspcode/sinemod
-' 92 22 /mnt/dspcode/bldc/bldc.c
-' 99 2 /mnt/dspcode/bldc/bldc.c
-' 47 2 /mnt/dspcode/sinemod/firstpwm.c
-' 29 59 /mnt/dspcode/sinemod/firstpwm.c
-' 4 71 /mnt/dspcode/bldc/bldc.c
-' 316 0 /mnt/dspcode/sinemod/firstpwm.c
-' 1 71 /mnt/dspcode/bldc/bldc.c
-' 5 0 /mnt/dspcode/bldc/bldc.c
-' 4424 22 /usr/local/share/vim/vim62/doc/options.txt
-' 653 33 /usr/local/share/vim/vim62/doc/various.txt
-' 1 0 /usr/local/share/vim/vim62/doc/various.txt
-' 17 31 /mnt/dspcode/bldc/bldc.c
-' 316 0 /mnt/dspcode/bldc/bldc.c
-' 459 0 /mnt/dspcode/bldc/bldc.c
-' 23 0 /mnt/dspcode/bldc/bldc.c.html
-' 8 0 /mnt/dspcode/bldc/bldc.c.html
-' 443 0 /mnt/dspcode/bldc/bldc.c.html
-' 459 4 /mnt/dspcode/bldc/bldc.c.html
-' 466 0 /mnt/dspcode/bldc/bldc.c.html
-' 39 0 /mnt/dspcode/bldc/bldc.c.html
-' 465 0 /mnt/dspcode/bldc/bldc.c.html
-' 7 0 /mnt/dspcode/bldc/bldc.c.html
-' 470 6 /mnt/dspcode/bldc/bldc.c.html
-' 1 0 /mnt/dspcode/bldc/bldc.c.html
-' 359 1 /mnt/dspcode/bldc/bldc.c
-' 369 1 /mnt/dspcode/bldc/bldc.c
-' 46 41 ~/.mailcap
-' 1 0 ~/.mailcap
-' 1 0 ~/test
-' 7 1 /tmp/mutt-zakalwe-8143-9
-' 89 42 /tmp/mutt-zakalwe-8143-9
-' 25 34 /tmp/mutt-zakalwe-8143-9
-' 91 0 /tmp/mutt-zakalwe-8143-9
-' 273 20 /mnt/dspcode/bldc/bldc.c
-' 22 17 /mnt/dspcode/bldc/bldc.c
-' 1 0 /mnt/dspcode/bldc/f2407_c.h
-' 80 90 /mnt/dspcode/bldc/f2407_c.h
-' 453 0 /mnt/dspcode/bldc/bldc.c
-' 356 2 /mnt/dspcode/bldc/bldc.c
-' 95 0 /mnt/dspcode/bldc/f2407_c.h
-' 331 1 /mnt/dspcode/bldc/bldc.c
-' 410 15 /mnt/dspcode/bldc/bldc.c
-' 440 12 /mnt/dspcode/bldc/bldc.c
-' 403 15 /mnt/dspcode/bldc/bldc.c
-' 2 0 ~/documents/latex/university/phd_notes/eqns/eqn.vdq.inj.tex
-' 22 10 ~/documents/latex/university/phd_notes/eqns/eqn.vdq.inj.tex
-' 1 0 ~/documents/latex/university/phd_notes/eqns/eqn.vdq.inj.tex
-' 113 22 ~/documents/latex/university/phd_notes/phd_notes.tex
-' 70 27 ~/documents/latex/university/phd_notes/phd_notes.tex
-' 1 0 ~/documents/latex/university/phd_notes/phd_notes.tex
-' 6 11 ~/documents/latex/university/phd_notes/phd_notes.tex
-' 10 0 ~/documents/latex/university/phd_notes/phd_notes.tex
# History of marks within files (newest to oldest):
> ~/current_work/dspwork/tmp/tmp.tex
" 4 8
^ 4 9
. 4 9
> ~/current_work/dspwork/tmp/preamble.sty
" 100 0
. 100 0
> ~/documents/latex/university/dsp_change_log/dsp_change_log.tex
" 15 9
^ 15 10
. 15 9
> ~/current_work/dspwork/newfile.tex
" 8 6
^ 8 7
. 8 7
> ~/.viminfo
" 12 0
> ~/documents/latex/university/dsp_change_log/preamble.sty
" 47 0
^ 40 36
. 40 35
> ~/documents/latex/university/phd_notes/eqns/eqn.hamming.window.function.t=
ex
" 4 0
> ~/.procmailrc
" 122 0
. 122 0
> /tmp/mutt-zakalwe-17972-3
" 9 0
. 7 62
> ~/current_work/gle/wouldnt_it_be_nice.gle
" 8 0
^ 8 1
. 8 0
> /usr/local/share/vim/vim62/doc/various.txt
" 672 39
> /usr/local/share/vim/vim62/doc/options.txt
" 4433 6
> /mnt/dspcode/bldc/bldc.c
" 92 22
^ 4 72
. 4 71
a 356 1
> ~/option-window
" 302 2
. 745 0
> ~/.vimrc
" 80 25
^ 80 26
. 80 25
> /mnt/dspcode/sinemod/firstpwm.c
" 47 2
^ 18 71
. 18 70
> ~/bin/psprint
" 8 0
^ 8 1
. 8 0
> ~/.printing/splx_print.ps
" 438 0
> /mnt/dspcode/bldc/bldc.c.html
" 23 0
^ 470 7
. 38 0
> ~/.mailcap
" 46 41
^ 45 1
. 46 41
|
|
From: Zhang Lin-bo <zl...@ls...> - 2003-06-16 07:57:34
|
Thanks for the quick response :-)
In fact I was trying to figure out what happened precisely
but since I'm not familiar with the Vim stuffs I have soon
found out that it was out of my reach :-(
Instead of seeking for a thorough solution which, as you stated,
seems to be quite involving, there might be some simple workaround.
For example, the '\usepackage' macros are generally placed in the
preamble before all sectioning commands and they don't cause troubles.
I ran into this problem because I was describing certain LaTeX packages,
and in my document the \usepackage commands which come after a \section
command are all between '\begin{verbatim}' and '\end{verbatim}'. I think
when generating foldmarkers the verbatim environments (as well as the
comment environment) should be skipped, and that will at least solve
my problem. Of course I don't know whether it's complicated or
not to skip the verbatim environments when scanning foldregions so
this is just a suggestion.
Best,
LB
On Sun, 15 Jun 2003, Srinath Avadhanula wrote:
>
> > https://sourceforge.net/forum/message.php?msg_id=2061707
> > By: zlb
> >
>
> Unfortunately, it looks like a vim bug:
>
> do the following: open up a new file and type:
>
> bar
> baz
> foo
> baz
>
> Set fdm=manual and fold up the whole file (using ggVGzf). Open the
> fold, put yourself on the first baz line. now close fold again. with
> fold closed, search for baz using /baz. You will still be on the first
> baz line, not the second.
>
> This seems to be due to the default fold-behavior described at:
>
> -----------------------------------%<-----------------------------------
> For Ex commands the range is adjusted to always start at the first line of a
> fold and end at the last line of a fold. Thus this command: >
> :s/foo/bar/g
> when used with the cursor on a closed fold, will replace "foo" with "bar" in
> all lines of the fold.
> This does not happen for |:folddoopen| and |:folddoclosed|.
> -----------------------------------%<-----------------------------------
>
> It will be kind of non-trivial to fix this! :( Basically, it will
> involve opening up the whole file, doing the package scanning and
> folding it back the way it was...
>
> Srinath
>
--
|
|
From: Srinath A. <sr...@fa...> - 2003-06-16 06:30:35
|
> https://sourceforge.net/forum/message.php?msg_id=2061707 > By: zlb > Unfortunately, it looks like a vim bug: do the following: open up a new file and type: bar baz foo baz Set fdm=manual and fold up the whole file (using ggVGzf). Open the fold, put yourself on the first baz line. now close fold again. with fold closed, search for baz using /baz. You will still be on the first baz line, not the second. This seems to be due to the default fold-behavior described at: -----------------------------------%<----------------------------------- For Ex commands the range is adjusted to always start at the first line of a fold and end at the last line of a fold. Thus this command: > :s/foo/bar/g when used with the cursor on a closed fold, will replace "foo" with "bar" in all lines of the fold. This does not happen for |:folddoopen| and |:folddoclosed|. -----------------------------------%<----------------------------------- It will be kind of non-trivial to fix this! :( Basically, it will involve opening up the whole file, doing the package scanning and folding it back the way it was... Srinath |
|
From: SourceForge.net <no...@so...> - 2003-06-16 05:42:30
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=2061814 By: srinathava Yes. I can reproduce this bug! Thanks for catching it. I'll take a look at it. Srinath ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/monitor.php?forum_id=173627 |
34 messages has been excluded from this view by a project administrator.
