git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amos Waterland <apw@us.ibm.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org, boutcher@cs.umn.edu
Subject: Re: [PATCH] do not open editor in dumb terminal
Date: Sat, 4 Feb 2006 19:37:41 -0500	[thread overview]
Message-ID: <20060205003741.GB29021@kvasir.watson.ibm.com> (raw)
In-Reply-To: <7vu0bgdxmh.fsf@assigned-by-dhcp.cox.net>

On Fri, Feb 03, 2006 at 11:56:54AM -0800, Junio C Hamano wrote:
> Amos Waterland <apw@us.ibm.com> writes:
> > Many people run git from a shell in emacs (obtained by M-x shell).  When
> > they try to do a commit without specifying a log message on the command
> > line with -m, git opens vi inside emacs, with unpleasant results.  I
> > think the right answer is to just refuse to open an editor in any dumb
> > terminal.
> 
> No, please don't.
> 
> I run 'git commit' from M-x shell or M-x compile.  My EDITOR is
> set to 'emacsclient' while inside Emacs.

If your TERM is set to `emacs' then that is fine.  If it is set to
`dumb' however, that seems a bit strange.  A dumb terminal is usually
understood to be one that does not have the ability to interpret control
sequences.

The reason I sent the patch is that people get a rather unpleasant
introduction to git when vi splatters control characters all over their
emacs session when they do their first commit.  I agree that people
probably should have their EDITOR set to emacsclient though, so if you
want to just leave the code as is that's cool with me.

  reply	other threads:[~2006-02-05  0:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03 11:41 [PATCH] do not open editor in dumb terminal Amos Waterland
2006-02-03 19:56 ` Junio C Hamano
2006-02-05  0:37   ` Amos Waterland [this message]
2006-02-05  1:58     ` H. Peter Anvin
2006-02-05  2:54     ` Junio C Hamano
2006-02-05  5:04       ` Daniel Barkalow
2006-02-05  5:48         ` Junio C Hamano
2006-02-05 17:44 ` Petr Baudis
2006-02-06  0:56   ` Junio C Hamano

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=20060205003741.GB29021@kvasir.watson.ibm.com \
    --to=apw@us.ibm.com \
    --cc=boutcher@cs.umn.edu \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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.
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 NNTP newsgroup(s).