From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sourceware.cygnus.com
Subject: Re: feeding make window
Date: Fri, 23 Mar 2001 01:20:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010323011517.20984I-100000@cse.cygnus.com> (raw)
In-Reply-To: <3AB7C9F7.978679B2@super.org>
On Tue, 20 Mar 2001, Celia McInnis wrote:
> Celia McInnis wrote:
>
> > How do I feed info (eg., command and directory name) automatically (ie.,
> > from another program) to a make window? (Right now I have no problem
> > getting my application to open up a SN make window, but I have not been
> > able to change the command and directory listed in the window).
>
> I managed to answer my own question on this one. In case anyone else wants
> to do this, here's how - put the following somewhere in your .sn/rc.tcl
> file to have the make window execute "cat $MyFileName":
>
> set appname [winfo name .]
> send $appname {set make [sn_make]; $make.make setmakecommand "cat
> $MyFileName"; $make.make ExecMake}
>
> Note that "sn_make.make" seems to fail - whereas $make.make succeeds when
> $make is sn_make - I'm not sure why... If someone can tell me why, I'd be
> grateful!
The sn_make command will return a unique window name.
The Window name is also the name of the Itcl object,
so that is why you call a method via [$window setmakecommand]
and at the same time are able to run [winfo exists $window]
or other Tk window commands with the name of the window.
Some good reading on this subject can be found here:
http://tcltk.com/itcl/
http://tcltk.com/itk/
Mo DeJong
Red Hat Inc
next prev parent reply other threads:[~2001-03-23 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-19 8:43 Celia McInnis
2001-03-20 13:22 ` Celia McInnis
2001-03-20 23:05 ` Chad Bryant
2001-03-23 1:20 ` Mo DeJong [this message]
2001-04-17 7:23 ` Commands in build window? Celia McInnis
2001-04-17 8:59 ` Ian Roxborough
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=Pine.SOL.3.91.1010323011517.20984I-100000@cse.cygnus.com \
--to=mdejong@cygnus.com \
--cc=sourcenav@sourceware.cygnus.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).