Bugs item #3223395, was opened at 2011-03-18 19:43
Message generated for change (Tracker Item Submitted) made by tukss
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=466456&aid=3223395&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: Philipp Edelmann (tukss)
Assigned to: Nobody/Anonymous (nobody)
Summary: Escaping in Tex_pack_updateall

Initial Comment:
The bug occurs when opening a TeX file which is not the .latexmain file in a 
directory whose path contains an asterisk or any other glob character which 
happens to expand to multiple paths.

The code in question is from packages.vim:
        if expand('%:p') != fname
                call Tex_Debug(':Tex_pack_updateall: sview 
'.Tex_EscapeSpaces(fname), 'pack')
                exe 'sview '.Tex_EscapeSpaces(fname)
        else
                call Tex_Debug(':Tex_pack_updateall: split', 'pack')
                split
        endif
                
        call Tex_ScanForPackages()
        q

The call to sview fails because Tex_EscapeSpaces doesn't escape the asterisk in 
the path. The error in verbose mode is:
    Error detected while processing function Tex_pack_updateall:
    line   29:
    E77: Too many file names

Because splitting the buffer fails, the following call to q closes the original 
buffer and therefore the instance of vim which was just opened. The user only 
sees vim close immediately with no error message.

A solution to this problem is to use fnameescape instead of Tex_EscapeSpaces 
because it properly escapes all characters not only spaces.

I think this problem could also occur at other places where Tex_EscapeSpaces is 
used in conjunction with asterisks in the path name. Maybe Tex_EscapeSpaces 
should use fnameescape internally. The problem might be that * expansion might 
be desired in certain places. I don't know if that is the case anywhere in 
latexsuite.

I attached a patch that fixes the problem for me.

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

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

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Vim-latex-devel mailing list
Vim-latex-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/vim-latex-devel

Reply via email to