Slackware 14.2: Emacs doesn't start when Internet is off
Emacs: 24.5.1 (i586-slackware-linux-gnu, GTK+ Version 2.24.28).
When I try to launch Emacs without Internet connection --- it doesn't run. Neither in GUI or console mode. I renamed my .emacs file to 1.emacs, and it still doesn't work. So it has nothing to do with my settings. After I plug in the Internet cable, it starts to work. What's up? How can I fix it? |
Does it start with
Code:
emacs -nw -Q Also, what is in /etc/hosts ? |
hahaha, this bug report gave me a good laugh, thank you for this. sorry i can't help in any way.
|
Quote:
no, doesn't start without the Internet connection. Quote:
Code:
# For loopbacking. |
Hi,
Try adding IPv6 for localhost to /etc/hosts: Code:
::1 localhost Best regards, Andrzej Telszewski |
Quote:
Do you have anything in your .emacs file (or newer equivalent)? If you wait ~12 minutes (that's default TCP timeout, BTW), does it come up? |
Quote:
|
Quote:
Quote:
Quote:
|
Quote:
|
Quote:
Code:
127.0.0.1 host.does.not.exist |
I saw you renamed ~/.emacs with no luck. Also try renaming Directory ~/.emacs.d
Another thing to check, did you copy any files to /usr/share/emacs/site-lisp ? John |
Quote:
Try Vim instead. :D |
Quote:
Personally, I've never used Emacs. Never had the need. It has been installed on my computer for a very long time though. |
Quote:
|
Quote:
|
Quote:
Quote:
|
Quote:
Quote:
|
have you tried to remove (rename) your .emacs.d , or what you use for emacs,
maybe there is some auto install update melpa other package manager configured that tries to get info from the net did you tried to use emacs clean? |
Quote:
|
Quote:
Code:
192.168.1.253 host.does.not.exist |
Quote:
|
Quote:
|
Quote:
Quote:
|
Do you use yp for user and any firewall rule on local client? local host's 127.0.0.1 has to connect to yp server.
|
So does the machine hostname (in /etc/HOSTNAME) have an entry in /etc/hosts ?
Also, you could perhaps try the idea from StackExchange (running it under strace) Code:
strace -o /tmp/foo emacs -Q -nw |
Also, there's no strange zombie processes are there? If you
Code:
killall emacs |
Do you use any rpc services? rpc binding port can be connected to 127.0.0.1 as well.
|
Quote:
Quote:
Here is the trace (seems that it tries to connect to laptop): Quote:
|
Hurray! After adding:
Quote:
|
Hi,
Quote:
-- Best regards, Andrzej Telszewski |
Quote:
|
Quote:
|
Quote:
Code:
# For loopbacking. |
Quote:
|
Quote:
What happened here? Was the file edited by the OP? |
Quote:
Quote:
|
BTW: never used that feature myself, but I know that you can start an "emacs daemon" and then when you launch emacs, it is spawned as a "client", usefull (at the time) to share memory between several "instances" of emacs in tmux or screen.
Anyway, I guess that on start of emacs, he tries to connect to a potential "daemon" first to know in which mode it must starts. And the daemon communication might goes through a "localhost" port and something in happens when the socket is created/bound, name resolution or something of this kind. This would lead me to think that this problem could happen on some other application which use the a local socket too, and might have similar code than emacs to do it. It was just to say... :) |
Actually to connect to the server you need to run 'emacsclient'. The regular 'emacs' command doesn't do that :)
|
Quote:
Bests. |
All times are GMT -5. The time now is 02:36 PM. |