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

make it easy to delete default channels, servers and networks #45

Closed
tykling opened this Issue Jun 16, 2014 · 13 comments

Comments

Projects
None yet
3 participants
@tykling

tykling commented Jun 16, 2014

irssi comes with a lot of networks and servers in the default config. They are there to make it easier for new users to get started.

Please make it easier to remove all networks and servers to get a "clean slate".

@tykling tykling changed the title from /network remove * and /server remove * to make it easy to delete default channels, servers and networks Jun 16, 2014

ahf referenced this issue Jul 6, 2014

Updated the TARGMAX of the default servers.
Most servers were outdates with their current TARGMAX capab; everything
should be up to date now.
@GeertHauwaerts

This comment has been minimized.

Member

GeertHauwaerts commented Jul 6, 2014

The command syntax for /SERVER and /NETWORK have been rewritten and now include examples to remove a server or network.

See:

How would you suggest making it easier to get into a clean state? If somebody really wants to get rid of the default servers and network, they usually know how to do so.

@ahf

This comment has been minimized.

Member

ahf commented Jul 6, 2014

I think this problem is twofold:

Firstly, most of our users are unaware that adding a server that already exists is a modification operation rather than an add operation. Hopefully, getting better documentation out in the next release will help a bit with this, but I still suspect most people are unaware of this.

Secondly, who are we targeting? As far as I can tell, it's good that we have our default configuration with information about the most commonly used networks and their respective behaviour, but what we want is to let people switch our default servers out with whatever they prefer with whatever options they prefer easily.

I'm unsure how we should go around and implementing something that makes this easier. I don't think there's much we can do to our interface as it is right now without implementing some odd behaviour only to support this.

We do have the slightly odd MANUAL-WINDOWS default alias in our configuration. Not sure if we could do something like that for this.

@GeertHauwaerts

This comment has been minimized.

Member

GeertHauwaerts commented Jul 6, 2014

I have removed the MANUAL-WINDOWS alias just a few days ago since it really didn't belong there; a default alias should be not something you only use once.

I will write a section on how to do manual windows in other parts of the documentation; I haven't decided where, but it's on my TODO.

@ahf

This comment has been minimized.

Member

ahf commented Jul 6, 2014

Could we consider a -recursive option to /NETWORK REMOVE? Then our users can get rid of everything by only removing the networks (instead of now where they need to remove the channels, servers and networks).

@GeertHauwaerts

This comment has been minimized.

Member

GeertHauwaerts commented Jul 6, 2014

I prefer -all or * for consistency, but I do like the idea.

@ahf

This comment has been minimized.

Member

ahf commented Jul 6, 2014

It's not to remove all networks, it's to remove servers and channels together with the network.

@GeertHauwaerts

This comment has been minimized.

Member

GeertHauwaerts commented Jul 6, 2014

Then /NETWORK is not the place to do this, then you probably want something like:

  • /SERVER REMOVE -network Freenode -all
  • /SERVER REMOVE -network Freenode *
@GeertHauwaerts

This comment has been minimized.

Member

GeertHauwaerts commented Jul 6, 2014

Wait, now I can't follow you. /NETWORK REMOVE Freenode does remove all the associated servers and channels already together with the network.

I assumed what he wanted is a way to remove all networks, servers and channels.

@ahf

This comment has been minimized.

Member

ahf commented Jul 6, 2014

I don't understand why pushing it one level down the chain helps? My thought on having that option on /SERVER makes me think this will leave an empty network around (in the above case, the Freenode network).

Anyway, this is not something we absolutely must get in for 0.8.17, so we toy around with various solutions once the upcoming release is out.

@ahf

This comment has been minimized.

Member

ahf commented Jul 6, 2014

It currently doesn't. Start irssi --home=foobar, /network remove IRCnet, /save. Then you will still have references to IRCnet in the configuration.

@GeertHauwaerts

This comment has been minimized.

Member

GeertHauwaerts commented Jul 6, 2014

Then we should fix that first, before adding anything new :)

@GeertHauwaerts

This comment has been minimized.

Member

GeertHauwaerts commented Jul 6, 2014

I will open a feature request for this.

@ahf

This comment has been minimized.

Member

ahf commented Jul 6, 2014

Making /NETWORK REMOVE behave in the same way as I proposed for the -recursive option might be the best solution for now.

If someone is up for implementing this, feel free - it will probably get in for 0.8.18 then.

I do not think we should modify /SERVER REMOVE to behave in the same way though as channels are bound to networks not servers.

@GeertHauwaerts GeertHauwaerts added this to the 0.8.18 milestone Jul 30, 2014

ailin-nemui added a commit that referenced this issue Nov 9, 2015

Merge pull request #313 from isundil/master
Fix #45 Make it easy to delete default channels, servers and networks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment