git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Brent Goodrick <bgoodr@gmail.com>, git@vger.kernel.org
Subject: Re: CR codes from git commands
Date: Thu, 22 Jan 2009 00:04:41 -0800	[thread overview]
Message-ID: <7vbptzahra.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0901220238380.19665@iabervon.org> (Daniel Barkalow's message of "Thu, 22 Jan 2009 02:46:57 -0500 (EST)")

Daniel Barkalow <barkalow@iabervon.org> writes:

> The terminal type, at least in my version of Emacs, is "dumb", which ought 
> to be sufficient to tell git that a pager isn't going to be useful is most 
> cases (might be worthwhile to keep "git log" from eating all your memory, 
> though), and that using CR to rewrite lines isn't going to work.

I think we pay attention to "dumb" when deciding if pager is useful and if
we can do color, but I do not think we check anything beyond "is it a tty"
when deciding to show progress or not.  The only thing we do differently
for "dumb" terminal is if we use ANSI clear-to-eol escape sequence or fill
with a run of SPs to overwrite trailing part of a line, and we assume even
dumb terminals know how to do a carriage-return.

  reply	other threads:[~2009-01-22  8:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20 16:26 CR codes from git commands Brent Goodrick
2009-01-20 17:08 ` Johannes Schindelin
     [not found]   ` <18806.44057.477379.215492@hungover.brentg.com>
     [not found]     ` <alpine.DEB.1.00.0901210930370.7929@racer>
2009-01-21 14:42       ` Brent Goodrick
2009-01-21 15:38         ` Johannes Schindelin
2009-01-22  4:00           ` Brent Goodrick
2009-01-22  4:47 ` Daniel Barkalow
2009-01-22  7:34   ` Brent Goodrick
2009-01-22  7:46     ` Daniel Barkalow
2009-01-22  8:04       ` Junio C Hamano [this message]
2009-01-22 10:04         ` Mike Ralphson
2009-01-22 16:13           ` Brent Goodrick
2009-01-22 16:41             ` Mike Ralphson
2009-01-22 16:50               ` Johannes Schindelin
2009-01-22 16:44             ` Daniel Barkalow
2009-01-22 16:52               ` Johannes Schindelin
2009-01-23 16:12                 ` Brent Goodrick
2009-01-23 16:59                   ` Junio C Hamano
2009-01-23 18:41                   ` Johannes Schindelin
2009-01-24 20:54                     ` Brent Goodrick
2009-01-24 21:14                       ` Johannes Schindelin
2009-01-25  9:19                       ` Boyd Stephen Smith Jr.
2009-01-25 18:47                         ` Brent Goodrick
2009-02-02  7:09                         ` Brent Goodrick
2009-01-25 20:35                       ` The lifecycle of a patch and the maintainer involvement 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=7vbptzahra.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.org \
    --cc=bgoodr@gmail.com \
    --cc=git@vger.kernel.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.
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).