Received: by 10.224.201.7 with SMTP id ey7mr3900837qab.0.1336165717721;
        Fri, 04 May 2012 14:08:37 -0700 (PDT)
X-BeenThere: vim_use@googlegroups.com
Received: by 10.224.110.137 with SMTP id n9ls2679972qap.3.gmail; Fri, 04 May
 2012 14:08:31 -0700 (PDT)
Received: by 10.224.39.70 with SMTP id f6mr3897140qae.2.1336165711472;
        Fri, 04 May 2012 14:08:31 -0700 (PDT)
Received: by 10.224.39.70 with SMTP id f6mr3897139qae.2.1336165711460;
        Fri, 04 May 2012 14:08:31 -0700 (PDT)
Return-Path: <kogor...@gmail.com>
Received: from mail-qc0-f177.google.com (mail-qc0-f177.google.com [209.85.216.177])
        by gmr-mx.google.com with ESMTPS id c25si3789081qch.2.2012.05.04.14.08.31
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 04 May 2012 14:08:31 -0700 (PDT)
Received-SPF: pass (google.com: domain of kogor...@gmail.com designates 209.85.216.177 as permitted sender) client-ip=209.85.216.177;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of kogor...@gmail.com designates 209.85.216.177 as permitted sender) smtp.mail=kogor...@gmail.com; dkim=pass header...@gmail.com
Received: by qcsu28 with SMTP id u28so2720807qcs.22
        for <vim_use@googlegroups.com>; Fri, 04 May 2012 14:08:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=UZv57m0TBb3AQTgkbERzLwrd3Pn3f4p7heKIqIzUUIk=;
        b=wY+bCPQd4NPMKe9dRy1N9UFnC+/Bz/+5zupz5w4l/NHxjNQ/nskiZZiVxSmFpD3rsC
         Rn3asIrrFZEGnqR1tK+yvEJ6t+Bu816sNUlGJ5ImoqJSO+JjcRNo0b0o1Y/Q7Ii4JDRm
         sW7dcQOaBPDLPzOwDdoWBYy3ek8Hj3vEHKEew9WgW7Ctt2YzsmdWgBDbv4LQNFpOQvDW
         C77UfQ+3Uvw+9EnmAZfR32VzoZ0/NT0A1jp/yih8Aa7hdBvlr9ID1OgH5y9gP8ocoR0z
         mHGJ1I0KKcGTAUWp+KzKqrTCQK/yeWda7Ix0g9Cdg1C7aNvs2nnnc6V4GTVU7WZKpYcv
         07Vg==
MIME-Version: 1.0
Received: by 10.224.178.9 with SMTP id bk9mr12168577qab.98.1336165711288; Fri,
 04 May 2012 14:08:31 -0700 (PDT)
Received: by 10.229.164.16 with HTTP; Fri, 4 May 2012 14:08:31 -0700 (PDT)
In-Reply-To: <jnudaa$2b...@dough.gmane.org>
References: <CAGVXcSbMhAbcGHg6jK0oEVVj2v2j=OteEGH34NRA9z61wPY...@mail.gmail.com>
	<4FA13AC7.2070...@tim.thechases.com>
	<jnrs16$68...@dough.gmane.org>
	<20120503085559.GC2013@ratatosk>
	<jnudaa$2b...@dough.gmane.org>
Date: Fri, 4 May 2012 14:08:31 -0700
Message-ID: <CAGVXcSaEpAy4fu4yeFe26JPVgcw26JsDKQd-dwYndDq4UyQ...@mail.gmail.com>
Subject: Re: vim says "No protocol specified" and I have no idea what it means
From: "Kevin O'Gorman" <kogor...@gmail.com>
To: vim_use@googlegroups.com
Content-Type: text/plain; charset=UTF-8

On Thu, May 3, 2012 at 9:55 AM, Thilo Six <T....@gmx.de> wrote:
> Hello Erik,
>
>
> Excerpt from Erik Christiansen:
>
> -- <snip> --
>> That looks like a neat fix, Thilo.
>>
>> But is there a weakness in the OP's access control config?
>> Here, on my ubuntu 10.04, unaltered and still as OOTB, starting X as
>> "erik", doing an "su -", then vimming anything which stands still, has
>> always worked, not least (I figure) because of:
>>
>> $ xhost
>> access control enabled, only authorized clients can connect
>> SI:localuser:erik
>> SI:localuser:gdm
>> SI:localuser:root
>>
>> So just doing an:
>>
>> $ xhost +root
>>
>> in ~/.bash_profile might just do it too?
>>
>> Erik
>
> I am not impolite but we are getting out of the focus of this list.
> Please ask this question again on an appropriate list.

Huh?  This was posted to vim_use, and it's about my difficulties using
vim.  It's a permissions problem that seems not to affect anything
else, so we're talking about permissions and strategies and scriptlets
to fix my problem using vim.

I'll bite: where would it be more appropriate?

-- 
Kevin O'Gorman, PhD