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

Re: [Vim-latex-devel] which github repository is more official?

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

Peng -

git is git regardless of the host. Moreover, sf provides much more than
just a repo to the latex suite. How has sf caused you trouble using the
official git repo hosted there?

Or are you just saying it would be easier for you to submit pull requests
rather than patches? Note that git itself is maintained via patches posted
to a mailing list rather than pull requests via github. Or do you just like
that LinkedIn provides a module for showing off your latex suite
contributions?

Why don't you just setup a clone on github that automatically pulls from
the sf git repo?

Or are you saying that there are already so many clones by people not
accustomed to anything but pull requests that the latex suite is getting
fragmented? (despite all the documentation hooks back to sf)

--Ted

--
Sent from the mobile device of Ted Pavlic
Please excuse typos, swypos, or very brief responses
On Jun 30, 2012 2:30 PM, "Peng Yu" <pen...@gm...> wrote:

> Hi,
>
> I have the feeling that sf sucks. Many developers has already been
> setting up github repositories. But it is not clear to me which one is
> the most official. I think that it is time to migrate the development
> to github and maintain a central repository there. Is there one that
> is the most official in giihub?
>
> https://github.com/jcf/vim-latex
>
> --
> Regards,
> Peng
>
>
> ------------------------------------------------------------------------------
> 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
>

[Vim-latex-devel] which github repository is more official?

[Peng Yu <pen...@gm...>]

Hi,

I have the feeling that sf sucks. Many developers has already been
setting up github repositories. But it is not clear to me which one is
the most official. I think that it is time to migrate the development
to github and maintain a central repository there. Is there one that
is the most official in giihub?

https://github.com/jcf/vim-latex

-- 
Regards,
Peng

[Vim-latex-devel] Disable short cut for things like ::

[Peng Yu <pen...@gm...>]

Hi,

I feel that the short cut defined in vim latex is in convenient. I'd
like to disable all keyboard shortcut like :: (which is changed to
\ldots). Is there a way to do?

-- 
Regards,
Peng

[Vim-latex-devel] shortcite

[Niels K. <ni...@ko...>]

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

Re: [Vim-latex-devel] Auto completion of references

[Tohiko L. <toh...@gm...>]

Yes, adding -_ to the iskeyword variable worked,
BTW, <C,n> and F9 show too different lists.

Thank you very much

Re: [Vim-latex-devel] Auto completion of references

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

Hi,

try (maybe with some quotes)

iskeyword+=-_


By the way, pressing <F9> after "\ref{eq:" should also work!?


Regards
Gerd


On 06/18/2012 11:27 PM, Tohiko Looka wrote:
> Greetings,
>
> I included the following line in my tex.vim file
> set iskeyword+=:
> And now I can type "\ref{eqn:" and then press <C-n> and a list of
> labels will show up
> However, I noticed that if I have an symbol in my label (like - or _ )
> then only the label up
> to that symbol shows up in the list.
>
> Any ideas on how to fix this?
> Thanks

[Vim-latex-devel] Auto completion of references

[Tohiko L. <toh...@gm...>]

Greetings,

I included the following line in my tex.vim file
set iskeyword+=:
And now I can type "\ref{eqn:" and then press <C-n> and a list of
labels will show up
However, I noticed that if I have an symbol in my label (like - or _ )
then only the label up
to that symbol shows up in the list.

Any ideas on how to fix this?
Thanks

[Vim-latex-devel] Indentation problem

[Tohiko L. <toh...@gm...>]

Greetings,
I've recently started using Vim-Latex (and Vim for that matter) and
I'm loving it.
One problem though that I wish would be fixed is the indentation.

I usually add a few spaces for every environment I'm in and using Vim
smart indent everything works beautifully
However, if I type "equation" on an empty indented line and then hit
F5, VIM-Latex inserts the equation environment unindented

Is there a way to fix this?
Thanks

Re: [Vim-latex-devel] Makefile

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

Raniere --

    See:

:help Tex_UseMakefile

By default, if vim-latex finds a Makefile, it will set makeprg to:

make pdf

So if your Makefile doesn't have a pdf target, it will fail. You can
simply define a pdf target that depends upon the target you actually
care about (or rename the target you care about "pdf").

    Alternatively, you can set g:Tex_UseMakefile to 0 and LaTeX-suite
will set makeprg to whatever you have in:

g:Tex_CompileRule_pdf

which you can read about in:

:help Tex_CompileRule_format

For example, in your .vimrc you can put:

let g:Tex_UseMakefile = 0
let g:Tex_CompileRule_pdf = "make"

which will make latex-suite call simply "make" when you use "\ll".

    Having said that, are you familiar with using latexmain files? See:

:help latex-master-file

By creating a latexmain file (e.g., "mymainfile.latexmain" or
"mymainfile.tex.latexmain") in your working directory (which you can
add to your git repo), you tell vim-latex that regardless of which
file you're editing, you want it to run pdflatex (or latex) on a
particular main file in the directory. Moreover, the contents of the
latexmain file help to setup project-specific configuration parameters
for the directory. That way you don't have to change your whole .vimrc
for a single directory. (you also don't have to stick to the
"latexmain" extension; see the help I referenced above for more
details)

   Does that help?
   --Ted

On Thu, May 31, 2012 at 9:41 PM, Raniere Gaia Silva <r.g...@gm...> wrote:
> Hello all,
> I'm working in some independent tex files at the same directory and
> this directory is sharing with git.
> I would like to have a easy way to compile all tex file to pdf so I
> write a Makefile.
> Unfortunate, the vim-latex has some problem with the  Makefile and I'm
> getting the message
>
> make: *** No rule to make target `pdf'.  Stop.
>
> Can anyone say if there is a way to fix it?
> Current, I remove the Makefile and write a bash script.
>
> Thanks,
> Raniere
>
> ------------------------------------------------------------------------------
> 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] Makefile

[Raniere G. S. <r.g...@gm...>]

Hello all,
I'm working in some independent tex files at the same directory and
this directory is sharing with git.
I would like to have a easy way to compile all tex file to pdf so I
write a Makefile.
Unfortunate, the vim-latex has some problem with the  Makefile and I'm
getting the message

make: *** No rule to make target `pdf'.  Stop.

Can anyone say if there is a way to fix it?
Current, I remove the Makefile and write a bash script.

Thanks,
Raniere

Re: [Vim-latex-devel] Forward search with okular

[Filip K. <ka...@fz...>]

Hello Peter,

  I think the problem is resolved now. The clue was in the line:
let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode $*'

instead of which I had

let g:Tex_CompileRule_pdf = "/usr/local/bin/latexmk -e '$pdflatex=q/pdflatex -interaction=nonstopmode -file-line-error -halt-on-error -synctex=1/' -pdf -bibtex $*"

coming from one of your posts. I think the synctex option was missing 
most. Now the forward search works.

Though, I had one more problem: both the forward and backward searches 
always launched a new instance of viewer / gvim. To resolve this, I have 
searched some older mailing list archives and modified my .vimrc lines as 
follows:

let g:Tex_ViewRule_pdf = 'okular --unique'
let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode $* -inverse-search "gvim --servername GVIM --remote +\%l \%f"'

These options enforce the use of already running okular / gvim, hopefully 
this will help somebody. I wonder why these options are not included in 
the latest vim-latex version which I had installed. The only detail still 
remaining is that the windows don't get the KDE focus, I am not sure this 
has a solution.

 		Filip


> Hi Filip,
>
> If you have something like this i your vimrc
>
> set grepprg=grep\ -nH\ $*
> let g:tex_flavor='latex'
> let g:Tex_DefaultTargetFormat = 'pdf'
> let g:Tex_ViewRule_pdf = 'okular'
> let g:Tex_CompileRule_pdf = 'pdflatex --synctex=1 -interaction=nonstopmode $*'
>
> and have a ...synctex.gz (this is the file with all information needed
> for forward searching) file in your project folder after compiling the
> document,
> I have no clue why forward search would not work.
>
> I use Okular version 0.14.2.
>
> Sorry if I cant help you more.
>
> Peter
>
> On Thu, May 17, 2012 at 4:46 PM, Filip Kadlec <ka...@fz...> wrote:
>> Dear Peter,
>>
>>  thanks so much for your description. I have updated vim-latex to the latest
>> version; installed and activated pathogen, un-installed the distribution
>> system-wide vim-latex, and then installed the latest vim-latex:
>>
>> ~>cd ~/.vim/bundle
>>
>> ~/.vim/bundle> git clone
>> git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex
>> Cloning into vim-latex...
>> remote: Counting objects: 4161, done.
>> remote: Compressing objects: 100% (1469/1469), done.
>> remote: Total 4161 (delta 2718), reused 4045 (delta 2665)
>> Receiving objects: 100% (4161/4161), 1003.90 KiB | 774 KiB/s, done.
>> Resolving deltas: 100% (2718/2718), done.
>>
>> After restarting vim, the scripts appear to be active; :scriptnames
>> provides:
>>
>> ...
>>  18: /home/kadlecf/.vim/bundle/vim-latex/plugin/SyntaxFolds.vim
>>  19: /home/kadlecf/.vim/bundle/vim-latex/plugin/filebrowser.vim
>>  20: /home/kadlecf/.vim/bundle/vim-latex/plugin/imaps.vim
>>  21: /home/kadlecf/.vim/bundle/vim-latex/plugin/libList.vim
>>  22: /home/kadlecf/.vim/bundle/vim-latex/plugin/remoteOpen.vim
>> ...
>>
>> Also, \ll and \lv work as expected. Alas, \ls still does not work. It only
>> states:
>> :call Tex_ForwardSearchLaTeX()
>>
>> but the okular window does not open. The situation is the same if I source
>> the files you sent in the previous post. Not sure if I am not doing
>> something wrong...
>>
>>        With best regards,
>>
>>                        Filip
>>
>>
>> On Thu, 17 May 2012, Peter Vasil wrote:
>>>
>>> On Thu, May 17, 2012 at 1:00 PM, Filip Kadlec <ka...@fz...> wrote:
>>>>
>>>> Peter,
>>>>  thanks for your reply.
>>>>
>>>> Having sourced the lines below into vim, there is some progress. Now,
>>>> when I
>>>> type \ls , three new okular instances will open; one contains the
>>>> compiled
>>>> file while the other two are empty. Each provides an error box, like
>>>> this:
>>>>
>>>> Could not open /home/kadlecf/Documents/path/file.tex            and
>>>> Could not open /home/kadlecf/Documents/path/40
>>>>
>>>> where 40 corresponds to the current line in the .tex source.
>>>
>>> This could be the thing with the old version of vim-latex. I just can
>>> say for the latest vim-latex version from the git-repository that
>>> forward search works because I made some fixes regarding okular which
>>> then went into the vim-latex source. Which vim-latex version do you
>>> use?
>>>
>>>>
>>>> Concerning the option "-synctex=1", sorry for my ignorance, but I don't
>>>> know
>>>> where to set it. What exactly does it influence?
>>>
>>> If you have put all lines in your vimrc which I posted in my previous
>>> email, then the synctex option is already there. This option generates
>>> the necessary data for forward search. Without this option forward
>>> search doesn't work and not only in vim-latex. All latex editors use
>>> the synctex option for forward search.
>>>
>>>>
>>>> Also, I would be ready to install the latest version using the
>>>> git-repository, but I do not know how to proceed...
>>>
>>> I use vim-pathogen [1] for managing my vim plugins. Simply clone the
>>> vim-latex repository into the bundle directory.
>>> If you read [1] then you will probably know what I mean with the
>>> bundle directory.
>>> The clone command is:
>>> git clone git://vim-latex.git.sourceforge.net/gitroot/vim-latex/vim-latex
>>>
>>> You could also clone the repoository and copy all files manually to
>>> ~/.vim/ folder. There is also some help on the vim-latex download page
>>> [2], where to put all files. But the description is without the
>>> pathogen plugin.
>>>
>>> [1]: http://www.vim.org/scripts/script.php?script_id=2332
>>> [2]: http://vim-latex.sourceforge.net/index.php?subject=download
>>>
>>>
>>> Hope this helps,
>>> Peter
>>>
>>>
>>>>
>>>>  Filip
>>>>
>>>>
>>>> On Thu, 17 May 2012, Peter Vasil wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I use vim-latex with okular and forward search works like a charm.
>>>>>
>>>>> I have this in my .vimrc
>>>>>
>>>>> set grepprg=grep\ -nH\ $*
>>>>> let g:tex_flavor='latex'
>>>>> let g:Tex_DefaultTargetFormat = 'pdf'
>>>>> let g:Tex_ViewRule_pdf = 'okular'
>>>>> let g:Tex_CompileRule_pdf = "/usr/local/bin/latexmk -e
>>>>> '$pdflatex=q/pdflatex -interaction=nonstopmode -file-line-error
>>>>> -halt-on-error -synctex=1/' -pdf -bibtex $*"
>>>>>
>>>>> I use latexmk for compilation and you have to set "-synctex=1"
>>>>> somewhere in the compile rules.
>>>>>
>>>>> Also, did you try to use the latest vim-latex from the git repository?
>>>>> I dont know which version is in the OpenSUSE repositories but okular
>>>>> forward search is working with the latest vim-latex version from the
>>>>> git repository.
>>>>>
>>>>> Peter
>>>>>
>>>>>
>>>>> On Thu, May 17, 2012 at 11:40 AM, Filip Kadlec <ka...@fz...> wrote:
>>>>>>
>>>>>>
>>>>>> Hello,
>>>>>>  I would appreciate if someone could help me to resolve this problem.
>>>>>>
>>>>>> I have installed vim-latex from the OpenSuSE distribution. Most of its
>>>>>> features work correctly. \ll will start latex translation, and \lv
>>>>>> launches the viewer. However, \ls , instead of launching the forward
>>>>>> search, does nothing. I have tried to make it work by entering, in vim:
>>>>>>
>>>>>> :let g:Tex_CompileRule_dvi = 'let'atex -src-specials
>>>>>> -interaction=nonstopmode $*' '
>>>>>>
>>>>>> and
>>>>>>
>>>>>> TCTarget dvi
>>>>>>
>>>>>> as found in the FAQ. However, this does not help. I understand from the
>>>>>> mailing list there were some quite recent patches to this behavior,
>>>>>> also
>>>>>> in order to get a single instance of okular, but I am not sure how it
>>>>>> is
>>>>>> best to proceed.
>>>>>>
>>>>>>         Thanks in advance for your assistance.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------------
>>>>>> 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
>>>>
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> 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
>>
>>
>> ------------------------------------------------------------------------------
>> 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

Re: [Vim-latex-devel] Forward search in windows with vim and sumatrapdf?

[Julien C. <jul...@gm...>]

Hi Jorge

As the co-author of the patch a while ago, I unfortunately can tell
you that, if there were a way in vim-latex already, Manuel and I
wouldn't have bothered writing it ;-)

The patch is very short, only adding an extra case-check to allow for
sumatrapdf along YAP and the other viewers
However, it is 3 years old, so I don't know if it's still working --
and I've stopped using vim-latex (let alone windows) a while ago.
Since vim-latex is entirely scripted, backing up vimlatex, applying
the patch, trying it and reverting if needs be is very easy -- nothing
to recompile or reinstall anywhere, just use your local vim folder, so
there's really nothing to be afraid of: just make a copy of your vim
folder before patching.


All the best,


Julien

On Sun, May 27, 2012 at 12:36 AM, jorge rodrigues <sk...@gm...> wrote:
> Hi
>
> I saw some recent messages about setting up forward search with okular
> for linux.
> I am using vim-latex in windows using sumatra pdf as the viewer.
> I can do inverse search (that is I click the pdf and it opens vim in
> the location),
> but I don't know how to setup forward search.
>
> Using google I found the page
> http://william.famille-blum.org/blog/static.php?page=static081010-000413
>
> that suggests using a patch against vim-latex.
>
> I don't fell comfortable using patches, so I would like to know if it
> this is already in vim-latex
> or if there exits a way of doing this in vim-latex without using the
> mentioned patch.
>
> thanks!
>
> ------------------------------------------------------------------------------
> 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] Spell-check not working with latex-suite

[Jeffrey L. <jef...@uc...>]

I also have the vim-latex suite installed and my spell check does not work. 
Intentionally misspelled works are not caught.

Yes, I have en_us as the spelllang and have turned on spell check. 

Did anyone find a solution to this?

[Vim-latex-devel] Forward search in windows with vim and sumatrapdf?

[jorge r. <sk...@gm...>]

Hi

I saw some recent messages about setting up forward search with okular
for linux.
I am using vim-latex in windows using sumatra pdf as the viewer.
I can do inverse search (that is I click the pdf and it opens vim in
the location),
but I don't know how to setup forward search.

Using google I found the page
http://william.famille-blum.org/blog/static.php?page=static081010-000413

that suggests using a patch against vim-latex.

I don't fell comfortable using patches, so I would like to know if it
this is already in vim-latex
or if there exits a way of doing this in vim-latex without using the
mentioned patch.

thanks!

[Vim-latex-devel] [ vim-latex-Patches-3529927 ] \iota IMAP is missing from ftplugin/latex-suite/main.vim

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

Patches item #3529927, was opened at 2012-05-26 02:42
Message generated for change (Tracker Item Submitted) made by donbex
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3529927&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: Alessandro Pezzoni (donbex)
Assigned to: Nobody/Anonymous (nobody)
Summary: \iota IMAP is missing from ftplugin/latex-suite/main.vim

Initial Comment:
As per summary, the IMAP for \iota is missing. I am attaching a patch which fixes this (some time ago I tried submitting it to the mailing list as suggested on the vim-latex website, to no avail).

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

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

[Vim-latex-devel] [ vim-latex-Patches-3057689 ] IMAP with mulitbyte lhs

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

Patches item #3057689, was opened at 2010-09-01 12:23
Message generated for change (Comment added) made by lux-vim-latex
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3057689&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: LuX (lux-vim-latex)
Assigned to: Nobody/Anonymous (nobody)
Summary: IMAP with mulitbyte lhs

Initial Comment:
The IMAP function, which comes with the latex-suite in the plugin imaps.vim, deals wrongly with multibyte left hand side (so-called lhs). The attached patch fixes this. 

Version number:
imaps.vim 997 2006-03-20 09:45:45Z srinathava $
VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Dec  1 2008)

Example: 
You want to chain IMAP mapping, as follows: 
        call IMAP("\\subset", "⊂", "")
        call IMAP("⊂eq", "⊆", "")
Type "1234\subset", you see "1234⊂" (good). But if you add "eq", you see "12⊆" (bad) instead of "1234⊆".

Description:
The attached patch adds to imaps.vim two functions called s:MultiByteStrlen and s:MultiByteStrpart, analogous to Vim's functions strlen and strpart but which deal with strings character per character instead of byte per byte. Every call to strlen and strpart is then replaced by a call to these variants, and as far as I can see it solved the problem. 

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

>Comment By: LuX (lux-vim-latex)
Date: 2012-05-25 16:54

Message:
*Bump*

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

Comment By: LuX (lux-vim-latex)
Date: 2010-11-14 13:40

Message:
> tmaas wrote:
> This change looks wrong:
> @@ -194,7 +194,7 @@
[..]
> Are you sure this is correct? I guess the new line needs to be:
> + let char = s:MultiByteStrpart(a:lhs,s:MultiByteStrlen(a:lhs)-1)

Yes, you're right, of course. Sorry about that. 

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

Comment By: Till Maas (tmaas)
Date: 2010-10-28 13:37

Message:
This change looks wrong:
@@ -194,7 +194,7 @@
 "
 " Added mainly for debugging purposes, but maybe worth keeping.
 function! IMAP_list(lhs)
-	let char = a:lhs[strlen(a:lhs)-1]
+ 	let lastLHSChar = s:MultiByteStrpart(a:lhs,s:MultiByteStrlen(a:lhs)-1)
 	let charHash = s:Hash(char)
 	if exists("s:LHS_" . &ft ."_". charHash) && a:lhs =~
s:LHS_{&ft}_{charHash}
 		let ft = &ft

Are you sure this is correct? I guess the new line needs to be:
+ 	let char = s:MultiByteStrpart(a:lhs,s:MultiByteStrlen(a:lhs)-1)

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

Comment By: LuX (lux-vim-latex)
Date: 2010-09-06 10:53

Message:
Sorry, it appeared to me that the previously attached patch was not correct
(I did not apply 'diff' to the right files). But most of all the strategy
of changing every call to strlen and strpart by my s:MultiByte* variants is
not good: in some case, it is really strpart or strlen which must be used.


Example: 
The following command appears 3 times in imaps.vim: 
        strpart(getline(".", 0, col(".")-1)
What is expected is the content of the current line before the cursor.
Since col(".") returns the number of bytes, not of characters, until the
first byte (not the last one) of the character under the cursor, col(".")-1
is just the number of bytes in the current line before the cursor. Thus
strpart will return what expected, and MultiByteStrpart will not (not
always).

So this time I have looked carefully at every place in imps.vim where
strlen and strpart were used, and I changed them to there
s:MuliByte-variants ONLY when I was sure that it was needed (I left strlen
and strpart also when it did not make any difference to use them or
s:MultiByte*, for example when they are called only to test wether or not a
string is empty). 

The result of this better strategy is the attached patch.

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

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

[Vim-latex-devel] [ vim-latex-Patches-3529836 ] Multiple \begin or \end in the same line

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

Patches item #3529836, was opened at 2012-05-25 13:15
Message generated for change (Comment added) made by tpavlic
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3529836&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: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Multiple \begin or \end in the same line

Initial Comment:
The indentation does not work if multiple \begin and \end are at the same line, here is a modified tex.vim indent file which should fix the problem.

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

Comment By: Ted Pavlic (tpavlic)
Date: 2012-05-25 14:15

Message:
Okay. Applied, but you didn't upload a patch, and I cannot infer any
identity information for you. So I didn't have anyone to credit in the
commit messages. 

I also split your contributions into two patches -- one that got rid of
some extra line spaces in indent/tex.vim, and the other that adjusted
indenting. I did not go through the code you added with a fine-toothed
comb, but I did a few spot checks in sample TeX files, and it seemed to
work (better than before too). So hopefully nothing terrible has been
broken.

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

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

[Vim-latex-devel] [ vim-latex-Patches-3529836 ] Multiple \begin or \end in the same line

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

Patches item #3529836, was opened at 2012-05-25 13:15
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3529836&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: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Multiple \begin or \end in the same line

Initial Comment:
The indentation does not work if multiple \begin and \end are at the same line, here is a modified tex.vim indent file which should fix the problem.

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

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

[Vim-latex-devel] [ vim-latex-Patches-3529763 ] Multiple \begin or \end in the same line

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

Patches item #3529763, was opened at 2012-05-25 07:02
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466458&aid=3529763&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: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Multiple \begin or \end in the same line

Initial Comment:
The indentation does not work if multiple \begin and \end are at the same line, here is a modified tex.vim indent file which should fix the problem.

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

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

Re: [Vim-latex-devel] pdflatex -output-dirctory and Tex_ViewRule

[Marijan S. <mar...@gm...>]

On Thu, May 24, 2012 at 3:52 PM, Ted Pavlic <te...@te...> wrote:

> > let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/$*'
> >
> > and I tried hardcoding path of produced pdf file like this:
> > let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/seminar.pdf'
>
> The hard-coded line works fine for me. Otherwise,
>
> let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/$*.pdf'
>
> works fine for me.
>
> If things aren't working fine for you, then while evince is running
> and telling you that the path is bad, can you jump into the terminal
> and do:
>
> ps auxww|grep evince
>
> and see what evince command is being called? That should give a hint
> as to what the unique problem is on your system.
>
> --Ted
>
>
So here is the output when i use:
let g:Tex_ViewRuleComplete_pdf = 'zathura /tmp/$*.pdf'

zathura /tmp/ /home/mesx/temp/2012_05_pero_PaaS/seminar.pdf

and here is the output afrer hardcoding
let g:Tex_ViewRuleComplete_pdf = 'zathura /tmp/seminar.pdf'

zathura /tmp/ /home/mesx/temp/2012_05_pero_PaaS/seminar.pdf


Dont know is it relevant or not, but I use Vundle for managing vim plugins.
and I installed vim-latex using this line in my .vimrc:
 Bundle 'LaTeX-Suite-aka-Vim-LaTeX'



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



-- 
http://www.google.com/profiles/marijan.svalina

[Vim-latex-devel] [ vim-latex-Bugs-3529684 ] Sometimes doesn't unindent with a \end

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

Bugs item #3529684, was opened at 2012-05-25 01:02
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3529684&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: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: Sometimes doesn't unindent with a \end

Initial Comment:
For a file like
\begin{test}
foo\end{test}
bar
After the indent, it should be like
\begin{test}
    foo\end{test}
bar
But when I use the automatic indent, it becomes
\begin{ŧest}
    foo\end{test}
    bar
After some experiment, I found out that \end were ignored every time there is other things that spaces and tabs before them on the line.
Looking at the source code of the file indent/tex.vim, I found that it was about the line 180 that reads
     if cline =~ '^\s*\\end' && cline !~ g:tex_noindent_env
I changed it on my computer to
     if cline =~ '^\s*\\end' && cline !~ g:tex_noindent_env
And it fixed the bug

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

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

Re: [Vim-latex-devel] pdflatex -output-dirctory and Tex_ViewRule

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

> let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/$*'
>
> and I tried hardcoding path of produced pdf file like this:
> let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/seminar.pdf'

The hard-coded line works fine for me. Otherwise,

let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/$*.pdf'

works fine for me.

If things aren't working fine for you, then while evince is running
and telling you that the path is bad, can you jump into the terminal
and do:

ps auxww|grep evince

and see what evince command is being called? That should give a hint
as to what the unique problem is on your system.

--Ted

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

Re: [Vim-latex-devel] pdflatex -output-dirctory and Tex_ViewRule

[Marijan S. <mar...@gm...>]

let g:Tex_ViewRule_pdf = 'evince /tmp/$*'
" let g:Tex_ViewRuleComplete_pdf = 'zathura /tmp/$*'
let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/$*'

and I tried hardcoding path of produced pdf file like this:
let g:Tex_ViewRuleComplete_pdf = 'evince /tmp/seminar.pdf'

But every time it fails, because pdf application receives worng path.
One that points at root folder of .tex files.

Ty, for trying :)


On Wed, May 23, 2012 at 10:10 PM, Ted Pavlic <te...@te...> wrote:

> Yes, but you did it wrong in your first e-mail. Can you go back and try
> it the right way? (i.e., with the file name *after* the path?)
>
> --Ted
>
> On 05/23/2012 04:03 PM, Marijan Svalina wrote:
> > Nope, I already try that and write about it in first mail.
> >
> > On Wed, May 23, 2012 at 7:22 PM, Ted Pavlic <te...@te...
> > <mailto:te...@te...>> wrote:
> >
> >     Hm. I wonder if a space is being added.
> >
> >     Have you tried using:
> >
> >     Tex_ViewRuleComplete_format
> >
> >     instead? See:
> >
> >     :help Tex_ViewRuleComplete_format
> >
> >     I have a feeling that that will be your answer.
> >
> >     Best --
> >     Ted
> >
> >
> >
> >     On Wed, May 23, 2012 at 1:16 PM, Marijan Svalina
> >     <mar...@gm... <mailto:mar...@gm...>>
> wrote:
> >     > Just tried that, and also no luck :/
> >     >
> >     >
> >     > On Wed, May 23, 2012 at 7:08 PM, Ted Pavlic <te...@te...
> >     <mailto:te...@te...>> wrote:
> >     >>
> >     >> > let g:Tex_ViewRule_pdf = 'zathura $*/tmp'
> >     >>
> >     >> Do you mean:
> >     >>
> >     >> let g:Tex_ViewRule_pdf = 'zathura /tmp/$*'
> >     >>
> >     >> ? Did you try that?
> >     >>
> >     >> --Ted
> >     >>
> >     >> --
> >     >> Ted Pavlic <te...@te... <mailto:te...@te...>>
> >     >
> >     >
> >     >
> >     >
> >     > --
> >     > http://www.google.com/profiles/marijan.svalina
> >
> >
> >
> >     --
> >     Ted Pavlic <te...@te... <mailto:te...@te...>>
> >
> >
> >
> >
> > --
> > http://www.google.com/profiles/marijan.svalina
>
> --
> Ted Pavlic <te...@te...>
>



-- 
http://www.google.com/profiles/marijan.svalina

Re: [Vim-latex-devel] pdflatex -output-dirctory and Tex_ViewRule

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

Yes, but you did it wrong in your first e-mail. Can you go back and try
it the right way? (i.e., with the file name *after* the path?)

--Ted

On 05/23/2012 04:03 PM, Marijan Svalina wrote:
> Nope, I already try that and write about it in first mail.
> 
> On Wed, May 23, 2012 at 7:22 PM, Ted Pavlic <te...@te...
> <mailto:te...@te...>> wrote:
> 
>     Hm. I wonder if a space is being added.
> 
>     Have you tried using:
> 
>     Tex_ViewRuleComplete_format
> 
>     instead? See:
> 
>     :help Tex_ViewRuleComplete_format
> 
>     I have a feeling that that will be your answer.
> 
>     Best --
>     Ted
> 
> 
> 
>     On Wed, May 23, 2012 at 1:16 PM, Marijan Svalina
>     <mar...@gm... <mailto:mar...@gm...>> wrote:
>     > Just tried that, and also no luck :/
>     >
>     >
>     > On Wed, May 23, 2012 at 7:08 PM, Ted Pavlic <te...@te...
>     <mailto:te...@te...>> wrote:
>     >>
>     >> > let g:Tex_ViewRule_pdf = 'zathura $*/tmp'
>     >>
>     >> Do you mean:
>     >>
>     >> let g:Tex_ViewRule_pdf = 'zathura /tmp/$*'
>     >>
>     >> ? Did you try that?
>     >>
>     >> --Ted
>     >>
>     >> --
>     >> Ted Pavlic <te...@te... <mailto:te...@te...>>
>     >
>     >
>     >
>     >
>     > --
>     > http://www.google.com/profiles/marijan.svalina
> 
> 
> 
>     --
>     Ted Pavlic <te...@te... <mailto:te...@te...>>
> 
> 
> 
> 
> -- 
> http://www.google.com/profiles/marijan.svalina

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

Re: [Vim-latex-devel] pdflatex -output-dirctory and Tex_ViewRule

[Marijan S. <mar...@gm...>]

Nope, I already try that and write about it in first mail.

On Wed, May 23, 2012 at 7:22 PM, Ted Pavlic <te...@te...> wrote:

> Hm. I wonder if a space is being added.
>
> Have you tried using:
>
> Tex_ViewRuleComplete_format
>
> instead? See:
>
> :help Tex_ViewRuleComplete_format
>
> I have a feeling that that will be your answer.
>
> Best --
> Ted
>
>
>
> On Wed, May 23, 2012 at 1:16 PM, Marijan Svalina
> <mar...@gm...> wrote:
> > Just tried that, and also no luck :/
> >
> >
> > On Wed, May 23, 2012 at 7:08 PM, Ted Pavlic <te...@te...> wrote:
> >>
> >> > let g:Tex_ViewRule_pdf = 'zathura $*/tmp'
> >>
> >> Do you mean:
> >>
> >> let g:Tex_ViewRule_pdf = 'zathura /tmp/$*'
> >>
> >> ? Did you try that?
> >>
> >> --Ted
> >>
> >> --
> >> Ted Pavlic <te...@te...>
> >
> >
> >
> >
> > --
> > http://www.google.com/profiles/marijan.svalina
>
>
>
> --
> Ted Pavlic <te...@te...>
>



-- 
http://www.google.com/profiles/marijan.svalina