Zugg Software :: View topic - [2.01] Tilde, ~, inserts extra space (not to be confused with ~ as quote char)

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

test~1
on the command input is changed to
test 1

Worth noting the space is only added when there is no space before the tilde. So "test ~1" is fine, but "test~1" is wrong

Novice Joined: 17 Aug 2007 Posts: 34

In preferences, the ~ is used as a quote character.

If you go under preferences and uncheck the box next to ~ in Scripting->Special Characters it displays perfectly.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

That's not what I'm getting at. It's inserting an extra space
"test~1" should show "test1" but instead it's showing "test 1"

Novice Joined: 17 Aug 2007 Posts: 34

Oh. When I did it, it showed test1 =/ . That's why I said that.

I can test again later.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Just a bump because Zugg's responded to most other bugs and this has dropped a way down

Novice Joined: 17 Aug 2007 Posts: 34

I can't get it to happen on my side.

Posted: Tue Aug 28, 2007 6:57 pm

This is a strange one, I got it to happen for me once. The first time I did I got the space as Guinn described, then I tried "test~l" without the quotes and it displayed as expected. The I tried it with a few single digit numbers and the displayed as expected. Finally I tried "test~1" again it displayed properly.

I also tried it with another session I already had open, it displayed properly there as well.

I closed all my CMUD instances, started it again and tried it from a blank session. the first time I do it I get the space as Guinn describes, after that it works as expected.

Really weird.

Posted: Tue Aug 28, 2007 7:14 pm

I'm also seeing this bug only in the first command that's entered.

1) Open CMUD
2) Close the Sessions dialogue with the X
3) Enter "test~1" on the command line - "test 1" is displayed
4) Press enter again - "test1" is displayed.

Apprentice Joined: 13 Aug 2007 Posts: 166

Wierd, when I do "#SHOW test~1", it shows "test1", just like it should.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

So do I win 'weirdest bug of 2.01' award? :)

I was actually trying first to write
blah#
and getting a parsing error, so that's why I did blah~#
and it put the space in.

Might be a second bug with the blah# where the smart command line could be smarter to realise that there's no command required when # is by itself or at the end of a word?

Posted: Wed Aug 29, 2007 8:17 pm

OK, that is pretty weird! I have reproduced it, but I have no idea what is causing it. Each time you enter something on the command line, it gets executed in a new thread.

Well, actually, I guess CMUD *does* reuse threads from it's "pool", so maybe something isn't getting initialized the first time a thread is used.

Added to bug list.