All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Grün" <christian.gruen@gmail.com>
To: stefan.naewe@atlas-elektronik.com
Cc: git@vger.kernel.org
Subject: Re: Resizing panels in the gitk window
Date: Fri, 6 May 2022 11:01:55 +0200	[thread overview]
Message-ID: <CAP94bnNw7rjiYQtv5k5vznwOi8tgQxzmJ3Wc_6Fvu9aXWqcPZQ@mail.gmail.com> (raw)
In-Reply-To: <ff856dc509c7424cb7137d9cac318714@atlas-elektronik.com>

Thanks, Stefan. I use Windows 10 Pro (latest version, 10.0.19044 Build
19044) and git version 2.36.0.windows.1.



On Fri, May 6, 2022 at 10:32 AM <stefan.naewe@atlas-elektronik.com> wrote:
>
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Christian Grün <christian.gruen@gmail.com>
> > Gesendet: Freitag, 6. Mai 2022 09:46
> > An: git@vger.kernel.org
> > Betreff: Re: Resizing panels in the gitk window
> >
> > Maybe there’s a better place to address gitk? Anyone?
> > Thanks  in advance, Christian
>
> I think it would be a good idea to at least say on which OS you're using gitk
> and which version of git is installed.
>
> Regards,
>   Stefan
>
> >
> > On Thu, May 5, 2022 at 9:01 AM Christian Grün <christian.gruen@gmail.com>
> > wrote:
> > >
> > > Resizing panels in the gitk window leads to a error message that’s presented
> > multiple times in a dialog:
> > >
> > > expected integer but got ""
> > > expected integer but got ""
> > >     while executing
> > > "$win sash place 0 $sash0 [lindex $s0 1]"
> > >     (procedure "resizeclistpanes" line 38)
> > >     invoked from within
> > > "resizeclistpanes .tf.histframe.pwclist 1834"
> > >     (command bound to event)
> > >
> > > Is this a known bug?
> > >
> > > I’ll be happy to give more details.
> > > Best, Christian
> > >

      reply	other threads:[~2022-05-06  9:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAP94bnOyrx6hCmWSjmejVfopUydk10ga42wJzm1M4nk_OXn9Mg@mail.gmail.com>
2022-05-05  7:06 ` Resizing panels in the gitk window Christian Grün
2022-05-06 12:00   ` Matthias Aßhauer
2022-05-06 12:12     ` Christian Grün
2022-05-06 16:23     ` Junio C Hamano
2022-05-09 12:46       ` Halil SEN
2022-05-09 17:11         ` Junio C Hamano
2022-05-11  8:20           ` Paul Mackerras
2022-05-11 15:08             ` Junio C Hamano
     [not found]           ` <CAOeUTusOW1=cDKNhrBCzdzfbVLmY_qb7yg114ukRfy904S34uA@mail.gmail.com>
2022-05-11  8:21             ` Paul Mackerras
2022-05-11 15:25               ` Junio C Hamano
2022-05-11  8:17       ` Paul Mackerras
2022-05-06  7:46 ` Christian Grün
2022-05-06  8:32   ` AW: " stefan.naewe
2022-05-06  9:01     ` Christian Grün [this message]

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=CAP94bnNw7rjiYQtv5k5vznwOi8tgQxzmJ3Wc_6Fvu9aXWqcPZQ@mail.gmail.com \
    --to=christian.gruen@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=stefan.naewe@atlas-elektronik.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.