So this is more than frustrating. I go to set up triggers and I can't hit enter in the response box. I have to cut and paste something else that is multiline into the box. Any idea why the enter key won't work? Same thing in aliases etc. Basically, any multi-line box in MUSHclient.
WINE + MUSHCLIENT = No multiline triggers :(
Posted by Keirath on Tue 27 May 2008 07:15 PM — 9 posts, 39,688 views.
Which field specifically are you trying to put a new line in? Is it the "Trigger" or "Send" field? Sometimes a newline escape code is required. The only time I ever wind up with this problem is with the test input window.
Also, which version of Wine and MUSHclient are you using?
Also, which version of Wine and MUSHclient are you using?
It's both of those fields.
Wine: wine-0.9.59
MUSHclient: 4.19
Wine: wine-0.9.59
MUSHclient: 4.19
First, some boxes are designed to not "receive" a return (for example, the command window, where you type something and hit <return>).
For such boxes, you can hit Ctrl+Enter. Or you should be able to, I can't get that to work right now running Ubuntu on the Mac under Parallels. ;) However I suspect that is a keyboard remapping issue.
Further testing on a PC running Ubuntu natively also exhibits this behaviour, I will have to investigate this. However on Windows, pressing Ctrl+Enter forces the entry of a newline, even into a box that is not "expecting" it.
On to your query, I am using Wine 0.9.33. The boxes work as designed for me, except I can't use Ctrl+Enter in the couple of places I expect to.
The trigger field does not expect multiple-line input, as you normally trigger on a single line. You can hit the "..." button to bring up a larger window, and if you need to - however it still does not expect a line break. For multi-line triggers you put \n into the trigger match field to signify a line break.
The send field however expects you to type multiple lines, and this works for me under Ubuntu running Wine. This applies to both triggers and aliases.
Which type and version of Linux are you using?
For such boxes, you can hit Ctrl+Enter. Or you should be able to, I can't get that to work right now running Ubuntu on the Mac under Parallels. ;) However I suspect that is a keyboard remapping issue.
Further testing on a PC running Ubuntu natively also exhibits this behaviour, I will have to investigate this. However on Windows, pressing Ctrl+Enter forces the entry of a newline, even into a box that is not "expecting" it.
On to your query, I am using Wine 0.9.33. The boxes work as designed for me, except I can't use Ctrl+Enter in the couple of places I expect to.
The trigger field does not expect multiple-line input, as you normally trigger on a single line. You can hit the "..." button to bring up a larger window, and if you need to - however it still does not expect a line break. For multi-line triggers you put \n into the trigger match field to signify a line break.
The send field however expects you to type multiple lines, and this works for me under Ubuntu running Wine. This applies to both triggers and aliases.
Which type and version of Linux are you using?
Further research seems to show potential problems with the way Wine handles the Ctrl+Enter combination.
Various messages on forums seem to be complaining about it, so it is not really a MUSHclient issue, as one that affects Wine.
However as I said, this should not stop you typing in multiple lines into the Send box for triggers and aliases, that seems to work for me, as you don't need to use Ctrl+Enter there.
Various messages on forums seem to be complaining about it, so it is not really a MUSHclient issue, as one that affects Wine.
However as I said, this should not stop you typing in multiple lines into the Send box for triggers and aliases, that seems to work for me, as you don't need to use Ctrl+Enter there.
I'm running Ubuntu. Hardy Heron. 64 bit.
Have you tried typing multiple lines into the Send box? I am not having a problem doing that here.
OK, well I installed Hardy Heron in another emulator window, and confirmed that the bug still persisted with wine 0.9.63 or whatever the lastest version was that came with Heron.
However, by upgrading to Wine release 1.0-rc2 the problem went away, so it is a bug in Wine, definitely. You can upgrade by following the instructions on this page:
http://www.winehq.org/site/download-deb
However, by upgrading to Wine release 1.0-rc2 the problem went away, so it is a bug in Wine, definitely. You can upgrade by following the instructions on this page:
http://www.winehq.org/site/download-deb
That fixed it. Thanks