Gammon Forum

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.

Entire forum ➜ MUSHclient ➜ General ➜ Changing the default "send to"

Changing the default "send to"

It is now over 60 days since the last post. This thread is closed. Refresh page

Pages: 1 2

Posted by

Caelen (81 posts) Bio

Date

Sat 17 Jul 2010 01:55 AM (UTC)

Message

Is it possible to change the default "send to" for new aliases, triggers, and multi-line triggers to always be "send to script"? I rarely use any others now, and it'd be handy to not have to select that every time. A few of the other options would be nice to have set on by default too, like expand variables.

Twisol suggested recompiling mushclient to do this, but I don't have the slightest clue what that entails... ^^;

Posted by

Twisol USA (2,257 posts) Bio

Date

Reply #1 on Sat 17 Jul 2010 01:57 AM (UTC)

Message

Haha, it wasn't a serious suggestion! =/ I wouldn't really expect someone to modify and recompile the source for something like that.

'Soludra' on Achaea

Blog: http://jonathan.com/
GitHub: http://github.com/Twisol

Posted by

Caelen (81 posts) Bio

Date

Reply #2 on Sat 17 Jul 2010 01:59 AM (UTC)

Amended on Sat 17 Jul 2010 03:55 AM (UTC) by Caelen

Message

Hee, I thought as much. But now maybe we'll both find out if there's already a way to do it!

Edit: I see what you did there, Mr Nick! Pointing out options in the newest version... hehe.

Edit 2: But... I see no mention of 4.54 being released yet... *sits and waits*

Posted by

WillFa USA (525 posts) Bio

Date

Reply #3 on Sat 17 Jul 2010 04:09 AM (UTC)

Message

4.53 came out an hour before you posted... patience grasshopper. :)

Posted by

Nick Gammon Australia (23,122 posts) Bio Forum Administrator

Date

Reply #4 on Sat 17 Jul 2010 04:43 AM (UTC)

Message

I don't like to release two versions within a day of each other unless some major bug is found. Maybe someone else will have another brilliant idea. :)

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by

Twisol USA (2,257 posts) Bio

Date

Reply #5 on Sat 17 Jul 2010 04:52 AM (UTC)

Message

I prefer to always have aliases -not- keep evaluating, but triggers -always- keep evaluating, but I can't really set that default separately with the current setup. Same with case sensitivity (aliases never, triggers always). Any chance it could be improved to allow this?

'Soludra' on Achaea

Blog: http://jonathan.com/
GitHub: http://github.com/Twisol

Posted by

Nick Gammon Australia (23,122 posts) Bio Forum Administrator

Date

Reply #6 on Sat 17 Jul 2010 05:32 AM (UTC)

Message

OK well spotted before I even announced it, and I changed as you suggested Twisol.

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by

Nick Gammon Australia (23,122 posts) Bio Forum Administrator

Date

Reply #7 on Sat 17 Jul 2010 05:34 AM (UTC)

Message

Oh, and now is the time to speak if you seriously want to have other defaults (not just because they may vaguely sound good, but because you can make out a good case for it).

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by

WillFa USA (525 posts) Bio

Date

Reply #8 on Sat 17 Jul 2010 05:42 AM (UTC)

Message

Oooh!

Could we have XML Import warning go to the world like other scripting errors too?

Basically, make the window just go away unless it's actually needed for the Global plugins which might not have a world open. It's a little annoying to have an XML Import window pop up and cover the error and the whole hitting enter thing in annoyance to clear away a messagebox to move this XML Import window ends up being "edit" despite it just being labeled "OK" so it reopens the file which is usually already open and the cursor sitting at the lines in error, oops not anymore since the file's newly opened dang it, cursor's back at the top of the file and arghhhh. *stops and takes a breath*

Okay, it's very annoying. :)

Posted by

Nick Gammon Australia (23,122 posts) Bio Forum Administrator

Date

Reply #9 on Sat 17 Jul 2010 05:44 AM (UTC)

Amended on Sat 17 Jul 2010 05:45 AM (UTC) by Nick Gammon

Message

It does what?

You mean when loading plugins? Or pasting triggers? Or something else?

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by

WillFa USA (525 posts) Bio

Date

Reply #10 on Sat 17 Jul 2010 05:48 AM (UTC)

Message

It happens when you load a plugin with a typo in it (leave out a paren somewhere)

Posted by

Twisol USA (2,257 posts) Bio

Date

Reply #11 on Sat 17 Jul 2010 05:51 AM (UTC)

Amended on Sat 17 Jul 2010 05:54 AM (UTC) by Twisol

Message

Yes please! Totally unrelated to the topic, but I really hate how a new notepad-ish window is opened every time something goes wrong with an XML import. Being able to note the XML errors would be great.

I think a case could be made for not opening the editor when a plugin fails to load, too. Normal users don't care about the plugin code, and us developers can just hit Edit (which is, after all, right there on the plugin dialog), open it ourselves, or more likely than not use the editor we already have open.

WillFa said:
Global plugins which might not have a world open.

AFAIK, global plugins are only loaded into a world, just like every other plugin. The only special thing is that they're automatically loaded into every world.

Nick Gammon said:
OK well spotted before I even announced it

Technically, you did, in the post detailing the non-GUI options MUSHclient supports. ;)

'Soludra' on Achaea

Blog: http://jonathan.com/
GitHub: http://github.com/Twisol

Posted by

WillFa USA (525 posts) Bio

Date

Reply #12 on Sat 17 Jul 2010 05:56 AM (UTC)

Message

Twisol said:
Yes please! Totally unrelated to the topic...

True, but he did ask for other brilliant ideas. :)

Posted by

Nick Gammon Australia (23,122 posts) Bio Forum Administrator

Date

Reply #13 on Sat 17 Jul 2010 06:11 AM (UTC)

Amended on Sat 17 Jul 2010 06:12 AM (UTC) by Nick Gammon

Message

Well here's the problem. The loading sequence is such that IIRC plugins are loaded early on - certainly into a world document, but before the document is fully established. There is a point in world creation where the output font, font size, window size, wrap column etc. are established (that is, they are read from the world file). Before that it isn't possible to do notes to the output window.

This is why when loading plugins, if they do a note as part of the install process you won't see it. However if you reload the plugin later on, you *do* see it.

So, an error during world loading (including plugin loading) rather than nicely being visible in the output window would totally disappear, possibly causing a lot of confusion.

Still, maybe errors could be batched up. ;)

- Nick Gammon

www.gammon.com.au, www.mushclient.com

Posted by

Twisol USA (2,257 posts) Bio

Date

Reply #14 on Sat 17 Jul 2010 06:21 AM (UTC)

Message

Remind me again why plugins are just not loaded until everything's set up? Was it because it's done as soon as each <plugin> tag is read from the XML file?

(I think I just answered my own question there...)

'Soludra' on Achaea

Blog: http://jonathan.com/
GitHub: http://github.com/Twisol

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.

53,072 views.

This is page 1, subject is 2 pages long: 1 2

It is now over 60 days since the last post. This thread is closed. Refresh page

Go to topic: Search the forum

Information and images on this site are licensed under the Creative Commons Attribution 3.0 Australia License unless stated otherwise.