unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
* bug#1467: 23.0.60; Cannot "emacsclient -c" to daemon started from tt1
@ 2008-12-01 20:03 pent
  0 siblings, 0 replies; 2+ messages in thread
From: pent @ 2008-12-01 20:03 UTC (permalink / raw)
  To: emacs-pretest-bug; +Cc: rfrancoise


0) Start X session.

1) Switch to tty1 or any other console terminal and run
  
   $ emacs --daemon

   Emacs server loads (correct).

2) Make sure you can connect to it by running

   $ emacsclient -t

   This should work from both tty and X sessions (correct).

3) Switch to X session and run

   $ emacsclient -c

   This fails with message

   Waiting for Emacs...
   *ERROR*: Display :0.0 can't be opened

I think it would be really nice if Emacs could easily survive X crash.

I'm ready to provide any additional info,
Andrey

In GNU Emacs 23.0.60.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11)
 of 2008-11-30 on elegiac, modified by Debian
 (emacs-snapshot package, version 1:20081129-1)
Windowing system distributor `The X.Org Foundation', version 11.0.10402000
configured using `configure  '--build' 'i486-linux-gnu' '--host' 'i486-linux-gnu' '--prefix=/usr' '--sharedstatedir=/var/lib' '--libexecdir=/usr/lib' '--localstatedir=/var' '--infodir=/usr/share/info' '--mandir=/usr/share/man' '--with-pop=yes' '--enable-locallisppath=/etc/emacs-snapshot:/etc/emacs:/usr/local/share/emacs/23.0.60/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/23.0.60/site-lisp:/usr/share/emacs/site-lisp' '--with-x=yes' '--with-x-toolkit=gtk' 'build_alias=i486-linux-gnu' 'host_alias=i486-linux-gnu' 'CFLAGS=-DDEBIAN -DSITELOAD_PURESIZE_EXTRA=5000 -g -O2' 'LDFLAGS=-g -Wl,--as-needed' 'CPPFLAGS=''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ru_RU.UTF-8
  value of $XMODIFIERS: nil
  locale-coding-system: utf-8-unix
  default-enable-multibyte-characters: t

Major mode: Info

Minor modes in effect:
  delete-selection-mode: t
  pc-selection-mode: t
  shell-dirtrack-mode: t
  tooltip-mode: t
  tool-bar-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  global-auto-composition-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  column-number-mode: t
  line-number-mode: t
  global-visual-line-mode: t
  visual-line-mode: t
  transient-mark-mode: t






^ permalink raw reply	[flat|nested] 2+ messages in thread

* bug#1467: 23.0.60; Cannot "emacsclient -c" to daemon started from tt1
@ 2008-12-27 15:14 Chong Yidong
  0 siblings, 0 replies; 2+ messages in thread
From: Chong Yidong @ 2008-12-27 15:14 UTC (permalink / raw)
  To: pent; +Cc: 1467

> 0) Start X session.
> 1) Switch to tty1 or any other console terminal and run
>    $ emacs --daemon
>    Emacs server loads (correct).
> 2) Make sure you can connect to it by running
>    $ emacsclient -t
>    This should work from both tty and X sessions (correct).
> 3) Switch to X session and run
>    $ emacsclient -c
>    This fails with message
>    Waiting for Emacs...
>    *ERROR*: Display :0.0 can't be opened

I can't reproduce this with the latest CVS.  Could you try that and see
if the bug is still present?






^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2008-12-27 15:14 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-12-27 15:14 bug#1467: 23.0.60; Cannot "emacsclient -c" to daemon started from tt1 Chong Yidong
  -- strict thread matches above, loose matches on Subject: below --
2008-12-01 20:03 pent

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).