Håkon Alstadheim <[EMAIL PROTECTED]> writes: >> 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
Thanks for the input... that is a good idea, and surprisingly works fine. But does not provide the slightest clue why such a work around is necessary. Nothing but the date gets written to emacs log. Apparently for some reason there needs to be a sort of cutout between Konq and emacs, but not so with kate or kwrite. > 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? I'm not sure how to capture whatever it is that konq is doing. I don't think its throwing an error. But not really sure how to tell other than looking for .xsessions* file or something else with a kde error in it. I think it is just timing out silently. However it seems it would be almost guaranteed that there would be spaces in the command `emacs %s' or something similar. > Experiment with adding </dev/null onto there (that never did it for > me). Have a look at what the log says. Just for the record... no soap there. I'd already tried another non-promising test, adding the background sign `&' which didn't seem likely to help and as expected, did not. -- gentoo-user@lists.gentoo.org mailing list
