HDTenEightyP/NetNews huggingface dataset:
From: x41@sun0.urz.uni-heidelberg.de (Werner Guenther)
Subject: Building shared tk & tcl libraries on AIX3.x
Organization: University of Heidelberg (Germany)
Date: Tue, 25 Aug 92 16:39:13 GMT

 I don't know if something similar has been posted before. 
Here are some patches to the tk2.3 distribution to build shared libraries
on an AIX 3.whatever system. The result was quite amazing, the size of 
'wish' was about 600k linked with static libraries and is around 10k now.
Please note that you have to install the libraries before making wish 
(or any other application) as the path to the libraries is stored in the
executables. This patch has been tested on 3.1.5 and 3.2.1 running X11R5
(should work with X11R3 too).

To apply the patch cd into the tk2.3 source tree and type 'patch -p <thisfile'

Good luck,
Werner Guenther
------------------------------------------------------------------------
*** Makefile.old	Fri Aug 14 23:38:12 1992
--- Makefile	Tue Aug 25 18:16:21 1992
***************
*** 28,36 ****
  #
  
  TCL_DIR		= tcl
! XLIB		= -lX11
  CC		= cc
! CFLAGS		= -I. -I$(TCL_DIR) -g -DTK_VERSION=\"2.2\"
  
  LIBS = libtk.a $(TCL_DIR)/libtcl.a
  
--- 28,36 ----
  #
  
  TCL_DIR		= tcl
! XLIB		= -L/usr/local/X11/lib -lX11
  CC		= cc
! CFLAGS		= -I/usr/local/X11/include -I. -I$(TCL_DIR) -g -DTK_VERSION=\"2.2\"
  
  LIBS = libtk.a $(TCL_DIR)/libtcl.a
  
***************
*** 73,81 ****
  	$(CC) $(CFLAGS) main.o $(LIBS) $(XLIB) -lm -o wish
  
  libtk.a: $(OBJS)
! 	rm -f libtk.a
! 	ar cr libtk.a $(OBJS)
! 	ranlib libtk.a
  
  $(TCL_DIR)/libtcl.a:
  	cd $(TCL_DIR); make libtcl.a
--- 73,86 ----
  	$(CC) $(CFLAGS) main.o $(LIBS) $(XLIB) -lm -o wish
  
  libtk.a: $(OBJS)
! 	rm -f $@~ shr.o
! 	ar clq $@~ $(OBJS)
! 	dump -g $@~ | sed -n -e 's/^[ 	]*[0-9][0-9]*[	 ]*\([^	 .][^	 ]*\)$$/\1/p' > $@.syms
! 	$(LD) -o shr.o $@~ -H512 -T512 -bM\:SRE -bE\:$@.syms -ltcl -lX11 -lc -lm -L$(TCL_DIR) $(XLIB)
! 	rm -f $@~
! 	ar clq $@~ shr.o
! 	rm -f $@.syms $@ shr.o
! 	mv $@~ $@
  
  $(TCL_DIR)/libtcl.a:
  	cd $(TCL_DIR); make libtcl.a
*** tcl/Makefile.old	Wed May 13 18:27:53 1992
--- tcl/Makefile	Tue Aug 25 18:13:15 1992
***************
*** 38,47 ****
  
  OBJS = ${GENERIC_OBJS} ${UNIX_OBJS} ${COMPAT_OBJS}
  
! libtcl.a: ${OBJS}
! 	rm -f libtcl.a
! 	ar cr libtcl.a ${OBJS}
! 	ranlib libtcl.a
  
  tclTest: tclTest.o libtcl.a
  	${CC} ${CFLAGS} tclTest.o libtcl.a -o tclTest
--- 38,52 ----
  
  OBJS = ${GENERIC_OBJS} ${UNIX_OBJS} ${COMPAT_OBJS}
  
! libtcl.a: $(OBJS)
! 	rm -f $@~ shr.o
! 	ar clq $@~ $(OBJS)
! 	dump -g $@~ | sed -n -e 's/^[ 	]*[0-9][0-9]*[	 ]*\([^	 .][^	 ]*\)$$/\1/p' > $@.syms
! 	$(LD) -o shr.o $@~ -H512 -T512 -bM\:SRE -bE\:$@.syms -lc
! 	rm -f $@~
! 	ar clq $@~ shr.o
! 	rm -f $@.syms $@ shr.o
! 	mv $@~ $@
  
  tclTest: tclTest.o libtcl.a
  	${CC} ${CFLAGS} tclTest.o libtcl.a -o tclTest
-- 
___________________________________________________________________________
Werner Guenther                | Computing Center, University of Heidelberg
x41@sun0.urz.uni-heidelberg.de | x41@aix0.urz.uni-heidelberg.de
x41@DHDURZ1.BITNET             |  
Newsgroups: comp.lang.tcl
From: karl@NeoSoft.com (Karl Lehenbauer)
Subject: Re: Announcing calc_object
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Wed, 02 Sep 1992 13:41:02 GMT

In article <TBRANNON.92Aug27085346@mars.csee.lehigh.edu> tbrannon@mars.csee.lehigh.edu (tbrannon) writes:
>set size [expr 5/([length "abcd" chars]+0.0)]

>Calc objects allow spacing between the + , - , / , and * operands
>while expr does not.

set size [expr {5 / ([length "abcd" chars] + 0.0)}]
-- 
-- Email info@NeoSoft.com for info on getting interactive Internet access.
You will now awaken feeling relaxed and refreshed, remembering everything 
you've read except the details of the Omega contingency plan.
From: smoot@gumby.cs.Berkeley.EDU (Stephen [Steve] R Smoot)
Newsgroups: comp.lang.tcl
Subject: wish -- command line editing
Followup-To: comp.lang.tcl
Date: 28 Aug 1992 22:56:40 GMT
Organization: UC Berkeley
Distribution: world
NNTP-Posting-Host: gumby.cs.berkeley.edu

Has anyone looked (or completed!) at adding tcsh-like command line 
editing to wish?

-s
Newsgroups: comp.lang.tcl,comp.databases,comp.databases.sybase
From: karl@NeoSoft.com (Karl Lehenbauer)
Newsgroups: comp.lang.tcl
Subject: Re: Help with expect inside TK/TCL
Date: 31 Aug 92 11:59:41 GMT
Organization: NeoSoft Communications Services -- (713) 684-5900

In article <1992Aug24.192950.23077@bwdls61.bnr.ca> muradia@bnr.ca writes:
>I have a progam written in TK/TCL that needs to invoke a program written in expect
>What is the best way to do this? I do not want to exec the expect program since
>it require some user input that I want to handle with TK. Any help would be 
>appreciated.

If you link Extended Tcl in with Tcl and Tk, you can use the "system"
command, as in:

	system "expect... &"
-- 
-- Email info@NeoSoft.com for info on getting interactive Internet access.
You will now awaken feeling relaxed and refreshed, remembering everything 
you've read except the details of the Omega contingency plan.
From: mycroft@hal.gnu.ai.mit.edu (Charles Hannum)
Newsgroups: comp.lang.tcl
Subject: Bug in autoload in 6.4
Date: 31 Aug 92 19:53:02 GMT
Organization: MIT Laboratory for Computer Science


For some reason, variables at the top-level of an autoloaded file are
not being propagated to the top level of my tcl interpreter (wish,
pish, tclTest, etc.).  Has anyone seen this problem before?

-- 
 \   Charles Hannum, mycroft@ai.mit.edu
 /\  White heterosexual atheist male (WHAM) pride!
Newsgroups: comp.lang.tcl
From: mathew@elroy.Jpl.Nasa.Gov (Mathew Yeates)
Subject: installation question
Organization: Image Analysis Systems Group, JPL
Date: Mon, 31 Aug 1992 20:32:55 GMT

I promise to go away quietly when this is built.
tk?? tcl? tclX??
which versions work with which other versions?

tcl 6.4 defines Tcl_GlobalEval in tclBasic.c. 
But tclX6.2b does not and replaces tclBasic.o in libtcl.a
And tk2.3 needs the symbol.

So..... I cannot build tk2.3 with this version of extended tcl.
Which versions should I use?

-Mathew
From: joe@athena.mit.edu (Joseph C Wang)
Newsgroups: comp.lang.tcl
Subject: Re: tk-style interface to other windowing systems
Date: 29 Aug 92 11:23:58 GMT
Organization: Massachusetts Institute of Technology

In article <1992Aug27.181758.27042@twg.com> "David Herron" <david@twg.com> writes:
[Possibilties for porting Tk to MS-Windows]

>1) Use MS-Windows soley to provide windows & graphics primitives.  This would
>be done the same as is currently done on top of Xlib.

>2) Do it as an encapsulation of MS-Windows widgets.  The `button' command
>would ultimately do whatever MS-Windows magic creates one of its button
>widgets, for instance.  MS-Windows events would be captured internally and
>fixed up so they become appropriate TK procedure calls.

>3) Create a 1-1 mapping of windows function calls and data structures to
>commands in TCL.  (Kind of like how WaFe is done).  Then proceed from there
>to somehow write an all new set of scripts for the user interface to
>the application.

I have a suggestion.......

Do 1), and then write a Tk initialization file so that MS-Windows
emulation is done in Tk instead on in C-code.  The advantage is that
you have the functionality of 2) with only the work of 1).  For one
thing, if you do things this way, you can grep the Tk code for the x
graphics primitives, and you'll know all the places that you need to
change.  

One BIG advantage in putting the Windows-like behavior in the Tk
initialization file is that you can get Windows-like behavior on a
unix X11 box through Tk.  This means that you can test your Windows
emulation on your sparcstation, while you are converting your C code.

In short, worry only about converting the graphics primitives while
you are converting C code.  Do all your worrying about getting
MS-Windows like behavior in Tk.

Also it would be really nice if while coding your new Windows-Tk, you
could arrange things so that all the system dependent calls are in one
file.  The Tk procedures would call procedures defined in a file
called "windows-primitives.c." To get an X application, one would call
procedures defined in a file "x11-primitives.c."  That way, it would
be possible for someone to port Tk be just writing a file
"mac-primitives.c" or "os2-primitives.c" or even maybe
"block-terminal-primitives.c"

Also, if you abstract away the system dependencies, then it would be
much, much easier to convert non-canonical Tk widgets to run in
MS-Windows.  Just use your graphics primitives instead of the X11
ones.

Whatever you do, don't do 3).  It's more work for you, and if you do 
either 1 or 2 instead of 3), we'll all be able to get our Tk scripts
running in MS-Windows.  In particular, if you do 1 or 2, I'll be able
to port my hypertext browser to MS-Windows and use Tk as a standard
hypertext interchange language.

Good luck!!!!!!!
From: joe@athena.mit.edu (Joseph C Wang)
Newsgroups: comp.lang.tcl
Subject: Re: Compiling tcl 6.3 with gcc 2.2.2
Date: 29 Aug 92 11:27:57 GMT
Organization: Massachusetts Institute of Technology

In article <WARSAW.92Aug28105321@anthem.nlm.nih.gov> warsaw@nlm.nih.gov (Barry A. Warsaw) writes:
[bugs in compiling tcl with gcc 2.2]

I've also noticed bugs you mentioned (needing -fno-builtin and
redefining open) on all the platforms I have gcc2.2 on (decmips, vax,
and rt)
Newsgroups: comp.lang.tcl
From: scott@sctc.com (Scott Hammond)
Subject: newbie tk question: extra window with 'wish -f'?  && border?
Organization: SCTC
Date: Mon, 31 Aug 1992 16:33:47 GMT

Trying to learn tk based on a demo fragment I've hacked.  
I have two questions:

1.  When I run this, I get two windows, one which wish puts up
automatically, and the one mkIcon puts up.  How do I get rid
of the first one?

2.  Neither window has a border visible on a white background (B&W
display).  How do I make a visible border on the mkIcon's window?

The code:


set auto_path "$tk_library/demos $auto_path"
#wm title . "Widget Demonstration"


proc mkIcon {{w .icon}} {
    global tk_library
    catch {destroy $w}
    toplevel $w
    dpos $w
    wm title $w "Iconic Button test"
    wm iconname $w "Icons"
    message $w.msg -font -Adobe-times-medium-r-normal--*-180* -aspect 300 \
            -text "This is a test"
    frame $w.frame -borderwidth 10
    pack append $w.frame \
        [button $w.frame.b1 -bitmap @$tk_library/demos/bitmaps/flagdown  \
                -command "iconCmd $w.frame.b1"] {left expand} \
        [frame $w.frame.right] {left expand}
    button $w.ok -text destroy -command "destroy $w"

    pack append $w $w.msg {top frame c} $w.frame {top expand fill} \
            $w.ok {bottom}

    return $w.frame.b1
}

proc iconCmd {w} {
    global tk_library
    set bitmap [lindex [$w config -bitmap] 4]
    if {$bitmap == "@$tk_library/demos/bitmaps/flagdown"} {
        $w config -bitmap @$tk_library/demos/bitmaps/flagup
    } else {
        $w config -bitmap @$tk_library/demos/bitmaps/flagdown
    }
}

# Position a dialog box at a reasonable place on the screen.

proc dpos w {
    wm geometry $w +300+300
}

set xyz [ mkIcon ]

puts stdout $xyz


--
Scott Hammond (scott@sctc.com)
From: adrianho@barkley.berkeley.edu (Adrian J Ho)
Newsgroups: comp.lang.tcl
Subject: Change of Tcl archive maintainer
Date: 26 Aug 92 17:13:50
Organization: University of California, Berkeley
NNTP-Posting-Host: barkley.berkeley.edu

[Sorry for the late notice -- things have been going to hell in a hurry.]

I'm handing off maintenance of the Tcl contrib archive to Jack Hsu
(jh@barkley.berkeley.edu) at least temporarily.  Please remember to
send email to

	tcl-archive@barkley.berkeley.edu

including a short description of whatever you upload to the /incoming
subdirectory of the archive.
--
-----------------------------------------------------------------------------
Adrian Ho, He With The *Dead* Passion           adrianho@barkley.berkeley.edu
Maintainer, Tcl/Tk Contrib Archive ---- barkley.berkeley.edu [128.32.142.237]
  Send all Tcl/Tk Archive-related stuff to tcl-archive@barkley.berkeley.edu
Newsgroups: comp.lang.tcl
From: mathew@elroy.Jpl.Nasa.Gov (Mathew Yeates)
Subject: extended Tcl 6.2b fails clock test
Organization: Image Analysis Systems Group, JPL
Date: Mon, 31 Aug 1992 19:01:23 GMT


I tried looking through the source but I can't figure it out.

The clock test 3-4 fails with 
==== clock-3.4 convertclock tests
==== Contents of test case:

    fmtclock [convertclock "Feb 14, 1992 12:20 PM"] {%D %r}

==== Result was:
02/13/92 09:20:00 PM
---- Result should have been:
02/14/92 12:20:00 PM
---- clock-3.4 FAILED


SunOS 4.1.1 and using the flags as given in Config.mk
Any clues?
Newsgroups: comp.lang.tcl
From: gaier@nova.tat.physik.uni-tuebingen.de (Karsten Gaier)
Subject: Re: errors in Tk2.3 demos
Organization: TAT (Theoretical Astrophysics Tuebingen), U. of Tuebingen, FRG
Date: Thu, 3 Sep 1992 11:25:49 GMT

gwlester@cpu.com (Gerald W. Lester) writes:

>In article <9209012315.AA06051@MATH13.CIMS.NYU.EDU>, walkerm@MATH13.CIMS.NYU.EDU (M.Walker) writes:
>> ...
>>invalid command name "tk_bindForTraversal"
>>	while executing
>> ...
>>Are there any changes I need to make?  Since I cannot install things in such 
>>places as /usr/local or /usr/lib, I installed the Tcl and Tk respectively in
>>$HOME/lib/tcl and $HOME/lib/tk where $HOME is /stumpy.a/misc/walkerm (along
>>with the various header files).  Wish is installed in $HOME/bin.  If there is
>>a problem with this installation, please let me know.

>Michael,

>	Sounds like you should check your tklibrary and tcllibrary variables.

I had the same problem. In wish.tcl you have to load some other files:

source [info library]/init.tcl
source $tk_library/button.tcl
source $tk_library/entry.tcl
source $tk_library/parray.tcl
source $tk_library/text.tcl
source $tk_library/menu.tcl
source $tk_library/tk.tcl

ciao, Karsten
From: gwlester@cpu.com (Gerald W. Lester)
Subject: Re: #!wish -f doesn't work
Organization: Computerized Processes Unlimited, Metairie, LA, (504)-889-2784
Date: Thu, 3 Sep 1992 13:30:00 GMT
Reply-To: gwlester@cpu.com

In article <1992Aug31.170411.26036@sierra.com>, jpalmer@sierra.com (Jeb Palmer) writes:

>2. "#!<full pathname to wish> -f returns:Permission denied

Jeb,

	This is the correct syntax.  My guess is that the system/shells are
truncateing the line on you (HP-UX does this at about 32!).  You have to the
the full path name down to something short (using links maybe?).   Let us know
if this was the only problem.

Good Luck!
From: markd@NeoSoft.com (Mark Diekhans)
Newsgroups: comp.lang.tcl
Subject: Update available for Extended Tcl
Date: 2 Sep 92 15:28:55 GMT
Organization: NeoSoft Communications Services -- (713) 684-5900


An an update is now available to bring Extended Tcl 6.2b up to version 6.4b.
This makes Extended Tcl compatible with Tcl 6.4 and Tk 2.3.  Some minor bugs
are fixed and Extended Tcl autoload mechanism is compatible with the Tk 2.3
demo  scripts.  Both the Tcl auto_path and the Extended Tcl TCLPATH variable
are honored when searching for auto-loadable procs.
   
It is available from barkley.berkeley.edu:

  tcl/extensions/tclX6.4b.upd.tar.Z

If your have any questions or problems, please mail:

         tcl-project@NeoSoft.com (uupsi!sugar!tcl-project).

Thanks and happy Tcl programming!
Newsgroups: comp.lang.tcl
From: mpm@bnr.ca (Mike Mogridge)
Subject: *geometry: specification grief
Organization: Bell-Northern Research, Ottawa, Canada
Date: Mon, 31 Aug 92 19:10:27 GMT

I've been running our Tk based application for months now with no problems ...
until now.  The problem is a *geometry: +5+64 specification that gets loaded
into the X server by another application.  If after this has occurred someone
runs our Tk application, prost, we get the following error:

bad geometry "+5+64": expected widthxheight
    while executing
"frame .menu -relief raised -borderwidth 0"
    (file "/usr/lab/bin/prost" line 1531)
    invoked from within
"source /usr/lab/bin/prost"

I've been told geometry specifications of this form are valid (ie. to simply
position windows).  So what should I do?  Can I
a) get our Tk application to ignore this specification somehow?
b) explicitly set something via the option add ... Tk command?

We're running tk1.4 (yeah I know 2.3 is available but 1.4 works great for what
we need; is the version the problem?)

Modifying the other application to remove the offending geometry specification
is *not* an option.

Any help would be appreciated.
Thanks,
Mike.
-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Mike Mogridge               | "Just once I wish we could encounter an      <
> Bell-Northern Research Ltd. |  alien menace that wasn't immune to bullets."<
> P.O. Box 3511 Station C     |       -The Brigadier, Doctor Who.            <
> Ottawa, ONT, Canada K1Y 4H7 |  INTERNET: mpm@bnr.ca                        <
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: vek@allegra.att.com (Van Kelly)
Newsgroups: comp.lang.tcl
Subject: Periodic Actions in Tcl/Tk
Date: 31 Aug 92 15:56:50 GMT
Organization: AT&T Bell Laboratories, Murray Hill, NJ, USA


What is the best way to define a period action (say, once every n seconds)
in a Tcl/TclX/Tk environment, given that there may be a number of these
one might wish to set up and later selectively cancel at a later date.

The first thing I thought of was to have a global variable, say FOO,
containing the code for a periodic action followed by an after command
to re-evaluate itself.  But this is obviously tail-recursive and may
explode its stack pretty fast.  If one could define a bunch of
pseudo-clocks as normal X-events to which one could bind actions, that would
clearly be a better approch, but there's no obvious way to do this in Tcl(X).

Any advice?  Email responses and followup posts are both satisfactory.

Van Kelly
vek@allegra.att.com
From: walkerm@MATH13.CIMS.NYU.EDU (M.Walker)
Newsgroups: comp.lang.tcl
Subject: errors in Tk2.3 demos
Date: 1 Sep 92 23:15:01 GMT
Organization: New York University

I am new to the Tk/Tcl world, so please bare with me.  I first built version 2.2
of the Tk library and tested it.  It worked well.  Then one the same day, version
2.3 was released (to my dismay :-().  Well any way, I built the new version of Tk.
When I tried any of the demos, I got the following errors:

invalid command name "tk_bindForTraversal"
	while executing
"error "invalid command name \"$name\"""
	(procedure "unknown" line 38)
	invoked from within
"tk_bindForTraversal Entry"
	(file "/stumpy.a/misc/walkerm/lib/tk/tk.tcl" line 81)
	invoked from within
"source $tk_library/tk.tcl"
	(file "/stumpy.a/misc/walkerm/lib/tk/wish.tcl" line 21)
	invoked from within
"source $tk_library/wish.tcl"

Are there any changes I need to make?  Since I cannot install things in such 
places as /usr/local or /usr/lib, I installed the Tcl and Tk respectively in
$HOME/lib/tcl and $HOME/lib/tk where $HOME is /stumpy.a/misc/walkerm (along
with the various header files).  Wish is installed in $HOME/bin.  If there is
a problem with this installation, please let me know.

Thanks in advance.

Michael A. Walker
Courant Institute of Mathematical Sciences
New York University
walkerm@math13.cims.nyu.edu
Newsgroups: comp.lang.tcl
From: "David Herron" <david@twg.com>
Subject: Re: tk-style interface to other windowing systems
Sensitivity: Personal
Encoding:  27 TEXT 
Conversion: Prohibited
Organization: The Wollongong Group, Inc., Palo Alto, CA
Conversion-With-Loss: Prohibited
Date: Mon, 31 Aug 1992 21:44:44 GMT

[My long posting deleted ...]

joe@athena.mit.edu (Joseph C Wang) writes:

> Do 1), and then write a Tk initialization file so that MS-Windows
> emulation is done in Tk instead on in C-code.  The advantage is that
> you have the functionality of 2) with only the work of 1).  For one
> thing, if you do things this way, you can grep the Tk code for the x
> graphics primitives, and you'll know all the places that you need to
> change.  

But this doesn't promote code re-use.  As the MicroSoft guys improve
and fix their code we wouldn't see the improvements unless we also
improved and fixed our emulation of their code.  This is why I preferred
the second route (of encapsulating the MS-Windows widgets into
tk-like commands).

Don't get me wrong, you have some good points and good suggestions
for another way of code reuse (resuing tk's code).  Your route also
gives us the problem of keeping up with tk's improvements &c, unless
these changes were to become part of the mainstream tk source base.
As Jon comes out with new releases we'd have to re-do the port over
to MS-Windows (and whatever-else-Windows)...

I'll spend some time this evening looking at this...

	David
From: jbuck@forney.berkeley.edu (Joe Buck)
Newsgroups: comp.lang.tcl
Subject: Re: Compiling tcl 6.3 with gcc 2.2.2
Date: 29 Aug 1992 21:37:44 GMT
Organization: U. C. Berkeley
NNTP-Posting-Host: forney.berkeley.edu

In article <1992Aug29.112757.11363@athena.mit.edu> joe@athena.mit.edu (Joseph C Wang) writes:
>I've also noticed bugs you mentioned (needing -fno-builtin and
>redefining open) on all the platforms I have gcc2.2 on (decmips, vax,
>and rt)

This is a Tcl bug, as ANSI C and Posix have agreed on what the prototype
for open and other functions is, and the Tcl prototypes don't agree with
the standard.  gcc's builtin definitions and those it builds with the
"fixincludes" script are correct; Tcl is wrong.



--
Joe Buck	jbuck@ohm.berkeley.edu
Newsgroups: comp.lang.tcl
From: tja@cpu.com (Thomas J. Accardo)
Subject: trace vinfo bug
Organization: Computerized Processes Unlimited Inc.
Date: Thu, 27 Aug 1992 20:52:32 GMT

Found a problem with the trace command in tcl 6.4.  If I set up a few
traces and then delete one, "trace vinfo" returns a bit of garbage.
All of the commands tied to the remaining traces still work, but
"trace vinfo" is confused.

tcl> info tclversion
6.4
tcl> trace variable x w {echo 1}
tcl> trace variable x w {echo 2}
tcl> trace variable x w {echo 3}
tcl> trace variable x w {echo 4}
tcl> trace variable x w {echo 5}
tcl> trace vinfo x
{w {echo 5}} {w {echo 4}} {w {echo 3}} {w {echo 2}} {w {echo 1}}
tcl> # everything seems fine up to this point....
tcl> trace vdelete x w {echo 3}
tcl> # ...but not I can't get the proper set of commands from "trace vinfo x"
tcl> trace vinfo x
{w {echo 5 }} {w {echo 4 dex($}} {w {echo 2 g ind}} {w {echo 1 e: ea}}
tcl> # The command still behaves as expected, though
tcl> set x 4
5 x  w
4 x  w
2 x  w
1 x  w
4
tcl> trace vinfo x
{w {echo 5 }} {w {echo 4 dex($}} {w {echo 2 g ind}} {w {echo 1 e: ea}}


tja

-------------------------------------
Thomas J. Accardo         tja@cpu.com
Computerized Processes Unlimited, Inc.
Metairie, LA
Newsgroups: comp.lang.tcl
From: bytor@grumpy.bellcore.com (Ross Huitt)
Subject: read-only tags
Organization: Bellcore
Date: Wed, 26 Aug 92 16:12:11 GMT

Is there some set of magic bindings that will let me define a text tag to be
read-only? Unfortunately, the tag level bindings do not override the text
widget bindings, so I can't just do it there. Any clues? I obviously don't
have one...

Ross Huitt
bytor@ctt.bellcore.com
Newsgroups: comp.lang.tcl