Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove join, nick and whois inputs, they are cleanly handled by the server #208

Merged
merged 1 commit into from Mar 22, 2016

Conversation

xPaw
Copy link
Member

@xPaw xPaw commented Mar 20, 2016

Fixes #201

@maxpoulin64
Copy link
Member

👍

@maxpoulin64 maxpoulin64 added Type: Feature Tickets that describe a desired feature or PRs that add them to the project. second review needed labels Mar 20, 2016
@@ -17,7 +17,6 @@ $(function() {
"/notice",
"/op",
"/part",
"/query",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just wondering, why removing this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was an alias for /whois, and since that's gone, that wouldn't work.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So it was (see src/plugins/inputs/whois.js, below). I'm guessing @astorije assumed, as I did at first glance, that /query was an alias for /msg. That is the common usage among other clients.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well not exactly an alias for /msg, as some clients don't open a query window for /msg, and just show the message sent/received in the server window and only show a query window when you do /query.

But certanarily, I don't like that, so it's essentially the same thing. The important thing is that it opens a query window, but does /query still do a whois by default, or do you have to do /whois for that?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't recall using any client that auto-whois'd on /query, no. But I also don't recall using any that didn't open a query window for /msg, so maybe I have limited experience.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @xPaw, my bad for forgetting that /query was merely an alias for /whois...

@astorije
Copy link
Member

I'll test tomorrow and will merge then.

@astorije astorije self-assigned this Mar 21, 2016
@astorije
Copy link
Member

Tested locally and all of the removed commands (well, apart from /query) still work.
👍 and merging.

When releasing this, I will specify in the release introduction that the /query command was removed.

My understanding is that usually, people expect that:

  • /whois displays the whois data of the user. In our case, opening a message window that begins with that info.
  • /msg sends a message to another user and opens a chat window with displaying that message.
  • /query simply opens a chat window with a user.

Am I correct?

We are definitely losing the last option with this PR. Would it be possible to re-add /query so that it only opens an empty chat? Something custom like the /clear command The Lounge has for example. Ideally early enough so we can add it to the release that ships this PR.

Also, @dgw rightly mentioned that /msg doesn't open a chat window. It's another problem indeed, but was here before this PR.

astorije added a commit that referenced this pull request Mar 22, 2016
Remove join, nick and whois inputs, they are cleanly handled by the server
@astorije astorije merged commit eadcca0 into master Mar 22, 2016
@astorije astorije deleted the xpaw/remove-commands branch March 22, 2016 06:03
@astorije astorije added this to the 1.4.1 milestone Apr 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature Tickets that describe a desired feature or PRs that add them to the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants