Am 30.07.2010 05:58, schrieb Walter Dnes:
On Thu, Jul 29, 2010 at 01:35:46PM -0700, Kevin O'Gorman wrote
I'm not exactly sure when, but starting a month or so ago, vim has been
acting weird when
I run it as root. For one thing, there are messages
Xlib: connection to :0.0 refused by server
On Thu, 29 Jul 2010 23:58:38 -0400, Walter Dnes wrote:
1) Get rid of the X-integration by going into /etc/portage/package.use
and adding the line...
app-editors/vim -X
You'll have to re-emerge vim after making that change. This gets rid
of X-integration for vim.
2) If you really
On 07/29/2010 08:58 PM, Walter Dnes wrote:
2) If you really really need the X-integration features, you can use the
xhost command to enable all users on your machine to run X apps on
your X session. E.g. my machine is 192.168.123.249 so I ran...
xhost +192.168.123.249
...to allow a
On Fri, Jul 30, 2010 at 6:43 AM, Bill Longman bill.long...@gmail.comwrote:
On 07/29/2010 08:58 PM, Walter Dnes wrote:
2) If you really really need the X-integration features, you can use the
xhost command to enable all users on your machine to run X apps on
your X session. E.g. my
On Fri, Jul 30, 2010 at 7:59 AM, Kevin O'Gorman kogor...@gmail.com wrote:
then the X app is not limited to using only IP but can choose whichever
transport it deems best. Of course the usual safety caveats apply. If
others are on your host, they'll have X access. If you're concerned
about
I'm not exactly sure when, but starting a month or so ago, vim has been
acting weird when
I run it as root. For one thing, there are messages
Xlib: connection to :0.0 refused by server
on the console. I presume this is an X authority thing, but I'm not sure
why it became an
issue when it
On Thu, Jul 29, 2010 at 01:35:46PM -0700, Kevin O'Gorman wrote
I'm not exactly sure when, but starting a month or so ago, vim has been
acting weird when
I run it as root. For one thing, there are messages
Xlib: connection to :0.0 refused by server
General rule... by default X apps
7 matches
Mail list logo
