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 20:13:56 +0300 [thread overview]
Message-ID: <83zkavidd7.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0jtL0FVbxA=77CrW+6t-_p=2tcB2zwJ40Ginh6DUkGvrA@mail.gmail.com>
> Date: Sun, 1 Apr 2012 10:44:35 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: lekktu@gmail.com, 11091@debbugs.gnu.org
>
> >> > [...] Emacs can create a graphical frame even if it was started in a
> >> > text-only terminal, provided it is able to connect to a graphical
> >> > display, and provided it can create graphical frames when started
> >> > from a text-only terminal.
> >>
> >> Isn't this wording a bit awkward? "Emacs can do X, provided it is
> >> able to do Y, and provided it can do X"
> >
> > I don't see anything awkward here. Using only one "provided that"
> > would produce an ambiguous sentence, so I used it twice.
>
> The problem are not the two "provided that", but having "X" as a
> prerequisite for itself.
Is this better?
@item -c
Create a new graphical frame, instead of using an existing Emacs
frame. Emacs can create a graphical frame even if it was started in a
text-only terminal, provided it is able to connect to a graphical
display. 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}). If you omit a filename argument
while supplying the @samp{-c} option, the new frame displays the
@samp{*scratch*} buffer (@pxref{Buffers}).
> >> On the "-t" option:
> >>
> >> > Create a new Emacs frame on the current text-only terminal, instead
> >> > of using an existing Emacs frame. If Emacs can open a text-only
> >> > terminal even if it was started in another text-only terminal, or on
> >> > a graphical display, it will create a text-only frame on the current
> >> > terminal.
> >>
> >> That is, "Do X instead of Y. If Emacs can do X even if Z, it will do
> >> X.". Not much clean, IMHO.
> >
> > The second "X" is not really a literal "X", it uses different
> > wording. I see no problem.
>
> The second sentence of this paragraph is IMO too long (not easy to parse).
How about this?
@item -t
@itemx --tty
@itemx -nw
Create a new Emacs frame on the current text-only terminal, instead of
using an existing Emacs frame. Emacs can open a text-only terminal
even if it was started in another text-only terminal, or on a
graphical display. On systems, such as MS-Windows, where this is
impossible, Emacs will create a new frame, either GUI or text-only, on
the same display where it was started. If you omit a filename
argument while supplying this option, the new frame displays the
@samp{*scratch*} buffer. @xref{Buffers}.
> >> Here the last part ("on the same terminal where...") gives the
> >> impression that the new frame will be created on a terminal,
> >> regardless of whether it is GUI or text-only.
> >
> > "Terminal" is used here in its Emacs sense, and you seem to think
> > about something slightly different.
>
> I think of "terminal" as a shell program designed to interact with the
> system using a text-only command-oriented interface. So far I've not
> seen in the manual other meanings for this. So, saying that a
> graphical Emacs frame will be created on a terminal marks no sense to
> me, but I can be wrong, of course.
I tried to fix that as well, see above.
> In short: I prefer my version of the doc fix
:-)
next prev parent reply other threads:[~2012-04-01 17:13 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 [this message]
2012-04-01 19:17 ` Dani Moncayo
2012-04-01 20:49 ` Eli Zaretskii
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=83zkavidd7.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.