unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Perry Smith <pedzsan@gmail.com>
Cc: Chong Yidong <cyd@gnu.org>, emacs-devel@gnu.org
Subject: Re: emacs 24 and vnc not working
Date: Wed, 8 Aug 2012 19:21:13 +0200	[thread overview]
Message-ID: <02AA9896-066F-43F0-9F15-1F18F1FB3294@swipnet.se> (raw)
In-Reply-To: <D28579F5-AE30-4EB0-B990-1D35F93EBC0E@gmail.com>

Hello.

This looks like it depends both on the client and the server.
A vnc server on Mandriva 2010.2 (TigerVNC 1.0.90) works with Jolly Fast VNC,
i.e. copy and paste in both directions to an Emacs running in the vnc client.
With the built in OSX client, only from Emacs to Mac works.

There is some workarounds discussed here:
http://www.csd.uwo.ca/staff/magi/doc/vnc/faq.html#q25

Do you run vncconfig in your session?

	Jan D.
 
8 aug 2012 kl. 17:13 skrev Perry Smith:

> 
> On Aug 8, 2012, at 2:51 AM, Chong Yidong wrote:
> 
>> Perry Smith <pedzsan@gmail.com> writes:
>> 
>>> Can we please bring back cut buffer support?  That is what I need.
>> 
>> What makes you think your vnc is using cut buffers?  That would
>> be... interesting, if true.  Cut buffers are incredibly obsolete.
>> 
>>>> I can verify that the clipboard and primary selection are both being
>>>> updated -- it just isn't working with the Xvnc server.
>> 
>> How did you verify this?  Your description is too vague to do much with.
> 
> I'm using an old VNC server on AIX -- two different ones I believe.
> 
> One comes from here:
> 
> http://www-03.ibm.com/systems/power/software/aix/linux/toolbox/date.html
> (search for "vnc")
> 
> The other comes from here:
> 
> ftp://www.oss4aix.org/latest/aix61/ 
> (search for tightvnc-server)
> 
> Building X11 (and thus any type of X11 server) for AIX is really
> hard and so we are stuck in the dark ages.
> 
> Both of those have a way to review the source.  I'm not an X11 type
> person.
> 
> Over the past two days I've been poking and prodding.  I'd LOVE
> to be wrong.  Or perhaps one of those vnc servers has an option
> that can alter its behavior.
> 
> The set up is emacs 22.3 running on AIX 5.3 verses emacs 24.1 running
> on 6.1.  I wish I could get on a common OS level but it is a lot
> of work.
> 
> On the AIX 5.3 host, I have the first vnc (which I'll call vnc 3.3).
> On the 6.1 host I have the tightvnc-server.  I have experimented
> with the four different combinations such as the emacs 22 version
> running on 5.3 but with its display pointing to the tightvnc server
> running on 6.1.
> 
> Then I have Jolly VNC running on a Mac which is a vnc viewer or a
> vnc client.  I have also tried the vncviewer that is stock in the
> Mac as well as the vncviewer that comes with the vnc 3.3 package
> listed above.  But I think the restriction is due to the vnc server.
> 
> I also have a copy of "xclip" which will dump out the Primary
> Selection, Secondary Selection, and Clipboard (not sure why I
> capitalized all that :-).
> 
> I noticed early that by some mysterious way, I can cut from a Mac
> window and paste into an xterm client on one of the different vnc
> servers and xclip would tell me that none of the three items it can
> display changed.
> 
> The original list of symptoms is that emacs 22, xterm, and Mac
> applications all play happily together.  emacs 24 and xterm also
> play happily together.  But emacs 24 and a Mac application (going
> through the vnc connection) do not work in either direction.
> 
> I finally put some simple lisp into *scratch* to dump out the cut
> buffer 0 (as well as the other three select / clipboard areas) and
> saw that it was the cut buffer that was the mysterious way that
> text was getting back and forth from the Mac applications and the
> older x11 applications (AIX's xterm and emacs 22.3).
> 
> I realize that this is way off the beaten path but it also seems
> like carrying the "bagage" of cut buffers isn't that big.
> 
> I can hack my local copy of emacs today and get my copy working but
> any AIXer is likely to hit this same issue.
> 
> Thank you,
> Perry
> 
> 




  reply	other threads:[~2012-08-08 17:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EE20F0BB-0E41-4FC4-A922-7262BCAFA6AA@gmail.com>
2012-08-08  0:59 ` emacs 24 and vnc not working Perry Smith
2012-08-08  7:51   ` Chong Yidong
2012-08-08 15:13     ` Perry Smith
2012-08-08 17:21       ` Jan Djärv [this message]
     [not found] ` <mailman.6526.1344387578.855.help-gnu-emacs@gnu.org>
2012-08-09 15:57   ` arenson9
2012-08-10 13:27     ` Perry Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=02AA9896-066F-43F0-9F15-1F18F1FB3294@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=cyd@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=pedzsan@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).