[EMAIL PROTECTED] wrote:
Håkon Alstadheim <[EMAIL PROTECTED]> writes:
[EMAIL PROTECTED] wrote:
Mick <[EMAIL PROTECTED]> writes:
Don't know the first thing about emacs, but it may need bringing up
a terminal first which in turn runs emacs. You may want to try
selecting the "Run in terminal" or invoke it like so:
xterm -e /usr/bin/emacs
This should not be a factor with X enabled emacs. And in fact calling
emacs at a cmd prompt just brigs up emacs in it own window, not
another xterm.
However, and surprisingly it does work... Inserting the xterm -e
command at: right click/ open with/ other
Brings first an xterm which immediately spawns a new emacs window (not
in the xterm but on its own)
I'm pretty sure this is not what SHOULD happen though. I SHOULD be
able to just insert /usr/bin/emacs since it does not run in an
xterm. But... thanks .. at least I can edit a page with emacs now.
I have this same problem on some machines. Notably the ones where I've
put the most cruft in .emacs. I suspect that there is some bug that
stops garbage-collection from happening during startup so emacs runs
out of memory. Somehow having a tty attached works around that.
A little more on this. Do you mean it works just fine on some
machines as well?
Something to test your theory... (I tried it here with no better
results) is from Konq, right click/open with/other and put /usr/bin/emacs -Q
Which will start emacs with no site-file or ~/.emacs being loaded.
I tried that here but still just got the bouncing emacs icon/cursor.
Can you start emacs without problems from konqueror at right
click/open with/ on any machine? I mean without `xterm -e emacs'
Not running konqueror here, but yes, emacs would fire up quite reliably
when I had it as my source editor in mozilla, way back when. You most
definitely SHOULD be able to run it without a terminal window. If you
are really keen on getting this to work, you could write a little script
like so to use as your editor: ----
#!/bin/bash
date >>~/emacs.log
emacs "$@" >>~/emacs.log 2>&1
-------
Come to think of it (while looking up the $@ semantics), could it be
that the argument fed from konqueror has spaces in it? Maybe it needs
quoting?
Experiment with adding </dev/null onto there (that never did it for me).
Have a look at what the log says.
--
gentoo-user@lists.gentoo.org mailing list
