Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Discuss Digest, Vol 15, Issue 23



It seems to me that this would be the correct behavior for emacs. If you
don't specify it to be use X11 protocol for UI, then it defaults to a
console text UI. In the "-f" mode there is no console to speak of and
stdin and stdout are NULL.

Try running "xemacs" or something.


> Date: Fri, 23 Jan 2009 11:57:09 -0500
> From: Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
> Subject: GNU emacs via ssh
> To: Boston Linux and Unix <discuss-mNDKBlG2WHs at public.gmane.org>
> Message-ID: <4979F6E5.2060808-mNDKBlG2WHs at public.gmane.org>
> Content-Type: text/plain; charset="iso-8859-1"
>
> When I ssh -X <host>, and run /usr/bin/emacs everything works fine:
> (emacs)
> Loading disp-table...done
> Loading tool-bar...done
> Loading image...done
> Loading tooltip...done
> Loading /usr/share/emacs/site-lisp/site-start.d/igrep-init.el
> (source)...done
> Loading
> /usr/share/emacs/site-lisp/site-start.d/lang-coding-systems-init.el
> (source)...
> Loading encoded-kb...done
> Loading
> /usr/share/emacs/site-lisp/site-start.d/lang-coding-systems-init.el
> (source)...done
> Loading /usr/share/emacs/site-lisp/site-start.d/php-mode-init.el
> (source)...done
> Loading /usr/share/emacs/site-lisp/site-start.d/po-mode-init.el
> (source)...done
> Loading /usr/share/emacs/site-lisp/site-start.d/python-mode-init.el
> (source)...done
> Loading /usr/share/emacs/site-lisp/site-start.d/rpm-spec-mode-init.el
> (source)...done
> Loading /usr/share/emacs/site-lisp/site-start.d/tramp-init.el
> (source)...done
> Loading mwheel...done
> Loading jka-compr...done
>
> But, when I run emacs using ssh -X -f <host> /usr/bin/emacs, it fails
> while reading lang-coding-systems-init.el.
> (emacs)
> Loading disp-table...done
> Loading tool-bar...done
> Loading image...done
> Loading tooltip...done
> Loading /usr/share/emacs/site-lisp/site-start.d/igrep-init.el
> (source)...done
> Loading
> /usr/share/emacs/site-lisp/site-start.d/lang-coding-systems-init.el
> (source)...
> or: Wrong type argument: stringp, nil
>
> In both cases the <host> I was coming from and going to are the same.
> The target system is running RHEL 5.2. I actually deleted
> /usr/share/emacs and deinstalled and reinstalled emacs just in case
> there were some artifacts from a previous installation, though the RHEL
> 5.2 was a clean install. The reason I can't run emacs on my workstation
> is that it is an IA64 system and I usually compile from emacs, so I need
> to be on an x86 system since I am using a pre-built set of compilation
> tools. I've tested this on a number of different systems we have here,
> and with a couple of different ~/.emacs files (and no ~/.emacs). I
> specified /usr/bin/emacs just to eliminate any hidden aliases. I suspect
> that the issue might be that it cannot detect the keyboard using the ssh
> -f (which implies -n) option.
>
>  --
> Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org>
> Boston Linux and Unix
> PGP key id: 537C5846
> PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB  CA3B 4607 4319 537C 5846






BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org