From: "Dickinson, Derek" <Derek.Dickinson@icn.siemens.com>
To: "'Peter Graf'" <p.graf@itknet.de>, insight@sources.redhat.com
Subject: RE: Insight 6.1 Cygwin GUI
Date: Fri, 14 May 2004 14:54:00 -0000 [thread overview]
Message-ID: <EA78B62757AF1E4799828249310AC4CA05D17AF4@stca206a.bus.sc.rolm.com> (raw)
I've seen this problem in 6.0. However, the status bar reappears as soon as
I resize the Source Window.
Good Luck,
Derek
-----Original Message-----
From: insight-owner@sources.redhat.com
[mailto:insight-owner@sources.redhat.com] On Behalf Of Peter Graf
Sent: Friday, May 14, 2004 9:35 AM
To: insight@sources.redhat.com
Subject: Re: Insight 6.1 Cygwin GUI
Keith Seitz wrote:
>On Thu, 2004-05-13 at 03:42, Peter Graf wrote:
>
>
>>Is there an configuration option or make target I have to add? Or is
>>there a new runtime switch for the GUI?
>>
>>
>
>I think this should fix it:
>http://sources.redhat.com/ml/insight/2004-q2/msg00032.html
>
>
Many thanks! I had cygwin specific problems to rebuild configure, but
after switching to a Linux box for that, the rest worked fine.
I've noticed a different problem: The Source Display Status Bar
(offering file/function selection below the Toolbar) doesn't appear when
I invoke Insight 6.1 using the
-command <commandfile>
option. This still worked in 5.3. For me it's quite annoying, since I
used this feature very much. It can also be done by the Function browser
Menu, but not as quick. Any hints?
All the best
Peter
next reply other threads:[~2004-05-14 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 14:54 Dickinson, Derek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-14 18:42 Stephen P. Smith
2004-05-13 10:42 Peter Graf
2004-05-13 14:04 ` Keith Seitz
2004-05-14 13:34 ` Peter Graf
2004-05-14 13:38 ` Jon Beniston
2004-05-14 14:25 ` Peter Graf
2004-05-14 13:43 ` Keith Seitz
2004-05-14 14:22 ` Peter Graf
[not found] ` <40A510E8.4030701@cox.net>
2004-05-14 18:59 ` Keith Seitz
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=EA78B62757AF1E4799828249310AC4CA05D17AF4@stca206a.bus.sc.rolm.com \
--to=derek.dickinson@icn.siemens.com \
--cc=insight@sources.redhat.com \
--cc=p.graf@itknet.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).