public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: Ruppert <dieter_ruppert@siemens.com>
To: nobody@sources.redhat.com
Cc: insight-prs@sources.redhat.com,
Subject: Re: insight/202: Error: bad text index "4"
Date: Thu, 14 Jul 2005 08:13:00 -0000	[thread overview]
Message-ID: <20050714081301.24043.qmail@sourceware.org> (raw)

The following reply was made to PR insight/202; it has been noted by GNATS.

From: Ruppert <dieter_ruppert@siemens.com>
To: insight-gnats@sources.redhat.com
Cc:  
Subject: Re: insight/202: Error: bad text index "4"
Date: Thu, 14 Jul 2005 10:06:08 +0200

 This is a simple bug in srctextwin.itb; the linenumber is missing from a 
 tag. Also, to be safe, it is better to create the tag if it is not 
 available.
 
 A patch for srctextwin.itb (relative to 6.1) fixes this:
 
 *** srctextwin.itb.orig Thu Jul 14 09:53:48 2005
 --- srctextwin.itb      Thu Jul 14 10:01:28 2005
 ***************
 *** 1378,1384 ****
        set other_tag [lindex $tag_list \
                       [lsearch -glob $tag_list {*[bt]p_tag}]]
        if {$other_tag == ""} {
 !       set stop 4
        } else {
          set stop [lindex [$win tag nextrange $other_tag \
                            $linenum.0 "$linenum.0 lineend"] 1]
 --- 1378,1384 ----
        set other_tag [lindex $tag_list \
                       [lsearch -glob $tag_list {*[bt]p_tag}]]
        if {$other_tag == ""} {
 !       set stop $linenum.4
        } else {
          set stop [lindex [$win tag nextrange $other_tag \
                            $linenum.0 "$linenum.0 lineend"] 1]
 ***************
 *** 1385,1392 ****
        }
 
        $win tag add $tag $linenum.0 $stop
 -     $win image configure $linenum.0 -image $break_images($img_name)
 
      }
    }
 
 --- 1385,1399 ----
        }
 
        $win tag add $tag $linenum.0 $stop
 
 +     # create tag if missing, otherwise: configure
 +
 +     if {$other_tag == ""} {
 +        $win image create $linenum.0 -image $break_images($img_name)
 +     } else {
 +        $win image configure $linenum.0 -image $break_images($img_name)
 +     }
 +
      }
    }
 
 


             reply	other threads:[~2005-07-14  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14  8:13 Ruppert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-09  3:08 kseitz
2005-04-23 18:03 Insight/202: " mozleron
2004-07-31 17:33 insight/202: " Bernhard Walle
2003-01-10 21:53 llewins

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=20050714081301.24043.qmail@sourceware.org \
    --to=dieter_ruppert@siemens.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=nobody@sources.redhat.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 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).