Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ MUSHclient
➜ Bug reports
➜ Mapping bug
It is now over 60 days since the last post. This thread is closed.
Refresh page
Pages: 1
2
| Posted by
| Nick Gammon
Australia (23,173 posts) Bio
Forum Administrator |
| Date
| Reply #15 on Tue 11 Jun 2002 05:09 AM (UTC) |
| Message
| The option is actually "keep commands on prompt line".
What that really does is allow you to mix different "types" of data on one line.
Prior to that, MUSHclient always kept the following three types of output data on separate lines:
- Output from the MUD
- Commands you type
- World.note output
Thus, if MUSHclient had a line with (say) 30 characters of world.tell on it (without a newline) and got some MUD output, then the MUD output would commence a new line, as you would expect it to (because they are different things).
Similarly, if you had a prompt, and then typed a command it used to start a new line, eg.
<31hp 100m 110mv> north
Using identical logic, it started a new line - so you actually saw:
<31hp 100m 110mv>
north
However some people complained that the commands should really be on the same line as the prompt, hence that option. Now what it does is, if it is about to switch from:
MUD output ---> Your command
It doesn't start a new line.
However, that is not really detecting a prompt as such. It is detecting some MUD output that hasn't finished with a newline. eg. you might have:
-- 10% read -- [more] ---
Or even, just a partially-received line (because TCP/IP breaks data up into packets).
Thus, I don't think that I can say that if I have MUD output, that doesn't have a newline after it, that it is necessarily the prompt, and thus I can't detect a prompt particularly reliably. Let's remember this whole thread started because you wanted the mapper to be more reliable, so trying to add to the reliability with something that itself is not reliable, is not really going to help. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Shadowfyr
USA (1,792 posts) Bio
|
| Date
| Reply #16 on Tue 11 Jun 2002 07:03 PM (UTC) |
| Message
| | Ah.. Well not being clear on what it did I made an obvious error. It simply means that the mapper needs to be able to ID the prompt to work. I am not sure what I thought, except that maybe telnet had some sort of special packet for 'this is a prompt', but obviously not. ;) | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
51,766 views.
This is page 2, subject is 2 pages long: ![[Previous page]](/images/thin_prev.gif)
1
2
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top