W dniu wtorek, 14 stycznia 2014 17:17:57 UTC+1 użytkownik yega...@gmail.com
napisał:
> Hi,
>
>
>
> On Tue, Jan 14, 2014 at 5:17 AM, lazureus wrote:
>
> > W dniu wtorek, 14 stycznia 2014 11:03:04 UTC+1 użytkownik JohnBeckett
> > napisał:
>
> >> It looks like the wiki has had the answer since
Hi,
On Tue, Jan 14, 2014 at 5:17 AM, lazureus wrote:
> W dniu wtorek, 14 stycznia 2014 11:03:04 UTC+1 użytkownik JohnBeckett napisał:
>> It looks like the wiki has had the answer since March 2013:
>>
>> http://vim.wikia.com/wiki/Script:311
>>
>> That is linked in the top line at:
>>
>> http://www
W dniu wtorek, 14 stycznia 2014 11:03:04 UTC+1 użytkownik JohnBeckett napisał:
> It looks like the wiki has had the answer since March 2013:
>
> http://vim.wikia.com/wiki/Script:311
>
>
>
> That is linked in the top line at:
>
> http://www.vim.org/scripts/script.php?script_id=311
>
>
>
> I
It looks like the wiki has had the answer since March 2013:
http://vim.wikia.com/wiki/Script:311
That is linked in the top line at:
http://www.vim.org/scripts/script.php?script_id=311
I have not used the plugin, but what is written at the above
looks exactly what is needed to fix the error quoted
W dniu wtorek, 14 stycznia 2014 07:27:03 UTC+1 użytkownik JohnBeckett napisał:
> lazureus wrote:
>
> > I'm encountering some similar problems as Dariusz have seen
>
> > however on the 64-bit Ubuntu. Trying to run :Rgrep from VIM
>
> > I get following error message :
>
> >
>
> > Error detected
lazureus wrote:
> I'm encountering some similar problems as Dariusz have seen
> however on the 64-bit Ubuntu. Trying to run :Rgrep from VIM
> I get following error message :
>
> Error detected while processing function
>
> 19_RunGrepRecursive..19_RunGrepCmd:
> line 20:
> E484: Can't open file /tm
W dniu niedziela, 28 kwietnia 2013 18:42:08 UTC+2 użytkownik yega...@gmail.com
napisał:
> Hi,
>
>
>
> On Tue, Apr 23, 2013 at 11:52 PM, Dariusz Gadomski
> wrote:
>
> >
>
> > This problem is caused by the shell command line quote escape
>
> > character in MS-Windows.
>
> >>>
Hi,
On Tue, Apr 23, 2013 at 11:52 PM, Dariusz Gadomski wrote:
>
> This problem is caused by the shell command line quote escape
> character in MS-Windows.
> I have a fix for this issue. I will update the grep plugin and release
> a new version.
>
> - Yegappan
>>
On Wednesday, April 24, 2013 1:55:57 AM UTC-5, Darek wrote:
> Hi
>
>
>
> On Tue, Apr 23, 2013 at 5:14 PM, Ben Fritz wrote:
>
> > On Tuesday, April 23, 2013 8:58:20 AM UTC-5, Darek wrote:
>
> >> Hi
>
> >>
>
> >>
>
> >>
>
> >> On Mon, Apr 15, 2013 at 6:07 PM, Yegappan Lakshmanan
>
> >>
>
Hi
On Tue, Apr 23, 2013 at 5:14 PM, Ben Fritz wrote:
> On Tuesday, April 23, 2013 8:58:20 AM UTC-5, Darek wrote:
>> Hi
>>
>>
>>
>> On Mon, Apr 15, 2013 at 6:07 PM, Yegappan Lakshmanan
>>
>> wrote:
>>
>> >
>>
>> >
>>
>> > This problem is caused by the shell command line quote escape
>>
>> > chara
Hi
On Wed, Apr 24, 2013 at 7:28 AM, Yegappan Lakshmanan
wrote:
> Hi,
>
> On Tue, Apr 23, 2013 at 6:00 PM, Yegappan Lakshmanan
> wrote:
>>> >
>>> > This problem is caused by the shell command line quote escape
>>> > character in MS-Windows.
>>> > I have a fix for this issue. I will update the gre
Hi,
On Tue, Apr 23, 2013 at 6:00 PM, Yegappan Lakshmanan
wrote:
>> >
>> > This problem is caused by the shell command line quote escape
>> > character in MS-Windows.
>> > I have a fix for this issue. I will update the grep plugin and release
>> > a new version.
>> >
>> > - Yegappan
>>
>> I was tr
Hi,
On Tue, Apr 23, 2013 at 6:58 AM, Dariusz Gadomski wrote:
>
> Hi
>
> On Mon, Apr 15, 2013 at 6:07 PM, Yegappan Lakshmanan
> wrote:
> >
> >
> > This problem is caused by the shell command line quote escape
> > character in MS-Windows.
> > I have a fix for this issue. I will update the grep pl
On Tuesday, April 23, 2013 8:58:20 AM UTC-5, Darek wrote:
> Hi
>
>
>
> On Mon, Apr 15, 2013 at 6:07 PM, Yegappan Lakshmanan
>
> wrote:
>
> >
>
> >
>
> > This problem is caused by the shell command line quote escape
>
> > character in MS-Windows.
>
> > I have a fix for this issue. I will u
Hi
On Mon, Apr 15, 2013 at 6:07 PM, Yegappan Lakshmanan
wrote:
>
>
> This problem is caused by the shell command line quote escape
> character in MS-Windows.
> I have a fix for this issue. I will update the grep plugin and release
> a new version.
>
> - Yegappan
I was trying to analyze this prob
Great! I would love to give it a try. Looking forward to trying your
fix, I will keep monitoring grep.vim page on vim.org. Thanks.
On Mon, Apr 15, 2013 at 6:07 PM, Yegappan Lakshmanan
wrote:
> Hi,
>
> On Mon, Apr 15, 2013 at 6:41 AM, Darek wrote:
>> Hi,
>>
>> This question has already been poste
Hi,
On Mon, Apr 15, 2013 at 6:41 AM, Darek wrote:
> Hi,
>
> This question has already been posted to vim_use list, but since I suspect
> this to be a bug in vim (or in Windows ;) ), this is probably a more
> appropriate place for it.
>
> I experience a strange problem with 64-bit vim/gvim on 64
On Monday, April 15, 2013 8:41:54 AM UTC-5, Darek wrote:
>
> I have did some debugging and looks like the error appears on the
> system() call in grep.vim:407. If I copy-n-paste system()'s argument to
> cmd.exe - it works as expected. Looks like there is a bug with the system()
> function on 64
Hi,
This question has already been posted to vim_use list, but since I suspect this
to be a bug in vim (or in Windows ;) ), this is probably a more appropriate
place for it.
I experience a strange problem with 64-bit vim/gvim on 64-bit Windows 7.
When I use Rgrep on 32-bit vim build everythi
19 matches
Mail list logo
