All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Robin Moussu <robin.moussu@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [bug] first line truncated with `git log --oneline --decorate --graph`
Date: Thu, 16 Apr 2015 08:28:43 -0700	[thread overview]
Message-ID: <xmqqwq1chz2s.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <552F8B85.2000908@gmail.com> (Robin Moussu's message of "Thu, 16 Apr 2015 12:14:29 +0200")

Robin Moussu <robin.moussu@gmail.com> writes:

> I have a bug using the following command:
>
>     git log --oneline --decorate --graph
>
> In short, the first line of the log is often truncated.
> ...
> # How to reproduce
>
> Open a small terminal windows (4*100)
>
>     mkdir tmp
>     cd tmp
>     git init
>     git commit --allow-empty -m 'Lorem ipsum dolor sit amet, consectetur
> adipiscing elit. Donec a diam lectus.'
>     git checkout -b long_branch_name_and_long_commit_name
>     git commit --allow-empty -m 'Maecenas congue ligula ac quam viverra
> nec consectetur ante hendrerit.'
>     git commit --allow-empty -m 'Praesent et diam eget libero egestas
> mattis sit amet vitae augue.'
>     git checkout master
>     git merge --no-ff long_branch_name_and_long_commit_name -m 'merge
> with a long commit message'
>     git checkout long_branch_name_and_long_commit_name
>     git merge master
>     git log --oneline  --decorate --graph
>
> I hope it is clear. The English is not my mother tongue.

It is clear and it does not reproduce for me.  I see

--------
*   5eff3a3 (HEAD -> long_branch_name_and_long_commit_name, master) merge with a long commit message
|\  
| * 61e21f3 Praesent et diam eget libero egestas mattis sit amet vitae augue.
:
--------

which looks perfectly sensible (my terminal is a "screen" running
on a Ubuntu machine, displaying to a SecureShell terminal on a
Chromebook).

Can you try running that problematic "git log" with its standard
output redirected to a file (i.e. "git log ... >output") and then
run your pager in that wide-but-short terminal (i.e. "less output"),
to see if the same problem is observed?  And then run "cat output"
in a taller terminal with the same width to see if it is the output
from "git log" that is causing you the problem?

  reply	other threads:[~2015-04-16 15:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 10:14 [bug] first line truncated with `git log --oneline --decorate --graph` Robin Moussu
2015-04-16 15:28 ` Junio C Hamano [this message]
2015-04-16 15:42   ` Johannes Schindelin
2015-04-16 15:56     ` David Miller
2015-04-16 16:11       ` git-owner, was " Johannes Schindelin
2015-04-16 16:26         ` Jeff King
2015-04-16 16:31           ` David Miller
2015-04-16 17:06             ` Johannes Schindelin
2015-04-17  7:14               ` Johannes Schindelin
2015-04-16 16:54         ` Robin Moussu

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=xmqqwq1chz2s.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=robin.moussu@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.
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.