1 |
On 09/23/2016 02:33 PM, William Ernesto Cárdenas Gómez wrote: |
2 |
> El Fri, 23 Sep 2016 09:24:02 -0700 |
3 |
> Daniel Frey <djqfrey@×××××.com> escribió: |
4 |
>> On 09/23/2016 08:00 AM, pc0147 Sistemas Will_ecg wrote: |
5 |
>>> El jue, 22-09-2016 a las 08:32 -0700, Daniel Frey escribió: |
6 |
>>>> For some reason, on one box, whenever I start vim it puts |
7 |
>>>> ":0000/0000/0000" on the command line. I've looked in vimrc and |
8 |
>>>> can't see any reference to this. Hitting Enter yields "E486: |
9 |
>>>> Pattern not found |
10 |
>>>> :0000" |
11 |
>>>> |
12 |
>>>> I've noticed that it's been behaving strangely but I cannot figure |
13 |
>>>> out |
14 |
>>>> the cause. Last time I noticed something odd was when I commented |
15 |
>>>> out something in package.mask (with #) and saved it. Portage |
16 |
>>>> complained it |
17 |
>>>> was invalid and when I opened it again the '#' changed to 'g'. |
18 |
>>>> |
19 |
>>>> I've removed and reinstalled vim packages, no luck. |
20 |
>>>> |
21 |
>>>> Has anyone seen this? |
22 |
>>>> |
23 |
>>>> Dan |
24 |
>>>> |
25 |
>>> |
26 |
>>> I had the same problem, the only solution I found was to add the |
27 |
>>> vimrc for user ~.vimrc and at least set one thing. I only set the |
28 |
>>> colorscheme and now works fine, the problem is that you should set |
29 |
>>> it for all your users, in my case was my personal user and root. |
30 |
>>> |
31 |
>> |
32 |
>> I tried this, with "set nowrap" in a .vimrc, and it made no |
33 |
>> difference. What I find baffling is that out of six machines only one |
34 |
>> is doing this! |
35 |
>> |
36 |
>> Dan |
37 |
>> |
38 |
> |
39 |
> I've just test again, and I tried with some other options and only |
40 |
> works with colorscheme. I don't know why. |
41 |
> |
42 |
|
43 |
You are right, this works. I wonder why? I'll look around for a bug report. |
44 |
|
45 |
Dan |