Re: [Anjuta-list] Tools editor

[Biswapesh Chattopadhyay <biswapesh_chatterjee tcscal co in>]

The current buffer content might be too big to be placed in a variable.
However, you can use the current buffer as standard input to the tool
(see the tools editor GUI in latest CVS which has this option). This
should work quite well. There is no need to save the file in this case
since the buffer contents are sent directly to stdin of the tool.

Hope this helps.

Rgds,
Biswa.

On Fri, 2002-12-13 at 21:00, Erwan Becquet wrote:
> 
> 
> 
> Le 2002.12.13 04:21, Biswapesh Chattopadhyay a écrit :
> > On Thu, 2002-12-12 at 20:21, Erwan Becquet wrote:
> > >
> > > Hi,
> > >
> > > I use tools since yesterday and everything is ok. I just donwloaded
> > and
> > > installed last version and I must say that the list of variables is
> > very
> > > useful !
> > >
> >
> > Thanks - feel free to propose further additions to variables that you
> > think might be useful.
> 
> I think a variable $(current.buffer.content) could be useful. For
> example
> you type some things in a buffer, like a description and launch a tool
> to transform it or whatever... For example, if doing a little script to
> add more precise cvs support and only commit submodules of the project
> could write changes in a buffer and call myCommit ...
> 
> What do you think ? Or maybe this variable already exists ?
> 
> I know that for a named buffer, you just have to read file in the script
> (and you get only the last saved version ! not the real buffer content)
> but my problem is on a new buffer (Newfile#xx) and I just can't get the
> content ?
> 
> Thanks. Erwan.
> 
> (See attached file: InterScan_SafeStamp.txt)