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

using /part I am still asked if I really want to leave #300

Open
computersarecool opened this issue Dec 21, 2016 · 4 comments
Open

using /part I am still asked if I really want to leave #300

computersarecool opened this issue Dec 21, 2016 · 4 comments
Milestone

Comments

@computersarecool
Copy link

If I type /part I leave the IRC channel. However, the buffer stays open and when I attempt to kill it I get a Really leave this channel? (y or n) message.

This is the same as if I just did not part the channel in the first place.

Is there any reason to use part then? It just creates and extra step. Would it be possible to part and close the buffer?

@jorgenschaefer jorgenschaefer added this to the Backlog milestone Dec 21, 2016
@jorgenschaefer
Copy link
Collaborator

The correct solution would be not to ask to part the channel when killing a buffer for a channel we're not in, I think.

@computersarecool
Copy link
Author

I am not sure I follow.... I think the solutions would be:

A. (Most optimal) To be prompted for a parting message when you C-k a channel (this would act as a confirmation as well).

B. Making /part kill the buffer as well

C. Not prompting for Are you sure when you have left the channel (as I think you mention).

What do you feel?

@jorgenschaefer
Copy link
Collaborator

Hm. I have to think about (A), I see why it might be a good idea, but it conflicts with some assumptions I had so far. Thank you for that suggestion.

@computersarecool
Copy link
Author

computersarecool commented Dec 22, 2016

I am sure you have more priorities, I just do not like being asked for what I consider to parting prompts. Great software though, the only one that lets me use Freenode from Amazon AWS because it supports SASL.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants