<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/expect/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/expect/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 07 Apr 2024 10:49:06 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/expect/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>#8 move VCS to git</title><link>https://sourceforge.net/p/expect/feature-requests/8/?limit=25#4be1</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I agree. This is on my to-do list, I'm afraid I've very much neglected expect since covid.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nils Carlson</dc:creator><pubDate>Sun, 07 Apr 2024 10:49:06 -0000</pubDate><guid>https://sourceforge.nete3092d14823a7a014ea73d12be1ef5b284a39357</guid></item><item><title>move VCS to git</title><link>https://sourceforge.net/p/expect/feature-requests/8/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be good to move VCS from cvs to git.&lt;br/&gt;
As long as sf.net VCS web interface sucks it would be good to move as well VCS from sf.net to github/gitlab.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tomasz K&amp;#322;oczko</dc:creator><pubDate>Sun, 20 Aug 2023 12:26:56 -0000</pubDate><guid>https://sourceforge.netffbbeebe4e12252ac113001ba9ec1d1cf052df73</guid></item><item><title>Allow editing the current command</title><link>https://sourceforge.net/p/expect/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;expect1.1&amp;gt; puts oooooops^[[D&lt;br /&gt;
^-------- left key&lt;/p&gt;
&lt;p&gt;+ i.e. add a cursor&lt;br /&gt;
+ allow insertion&lt;br /&gt;
+ allow deletion of other than the last character (BKSP &amp;amp; DEL)&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">heinrichmartin</dc:creator><pubDate>Wed, 21 Dec 2011 10:37:20 -0000</pubDate><guid>https://sourceforge.nete50b18dcfde9c69205618bbccb97b490dadd9c11</guid></item><item><title>Add command history to interactive Expect</title><link>https://sourceforge.net/p/expect/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;expect1.1&amp;gt; puts 42&lt;br /&gt;
bla&lt;br /&gt;
expect1.2&amp;gt; ^[[A&lt;br /&gt;
^-------- up key&lt;/p&gt;
&lt;p&gt;+ a history per session is helpful already (eg for typos)&lt;br /&gt;
+ a persistent history is the next step&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">heinrichmartin</dc:creator><pubDate>Wed, 21 Dec 2011 10:35:08 -0000</pubDate><guid>https://sourceforge.net59922942ddd2c38905b4a5863491cedb6250d417</guid></item><item><title>Thread-safe Expect</title><link>https://sourceforge.net/p/expect/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I would like to see changes made to Expectto make it thread safe. I have several iTcl applications where I want to add threading to allow concurrent interaction with many of our products. Unfortunately, I was unable to do this in a nice OO way due to the fact that Expect is currently thread unsafe, at least it is on Windows. I'm not sure of it's state on other OSs but all my apps are being used by folks that have Windows boxes so I would like this. At this point I am going to spawn several processes and use comm to "simulate" the desired behavior but this means the user will see a ton of new processes being spawned for a single applicaiton and this is not a very friendly approach. If you can make the needed changes it would be much appreciated! :) Thanks!&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Robert Joy</dc:creator><pubDate>Mon, 30 Nov 2009 18:09:11 -0000</pubDate><guid>https://sourceforge.netf72fd3072649f85a54a531e869a1212a710b982f</guid></item><item><title>Merge expect 5.39.0 source into sf.net</title><link>https://sourceforge.net/p/expect/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It really is a shame that the sf.net cvs has to play&lt;br /&gt;
catchup.&lt;/p&gt;
&lt;p&gt;But, since that's how things work, I would like to&lt;br /&gt;
request that&lt;br /&gt;
someone incorporate the changes from the July 31&lt;br /&gt;
release of expect into the sf.net cvs and then,&lt;br /&gt;
hopefully, 'release' the source so that the sf project&lt;br /&gt;
tracks the nist releases.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 11 Sep 2003 11:54:54 -0000</pubDate><guid>https://sourceforge.net409ac53ccaa02372c445da0ba988a391711b5cfc</guid></item><item><title>Add copies of the docs to sf.net doc manager</title><link>https://sourceforge.net/p/expect/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;There doesn't appear to be any official online Expect&lt;br /&gt;
documentation, which seems a shame.&lt;/p&gt;
&lt;p&gt;It would be useful to put the Expect docs up online&lt;br /&gt;
here on sf.net.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larry W. Virden</dc:creator><pubDate>Fri, 28 Mar 2003 12:20:45 -0000</pubDate><guid>https://sourceforge.net3d7de320e76cf080b6d72eed7ceb5580c3d8cf23</guid></item><item><title>Integrate Don's 5.33 release</title><link>https://sourceforge.net/p/expect/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I would like to request that the sf.net project&lt;br /&gt;
integrate Don Libes expect 5.33 release from&lt;br /&gt;
&lt;a href="http://expect.nist.gov/" rel="nofollow"&gt;http://expect.nist.gov/&lt;/a&gt; and then release the files&lt;br /&gt;
here so that others who come to this site actually&lt;br /&gt;
have files that can be downloaded.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Larry W. Virden</dc:creator><pubDate>Tue, 02 Oct 2001 13:18:15 -0000</pubDate><guid>https://sourceforge.net469ca82a849dcba654a4d6d7803571bd6cfb8af2</guid></item><item><title>RFE: make exit functionality similar2tcl</title><link>https://sourceforge.net/p/expect/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;The expect interpreter calls Tcl_Exit function at the end to terminate a&lt;br /&gt;
script. Due to this, we cannot do additional cleanup (ie. collect&lt;br /&gt;
profiling data and save it in a file) on exit.&lt;/p&gt;
&lt;p&gt;Would it be reasonable to ask that the exit functionality of expect be&lt;br /&gt;
changed to follow that of the tclsh interpreter?&lt;/p&gt;
&lt;p&gt;Here's the relevant code from tclMain.c file that should replace the&lt;br /&gt;
Tcl_Exit function call in exp_main_exp.c file:&lt;/p&gt;
&lt;p&gt;/* need to declare buffer[1000] variable */&lt;/p&gt;
&lt;p&gt;/*&lt;br /&gt;
* Rather than calling exit, invoke the &amp;amp;quot;exit&amp;amp;quot; command so that&lt;br /&gt;
* users can replace &amp;amp;quot;exit&amp;amp;quot; with some other command to do additional&lt;br /&gt;
* cleanup on exit.  The Tcl_Eval call should never return.&lt;br /&gt;
*/&lt;/p&gt;
&lt;p&gt;sprintf(buffer, &amp;amp;quot;exit %d&amp;amp;quot;, exitCode);&lt;br /&gt;
Tcl_Eval(interp, buffer);&lt;/p&gt;
&lt;p&gt;The Tcl_Exit function is invoked in the following files.&lt;/p&gt;
&lt;p&gt;godel&amp;amp;gt; fgrep -l Tcl_Exit *.c&lt;br /&gt;
exp_command.c&lt;br /&gt;
exp_main_exp.c&lt;br /&gt;
exp_main_sub.c&lt;br /&gt;
exp_main_tk.c&lt;br /&gt;
exp_tty.c&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Hemang Lavana</dc:creator><pubDate>Fri, 06 Jul 2001 13:08:42 -0000</pubDate><guid>https://sourceforge.neta7431bc0ac36f8d62af50d73284763d784b5c88f</guid></item></channel></rss>