emacs-bug-tracker
[Top][All Lists]
Advanced

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

[Emacs-bug-tracker] bug#8143: closed (Fwd: emacs --daemon and emacsclien


From: GNU bug Tracking System
Subject: [Emacs-bug-tracker] bug#8143: closed (Fwd: emacs --daemon and emacsclient issue)
Date: Tue, 01 Mar 2011 14:39:02 +0000

Your message dated Tue, 01 Mar 2011 09:38:23 -0500
with message-id <address@hidden>
and subject line Re: bug#8143: Acknowledgement (Fwd: emacs --daemon and 
emacsclient issue)
has caused the GNU bug report #8143,
regarding Fwd: emacs --daemon and emacsclient issue
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
8143: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8143
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Fwd: emacs --daemon and emacsclient issue Date: Tue, 1 Mar 2011 12:14:14 +0530
Forwarding to bug mailing list.

---------- Forwarded message ----------
From: Noorul Islam <address@hidden>
Date: Mon, Feb 28, 2011 at 2:46 PM
Subject: emacs --daemon and emacsclient issue
To: Emacs Development <address@hidden>


With last weeks trunk build "emacs --daemon" is behaving in a strange
manner. I usually run "emacs --daemon" and then use "emacsclient -c"
to have any number of frames. But now what happens is, when I lock my
screen, after certain period my frames get closed automatically. But
"emacs --daemon" process is still running. If I try "emacsclient -c"
again, I get socket not found error asking me to start server again.
Anyone else facing similar problem? Since I no longer able to
communicate with the server I could not figure out for what reason it
broke. strace on the daemon is also not helping.

Thanks and Regards
Noorul



--- End Message ---
--- Begin Message --- Subject: Re: bug#8143: Acknowledgement (Fwd: emacs --daemon and emacsclient issue) Date: Tue, 01 Mar 2011 09:38:23 -0500 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)
> Please ignore this bug. Looks like an issue with one of my
> configuration file.

OK, thanks, closing,


        Stefan


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]