From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: lekktu@gmail.com, 11091@debbugs.gnu.org
Subject: bug#11091: 24.0.94; emacsclient -t
Date: Sun, 01 Apr 2012 23:49:30 +0300 [thread overview]
Message-ID: <83y5qfi3dx.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0iHB6WkSCu66iM7GJjPW4C7k87YY_BpM99AaOTSkcAa8g@mail.gmail.com>
> Date: Sun, 1 Apr 2012 21:17:58 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: lekktu@gmail.com, 11091@debbugs.gnu.org
>
> > If it is unable to connect to a graphical display, and on
> > systems, such as MS-Windows, where it cannot create graphical frames
> > when started from a text-only terminal, Emacs creates a new text-only
> > terminal frame (@pxref{Frames}).
>
> It's unclear from that in which terminal will be created the new
> text-only frame (whether on the current one or on the server one).
I added "on the same terminal where it was started".
> :( I still wonder what was wrong with my version.
It was too wordy.
> Thanks for your work on Emacs.
Thanks for helping me clarify the text.
next prev parent reply other threads:[~2012-04-01 20:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 22:10 bug#11091: 24.0.94; emacsclient -t Dani Moncayo
2012-03-25 22:29 ` Dani Moncayo
2012-03-25 23:39 ` Juanma Barranquero
2012-03-25 23:45 ` Juanma Barranquero
2012-03-26 6:40 ` Dani Moncayo
2012-03-26 9:19 ` Juanma Barranquero
2012-03-26 9:25 ` Dani Moncayo
2012-03-26 9:27 ` Juanma Barranquero
2012-03-26 22:49 ` Dani Moncayo
2012-03-31 9:54 ` Eli Zaretskii
2012-03-31 11:38 ` Dani Moncayo
2012-03-31 11:45 ` Dani Moncayo
2012-04-11 16:40 ` Glenn Morris
2012-04-11 19:53 ` Dani Moncayo
2012-03-31 12:34 ` Eli Zaretskii
2012-04-01 8:44 ` Dani Moncayo
2012-04-01 17:13 ` Eli Zaretskii
2012-04-01 19:17 ` Dani Moncayo
2012-04-01 20:49 ` Eli Zaretskii [this message]
2012-04-02 7:01 ` Dani Moncayo
2012-04-02 17:36 ` Eli Zaretskii
2012-03-26 12:39 ` Stefan Monnier
2012-03-26 14:03 ` Juanma Barranquero
2012-03-26 19:15 ` 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=83y5qfi3dx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11091@debbugs.gnu.org \
--cc=dmoncayo@gmail.com \
--cc=lekktu@gmail.com \
/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.