|Anonymous | Login | Signup for a new account||2017-04-26 01:12 WAT|
|My View | View Issues | Roadmap | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001221||Anope Development (1.9.x series)||MemoServ||public||2010-12-26 20:41||2015-07-17 17:17|
|Target Version||Fixed in Version|
|Summary||0001221: /memoserv read all|
|Description||What's chances of having a "read all" command for MemoServ ?|
There's a "del all" command .. so yeah can this be swapped around?
|Tags||No tags attached.|
Since this was requested, I added Pull request 0000130 on GitHub.
|This is an interesting idea. I suppose it's possible, but the concept already exists in a different feature. (See Above). Not that my opinion matters at all.|
As someone above already pointed out, you already can do this in another way:
Lets say you have for example 16 memos, then you do this: /MS READ 1-16
and it will show you all the memos from 1 to 16 at once.
Also, MemoServ will show you all new memos at once if you do: /MS READ NEW
See /MS HELP READ for full details.
So, in a way, this already exists anyway.
i liked that idea too, BUT read all should definitely be default disabled and config enableable.
Why: if you have a limit of 100 memos/user they wont type /quote ms read 1-100 very often, but i fear they would type read all.
So if you have a more relaxed memo limit (we have a limit of 500 and me and some other users have ~400 memos), it would generate quite a lot traffic, if you had like 20 users that would "read all" every x mins... (services reaching ircd sendq limit and getting disconnected ;)
|2010-12-26 20:41||CereaL||New Issue|
|2011-10-30 14:36||someone||Note Added: 0005989|
|2011-11-04 12:08||Robby||Note Added: 0006005|
|2013-12-16 17:21||Yoerger||Note Added: 0006555|
|2015-07-17 17:17||AlphaTech||Note Added: 0006747|
|Copyright © 2000 - 2017 MantisBT Team|