From: Drew Adams <drew.adams@oracle.com>
To: Juanma Barranquero <lekktu@gmail.com>, Juri Linkov <juri@jurta.org>
Cc: EMACS development team <emacs-devel@gnu.org>
Subject: RE: Desktop tty frames (was: today's git does not run on Ubuntu)
Date: Sun, 15 Dec 2013 13:47:37 -0800 (PST) [thread overview]
Message-ID: <96023a12-0c3d-4141-8feb-0f9f67d8ff71@default> (raw)
In-Reply-To: <CAAeL0STZiWt-g=CAjRO+WWGMtNo7gwBgzjaVOinNV1xq=5ygaQ@mail.gmail.com>
> So I suppose the answer is:
> - do we want to default to non-GUI frames on POSIX -nw runs? If so, do
> we force them to tty frames or ignore them?
> - do we want to select this behavior through and option?
> - some other idea?
It sounds to me like a user might prefer either respecting what was
recorded or limiting to non-GUI (on -nw). So I'd guess that the
choice should be up to users, as an option.
next prev parent reply other threads:[~2013-12-15 21:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-15 13:56 today's git does not run on Ubuntu Susan Cragin
2013-12-15 15:20 ` Juanma Barranquero
2013-12-15 16:36 ` Eli Zaretskii
2013-12-15 17:02 ` Paul Eggert
2013-12-15 19:48 ` Desktop tty frames (was: today's git does not run on Ubuntu) Juri Linkov
2013-12-15 20:13 ` Juanma Barranquero
2013-12-15 20:52 ` Juanma Barranquero
2013-12-15 21:14 ` Desktop tty frames Juri Linkov
2013-12-15 21:52 ` Drew Adams
2013-12-15 21:56 ` Juanma Barranquero
2013-12-15 22:27 ` Drew Adams
2013-12-15 22:31 ` Juanma Barranquero
2013-12-16 0:27 ` Stephen J. Turnbull
2013-12-16 12:37 ` Juanma Barranquero
2013-12-16 14:55 ` Stephen J. Turnbull
2013-12-16 16:27 ` Juanma Barranquero
2013-12-16 16:36 ` chad
2013-12-16 16:38 ` Juanma Barranquero
2013-12-15 21:47 ` Drew Adams [this message]
2013-12-15 21:52 ` Desktop tty frames (was: today's git does not run on Ubuntu) Juanma Barranquero
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=96023a12-0c3d-4141-8feb-0f9f67d8ff71@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--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 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).