[vimshell] Errors with vimshell for 7.0 and 7.2

[Mark Ebbert]

That was very helpful. I appreciate it.

I have one other question, if you don't mind. I'm pretty comfortable  
with Unix platforms, but I'm always wary of making changes at the  
system level. I want to make this newly compiled version of Vim the  
default from the command line, but I do not want to disturb the  
integrity of the Vim that was built into my system (OS X). Basically,  
I would like to make this new version the default, but be able to  
easily revert in case something ever goes wrong. Do you know the best  
way to do that? I'm thinking symbolic links, but again, I'm wary of  
doing that.

Thanks again for your help!
On Nov 6, 2008, at 11:20 AM, Eugeni Dodonov wrote:

> Basically, -p0 means that the files to be patched are to be found in  
> current directory (if you look into the .patch file, you'll see that  
> the new files start with +++ vim/dir1/dir2/file). -p1 means that one  
> sub-directory should be removed from the path (so the changed that  
> were supposed to go into vim/dir1/dir2/file will go into dir1/dir2/ 
> file). -p2, in the same way, will apply changes to 'dir2/file'.
>
> From man patch:
>        -pnum  or  --strip=num
>           Strip the smallest prefix containing num leading slashes   
> from  each
>           file  name found in the patch file.  A sequence of one or  
> more adja‐
>           cent slashes is counted as a single slash.  This controls   
> how  file
>           names  found  in  the  patch file are treated, in case you  
> keep your
>           files in a different directory than the  person  who   
> sent  out  the
>           patch.  For example, supposing the file name in the patch  
> file was
>
>              /u/howard/src/blurfl/blurfl.c
>
>           setting -p0 gives the entire file name unmodified, -p1 gives
>
>              u/howard/src/blurfl/blurfl.c
>
>           without the leading slash, -p4 gives
>
>              blurfl/blurfl.c
>
>           and  not specifying -p at all just gives you blurfl.c.   
> Whatever you
>           end up with is looked for either in the current   
> directory,  or  the
>           directory specified by the -d option.
>
>
>
> I guess that the 'test.txt' file was used just for testing, so it is  
> not used in the actual compilation. So vimshell will work fine even  
> with this patching error.
>
> On Thu, Nov 6, 2008 at 15:08, Mark Ebbert <me.mark at gmail.com> wrote:
> Thank you for the idea.
>
> I actually did run it from within the vim72 directory. The command I  
> ran was "bzcat ../vimshell_1.0_vim7.2.patch.bz2 | patch -p0"
>
> But I noticed that you used the option "-p1" instead of "-p0," can  
> you explain why? I tried it with "-p1" and it got farther, but ended  
> with:
> ### BEGIN ###
> patching file test.txt
> patch unexpectedly ends in middle of line
> patch unexpectedly ends in middle of line
> ### END ###
>
> I continued to compile vim and vimshell appears to be working. Can  
> you (or anyone else) tell me if anything important is missing since  
> the patch failed at the point described above?
>
> Thank you.
>
> On Nov 6, 2008, at 4:05 AM, Eugeni Dodonov wrote:
>
>> Hi,
>>
>> Try running the patch inside the VIM directory (like vim72):
>>
>> tar xvfj vim-7.2.tar.bz2
>> cd vim72
>> bzcat ../vimshell_1.0_vim7.2.patch.bz2 | patch -p1
>>
>> Or edit the patch, changing the entries from '+++ vim/' to '+++  
>> vim72/'. Like
>> vi vimshell.patch.bz2
>> :%s:+++ vim/:+++ vim72/:g
>>
>> See if it works.
>>
>> On Thu, Nov 6, 2008 at 00:52, Mark Ebbert <me.mark at gmail.com> wrote:
>> I'm having trouble getting vimshell to work on either 7.0 or 7.2.
>>
>> I noticed in the archives that John Greco posted a patch for 7.2 in
>> September, but didn't give any special instructions. So I tried using
>> the regular instructions on the vimshell main page. Here is the error
>> I got:
>>
>> ### BEGIN ###
>> $ bzcat ../vimshell_1.0_vim7.2.patch.bz2 | patch -p0
>> missing header for unified diff at line 3 of patch
>> patching file vim/README_vimshell.txt
>> patching file vim/runtime/doc/vimshell.txt
>> can't find file to patch at input line 114
>> Perhaps you used the wrong -p or --strip option?
>> The text leading up to this was:
>> --------------------------
>> |--- vim/src/auto/configure
>> |+++ vim/src/auto/configure
>> --------------------------
>> File to patch:
>> ### END ###
>>
>> I confirmed that "vim/src/auto/configure" does not exist. There isn't
>> even a "vim/src"
>>
>> With version 7.0, I was getting "Hunk #XX FAILED at XXXX." on some of
>> the patches. On both versions I am using revision 1221. Any help  
>> would
>> be greatly appreciated.
>> _______________________________________________
>> The VIM-Shell Mailing List
>> vimshell at vimshell.wana.at
>> VIM-Shell Homepage: http://vimshell.wana.at
>>
>>
>>
>> -- 
>> Eugeni Dodonov
>> http://eugeni.dodonov.net/
>
>
>
>
> -- 
> Eugeni Dodonov
> http://eugeni.dodonov.net/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.wogri.at/pipermail/vimshell/attachments/20081106/28a84d50/attachment-0001.htm