On Tuesday, April 21, 2020 at 9:35:23 PM UTC+12, Andreas Plesner wrote:
> My school provide a server from which we can run code...
>BadAccess (attempt to access private resource denied)
>Vim: Got X error
>Vim: Finished.
(I'm guessing... the error suggests the X server is running as a different
user from the vim user, or on a different host. You might be able to solve
this by some .Xauthority manipulation, or the brute force use of xhost. I
suggest reading the Xsecurity(7) man page. These aspects of X are unknown
by most, including me, and only a dim memory for most of the rest.)
I can report that I run vim with the change that Christian Brabandt has
suggested to no ill effect, and have done so for many years. I
occasionally get BadWindow X errors when vim puts 256 kiB or more on the
clipboard. (I've never been able to track it down, as it happens
asynchronously.) The one extra change I make is to add the line
g_print("%s", IObuff);
that causes the error message to go to standard output, wherever that may
be. Without the preserve_exit() call the message doesn't otherwise appear
anywhere.
I expect that vim's clipboard support will not work, though. For editing
files on a server, it may be easier to run vim locally, and use netrw to
access the files.
HTH, John Little
--
--
You received this message from the "vim_dev" 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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/6ec5e3d2-663a-4df6-b55d-142111b9e5d2%40googlegroups.com.
