On 04.05.12 14:08, Kevin O'Gorman wrote: > On Thu, May 3, 2012 at 9:55 AM, Thilo Six <[email protected]> wrote: > > 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?
Hi Kevin, Your difficulties, and the various ways to negate them informed me, and I expect they gave you choice of ways out of strife. Thilo seems to be sorely confused. My post included one passing rhetorical question, as a lead-in to a proposal for another way to avoid your problem, which Thilo himself attempted to solve. It was not asking any real question, but offering vim-related help. Perhaps Thilo can outline why he may try to help, but others may not. Erik -- Once it hits the fan, the only rational choice is to sweep it up, package it, and sell it as fertilizer. - Anonymous? -- 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
