bug#11765: 24.1 upgrade breaks porkrind Emacs over Mac-to-Mac screen sharing

[Mike Orr <morr@adobe.com>]

Thanks for the super-quick turnaround. Not sure whether an email reply is what you had in mind - let me know if you want me to do something else with the below...

I entered this sequence in the scratch buffer (the vertical bars are literal):

  | C-a | C-b | C-c | C-d | C-h | C-j | C-m | C-z | M-x | M-z | C-c  c | C-c C-c | C-M-a | C-M-<up> | M-s w | M-g M-g |

Here's the result from evaluating (view-lossage):

| | | | | <backspace> | | | | µ | ≈ | c | | C-a | <C-M-up>
| ß w | © © | <return> ( v i e w - l o s s a g e ) <menu-bar>
<lisp-interaction> <eval-print-last-sexp>

So the "start Emacs and hit C-h" behavior is clear at one level: C-h is being folded into an ASCII 8 aka BS, tty-style, upstream of the command intake. 

Let me know if I can try anything else,
Mike


-----Original Message-----
From: Stefan Monnier [mailto:monnier@iro.umontreal.ca] 
Sent: Friday, June 22, 2012 1:04 PM
To: Mike Orr
Cc: 11765@debbugs.gnu.org
Subject: Re: bug#11765: 24.1 upgrade breaks porkrind Emacs over Mac-to-Mac screen sharing

> 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".

Thanks for your report.  Hopefully someone more knowledgeable about the
Mac OS X code than I will be able to look into it, but in the mean time,
can you use C-h l to see what events Emacs thinks it is receiving?
E.g. try the "start Emacs and hit C-h" and then do C-h l or M-x
view-lossage RET or type "(view-lossage)" in the *scratch* buffer and
then select "Evaluate and Print" in the "Lisp-Interaction" menu, in case
the C-h and M-x bindings are too messed-up to use.

You can try it after hitting a few different C-<something> and
M-<something> combinations, just just make sure you type something
recognisable in-between so that you can figure out which (sequences) of
events corresponds to those bindings in the view-lossage output.


        Stefan