Mini-Edit Session?

CthulhuMud Discussion

Moderators: mgmirkin, Bast, Quanqued, Moderators

Post Reply
Jebediah Noyes
Mi-Go Brain-Bait
Mi-Go Brain-Bait
Posts: 4
Joined: Sun Dec 02, 2007 11:56 am
Location: Upstate NY

Mini-Edit Session?

Post by Jebediah Noyes »

My Description is all messed up.
How does the mini-edit session work, other than the obvious ~ or @ to end it?
I can get that to work. But .h doesn't give me Help at all.
I can't find anything about Mini-edits on the website.

I am defaulting to Append mode and just keep making it worse when I try to erase / fix it.
What other modes are there and how do I access them?
Also, why doesn't ".h" work?

Any help or a list of commands / instructions would be appreciated.

Thanks,
Jebediah Noyes
Raymond
Scholar
Scholar
Posts: 47
Joined: Sat Feb 12, 2005 9:52 am

Post by Raymond »

Hello Jebediah,
probably your MUD client is having trouble with the initial dot in ".h" and is not sending the command to the MUD at all.

One suggestion (thanks to Quanqued!) is to add a tilde "~" before the command. That is, use "~.h". This should make it sure that your editor is correctly sending the command to the MUD server.

Another suggestion (what I usually do when i'm editing something) is to disable command parsing. If you're using zMud, you can just type CTRL+R to toggle parsing on/off. With command parsing disabled, commands will be sent straight as they are, and aliases won't be expanded when they shouldn't (e.g. "to me" becoming "take obsidian me").

Send a hey if this didn't work!

Raymond
We will all diiiiiiiiiiiiiee! *goes catatonic*
Quanqued
Librarian
Librarian
Posts: 61
Joined: Sun Sep 19, 2004 1:53 pm
Location: USA
Contact:

Post by Quanqued »

As a side note, the ~ only applies to ZMud. I've attached the output from '.h' for the info. Note that the dot commands need to be placed at the beginning of a new line. You should probably just clear the whole thing and start over (using .c).

Code: Select all

-=======- Entering APPEND Mode -========-
    Type .h on a new line for help
 Terminate with a ~ or @ on a blank line.
-=======================================-

> Sedit help (commands on blank line):
.r 'old' 'new'   - replace a substring
.rl <line> <text> - replaces a line
.h               - get help &#40;this info&#41;
.s               - show string so far
.f               - format and wordwrap string
.w               - wordwrap string only
.c               - clear string so far
.d <line>        - deletes a line
.dl              - deletes last line
.i <line> &#123;text&#125; - inserts a line
./ <command>     - do a regular command
.?                - show string
@                - end string
>
~Quanqued

=============================
- "Who says mortality can't be overcome?"
- "Well yeah, the trick is avoiding the death part."

For more prompt responses, please use the in-game boards, or email: cthulhumud@foxpaws.net
Jebediah Noyes
Mi-Go Brain-Bait
Mi-Go Brain-Bait
Posts: 4
Joined: Sun Dec 02, 2007 11:56 am
Location: Upstate NY

Mini-Editing Revisited

Post by Jebediah Noyes »

Thanks for trying to help me, but it's only getting worse.

I've tried .c on a blank line and .dl to supposedly erase the last line. None of these are having the desired effect. I'm using Fire Client 2.14, if that helps the troubleshoot.

I just keep adding more junk to my description, and it's getting very frustrating.
If you are an Admin, LOOK at Jebnoyes and see what I'm talking about, or catch me in the game if we coincide.

What can I do to clear my whole description that will actually work?
Can I enter any Mode other than Append?
Please note that I (obviously) have almost no experience with this kind of editing interface. I only used to program a little BASIC back in the day. None of this stuff is obvious or intuitive to me.

I've read the command list and tried several of them. No luck whatsoever.

Please help!

Thanks,
Jebediah Noyes
Khlak
Mi-Go Brain-Bait
Mi-Go Brain-Bait
Posts: 3
Joined: Fri Feb 08, 2008 12:13 am

Post by Khlak »

My bit of advice in-game was based on v2.13 of the client (I didn't know it'd been updated recently), but I've just now installed a copy of 2.14, and got through the mini-edit with no trouble.

No idea if it'll help, but these are the options as they're set in my copy of the program:

Code: Select all

General
=======
Ansi enabled
local echo
autodetect IMP
autohighlight web links
autocopy highlighted
triggers enabled
sounds enabled
paths expanded
toggle icon
wrap history

Fonts/Colors
========
Courier New, 9pt. Black bg with white text

ANSI
====
untouched

IMP/Fire Portal
=========
IMP enabled
Font changes enabled
images enabled

Other
=====
expression separator    ;
command character      /
path character              .
end=line character      LF

Logging
=====
single file
If none of this works, and you don't want to learn a new client, temporarily logging into the game through the barebones telnet client (I think most OSes have one) just to edit your desc might be an option. A clunky, somewhat frustrating option. But one nonetheless. And it does have the benefit of not doing anything fancy, so the input is sent straight through with no pre-processing to muck it up.
Blargh
Neophyte
Neophyte
Posts: 18
Joined: Mon Jun 06, 2005 8:05 am
Location: Australia

Post by Blargh »

I find Fireclient likes you to use a space in front of your editor commands, for example " .c" on a blank line. If that's what you were already doing and it's not working, then disregard this.
END COMMUNICATION!
Jebediah Noyes
Mi-Go Brain-Bait
Mi-Go Brain-Bait
Posts: 4
Joined: Sun Dec 02, 2007 11:56 am
Location: Upstate NY

Thanks!

Post by Jebediah Noyes »

Thanks, Khlak, for going to all the trouble of testing FireClient 2.14 for me.
I compared your settings to mine and found that the Fonts and Logging where different -- don't see how those could be factors though. But the "IMP enabled" was not enabled in my configuration previously. I did so, but I still couldn't get my desired commands to take in Mini-Edit. Thanks though, for all your time!

The IMP thing might have played a role though, because Blargh's advice to put a space before the command worked! Thanks! I was able to at least clear my description.

I suspect the combined advice from both of you did the trick.

Thanks again!

Jebediah Noyes
Blargh
Neophyte
Neophyte
Posts: 18
Joined: Mon Jun 06, 2005 8:05 am
Location: Australia

Post by Blargh »

I'm fairly certain Fireclient is just picky like that. I went through the same issue looong ago. The piece of advice that did the trick for me was the same as what I told you. The space just seems to be needed for Fireclient.
END COMMUNICATION!
Quanqued
Librarian
Librarian
Posts: 61
Joined: Sun Sep 19, 2004 1:53 pm
Location: USA
Contact:

Post by Quanqued »

I'd be willing to bet if you changed your path character from . to some other character it would work. Since it's . then Fireclient will think that the dot commands are actually supposed to be interpreted as paths.
~Quanqued

=============================
- "Who says mortality can't be overcome?"
- "Well yeah, the trick is avoiding the death part."

For more prompt responses, please use the in-game boards, or email: cthulhumud@foxpaws.net
Post Reply