It appears that the "send unknown slash commands as messages" option has disappeared with this release of Pidgin. Is there a way to enable it elsewhere? I found a page via Google that mentions some GTK config thing, but wasn't sure where I'd put that to re-enable this option.
Thanks in advance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The preference was removed and pidgin now sends unknown commands as messages on protocols which do not 'natively' or normally support /commands. On protocols which do support them the decision was that a mistype or extra space should not cause a command 'leak'. Those protocols are XMPP, IRC, and SILC.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Which would explain why on GTalk it's not working, since that's XMPP.
That's really a shame - why remove the option? Couldn't you just enable it by default (or disable it by default, but still leave it as an option)? I use the / in chat all the time for various things. Is there a workaround so that I can still do that?
It seems like with every release, the interface is getting more and more simplified. I'm hoping that in the long run, some of the advanced features and options will remain. Otherwise I'm going to have to downgrade and stick with an obsolete version. :(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The presence of the option really did confuse significantly more people than the lack of the option has seemed to hurt. If you want to send a message with a leading / you can use " /command" which should work just fine. "/ /command" will (oddly enough) send "/ /command" through literally though "/ command" will not work.
What 'advanced' features/options are you actually missing from pidgin at this point? And why do you need/want them?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I rather miss the old interface for away messages, and I've already mentioned that I'm not a fan of the new formatting toolbar.
I also prefer the old IM windows with the bottom buttons for warn, block, info, add, etc. I don't remember if the Gaim 1.5 log viewer allowed viewing all logs at once (e.g. select a user from a dropdown, instead of having to select a user to view their logs).. It's been awhile now since I've used 1.5, but I recall not upgrading to 2.0 before it was renamed Pidgin because the stuff I was used to had disappeared.
I understand that some change is inevitable, but the interface simplification seems to be unnecessary. Putting advanced features on an "advanced" tab in the settings dialog(s) generally allows hardcore users to get the features they want without confusing the rest of us. Considering that Gaim started out in Linux (IIRC, that is), I'd think you'd WANT to make the advanced stuff easily accessible to the geeky users.
Also: I posted a different thread with the dump file for the meanwhile plugin crashes I'm experiencing on a daily basis. I don't know what changed in that plugin between this version of Pidgin and the previous version, but that alone is going to force me to downgrade unless someone can figure out what that problem is - I use Sametime for work constantly, and I need something that won't crash constantly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It appears that the "send unknown slash commands as messages" option has disappeared with this release of Pidgin. Is there a way to enable it elsewhere? I found a page via Google that mentions some GTK config thing, but wasn't sure where I'd put that to re-enable this option.
Thanks in advance.
hmm weird. its working for me. what protocol are you using where you receive the error?
The preference was removed and pidgin now sends unknown commands as messages on protocols which do not 'natively' or normally support /commands. On protocols which do support them the decision was that a mistype or extra space should not cause a command 'leak'. Those protocols are XMPP, IRC, and SILC.
Which would explain why on GTalk it's not working, since that's XMPP.
That's really a shame - why remove the option? Couldn't you just enable it by default (or disable it by default, but still leave it as an option)? I use the / in chat all the time for various things. Is there a workaround so that I can still do that?
It seems like with every release, the interface is getting more and more simplified. I'm hoping that in the long run, some of the advanced features and options will remain. Otherwise I'm going to have to downgrade and stick with an obsolete version. :(
The presence of the option really did confuse significantly more people than the lack of the option has seemed to hurt. If you want to send a message with a leading / you can use " /command" which should work just fine. "/ /command" will (oddly enough) send "/ /command" through literally though "/ command" will not work.
What 'advanced' features/options are you actually missing from pidgin at this point? And why do you need/want them?
I rather miss the old interface for away messages, and I've already mentioned that I'm not a fan of the new formatting toolbar.
I also prefer the old IM windows with the bottom buttons for warn, block, info, add, etc. I don't remember if the Gaim 1.5 log viewer allowed viewing all logs at once (e.g. select a user from a dropdown, instead of having to select a user to view their logs).. It's been awhile now since I've used 1.5, but I recall not upgrading to 2.0 before it was renamed Pidgin because the stuff I was used to had disappeared.
I understand that some change is inevitable, but the interface simplification seems to be unnecessary. Putting advanced features on an "advanced" tab in the settings dialog(s) generally allows hardcore users to get the features they want without confusing the rest of us. Considering that Gaim started out in Linux (IIRC, that is), I'd think you'd WANT to make the advanced stuff easily accessible to the geeky users.
Also: I posted a different thread with the dump file for the meanwhile plugin crashes I'm experiencing on a daily basis. I don't know what changed in that plugin between this version of Pidgin and the previous version, but that alone is going to force me to downgrade unless someone can figure out what that problem is - I use Sametime for work constantly, and I need something that won't crash constantly.