[SOLVED] Slackware 14.2: Emacs doesn't start when Internet is off

usr345 · 10-27-2016, 01:02 PM

Quote:

Originally Posted by atelszewski

Hi,

This does not look like a correct entry for /etc/hosts (i.e. IP address should be first).

Fixed the post.

Richard Cranium · 10-27-2016, 09:27 PM

Quote:

Originally Posted by usr345

Tried it. It gave just the info about successfully loading my packages:

Hmm. I see a lot of stuff from your ~/.emacs.d directory loading.

drgibbon · 10-27-2016, 09:47 PM

Quote:

Originally Posted by usr345

Hurray! After adding:

Code:

127.0.0.1 laptop

to /etc/hosts it started to work. Thank you, drgibbon, sir.

Nice! Emacs on

By the way, if you have "laptop.local" as the hostname, I think it should be at least;

Code:

# For loopbacking.
127.0.0.1		localhost
127.0.0.1		laptop.local laptop
# End of hosts.

In /etc/hosts (plus whatever else you want in there).

usr345 · 10-28-2016, 03:26 PM

Quote:

Originally Posted by drgibbon

By the way, if you have "laptop.local" as the hostname, I think it should be at least;

Code:

# For loopbacking.
127.0.0.1		localhost
127.0.0.1		laptop.local laptop
# End of hosts.

Done.

rkelsen · 10-28-2016, 05:13 PM

Quote:

Originally Posted by drgibbon

Nice! Emacs on

By the way, if you have "laptop.local" as the hostname, I think it should be at least;

Code:

# For loopbacking.
127.0.0.1		localhost
127.0.0.1		laptop.local laptop
# End of hosts.

In /etc/hosts (plus whatever else you want in there).

Doesn't Slackware usually put the correct information in /etc/hosts as part of the installation?

What happened here? Was the file edited by the OP?

usr345 · 10-29-2016, 02:33 AM

Quote:

Originally Posted by rkelsen

Doesn't Slackware usually put the correct information in /etc/hosts as part of the installation?

In my case it didn't. I installed fresh Slackware 14.2 and chose "laptop" as my host name.

Quote:

Originally Posted by rkelsen

Was the file edited by the OP?

It was edited by me (needed to add names of locally developed websites), but I didn't delete anything from it.

NoStressHQ · 10-29-2016, 08:46 AM

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...

drgibbon · 10-29-2016, 08:54 AM

Actually to connect to the server you need to run 'emacsclient'. The regular 'emacs' command doesn't do that

NoStressHQ · 11-03-2016, 09:17 AM

Quote:

Originally Posted by drgibbon

Actually to connect to the server you need to run 'emacsclient'. The regular 'emacs' command doesn't do that

Alright I did it again... Should have tried it before guessing

.

Bests.