all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mike Orr <morr@adobe.com>
To: 11765@debbugs.gnu.org
Subject: bug#11765: 24.1 upgrade breaks porkrind Emacs over Mac-to-Mac screen sharing
Date: Fri, 22 Jun 2012 08:19:40 -0700	[thread overview]
Message-ID: <D1BD34D222D4E14092E945972AB325FC2319A00065@nambxv01a.corp.adobe.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]

I have a regression between vanilla installs of 23.4.1 and 24.1.1 porkrind.org Emacs on a Lion (10.7.4) Mac Pro. I see the regression only in the context of running Emacs over Mac-to-Mac OS X Screen Sharing - 24.1 is running fine when executed locally. I'm testing with my Emacs init file disappeared via renaming.

I'm observing this on two Screen Sharing clients: one is a Snow Leopard (10.6.8) Mac Pro; the other is a Lion (10.7.4) MacBook Pro. I get the same results with both.

The regression is that Ctrl- and Alt- key chords don't work in 24.1 (only) over Screen Sharing. It's *not* simply that Ctrl and Alt are not seen; in other words it's *not* the case that when I type C-x I get an 'x' in the buffer. I don't have a concrete description of exactly what occurs - visually I either see nothing, I see a symbol appear in the buffer, or I see an error message that might be appropriate for some command, but is unrelated to what I tried to type. One thing I know to be reliably reproducible is that if I start Emacs and immediately type C-h, I get the message "Beginning of buffer".

Fwiw, this is in a VPN context. The VPN config is very different for the two clients; Cisco hardware in one case, Cisco AnyConnect software in the other.

Hope it helps,
Mike Orr


[-- Attachment #2: Type: text/html, Size: 3177 bytes --]

             reply	other threads:[~2012-06-22 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-22 15:19 Mike Orr [this message]
2012-06-22 20:03 ` bug#11765: 24.1 upgrade breaks porkrind Emacs over Mac-to-Mac screen sharing Stefan Monnier
2012-06-22 20:58   ` Mike Orr

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

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

  git send-email \
    --in-reply-to=D1BD34D222D4E14092E945972AB325FC2319A00065@nambxv01a.corp.adobe.com \
    --to=morr@adobe.com \
    --cc=11765@debbugs.gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.