From: "andrés ramírez" <rrandresf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: alex.bennee@linaro.org, emacs-devel@gnu.org
Subject: opening an emacs frame on another display (was: Terminal locked when spawning a new tty frame)
Date: Thu, 17 Oct 2019 04:47:15 +0000 [thread overview]
Message-ID: <86zhi0q8q4.fsf@gmail.com> (raw)
In-Reply-To: <83o8ygelns.fsf@gnu.org>
Hi Eli.
Eli> I understand where you are coming from, but this is a mistake.
Eli> It is better to report a bug with whatever details you have, even
Eli> if you cannot reproduce it at will or in "emacs -Q". Why?
Eli> because someone else could try reproducing it, and if successful,
Eli> could then add more details, or even debug it and solve it.
Eli> So please do report it. If you cannot reproduce in "emacs -Q",
Eli> see if you can find the minimal .emacs that reproduces it -- if
Eli> you can afford the time necessary for dissecting your
Eli> customizations.
Eli> It would be better to post the *Backtrace* buffer with the bug
Eli> report. It will probably tell us something important about the
Eli> cause of the problem.
The *Backtrace* is very short:
--8<---------------cut here---------------start------------->8---
Debugger entered--Lisp error: (error "Connection lost to X server 'localhost:10.0'")
--8<---------------cut here---------------end--------------->8---
Best Regards
next prev parent reply other threads:[~2019-10-17 4:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 9:56 Terminal locked when spawning a new tty frame Alex Bennée
2019-10-16 10:25 ` Andreas Schwab
2019-10-23 13:31 ` Alex Bennée
2019-10-23 15:38 ` Andreas Schwab
2019-10-23 16:43 ` Alex Bennée
2019-10-23 16:58 ` Andreas Schwab
2019-10-23 17:48 ` Alex Bennée
2019-11-06 17:17 ` Alex Bennée
2019-10-16 15:12 ` rrandresf
2019-10-16 15:48 ` Eli Zaretskii
2019-10-17 4:47 ` andrés ramírez [this message]
2019-10-17 8:24 ` opening an emacs frame on another display (was: Terminal locked when spawning a new tty frame) Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86zhi0q8q4.fsf@gmail.com \
--to=rrandresf@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.