Thank you Gerd,

I wish to apologize.
I've been using tex and latex for a couple of years now, and it's only
since I decided to give a try to vim-latexsuite that this behaviour
appeared.

--
EEva

On Wed, Feb 08, 2012 at 05:51:29PM +0000, 
vim-latex-devel-requ...@lists.sourceforge.net wrote:
> Send Vim-latex-devel mailing list submissions to
>       vim-latex-devel@lists.sourceforge.net
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>       https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> or, via email, send a message with subject or body 'help' to
>       vim-latex-devel-requ...@lists.sourceforge.net
> 
> You can reach the person managing the list at
>       vim-latex-devel-ow...@lists.sourceforge.net
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Vim-latex-devel digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Uses of the glossaries package (Ted Pavlic)
>    2. [BUG?] Character problem (EEva)
>    3. Re: [BUG?] Character problem (Gerd Wachsmuth)
>    4. GotoError not working with graphicx or siunitx  packages
>       (David Chamberlain)
>    5. Is it possible to have the mappings in imaps.vim        only for
>       latex filetypes? (jorge rodrigues)
>    6. Re: Is it possible to have the mappings in imaps.vim only for
>       latex filetypes? (Gary Johnson)
>    7. Re: Is it possible to have the mappings in imaps.vim only for
>       latex filetypes? (jorge rodrigues)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 27 Jan 2012 15:16:18 -0500
> From: Ted Pavlic <t...@tedpavlic.com>
> Subject: Re: [Vim-latex-devel] Uses of the glossaries package
> To: vim-latex-devel@lists.sourceforge.net
> Message-ID: <4f230612.8010...@tedpavlic.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Pierre-Alain --
> 
> I haven't had a chance to look into this in detail, but I point you to
> one example that I used a long time ago to get glossaries, acronyms,
> terms, and other similar lists building automatically in Vim-LaTeX.
> 
> At that time, I manually modified compiler.vim to overload makeindex
> with support for other list types. You can find the source code for the
> entire document here:
> 
> http://www.tedpavlic.com/research_related/tpavlic_masters_thesis/
> 
> but the relevant modifications (which may not work in this version of
> Vim-LaTeX, but they give you a hint how to make the modifications) are in:
> 
> http://www.tedpavlic.com/research_related/tpavlic_masters_thesis/texrc
> 
> and
> 
> http://www.tedpavlic.com/research_related/tpavlic_masters_thesis/compiler.vim
> 
> As you can see, the "MakeIndex" related code in compiler.vim was
> duplicated for different other list types (Glo, Acr, and others). When
> LaTeX found the appropriate files, it would make the other MakeIndex
> calls (which were defined in texrc).
> 
> It worked really well then. Maybe something similar to be added to the
> official distribution. I didn't do it then because I didn't want to take
> the time to document it. Now, I built a custom Makefile that takes care
> of this stuff for me... so I've become disconnected with Vim-LaTeX's
> automation...
> 
> Best --
> Ted
> 
> On 01/27/2012 02:06 AM, Pierre-Alain Bourdil wrote:
> > Hi,  
> > 
> >   latex-suite provides the packate acromake, but i  did not find out how to 
> > produce  the acronym list, as the glossaries package do. 
> >   So i tried the latter. I defined glossary entry, as wall as a glossary 
> > with no problem, provided the multiple compilation enable for pdf output.  
> > But i can't use \newacronym and can't generate a acronym list at the end of 
> > the document, with \printacronym. I manually ran makeindex, after a \ll, 
> > but as i can't reference my acronym (using the generated \acro command), 
> > it's useless . 
> > 
> >    Is there a way to do use the acronym functionnality of the glossaries 
> > package (http://en.wikibooks.org/wiki/LaTeX/Glossary) ? 
> > 
> > 
> > Greetings, 
> > 
> > 
> > btw vim latex-suite rocks. 
> > 
> > 
> > ++ 
> > 
> > 
> > 
> > 
> > ------------------------------------------------------------------------------
> > Try before you buy = See our experts in action!
> > The most comprehensive online learning library for Microsoft developers
> > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> > Metro Style Apps, more. Free future releases when you subscribe now!
> > http://p.sf.net/sfu/learndevnow-dev2
> > _______________________________________________
> > Vim-latex-devel mailing list
> > Vim-latex-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> -- 
> Ted Pavlic <t...@tedpavlic.com>
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 3 Feb 2012 13:46:22 +0100
> From: EEva <e...@marvid.fr>
> Subject: [Vim-latex-devel] [BUG?] Character problem
> To: vim-latex-devel@lists.sourceforge.net
> Message-ID: <20120203124622.GA18240@parallel>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi vim-latex list,
> 
> I come to you since I encountered a strange behaviour from both vim and gvim
> while using the vim-latexsuite extension. I just can't type '?' (in Insertion
> mode that goes without saying). All other letters are fine, even ?, ?, etc.
> 
> I'm using a french keyboard on a UTF8 system. Vim has apparently no problem
> with this particular letter since writting it with any other extension works 
> as
> expected.
> 
> Is there a binding on '?' I'm not aware of ?
> 
> Attached to this email is my 
> $ vim --version
> 
> Thanks for reading until here x)
> -------------- next part --------------
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jan 15 2012 06:07:20)
> Rustines incluses : 1-401
> Compil? par ArchLinux
> Grosse version avec interface graphique GTK2.
>   Fonctionnalit?s incluses (+) ou non (-) :
> +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent 
> +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
> +conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui +diff 
> +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi 
> +file_in_path +find_in_path +float +folding -footer +fork() +gettext 
> -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall 
> +linebreak +lispindent +listcmds +localmap +lua +menu +mksession 
> +modify_fname 
> +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm 
> -mouse_sysmouse +mouse_xterm +mouse_urxvt +multi_byte +multi_lang -mzscheme 
> +netbeans_intg +path_extra +perl +persistent_undo +postscript +printer 
> -profile
>  +python -python3 +quickfix +reltime +rightleft +ruby +scrollbind +signs 
> +smartindent -sniff +startuptime +statusline -sun_workshop +syntax 
> +tag_binary 
> +tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects 
> +title
>  +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra 
> +viminfo 
> +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim 
> +xsmp_interact +xterm_clipboard -xterm_save 
>          fichier vimrc syst?me : "/etc/vimrc"
>      fichier vimrc utilisateur : "$HOME/.vimrc"
>       fichier exrc utilisateur : "$HOME/.exrc"
>         fichier gvimrc syst?me : "/etc/gvimrc"
>     fichier gvimrc utilisateur : "$HOME/.gvimrc"
>           fichier menu syst?me : "$VIMRUNTIME/menu.vim"
>                $VIM par d?faut : "/usr/share/vim"
> Compilation : gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread 
> -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 
> -I/usr/include/freetype2 -I/usr/include/libpng14   -I/usr/local/include  
> -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector 
> --param=ssp-buffer-size=4  -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1      
> ?dition de liens : gcc   -L. 
> -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -rdynamic 
> -Wl,-export-dynamic  -Wl,-E -Wl,-rpath,/usr/lib/perl5/core_perl/CORE  
> -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -L/usr/local/lib 
> -Wl,--as-needed -o vim   -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 
> -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo 
> -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 
> -lrt -lglib-2.0   -lSM -lICE -lXt -lX11 -lXdmcp -lSM -lICE -lm -lncurses 
> -lnsl   -lacl -lattr -lgpm -ldl  -L/usr/lib -llua  -Wl,-E 
> -Wl,-rpath,/usr/lib/perl5/core_perl/CORE 
> -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -fstack-protector 
> -L/usr/local/lib  -L/usr/lib/perl5/core_perl/CORE -lperl -lnsl -ldl -lm 
> -lcrypt -lutil -lpthread -lc -L/usr/lib/python2.7/config -lpython2.7 
> -lpthread -ldl -lutil -lm -Xlinker -export-dynamic   -lruby -lpthread -lrt 
> -ldl -lcrypt -lm  -L/usr/lib   
> 
> ------------------------------
> 
> Message: 3
> Date: Fri, 03 Feb 2012 14:58:35 +0100
> From: Gerd Wachsmuth <gerd.wachsm...@mathematik.tu-chemnitz.de>
> Subject: Re: [Vim-latex-devel] [BUG?] Character problem
> To: vim-latex-devel@lists.sourceforge.net
> Message-ID: <4f2be80b.6070...@mathematik.tu-chemnitz.de>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Please read the FAQ:
> 
> http://vim-latex.sourceforge.net/index.php?subject=faq&title=FAQ
> 
> On 02/03/2012 01:46 PM, EEva wrote:
> > Hi vim-latex list,
> > 
> > I come to you since I encountered a strange behaviour from both vim and gvim
> > while using the vim-latexsuite extension. I just can't type '?' (in 
> > Insertion
> > mode that goes without saying). All other letters are fine, even ?, ?, etc.
> > 
> > I'm using a french keyboard on a UTF8 system. Vim has apparently no problem
> > with this particular letter since writting it with any other extension 
> > works as
> > expected.
> > 
> > Is there a binding on '?' I'm not aware of ?
> > 
> > Attached to this email is my 
> > $ vim --version
> > 
> > Thanks for reading until here x)
> > 
> > 
> > 
> > ------------------------------------------------------------------------------
> > Try before you buy = See our experts in action!
> > The most comprehensive online learning library for Microsoft developers
> > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> > Metro Style Apps, more. Free future releases when you subscribe now!
> > http://p.sf.net/sfu/learndevnow-dev2
> > 
> > 
> > 
> > _______________________________________________
> > Vim-latex-devel mailing list
> > Vim-latex-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Fri, 03 Feb 2012 23:48:39 -0800
> From: David Chamberlain <dc46a...@gmail.com>
> Subject: [Vim-latex-devel] GotoError not working with graphicx or
>       siunitx packages
> To: vim-latex-devel@lists.sourceforge.net
> Message-ID: <4f2ce2d7.9050...@gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> 
> Hi all,
> 
> I've noticed that when I use the graphicx or siunitx packages, the 
> goto-error functionality stops working.  Specifically, when a 
> compilation error occurs, the cursor moves to the error message in the 
> compiler output window instead of jumping to the error in the main 
> window.  Pressing enter over the error message does nothing either.  The 
> current workaround is to set g:Tex_GotoError=0 in my tex.vim and 
> manually navigate to errors.  A minimal example:
> 
> \documentclass{article}
> \usepackage{graphicx}
> \begin{document}
> \mistake
> \end{document}
> 
> If I comment out the graphicx package, everything works: the cursor 
> jumps to \mistake.
> 
> This example produces more interesting results:
> 
> \documentclass{article}
> \usepackage{siunitx}
> \mistake
> \begin{document}
> \end{document}
> 
> In this case, the cursor does move to the correct line number in the 
> main window, but the file I was editing is no longer there!  It is 
> replaced with the text of siunitx.sty.
> 
> If you would like to try reproducing this, here are the details:
> 
> Arch Linux x86_64
> TeX Live 2011.3-1.2  (compiling with pdflatex)
> gvim 7.3.401-1  (tried it in vim too)
> vim-latex-1.8.23-20120125.768-git8b62284
> 
> I would appreciate any suggestions about how to get this functionality back.
> 
> Gratefully,
> David C
> 
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Tue, 7 Feb 2012 15:54:17 -0500
> From: jorge rodrigues <ske...@gmail.com>
> Subject: [Vim-latex-devel] Is it possible to have the mappings in
>       imaps.vim       only for latex filetypes?
> To: vim-latex-devel@lists.sourceforge.net
> Message-ID:
>       <CALvSa=q7qe6rsa+4je66bzfvsfis1zuh3f7vpx_czagatbe...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> Would it be possible to have the mappings that are defined in
> imaps.vim defined only for latex files?
> Are they useful for other file types?
> 
> thank you.
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Tue, 7 Feb 2012 17:46:06 -0800
> From: Gary Johnson <garyj...@spocom.com>
> Subject: Re: [Vim-latex-devel] Is it possible to have the mappings in
>       imaps.vim only for latex filetypes?
> To: vim-latex-devel@lists.sourceforge.net
> Message-ID: <20120208014606.GA12530@phoenix>
> Content-Type: text/plain; charset=us-ascii
> 
> On 2012-02-07, jorge rodrigues wrote:
> > Would it be possible to have the mappings that are defined in
> > imaps.vim defined only for latex files?
> > Are they useful for other file types?
> 
> As far as I can tell, the mappings aren't defined in imaps.vim; the
> LaTeX mappings are defined in various files in the latex-suite.  The
> imaps.vim file simply defines the functions used to create the
> mappings.
> 
> So, the IMAP mappings defined for LaTeX files are already used only
> for LaTeX files.  I doubt that the LaTeX mappings would be useful
> for any other file type, but the IMAP mapping mechanism would be
> useful for creating mappings tailored to other file types.
> 
> Regards,
> Gary
> 
> 
> 
> 
> ------------------------------
> 
> Message: 7
> Date: Wed, 8 Feb 2012 12:51:22 -0500
> From: jorge rodrigues <ske...@gmail.com>
> Subject: Re: [Vim-latex-devel] Is it possible to have the mappings in
>       imaps.vim only for latex filetypes?
> To: vim-latex-devel@lists.sourceforge.net
> Message-ID:
>       <CALvSa=RO7Jgij+SWCV6wS5LQbbvkQmi_bU2n7=wrnj0mpuf...@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
> 
> When I am in a c file I type
> :verbose imap <c-j>
> and get:
> i  <NL>          <Plug>IMAP_JumpForward
>         Last set from ~/.vim/bundle/vlatex/plugin/imaps.vim
> 
> I would like to use <c-j> with this mapping in latex files, but leave
> it for other mappings with other file types.
> I tried mapping it to something else in my vimrc but it still shows
> the above mapping.
> 
> Regards,
> 
> Jorge
> 
> On Tue, Feb 7, 2012 at 8:46 PM, Gary Johnson <garyj...@spocom.com> wrote:
> > On 2012-02-07, jorge rodrigues wrote:
> >> Would it be possible to have the mappings that are defined in
> >> imaps.vim defined only for latex files?
> >> Are they useful for other file types?
> >
> > As far as I can tell, the mappings aren't defined in imaps.vim; the
> > LaTeX mappings are defined in various files in the latex-suite. ?The
> > imaps.vim file simply defines the functions used to create the
> > mappings.
> >
> > So, the IMAP mappings defined for LaTeX files are already used only
> > for LaTeX files. ?I doubt that the LaTeX mappings would be useful
> > for any other file type, but the IMAP mapping mechanism would be
> > useful for creating mappings tailored to other file types.
> >
> > Regards,
> > Gary
> >
> >
> > ------------------------------------------------------------------------------
> > Keep Your Developer Skills Current with LearnDevNow!
> > The most comprehensive online learning library for Microsoft developers
> > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> > Metro Style Apps, more. Free future releases when you subscribe now!
> > http://p.sf.net/sfu/learndevnow-d2d
> > _______________________________________________
> > Vim-latex-devel mailing list
> > Vim-latex-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
> 
> ------------------------------
> 
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft developers
> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
> Metro Style Apps, more. Free future releases when you subscribe now!
> http://p.sf.net/sfu/learndevnow-d2d
> 
> ------------------------------
> 
> _______________________________________________
> Vim-latex-devel mailing list
> Vim-latex-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
> End of Vim-latex-devel Digest, Vol 60, Issue 1
> **********************************************

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Reply via email to