The one I have is 23.4.1. Are you running ssh through cygwin? I'd suggest that but also don't know if that would then also support the -X option. Also look for an option called "ForwareX11" that's what the -X option activates in ssh.
- RT On Wed, Dec 18, 2013 at 7:05 PM, <[email protected]> wrote: > I'm using SSH Secure Shell on a Windows XP machine, not ssh on a Linux > box, and there's no -X option that I'm aware of. As far as I can tell from > the man page, whatever it is that the -X option does is automatically > provided by the SSH program. Also, I've used this software for accessing > emacs on many machines for years with no bad experiences that I can recall > ... until now. > > I suspect that there's some flag or option that has to be adjusted on the > BBB side, either for the shell or more likely for emacs, but I have no > idea what it might be. > > A little more googling and I see that there may be some bug in emacs that > causes this. So, another question: has anybody gotten emacs 23.4-r2 to > work in the BBB running Angstrom? > > On Wednesday, December 18, 2013 12:45:55 PM UTC-5, RT Mistler wrote: >> >> Hi, >> >> Do you use the -X switch when you invoke ssh? I was searching for how to >> install emacs on beaglebone black and found your note. It worked for me, I >> use: >> >> ssh -X root@<ip-address> >> >> to attach to my BBB and now that I've installed gnuemacs, it works >> correctly, window pops up and all; no problems with key sequences. >> >> I am ssh'ing over from a Ubuntu distribution. >> >> - RT >> >> On Wednesday, December 11, 2013 5:42:01 PM UTC-5, [email protected]: >>> >>> I installed emacs on my brand new BBB, but although emacs starts up, no >>> key ever makes it to into the program. >>> >>> The installation was as simple as >>> 1) log in as root using SSH Secure Shell 3.2.9 (see comments below) to >>> 192.168.1.xxx (via the ethernet cable, address assigned via DHCP) >>> 2) execute >>> opkg update >>> opkg install emacs >>> 3) run emacs by typing >>> emacs >>> >>> No key is recognized, not M-<key>, not C-<key> , not even just a letter >>> <key> (and worst of all, not C-x C-c, which would cause emacs to exit). >>> Same result occurs if I create a text file test.txt and then execute >>> emacs test.txt >>> >>> And just to cut off one possibility: note that I've been using SSH >>> Secure Shell with emacs for years, and I tested it just now with another >>> system; it works just fine. Obviously, too, it accesses the BBB, because >>> that's how I entered the commands that installed and executed emacs. And, >>> of course, I've rebooted the BBB several times. >>> >>> Any thoughts? >>> >>> Thanks, >>> Richard >>> >>> P.S. SSH Secure Shell 3.2.9 is a very nice TTY program, which I vastly >>> prefer over PuTTY. >>> Search for >>> ssh secure shell 3.2.9 download free >>> and you'll find various sources, including universities, that offer the >>> software for free, e.g.William & Mary, Dartmouth, Northwestern, UCLA, etc. >>> In other words, you won't be downloading some cracked and potentially >>> dangerous piece of software. >>> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/I0B2Jj1pa78/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
