vim-latex-devel — Mailing list for developers/maintainers of the vim-latex project

[Vim-latex-devel] [ vim-latex-Patches-3551589 ] Improves indentation for 'begin'/'end' while several ones

[SourceForge.net <no...@so...>]

Patches item #3551589, was opened at 2012-07-29 14:20
Message generated for change (Comment added) made by gerw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3551589&group_id=52322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Benoît Legat (blegat8)
Assigned to: Nobody/Anonymous (nobody)
Summary: Improves indentation for 'begin'/'end' while several ones

Initial Comment:
When several \end and/or \begin of environments lies on the same line, the indentation is not always relevant.
This patch tries to fix it with a little bit of refactoring too (the code for \begin and \end is refactored to one function).
I did some tests and it should normally work now for even the most extreme cases.

----------------------------------------------------------------------

Comment By: Gerd Wachsmuth (gerw)
Date: 2012-08-01 04:54

Message:
I've also tried to improve the indentation of multiple \begin and \end on
one line. See
https://github.com/gerw/vim-latex-suite/blob/master/indent/tex.vim

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3551589&group_id=52322

[Vim-latex-devel] [ vim-latex-Patches-3551589 ] Improves indentation for 'begin'/'end' while several ones

[SourceForge.net <no...@so...>]

Patches item #3551589, was opened at 2012-07-29 14:20
Message generated for change (Tracker Item Submitted) made by blegat8
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3551589&group_id=52322

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Benoît Legat (blegat8)
Assigned to: Nobody/Anonymous (nobody)
Summary: Improves indentation for 'begin'/'end' while several ones

Initial Comment:
When several \end and/or \begin of environments lies on the same line, the indentation is not always relevant.
This patch tries to fix it with a little bit of refactoring too (the code for \begin and \end is refactored to one function).
I did some tests and it should normally work now for even the most extreme cases.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3551589&group_id=52322

Re: [Vim-latex-devel] Mouse middle button does not work using vim-latex in gvim-7.3

[Ted P. <te...@te...>]

Liang --

Here's what happens on my system.

1. I highlight the text "abcd" in GVim, I then middle-click inside
Firefox or Konsole, and "abcd" shows up.

2. I highlight the text "cdef" in Konsole or Firefox. I then
middle-click inside Gvim, and "cdef" shows up.

I *think* that's the functionality you're looking for. Right?

If it's not working that way, then there's something special about your system.

For comparison, here's my entire version dump (pasted using middle
click after highlighting in Gvim, by the way):

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 13 2012 05:24:27)
Included patches: 1-600
Compiled by ArchLinux
Big version with GTK2 GUI.  Features included (+) or not (-):
+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
   system vimrc file: "/etc/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "/etc/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/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-pi
xbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -I/usr/i
nclude/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng15
-I/usr/local/include  -marc
h=x86-64 -mtune=generic -pipe -fstack-protector
--param=ssp-buffer-size=4  -U_FORTIFY_SOURCE -
D_FORTIFY_SOURCE=1
Linking: 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-ne
eded,-z,relro -L/usr/local/lib -Wl,--as-needed -o vim   -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 -lfo
ntconfig -lgobject-2.0 -lglib-2.0   -lSM -lICE -lXt -lX11 -lXdmcp -lSM
-lICE -lm -lncurses -ln
sl   -lacl -lattr -lgpm -ldl  -L/usr/lib -llua  -Wl,-E
-Wl,-rpath,/usr/lib/perl5/core_perl/COR
E -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu
-fstack-protector -L/usr/local/l
ib  -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


    Notice anything strange/different? --
Ted

On Wed, Jul 25, 2012 at 7:39 AM, Liang Guo <lia...@gm...> wrote:
> Hi Ted,
>
> I'm getting more and more confused by the copy/paste to and from gvim.
>
> In genenral (not in TeX files), hightlight then middle-click works
> Xwindow-->Gvim; but highlight then middle-click doesnot work the other
> way (Gvim-->Xwindow).
>
> This is beause text is copy to different selections. In short, can I
> make highlight and middle-click works at both directions
> (Xwindow<-->GVIM)?
>
> Thank you,
> Liang
>
>
>
> my OS is:
> Linux titania 2.6.34.10-0.4-desktop #1 SMP PREEMPT 2011-10-19 22:16:41
> +0200 x86_64 x86_64 x86_64 GNU/Linux
>
> And my Gvim version is:
> titania$ gvim --version
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 20 2012 17:49:19)
> Compiled by dh023729@chestnut
> Normal version with X11-Athena GUI.  Features included (+) or not (-):
> -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 -multi_byte +multi_lang -mzscheme +netbeans_intg
> -osfiletype +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
>    system vimrc file: "$VIM/vimrc"
>      user vimrc file: "$HOME/.vimrc"
>       user exrc file: "$HOME/.exrc"
>   system gvimrc file: "$VIM/gvimrc"
>     user gvimrc file: "$HOME/.gvimrc"
>     system menu file: "$VIMRUNTIME/menu.vim"
>   fall-back for $VIM: "/home/dh023729/share/vim"
> Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_ATHENA
> -DFUNCPROTO=15 -DNARROWPROTO    -O2 -fno-strength-reduce -Wall
> -D_FORTIFY_SOURCE=1
> Linking: gcc    -o vim -lXaw -lXext -lm -lncurses -lgpm
>
>
> On 23 July 2012 18:12, Ted Pavlic <te...@te...> wrote:
>> Liang --
>>
>>         You have the problem with every TeX file you open?
>>
>>         From your message, it sounds like the major problem is that "+p and "*p
>> are not functioning the same in TeX files as they do elsewhere. Correct?
>> That is, middle-click activates "*p as designed, but "*p isn't grabbing
>> your primary selection (which is what you would prefer). Correct?
>>
>>         I don't have this problem on my machine. My :version reports:
>>
>> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 13 2012 05:24:27)
>> Included patches: 1-600
>> Compiled by ArchLinux
>>
>> along with several features included and excluded, including
>>
>> +X11
>> -xfontset
>> +xim
>> +xterm_clipboard
>> -xterm_save
>>
>> I don't recall what all of those features are, but I believe that some
>> (most definitely +xterm_clipboard) affect the handling of "*p and "+p.
>>
>>         I did a git grep through the vim-latex repo for things that I thought
>> might be related, but I didn't see anything that caught my eye.
>>
>>         Are you sure there's no other tex-specific settings you have? Say in
>> your ftplugin/tex? (I don't even know what sort of setting you would
>> look for; as far as I know (??), the semantics of "*p and "+p are
>> hard-coded at compile time)
>>
>>         --Ted
>>
>>
>>
>> On 07/23/2012 02:21 AM, Liang Guo wrote:
>>> Hi Ted,
>>>
>>> Thanks for the reply. I figured that you tried tell me that i confused the two copy-paste methods. You think that I highlight some text, and then ctrl+C (copy text in clipboard selection), then used middle-click in gvim. The random text is  because the middle-click pass the text from primary selection (as I highlight other text somewhere else) rather than from clipboard selection.
>>>
>>> However, this is not the case. I tried both "*p and "+p. "*p pasted the text from ctrl+C. But, "+p did not pasted anything which I highlighted, instead it shown some text like a latex template.
>>>
>>> This situation occurs only when I edit a latex file. The middle-click or "+p/"*p works fine when I edit files with other suffixes.
>>>
>>> Any idea?
>>>
>>> Liang
>>>
>>> On 23 Jul 2012, at 08:38, Ted Pavlic <te...@te...> wrote:
>>>
>>>> Liang --
>>>>
>>>> Before continuing, are you sure there's no confusion about "primary"
>>>> and "clipboard" selections in X11? Your trouble may come from being
>>>> accustomed to using vim in a terminal (not an X virtual terminal) and
>>>> then moving to using gvim alone (or, perhaps, vim in a virtual
>>>> terminal in X11). What is getting pasted when you hit your middle
>>>> button is not random; it is likely text you have highlighted (perhaps
>>>> inadvertently) in another window.
>>>>
>>>> Here's a decent reference on primary and clipboard selections in X11
>>>> (in this case, they refer to EMacs and XEmacs, but the general
>>>> description of these different types of selections applies for Vim and
>>>> Gvim as well):
>>>>
>>>> http://www.jwz.org/doc/x-cut-and-paste.html
>>>>
>>>> Your middle mouse button in an X11 application (like GVim) will access
>>>> the "primary" (as opposed to "clipboard") selection. So if you've
>>>> highlighted some text in one window and middle-click in GVim, you
>>>> should expect that highlighted text to get pasted even if you didn't
>>>> explicitly "copy" it anywhere.
>>>>
>>>> It sounds like you would prefer your middle mouse button to do the same thing as
>>>>
>>>> "+p
>>>>
>>>> but instead you're getting the result of
>>>>
>>>> "*p
>>>>
>>>> Is that correct? Can you try those two combinations and compare them
>>>> to your mouse click?
>>>>
>>>>     You may be interested in:
>>>>
>>>> :help clipboard
>>>>
>>>> and
>>>>
>>>> :help x11-selection
>>>>
>>>>    Best --
>>>>    Ted
>>>>
>>>> On Fri, Jul 20, 2012 at 10:46 AM, Liang Guo (Gmail)
>>>> <lia...@gm...> wrote:
>>>>> Hi,
>>>>>
>>>>> I used to use vim-latex in vim-7.3, and I do not have any problem to use mouse middle button to paste text from elsewhere.
>>>>>
>>>>> And, now I try to edit my latex file in gvim-7.3, things getting bizarre. Every time I press middle button, random text is pasted. And this only occurred when I'm editing latex file, files with .tex as suffix. Therefore, I'm sure it is something related to vim-latex in gvim.
>>>>>
>>>>> Does anyone encounter the similar problem?
>>>>>
>>>>> Thank you,
>>>>> Liang
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Live Security Virtual Conference
>>>>> Exclusive live event will cover all the ways today's security and
>>>>> threat landscape has changed and how IT managers can respond. Discussions
>>>>> will include endpoint security, mobile security and the latest in malware
>>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>>> _______________________________________________
>>>>> Vim-latex-devel mailing list
>>>>> Vim...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>>
>>>>
>>>>
>>>> --
>>>> Ted Pavlic <te...@te...>
>>
>> --
>> Ted Pavlic <te...@te...>



-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Mouse middle button does not work using vim-latex in gvim-7.3

[Liang G. <lia...@gm...>]

Hi Ted,

I'm getting more and more confused by the copy/paste to and from gvim.

In genenral (not in TeX files), hightlight then middle-click works
Xwindow-->Gvim; but highlight then middle-click doesnot work the other
way (Gvim-->Xwindow).

This is beause text is copy to different selections. In short, can I
make highlight and middle-click works at both directions
(Xwindow<-->GVIM)?

Thank you,
Liang



my OS is:
Linux titania 2.6.34.10-0.4-desktop #1 SMP PREEMPT 2011-10-19 22:16:41
+0200 x86_64 x86_64 x86_64 GNU/Linux

And my Gvim version is:
titania$ gvim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 20 2012 17:49:19)
Compiled by dh023729@chestnut
Normal version with X11-Athena GUI.  Features included (+) or not (-):
-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 -multi_byte +multi_lang -mzscheme +netbeans_intg
-osfiletype +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
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  system gvimrc file: "$VIM/gvimrc"
    user gvimrc file: "$HOME/.gvimrc"
    system menu file: "$VIMRUNTIME/menu.vim"
  fall-back for $VIM: "/home/dh023729/share/vim"
Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_ATHENA
-DFUNCPROTO=15 -DNARROWPROTO    -O2 -fno-strength-reduce -Wall
-D_FORTIFY_SOURCE=1
Linking: gcc    -o vim -lXaw -lXext -lm -lncurses -lgpm


On 23 July 2012 18:12, Ted Pavlic <te...@te...> wrote:
> Liang --
>
>         You have the problem with every TeX file you open?
>
>         From your message, it sounds like the major problem is that "+p and "*p
> are not functioning the same in TeX files as they do elsewhere. Correct?
> That is, middle-click activates "*p as designed, but "*p isn't grabbing
> your primary selection (which is what you would prefer). Correct?
>
>         I don't have this problem on my machine. My :version reports:
>
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 13 2012 05:24:27)
> Included patches: 1-600
> Compiled by ArchLinux
>
> along with several features included and excluded, including
>
> +X11
> -xfontset
> +xim
> +xterm_clipboard
> -xterm_save
>
> I don't recall what all of those features are, but I believe that some
> (most definitely +xterm_clipboard) affect the handling of "*p and "+p.
>
>         I did a git grep through the vim-latex repo for things that I thought
> might be related, but I didn't see anything that caught my eye.
>
>         Are you sure there's no other tex-specific settings you have? Say in
> your ftplugin/tex? (I don't even know what sort of setting you would
> look for; as far as I know (??), the semantics of "*p and "+p are
> hard-coded at compile time)
>
>         --Ted
>
>
>
> On 07/23/2012 02:21 AM, Liang Guo wrote:
>> Hi Ted,
>>
>> Thanks for the reply. I figured that you tried tell me that i confused the two copy-paste methods. You think that I highlight some text, and then ctrl+C (copy text in clipboard selection), then used middle-click in gvim. The random text is  because the middle-click pass the text from primary selection (as I highlight other text somewhere else) rather than from clipboard selection.
>>
>> However, this is not the case. I tried both "*p and "+p. "*p pasted the text from ctrl+C. But, "+p did not pasted anything which I highlighted, instead it shown some text like a latex template.
>>
>> This situation occurs only when I edit a latex file. The middle-click or "+p/"*p works fine when I edit files with other suffixes.
>>
>> Any idea?
>>
>> Liang
>>
>> On 23 Jul 2012, at 08:38, Ted Pavlic <te...@te...> wrote:
>>
>>> Liang --
>>>
>>> Before continuing, are you sure there's no confusion about "primary"
>>> and "clipboard" selections in X11? Your trouble may come from being
>>> accustomed to using vim in a terminal (not an X virtual terminal) and
>>> then moving to using gvim alone (or, perhaps, vim in a virtual
>>> terminal in X11). What is getting pasted when you hit your middle
>>> button is not random; it is likely text you have highlighted (perhaps
>>> inadvertently) in another window.
>>>
>>> Here's a decent reference on primary and clipboard selections in X11
>>> (in this case, they refer to EMacs and XEmacs, but the general
>>> description of these different types of selections applies for Vim and
>>> Gvim as well):
>>>
>>> http://www.jwz.org/doc/x-cut-and-paste.html
>>>
>>> Your middle mouse button in an X11 application (like GVim) will access
>>> the "primary" (as opposed to "clipboard") selection. So if you've
>>> highlighted some text in one window and middle-click in GVim, you
>>> should expect that highlighted text to get pasted even if you didn't
>>> explicitly "copy" it anywhere.
>>>
>>> It sounds like you would prefer your middle mouse button to do the same thing as
>>>
>>> "+p
>>>
>>> but instead you're getting the result of
>>>
>>> "*p
>>>
>>> Is that correct? Can you try those two combinations and compare them
>>> to your mouse click?
>>>
>>>     You may be interested in:
>>>
>>> :help clipboard
>>>
>>> and
>>>
>>> :help x11-selection
>>>
>>>    Best --
>>>    Ted
>>>
>>> On Fri, Jul 20, 2012 at 10:46 AM, Liang Guo (Gmail)
>>> <lia...@gm...> wrote:
>>>> Hi,
>>>>
>>>> I used to use vim-latex in vim-7.3, and I do not have any problem to use mouse middle button to paste text from elsewhere.
>>>>
>>>> And, now I try to edit my latex file in gvim-7.3, things getting bizarre. Every time I press middle button, random text is pasted. And this only occurred when I'm editing latex file, files with .tex as suffix. Therefore, I'm sure it is something related to vim-latex in gvim.
>>>>
>>>> Does anyone encounter the similar problem?
>>>>
>>>> Thank you,
>>>> Liang
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Live Security Virtual Conference
>>>> Exclusive live event will cover all the ways today's security and
>>>> threat landscape has changed and how IT managers can respond. Discussions
>>>> will include endpoint security, mobile security and the latest in malware
>>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>> _______________________________________________
>>>> Vim-latex-devel mailing list
>>>> Vim...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>
>>>
>>>
>>> --
>>> Ted Pavlic <te...@te...>
>
> --
> Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Mouse middle button does not work using vim-latex in gvim-7.3

[Ted P. <te...@te...>]

Liang --

	You have the problem with every TeX file you open?

	From your message, it sounds like the major problem is that "+p and "*p
are not functioning the same in TeX files as they do elsewhere. Correct?
That is, middle-click activates "*p as designed, but "*p isn't grabbing
your primary selection (which is what you would prefer). Correct?

	I don't have this problem on my machine. My :version reports:

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 13 2012 05:24:27)
Included patches: 1-600
Compiled by ArchLinux

along with several features included and excluded, including

+X11
-xfontset
+xim
+xterm_clipboard
-xterm_save

I don't recall what all of those features are, but I believe that some
(most definitely +xterm_clipboard) affect the handling of "*p and "+p.

	I did a git grep through the vim-latex repo for things that I thought
might be related, but I didn't see anything that caught my eye.

	Are you sure there's no other tex-specific settings you have? Say in
your ftplugin/tex? (I don't even know what sort of setting you would
look for; as far as I know (??), the semantics of "*p and "+p are
hard-coded at compile time)

	--Ted



On 07/23/2012 02:21 AM, Liang Guo wrote:
> Hi Ted, 
> 
> Thanks for the reply. I figured that you tried tell me that i confused the two copy-paste methods. You think that I highlight some text, and then ctrl+C (copy text in clipboard selection), then used middle-click in gvim. The random text is  because the middle-click pass the text from primary selection (as I highlight other text somewhere else) rather than from clipboard selection.
> 
> However, this is not the case. I tried both "*p and "+p. "*p pasted the text from ctrl+C. But, "+p did not pasted anything which I highlighted, instead it shown some text like a latex template.
> 
> This situation occurs only when I edit a latex file. The middle-click or "+p/"*p works fine when I edit files with other suffixes.
> 
> Any idea?
> 
> Liang
> 
> On 23 Jul 2012, at 08:38, Ted Pavlic <te...@te...> wrote:
> 
>> Liang --
>>
>> Before continuing, are you sure there's no confusion about "primary"
>> and "clipboard" selections in X11? Your trouble may come from being
>> accustomed to using vim in a terminal (not an X virtual terminal) and
>> then moving to using gvim alone (or, perhaps, vim in a virtual
>> terminal in X11). What is getting pasted when you hit your middle
>> button is not random; it is likely text you have highlighted (perhaps
>> inadvertently) in another window.
>>
>> Here's a decent reference on primary and clipboard selections in X11
>> (in this case, they refer to EMacs and XEmacs, but the general
>> description of these different types of selections applies for Vim and
>> Gvim as well):
>>
>> http://www.jwz.org/doc/x-cut-and-paste.html
>>
>> Your middle mouse button in an X11 application (like GVim) will access
>> the "primary" (as opposed to "clipboard") selection. So if you've
>> highlighted some text in one window and middle-click in GVim, you
>> should expect that highlighted text to get pasted even if you didn't
>> explicitly "copy" it anywhere.
>>
>> It sounds like you would prefer your middle mouse button to do the same thing as
>>
>> "+p
>>
>> but instead you're getting the result of
>>
>> "*p
>>
>> Is that correct? Can you try those two combinations and compare them
>> to your mouse click?
>>
>>     You may be interested in:
>>
>> :help clipboard
>>
>> and
>>
>> :help x11-selection
>>
>>    Best --
>>    Ted
>>
>> On Fri, Jul 20, 2012 at 10:46 AM, Liang Guo (Gmail)
>> <lia...@gm...> wrote:
>>> Hi,
>>>
>>> I used to use vim-latex in vim-7.3, and I do not have any problem to use mouse middle button to paste text from elsewhere.
>>>
>>> And, now I try to edit my latex file in gvim-7.3, things getting bizarre. Every time I press middle button, random text is pasted. And this only occurred when I'm editing latex file, files with .tex as suffix. Therefore, I'm sure it is something related to vim-latex in gvim.
>>>
>>> Does anyone encounter the similar problem?
>>>
>>> Thank you,
>>> Liang
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>
>>
>>
>> -- 
>> Ted Pavlic <te...@te...>

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Mouse middle button does not work using vim-latex in gvim-7.3

[Liang G. <lia...@gm...>]

Hi Ted, 

Thanks for the reply. I figured that you tried tell me that i confused the two copy-paste methods. You think that I highlight some text, and then ctrl+C (copy text in clipboard selection), then used middle-click in gvim. The random text is  because the middle-click pass the text from primary selection (as I highlight other text somewhere else) rather than from clipboard selection.

However, this is not the case. I tried both "*p and "+p. "*p pasted the text from ctrl+C. But, "+p did not pasted anything which I highlighted, instead it shown some text like a latex template.

This situation occurs only when I edit a latex file. The middle-click or "+p/"*p works fine when I edit files with other suffixes.

Any idea?

Liang

On 23 Jul 2012, at 08:38, Ted Pavlic <te...@te...> wrote:

> Liang --
> 
> Before continuing, are you sure there's no confusion about "primary"
> and "clipboard" selections in X11? Your trouble may come from being
> accustomed to using vim in a terminal (not an X virtual terminal) and
> then moving to using gvim alone (or, perhaps, vim in a virtual
> terminal in X11). What is getting pasted when you hit your middle
> button is not random; it is likely text you have highlighted (perhaps
> inadvertently) in another window.
> 
> Here's a decent reference on primary and clipboard selections in X11
> (in this case, they refer to EMacs and XEmacs, but the general
> description of these different types of selections applies for Vim and
> Gvim as well):
> 
> http://www.jwz.org/doc/x-cut-and-paste.html
> 
> Your middle mouse button in an X11 application (like GVim) will access
> the "primary" (as opposed to "clipboard") selection. So if you've
> highlighted some text in one window and middle-click in GVim, you
> should expect that highlighted text to get pasted even if you didn't
> explicitly "copy" it anywhere.
> 
> It sounds like you would prefer your middle mouse button to do the same thing as
> 
> "+p
> 
> but instead you're getting the result of
> 
> "*p
> 
> Is that correct? Can you try those two combinations and compare them
> to your mouse click?
> 
>     You may be interested in:
> 
> :help clipboard
> 
> and
> 
> :help x11-selection
> 
>    Best --
>    Ted
> 
> On Fri, Jul 20, 2012 at 10:46 AM, Liang Guo (Gmail)
> <lia...@gm...> wrote:
>> Hi,
>> 
>> I used to use vim-latex in vim-7.3, and I do not have any problem to use mouse middle button to paste text from elsewhere.
>> 
>> And, now I try to edit my latex file in gvim-7.3, things getting bizarre. Every time I press middle button, random text is pasted. And this only occurred when I'm editing latex file, files with .tex as suffix. Therefore, I'm sure it is something related to vim-latex in gvim.
>> 
>> Does anyone encounter the similar problem?
>> 
>> Thank you,
>> Liang
>> 
>> 
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
> 
> -- 
> Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Mouse middle button does not work using vim-latex in gvim-7.3

[Ted P. <te...@te...>]

Liang --

Before continuing, are you sure there's no confusion about "primary"
and "clipboard" selections in X11? Your trouble may come from being
accustomed to using vim in a terminal (not an X virtual terminal) and
then moving to using gvim alone (or, perhaps, vim in a virtual
terminal in X11). What is getting pasted when you hit your middle
button is not random; it is likely text you have highlighted (perhaps
inadvertently) in another window.

Here's a decent reference on primary and clipboard selections in X11
(in this case, they refer to EMacs and XEmacs, but the general
description of these different types of selections applies for Vim and
Gvim as well):

http://www.jwz.org/doc/x-cut-and-paste.html

Your middle mouse button in an X11 application (like GVim) will access
the "primary" (as opposed to "clipboard") selection. So if you've
highlighted some text in one window and middle-click in GVim, you
should expect that highlighted text to get pasted even if you didn't
explicitly "copy" it anywhere.

It sounds like you would prefer your middle mouse button to do the same thing as

"+p

but instead you're getting the result of

"*p

Is that correct? Can you try those two combinations and compare them
to your mouse click?

     You may be interested in:

:help clipboard

and

:help x11-selection

    Best --
    Ted

On Fri, Jul 20, 2012 at 10:46 AM, Liang Guo (Gmail)
<lia...@gm...> wrote:
> Hi,
>
> I used to use vim-latex in vim-7.3, and I do not have any problem to use mouse middle button to paste text from elsewhere.
>
> And, now I try to edit my latex file in gvim-7.3, things getting bizarre. Every time I press middle button, random text is pasted. And this only occurred when I'm editing latex file, files with .tex as suffix. Therefore, I'm sure it is something related to vim-latex in gvim.
>
> Does anyone encounter the similar problem?
>
> Thank you,
> Liang
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel



-- 
Ted Pavlic <te...@te...>

[Vim-latex-devel] Mouse middle button does not work using vim-latex in gvim-7.3

[Liang G. (Gmail) <lia...@gm...>]

Hi,

I used to use vim-latex in vim-7.3, and I do not have any problem to use mouse middle button to paste text from elsewhere.

And, now I try to edit my latex file in gvim-7.3, things getting bizarre. Every time I press middle button, random text is pasted. And this only occurred when I'm editing latex file, files with .tex as suffix. Therefore, I'm sure it is something related to vim-latex in gvim. 

Does anyone encounter the similar problem?

Thank you,
Liang 

[Vim-latex-devel] 1 little change for kbibtex users

[Simon <sim...@gm...>]

I had the same probleme than here :
http://ubuntuforums.org/showthread.php?t=952911
and as I don't wand to edit my .bib each time kbibtex save the file, I
change the ftplugin/latex-suite/bibtools.py file in order to allow space
before the key of the bib entry :
Line 32 :
m = re.match(r'\s*@(\w+){((\S+),)?(.*)}\s*', txt,re.MULTILINE | re.DOTALL)
I just add a \s* 
m = re.match(r'\s*@(\w+){\s*((\S+),)?(.*)}\s*', txt, re.MULTILINE | re.DOTALL)

Maybe it can be a good idea to add it into the repository, I spend long
time to find why I wasn't able to have this beautiful completion
working, and it's not so much change to do :)

have a nice week!

Simon

[Vim-latex-devel] IMAP does not work with numpad in gvim

[Bodo G. <ma...@bo...>]

Hi,

I have the following mapping in my
$HOME/.vim/after/ftplugin/tex/latex_suite.vim

call IMAP('1/2', '\frac12', 'tex')

But when I type the '2' with my numpad (or neo2 layer 4 for that
matter), it is not getting executed. But when I do it with the normal
key or even in the console with the numpad, it works.
(Although I have to admit, that for the console 'urxvt' I have settings
like the following in .Xdefaults:

URxvt.keysym.KP_1:      1

)

So is there anything that can be done?

best regards,
Bodo

Re: [Vim-latex-devel] Change compile rule

[Ted P. <te...@te...>]

>> So instead, put your changes in .vimrc (and you made the correct changes
>> to get dvi->ps->pdf working).
> IMHO, it's better to put these changes inside .vim/ftplugin/tex.vim, 
> such that they will be sourced only when editing a tex file.

I think it depends on the particular changes you want to make. For example,

let g:tex_flavor='latex'

should go in your .vimrc. Most of the changes mentioned in this thread
could definitely go in your personal .vim/ftplugin (or behind an
autocommand (block) that masks off the changes for all but TeX files).
However, you have to be careful to make that as a rule. For example, if
you want to change the way placeholders work, you must put those imaps
in your .vimrc as the imaps.vim plugin gets sourced as soon as Vim
starts. See:

:help remapping-latex-suite-keys
:help ls_a_ei

for details.

Still, some people might not use pathogen and are hesitant to backup
their configuration modifications in .vim/ftplugin because they don't
want to backup a bunch of other junk... Some people might also just be
uncomfortable with .vim/ftplugin (and .vim/after/, etc.) and thus want
to keep things in .vimrc. Others just might think debugging is easier
when all configuration options are set in one place (and after all, you
can setup autocommands in the .vimrc to source other configuration files
on demand that are located in other places).

--Ted


-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Change compile rule

[Gerd W. <ger...@ma...>]

On 07/17/2012 09:01 PM, Ted Pavlic wrote:
>> Is that means I donot need to modify ~.vim/ftplugin/latex-suite/texrc, and just overwrite it by putting setting in .vimrc file?
>
> That's correct. You should not edit the texrc file. For one, if you ever
> update your LaTeX-suite to add new bug fixes, your changes to the texrc
> file will get wiped away.
>
> So instead, put your changes in .vimrc (and you made the correct changes
> to get dvi->ps->pdf working).
IMHO, it's better to put these changes inside .vim/ftplugin/tex.vim, 
such that they will be sourced only when editing a tex file.

Best Regards
Gerd

Re: [Vim-latex-devel] Change compile rule

[Ted P. <te...@te...>]

> Is that means I donot need to modify ~.vim/ftplugin/latex-suite/texrc, and just overwrite it by putting setting in .vimrc file?

That's correct. You should not edit the texrc file. For one, if you ever
update your LaTeX-suite to add new bug fixes, your changes to the texrc
file will get wiped away.

So instead, put your changes in .vimrc (and you made the correct changes
to get dvi->ps->pdf working).

--Ted

> Thanks,
> Liang
> 
> 
> On 17 Jul 2012, at 07:41, Alessandro Pezzoni wrote:
> 
>> On Tue, Jul 17, 2012 at 12:34:55AM +0100, Liang Guo (Gmail) wrote:
>>> I'm new to vim-latex, I had a silly question. I'm using latex on my
>>> mac with mvim. When I compiled it using '\ll', I assume it uses
>>> pdflatex rather than latex as all my *.eps have been converted into
>>> *.pdf.
>>>
>>> I tried to change the compile rule to using latex. Here is what I did
>>> in ~.vim/ftplugin/latex-suite/texrc :
>>>
>>> However, it turned out that there is nothing happened, every time as I
>>> used '\ll' to compile, at the bottom of the mvim shown "Ran latex 1
>>> time(s)". And there was nothing occurred except a blank .pdf file.
>>
>> Hello,
>> could you please tell me what happens when you try to compile the latex
>> file yourself (from a terminal)?
>> Moreover, could you please post your latex-suite related vim settings?
>>
>> Alessandro
>>
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and 
>> threat landscape has changed and how IT managers can respond. Discussions 
>> will include endpoint security, mobile security and the latest in malware 
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Vim-latex-devel mailing list
>> Vim...@li...
>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] Change compile rule

[Liang G. (Gmail) <lia...@gm...>]

Hi Alessandro,

When I compile the latex file myself from a terminal, it works fine.

And, I kind of got the idea how to make it work, as I put the following setting in my .vimrc file, the compile works fine.
===============
let g:Tex_FormatDependency_pdf = 'dvi,ps,pdf'

let g:Tex_CompileRule_dvi = 'latex --interaction=nonstopmode $*'
let g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'
let g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'
===============

Is that means I donot need to modify ~.vim/ftplugin/latex-suite/texrc, and just overwrite it by putting setting in .vimrc file?

Thanks,
Liang


On 17 Jul 2012, at 07:41, Alessandro Pezzoni wrote:

> On Tue, Jul 17, 2012 at 12:34:55AM +0100, Liang Guo (Gmail) wrote:
>> I'm new to vim-latex, I had a silly question. I'm using latex on my
>> mac with mvim. When I compiled it using '\ll', I assume it uses
>> pdflatex rather than latex as all my *.eps have been converted into
>> *.pdf.
>> 
>> I tried to change the compile rule to using latex. Here is what I did
>> in ~.vim/ftplugin/latex-suite/texrc :
>> 
>> However, it turned out that there is nothing happened, every time as I
>> used '\ll' to compile, at the bottom of the mvim shown "Ran latex 1
>> time(s)". And there was nothing occurred except a blank .pdf file.
> 
> Hello,
> could you please tell me what happens when you try to compile the latex
> file yourself (from a terminal)?
> Moreover, could you please post your latex-suite related vim settings?
> 
> Alessandro
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Re: [Vim-latex-devel] Change compile rule

[Alessandro P. <ale...@la...>]

On Tue, Jul 17, 2012 at 12:34:55AM +0100, Liang Guo (Gmail) wrote:
> I'm new to vim-latex, I had a silly question. I'm using latex on my
> mac with mvim. When I compiled it using '\ll', I assume it uses
> pdflatex rather than latex as all my *.eps have been converted into
> *.pdf.
> 
> I tried to change the compile rule to using latex. Here is what I did
> in ~.vim/ftplugin/latex-suite/texrc :
> 
> However, it turned out that there is nothing happened, every time as I
> used '\ll' to compile, at the bottom of the mvim shown "Ran latex 1
> time(s)". And there was nothing occurred except a blank .pdf file.

Hello,
could you please tell me what happens when you try to compile the latex
file yourself (from a terminal)?
Moreover, could you please post your latex-suite related vim settings?

Alessandro

[Vim-latex-devel] Change compile rule

[Liang G. (Gmail) <lia...@gm...>]

Hi,

I'm new to vim-latex, I had a silly question. I'm using latex on my mac with mvim. When I compiled it using '\ll', I assume it uses pdflatex rather than latex as all my *.eps have been converted into *.pdf.

I tried to change the compile rule to using latex. Here is what I did in ~.vim/ftplugin/latex-suite/texrc :
" ==============================================================================
" Rules: specifications of programs for compiling and viewing {{{
"

" By default, when you compile a tex file using \ll, then you will be
" generating a .dvi file. Change this line if you want to set another default.
" NOTE: Make sure that a target for this format exists in the 'Compiler rules'
"       section below and is set up properly for your system.
if has('macunix')
	TexLet g:Tex_DefaultTargetFormat = 'pdf'
else
	TexLet g:Tex_DefaultTargetFormat = 'dvi'
endif

" A comma seperated list of formats which need multiple compilations to be
" correctly compiled.
TexLet g:Tex_MultipleCompileFormats = 'dvi'

" Uncomment this line if you compile ps files via dvi files.
TexLet g:Tex_FormatDependency_ps = 'dvi,ps,pdf'		%% add pdf on the dependency %%

" ------------------------------------------------------------------------------
" Compiler rules {{{
" This is the first thing you should customize. It is set up for most common
" values, but if use some other compiler, then you will want to change this.
" As CompileFlags value you'd perhaps like to use, e.g., '-src-specials',
" but it is known that it can sometimes give different results in the output,
" so use it with care. The '-file-line-error' flag helps sanitize LaTeX error
" messages for processing by Vim.
TexLet g:Tex_CompileRule_dvi = 'latex -interaction=nonstopmode $*'
TexLet g:Tex_EscapeChars = '{}\'

TexLet g:Tex_CompileRule_ps = 'dvips -Ppdf -o $*.ps $*.dvi'

" ways to generate pdf files. there are soo many...
" NOTE: pdflatex generates the same output as latex. therefore quickfix is
"       possible.
" TexLet g:Tex_CompileRule_pdf = 'pdflatex -interaction=nonstopmode $*'
TexLet g:Tex_CompileRule_pdf = 'ps2pdf $*.ps'			%% generate pdf from ps	%%
" TexLet g:Tex_CompileRule_pdf = 'dvipdfm $*.dvi'
" TexLet g:Tex_CompileRule_pdf = 'dvipdf $*.dvi'

TexLet g:Tex_CompileRule_html = 'latex2html $*.tex'

TexLet g:Tex_CompileRule_bib = g:Tex_BibtexFlavor . ' $*'

" Set Tex_UseMakefile to 0 if you want to ignore the presence of a Makefile 
" when deciding how to compile
TexLet g:Tex_UseMakefile = 1

" }}}
" ------------------------------------------------------------------------------ 


However, it turned out that there is nothing happened, every time as I used '\ll' to compile, at the bottom of the mvim shown "Ran latex 1 time(s)". And there was nothing occurred except a blank .pdf file.

Can anyone help me out?

Thank you very much,
Liang

[Vim-latex-devel] [PATCH] imaps.vim: make IMAP undoable

[Bodo G. <ma...@bo...>]

Hi,

It may happen that something (possibly quite long) inserted by IMAP was
not desired. Either because one mistyped or because the LHS pattern
was supposed to stay as is. In the second case one could avoid this by
typing the characters in a way that does not trigger IMAP. But this is quite
inconvenient.
So one could think, just doing <Esc>ua would do the trick. But no, this
often undoes a lot of previously written text and is thus not usable.
The only other solution is to manually delete all the insertions from
IMAP and try again.
Because of this annoying behaviour, some people even disable IMAP
completely, although I feel it is a vital part of vim-latex and is
really helpful especially for those longer replacement texts.

So in order to circumvent the described problem, I modified the
imaps.vim script and inserted an undo point "^Gu" before doing any IMAP
replacements. I'm not sure whether this is the best way to do it or if
the insert of a:char could make new problems with abbreviations. But
please take a look at the appended patch.

Also just fyi, I'm using the following, to make undoing easily possible
in input mode:

imap <Undo> <Esc>ua

best regards,
Bodo

PS:
is there a reason, that the following patch is not applied?

https://sourceforge.net/tracker/?func=detail&aid=3057689&group_id=52322&atid=466458

[Vim-latex-devel] reference/citation completion returns to wrong window

[Jonas D. <di...@gm...>]

Hi,

I usually have two windows open (project plugin and main text). When I
do a F9 completion (ref/cite), the completed text is erraneously
pasted into the wrong window (the project window).

How do I fix this?

Regards
Jonas

Re: [Vim-latex-devel] shortcite

[Ted P. <te...@te...>]

> What about putting something like
> 
> syn match  texRefZone		'\\shortcite\%(\*\=\)\='
> nextgroup=texRefOption,texCite
> 
> into ~/.vim/after/syntax/tex.vim (or similar on mac)?

That is by far the best solution. I didn't think syntax files were
cumulative, and so I didn't suggest after. I've tried it, and that works
very well.

--Ted

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] shortcite

[Gerd W. <ger...@ma...>]

On 07/09/2012 09:25 AM, Ted Pavlic wrote:
>>> for shortcite (and do something similar for your other options).
>>
>> I actually do not want to go this way. When tex.vim gets updated, I have
>> to copy it over again, patch in my stuff again etc. Thus I hope for
>> finding a way to do it locally as in an extra file that extends the
>> already existing tex.vim.
>
> Okay, fine, then add something like:
>
> au BufWinEnter *.tex let w:m1=matchadd('texRefZone', '\\shortcite', -1)
>
> To your .vimrc for each citation that you'd like to add.
>
What about putting something like

syn match  texRefZone		'\\shortcite\%(\*\=\)\='
nextgroup=texRefOption,texCite

into ~/.vim/after/syntax/tex.vim (or similar on mac)?


Gerd

Re: [Vim-latex-devel] shortcite

[Ted P. <te...@te...>]

>> for shortcite (and do something similar for your other options).
> 
> I actually do not want to go this way. When tex.vim gets updated, I have
> to copy it over again, patch in my stuff again etc. Thus I hope for
> finding a way to do it locally as in an extra file that extends the
> already existing tex.vim.

Okay, fine, then add something like:

au BufWinEnter *.tex let w:m1=matchadd('texRefZone', '\\shortcite', -1)

To your .vimrc for each citation that you'd like to add.

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] shortcite

[Ted P. <te...@te...>]

Niels --

> I don't speak about F9. That doesn't really work for me. The application
> (Papers2) I am using for creating my Bibtex-files doesn't seem to write
> clean enough Bibtex for the plugin, but that's not that much of a
> problem for me.

	Hm. I have a feeling that's not actually what the problem is, but it
sounds like it would be a moot point anyway.

> Ok, I see. Syntax highlighting is my problem. Then I know where to look
> (and have to find out how I extend that locally)

	Well, on my machine, the important file is located in:

/usr/share/vim/vim73/syntax/tex.vim

On your Mac, the tex.vim syntax file will be located under the "syntax"
folder of wherever your Vimfiles are. Inside Vim, you can try:

:echo $VIMRUNTIME

to see where to start looking for the "syntax" folder.

	You then could try copying "tex.vim" into your own ~/.vim/syntax folder
(which I *think* (??) will take precedence over the system one). You can
then edit it and search for "cite". You should find a line like:

syn match  texRefZone		'\\cite\%([tp]\*\=\)\='
nextgroup=texRefOption,texCite

which matches \cite, \citet, and \citep. There are several options. The
simplest is probably to try adding a similar line like:

syn match  texRefZone		'\\shortcite\%(\*\=\)\='
nextgroup=texRefOption,texCite

for shortcite (and do something similar for your other options).

>> [ by the way, I use natbib, which gives me \citep, \citet, \citeauthor,
>> \citeyear, and much more... and it makes it much easier to switch from
>> Harvard-style to numbered citations right from within the TeX body ]
> 
> I use something where I used chicago as a base because it is nearer to
> the cite-style I need for what my professor wants from me in terms of
> citation style.

	Well, natbib is completely compatible with the chicago BST style. It's
just a different set of macros that provides me with some nice features,
especially when I hop across journals that have very different editorial
conventions. Anyway, another moot point.

	Best --
	Ted


> Niels
> 
>> On 06/27/2012 10:53 AM, Niels Kobschätzki wrote:
>>> Hi,
>>>
>>> for citations I am using the chicago-style which offers more
>>> cite-commands than just \cite. I use fairly often \shortcite. Is there a
>>> way to give shortcite the same functionality as cite?
>>>
>>> Niels
>>>
>>> ------------------------------------------------------------------------------
>>>
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond.
>>> Discussions
>>> will include endpoint security, mobile security and the latest in
>>> malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>> _______________________________________________
>>> Vim-latex-devel mailing list
>>> Vim...@li...
>>> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
>>>
>>
>> -- 
>> Ted Pavlic <te...@te...>

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] shortcite

[Ted P. <te...@te...>]

Niels --

	What functionality are you speaking of in particular?

	For example, the F9 completion for citations will work in any macro
that contains "cite" in it. So if you do

\shortcite{

and then hit F9, you'll get the same completion window as you'd see from
doing a simple \cite.

	Or are you more interested in improving the syntax highlighting? Syntax
highlighting of TeX files is actually handled by syntax/tex.vim that is
distributed with Vim. So that's outside of the suite.

	So what's missing in your case?

[ by the way, I use natbib, which gives me \citep, \citet, \citeauthor,
\citeyear, and much more... and it makes it much easier to switch from
Harvard-style to numbered citations right from within the TeX body ]

	--Ted

On 06/27/2012 10:53 AM, Niels Kobschätzki wrote:
> Hi,
> 
> for citations I am using the chicago-style which offers more 
> cite-commands than just \cite. I use fairly often \shortcite. Is there a 
> way to give shortcite the same functionality as cite?
> 
> Niels
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel
> 

-- 
Ted Pavlic <te...@te...>

Re: [Vim-latex-devel] [PATCH] indent: Fix de-indentation of \]

[Ted P. <te...@te...>]

Applied. Thanks!

--Ted

On Fri, Jul 6, 2012 at 12:35 PM, Sebastian Ullrich <se...@nu...> wrote:
> '[' should not be escaped inside regex collections. \[ was being
> indented, but not \[.
> ---
>  indent/tex.vim | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/indent/tex.vim b/indent/tex.vim
> index b92d342..95865de 100644
> --- a/indent/tex.vim
> +++ b/indent/tex.vim
> @@ -240,7 +240,7 @@ function GetTeXIndent()
>          endif
>        " Remove a 'shiftwidth' after a "}" or "]" while there are not "{" and "["
>        " before them. \m for magic
> -        if cline =~ '\m^\(\([^\[]*\]\)\|\([^{]*}\)\)'
> +        if cline =~ '\m^\(\([^[]*\]\)\|\([^{]*}\)\)'
>              let ind = ind - &sw
>          endif
>      endif
> --
> 1.7.11.1
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Vim-latex-devel mailing list
> Vim...@li...
> https://lists.sourceforge.net/lists/listinfo/vim-latex-devel



-- 
Ted Pavlic <te...@te...>

[Vim-latex-devel] [PATCH] indent: Fix de-indentation of \]

[Sebastian U. <se...@nu...>]

'[' should not be escaped inside regex collections. \[ was being
indented, but not \[.
---
 indent/tex.vim | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/indent/tex.vim b/indent/tex.vim
index b92d342..95865de 100644
--- a/indent/tex.vim
+++ b/indent/tex.vim
@@ -240,7 +240,7 @@ function GetTeXIndent()
         endif
       " Remove a 'shiftwidth' after a "}" or "]" while there are not "{" and "["
       " before them. \m for magic
-        if cline =~ '\m^\(\([^\[]*\]\)\|\([^{]*}\)\)'
+        if cline =~ '\m^\(\([^[]*\]\)\|\([^{]*}\)\)'
             let ind = ind - &sw
         endif
     endif
-- 
1.7.11.1