Thursday, May 3, 2012

Re: vim says "No protocol specified" and I have no idea what it means

On 02.05.12 19:48, Thilo Six did (boldly) proffer wisdom:
> 4)
> ,----[ ~/.bashrc ]--------
>
> if [[ ${EUID} -eq 0 ]] ; then
> [[ -n ${DISPLAY} ]] && unset DISPLAY
> fi
> `---------------------------------------------
>
>
> ,----[ man su ]--------
>
> If --login is used, the $TERM, $COLORTERM, $DISPLAY,
> and $XAUTHORITY environment variables are copied if
> they were set.
> `---------------------------------------------

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 never pray before meals -- my mum's a good cook.

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

No comments:

Post a Comment