<?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/tinyfugue/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/tinyfugue/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Thu, 06 Aug 2009 03:27:48 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/tinyfugue/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>block_comment.patch</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/13/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;This is a patch provides a way to block-comment tf code files using the "-" character at the beginning of a line.&lt;/p&gt;
&lt;p&gt;Example:&lt;br /&gt;
&amp;lt;snip&amp;gt;&lt;br /&gt;
/def t = /echo t&lt;br /&gt;
-&lt;br /&gt;
/def t2 = /echo t2&lt;br /&gt;
/def t3 = /echo t3&lt;br /&gt;
-&lt;br /&gt;
/def t4 = /echo t4&lt;br /&gt;
&amp;lt;snip&amp;gt;&lt;br /&gt;
defs t2 and t3 are ignored.&lt;/p&gt;
&lt;p&gt;Instructions:&lt;/p&gt;
&lt;p&gt;1) Copy the patch file into your tf-50b8 folder (where you would normally&lt;br /&gt;
type ./configure)&lt;/p&gt;
&lt;p&gt;2) Go into your tf-50b8 folder and test the patch file: patch --dry-run -p1 -i block_comment.patch&lt;/p&gt;
&lt;p&gt;If you get output like:&lt;/p&gt;
&lt;p&gt;patching file src/command.c&lt;/p&gt;
&lt;p&gt;.. then everything is set.&lt;/p&gt;
&lt;p&gt;3) Apply the patch: patch -p1 -i block_comment.patch&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">RPhillips</dc:creator><pubDate>Thu, 06 Aug 2009 03:27:48 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net474106f073bceaeeb5fe0a839b0dc02dd7458965</guid></item><item><title>Old style /fg switching</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/12/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;This is a patch that gives an additional flag variable: oldstyle_fg&lt;/p&gt;
&lt;p&gt;If applied set, tf-50b8 will do oldstyle world switching, where it just shows the ---- world ---- name, and the new text; without clearing the screen (like tf4).&lt;/p&gt;
&lt;p&gt;Example:&lt;br /&gt;
/set oldstyle_fg=1&lt;/p&gt;
&lt;p&gt;Instructions:&lt;/p&gt;
&lt;p&gt;1) Copy the patch file into your tf-50b8 folder (where you would normally type ./configure)&lt;/p&gt;
&lt;p&gt;2) Go into your tf-50b8 folder and test the patch file: patch --dry-run -p1 -i oldstyle_fg.patch&lt;/p&gt;
&lt;p&gt;If you get output like:&lt;br /&gt;
patching file src/output.c&lt;br /&gt;
patching file src/socket.c&lt;br /&gt;
patching file src/varlist.h&lt;br /&gt;
.. then everything is set.&lt;/p&gt;
&lt;p&gt;3) Apply the patch: patch -p1 -i oldstyle_fg.patch&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">RPhillips</dc:creator><pubDate>Wed, 05 Aug 2009 01:39:50 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net2d76df474397e1102895a79c0c200cb77a5ab439</guid></item><item><title>Keyboard input hook</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/11/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;I'd like to request the addition of a "keyboard input hook".  This allows a number of things, for example to disconnect from the mud after X mins of inactivity, regardless of trigger firing or /repeat's running.  just /hook KEYBINPUT = /repeat -X 1 /dc.   Other examples would include checking the status of and recasting various protection spells etc only when keyboard input is detected.  This is highly useful on mud where bots are frowned upon.&lt;/p&gt;
&lt;p&gt;Here's the code modifications needed:&lt;/p&gt;
&lt;p&gt;In hooklist.h add:&lt;br /&gt;
gencode(KEYBINPUT,0),&lt;/p&gt;
&lt;p&gt;In keyboard.c add:&lt;br /&gt;
do_hook(H_KEYBINPUT,NULL,"%d",1);&lt;/p&gt;
&lt;p&gt;just before the return of the "handle_input_line" function.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Wassman</dc:creator><pubDate>Tue, 16 Jun 2009 15:17:31 -0000</pubDate><guid isPermaLink="false">https://sourceforge.neta729df79757667dc10058d1d2bcfbe3120a8eb63</guid></item><item><title>SSL root CA check</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/10/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi.  There's a spiffy certificate authority out there that gives out free class 1 certificates.  startssl.com&lt;br /&gt;
They're trusted by mozilla/firefox as a legitimate root CA authority (if your certs are up to date.  Not yet with Microsoft)&lt;/p&gt;
&lt;p&gt;So now I'm able to (and I have) signed the certificate for my MUCK at telnets://latitude.muck.ca:992&lt;/p&gt;
&lt;p&gt;I'm not sure if tinyfugue can do this already or not, but I'd like to request to be able to verify the root authority in tinyfugue with openssl (Which on my system is configured to look in /etc/ssl/certs for trusted root certificates), and ensure the certificate is up to date and otherwise valid (and preferably even check for CRL revokations).&lt;/p&gt;
&lt;p&gt;This would protect me from man-in-the-middle attacks while connecting to my MUCK :)&lt;/p&gt;&lt;/div&gt;</description><pubDate>Tue, 26 May 2009 20:54:42 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net13730973a0c0ed5c1552b108978e9312e0cf16c1</guid></item><item><title>Bytewise character parsing interacts poorly with UTF-8</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/9/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;TinyFugue performs bytewise character parsing. Unfortunately, this interacts poorly with multibyte character encodings, such as UTF-8.&lt;/p&gt;
&lt;p&gt;The case we've noticed most often is the closing curly quote (0xe2809d). TinyFugue drops the high-order bit from the last byte, resulting in 0x1d (ctrl-]), which triggers the stock keybinding for /bg.&lt;/p&gt;
&lt;p&gt;This patch will:&lt;/p&gt;
&lt;p&gt;- Identify and leave UTF-8 characters unmolested (no high-order bit stripping, meta_esc processing).&lt;br /&gt;
- Skip over UTF-8 characters when locating macro keystrokes.&lt;br /&gt;
- Send UTF-8 characters to the remote world, which probably can't make much more sense of them, but allows a fighting chance.&lt;/p&gt;
&lt;p&gt;&lt;a href="http://horde.net/~jwm/software/misc/tf-handle-utf-8-somewhat-gracefully.patch" rel="nofollow"&gt;http://horde.net/~jwm/software/misc/tf-handle-utf-8-somewhat-gracefully.patch&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><pubDate>Sat, 10 Jan 2009 16:57:15 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net146a6599b96edfdccc46678a75b07cc6bb9ced50</guid></item><item><title>Add NOMORE hook (to complement MORE)</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/8/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;A NOMORE hook (to complement the MORE hook) would be useful.&lt;/p&gt;
&lt;p&gt;I recently wrote something[1] to watch my tf log and notify me[2] when highlighted patterns are matched. I wanted to have certain notification methods triggered *only* when tf was in backscroll (i.e., the world paused and More displayed) and needed a way to have tf communicate this status to outside applications. I added a NOMORE hook to complement the MORE hook and use these hooks:&lt;/p&gt;
&lt;p&gt;/hook MORE = /sys chmod -t ~jwm/.tf.log&lt;br /&gt;
/hook NOMORE = /sys chmod +t ~jwm/.tf.log&lt;/p&gt;
&lt;p&gt;to set/clear the sticky bit on my tf log to indicate whether tf is in backscroll. The attached patch seems to work correctly in that the NOMORE hook is only called when tf full emerges from pending backscroll (outcount == -1).&lt;/p&gt;
&lt;p&gt;[1] &lt;a href="http://horde.net/~jwm/software/misc/tf-notifier" rel="nofollow"&gt;http://horde.net/~jwm/software/misc/tf-notifier&lt;/a&gt;&lt;br /&gt;
[2] via e-mail/SMS, Mac OS X Growl, and/or Gnome libnotify&lt;/p&gt;&lt;/div&gt;</description><pubDate>Sat, 08 Nov 2008 15:49:59 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net9416a43d779aaebecb0bfe0417f9278e38853cc2</guid></item><item><title>Custom error prefix</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It seems some users can't tell the difference between game generated errors and client generated ones (% is kinda ambiguous). This would allow those of us who release public triggers to set a more meaningful prefix and those who just want something more noticeable than a percent sign.&lt;/p&gt;
&lt;p&gt;Should be an easy enough change, patch attached for your consideration.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">steve tremel</dc:creator><pubDate>Mon, 07 Jul 2008 00:15:59 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netac9b225a2cd2f4c32597d7344e2c3d0dc63fcc54</guid></item><item><title>Named processes...</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Named processes and infinite repeats.. For example:&lt;/p&gt;
&lt;p&gt;/ps -name mud_timer +11 -1 say Hello world.&lt;/p&gt;
&lt;p&gt;/kill -name mud_timer&lt;/p&gt;
&lt;p&gt;/pstickle -name mud_timer&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 19 Mar 2008 03:56:22 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc4da404ebc24f1c2d76f5c590e14de5b994d1eb6</guid></item><item><title>Embedded virtual windows</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The MUD I play on provides a map that updates with each movement into a new room.  With another client, I capture the output of the map (which is helpfully enclosed in HTML-like tags) and put it into a small "floating" window I have in the upper-right hand corner of the screen.&lt;/p&gt;
&lt;p&gt;This makes the map is always in the same place, and updates fluidly.  Could you please consider adding a feature to allow us to create sub-windows within world windows, and to direct output to it?&lt;/p&gt;
&lt;p&gt;I have attached a screenshot demonstrating the map window in my graphical windows client. (zmud, blech).  If I could get a map window in tf, I'd ditch zmud entirely and go back to tf.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Hilts</dc:creator><pubDate>Thu, 02 Aug 2007 18:49:08 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netf675d5d3ad48837f6353df3c3e78821094889029</guid></item><item><title>SQLite database support</title><link>https://sourceforge.net/p/tinyfugue/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Would it be possible to include functions to access SQLite database (and/or another database) from within tinyfugue? I have included a patch which includes some basic support for this, and a brief description of the functions follows.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Mark&lt;/p&gt;
&lt;p&gt;Functions:&lt;/p&gt;
&lt;p&gt;dbopen(filename)&lt;br /&gt;
- Opens a database.&lt;br /&gt;
- Returns the database handle if successful.&lt;br /&gt;
- Returns -1 if failed.&lt;br /&gt;
dbclose(db_handle)&lt;br /&gt;
- Closes a previously opened database.&lt;br /&gt;
- Returns 0 if successful.&lt;br /&gt;
- Returns -1 if an invalid handle is given.&lt;br /&gt;
dbprepare(db_handle, query)&lt;br /&gt;
- Sets up a prepared statement (SQL query) for later execution.&lt;br /&gt;
- Returns -1 if an invalid database handle is given.&lt;br /&gt;
- Returns -2 if there is another problem with the query.&lt;br /&gt;
- Otherwise returns a handle to the prepared statement for later use.&lt;/p&gt;
&lt;p&gt;- SQL statements here can contain question marks '?' which can have&lt;br /&gt;
values bound to them later using dbbind().&lt;br /&gt;
dbstep(statement_handle)&lt;br /&gt;
- Executes a prepared statement, returning a row at a time.&lt;br /&gt;
- Columns for each row are stored in the variables D0-D9, then DA-DZ&lt;br /&gt;
if there are more than 10 columns returned. If more than 36&lt;br /&gt;
columns are returned, further columns are discarded.&lt;br /&gt;
- Return values:&lt;br /&gt;
0  - Row returned&lt;br /&gt;
1  - Done. No more rows to return.&lt;br /&gt;
2  - Busy. Database may be locked by another process. Try again&lt;br /&gt;
later.  No rows have been returned.&lt;br /&gt;
-1 - Invalid statement handle given&lt;br /&gt;
-2 - Called incorrectly. E.g. after all rows returned and before&lt;br /&gt;
a reset or if the database has been closed.&lt;br /&gt;
-255 - Other error. Error message is printed.&lt;br /&gt;
dbbind(statement_handle, value, value, ...)&lt;br /&gt;
- Binds one or more values to a statement. If you bind too many&lt;br /&gt;
values, an error occurs. If you bind too few, the remaining ones&lt;br /&gt;
are null.&lt;br /&gt;
Example of a statement to bind values to:&lt;br /&gt;
SELECT * FROM tablename WHERE id=? and name=?;&lt;br /&gt;
- Return values:&lt;br /&gt;
0  - Success&lt;br /&gt;
-1 - Invalid statement handle given&lt;br /&gt;
-2 - Tried to bind too many paramaters&lt;br /&gt;
-3 - Called incorrectly. Perhaps the statement was finalized or&lt;br /&gt;
database closed.&lt;br /&gt;
-4 - Out of memory. Shouldn't happen.&lt;br /&gt;
-255 - Other error. Error message is printed.&lt;br /&gt;
dbreset(statement_handle)&lt;br /&gt;
- Resets a prepared statement so it can be executed again.&lt;br /&gt;
- Note: dbstep will automatically reset the statement once all rows&lt;br /&gt;
have been returned, but this is still useful if you don't want to&lt;br /&gt;
fetch any further rows and just want to start again.&lt;br /&gt;
- Returns 0 if successful, -1 if an invalid handle is given.&lt;br /&gt;
dbfinalize(statement_handle)&lt;br /&gt;
- Finalizes (closes/removes) a prepared statement when you have&lt;br /&gt;
finished using it.&lt;br /&gt;
- Sort of akin to dbclose() but for prepared statements.&lt;br /&gt;
- Returns 0 if successful, -1 if an invalid handle is given.&lt;/p&gt;
&lt;p&gt;Example code:&lt;/p&gt;
&lt;p&gt;/let db_handle=$[dbopen('filename.db')]&lt;br /&gt;
/let st_handle=$[dbprepare(db_handle, "SELECT * FROM tablename")]&lt;br /&gt;
/while (dbstep(st_handle) == 0) \
/echo %D0 %D1 %D2%;\
/done&lt;br /&gt;
/let retval=dbfinalize(st_handle)&lt;br /&gt;
/let retval=dbclose(db_handle)&lt;/p&gt;
&lt;p&gt;Or, with binding variables:&lt;br /&gt;
/let db_handle=$[dbopen('filename.db')]&lt;br /&gt;
/let st_handle=$[dbprepare(\
db_handle, "SELECT * FROM tablename WHERE id=?")]&lt;br /&gt;
/test db_bind(st_handle, 3)&lt;br /&gt;
/while (dbstep(st_handle) == 0) \
/echo %D0 %D1 %D2%;\
/done&lt;br /&gt;
/let somevar=4&lt;br /&gt;
/test db_bind(st_handle, somevar)&lt;br /&gt;
; Note - no need to call dbreset as this is done automatically when all&lt;br /&gt;
; rows are returned in the previous run through.&lt;br /&gt;
/while (dbstep(st_handle) == 0) \
/echo %D0 %D1 %D2%;\
/done&lt;br /&gt;
/test dbfinalize(st_handle)&lt;br /&gt;
/test dbclose(db_handle)&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Harrison</dc:creator><pubDate>Mon, 02 Jul 2007 10:08:22 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc0d6a2ec3dac358b1dcc381ca264a9ba6238e779</guid></item></channel></rss>