Open ayust opened 12 years ago
I'm all for it - but perhaps /twirssi_help
? Or, I think there's a way to integrate with irssi's /help
tree, so we could add the /twirssi
commands there.
What, didn't mean to close it.
just to clarify, you have tried /twi<TAB><TAB><TAB>
right? :-)
Rather inefficient when you consider that there are about 50 commands.
Also, wouldn't be a bad idea to be able to add some inline documentation.
On Sat, Oct 15, 2011 at 16:45, Amber Yust < reply@reply.github.com>wrote:
Rather inefficient when you consider that there are about 50 commands.
Reply to this email directly or view it on GitHub: https://github.com/zigdon/twirssi/issues/43#issuecomment-2418302
Dan Boger
I sympathise that there are lots of (too many?) commands. I also find it frustrating to find the right command (I like tab-completion, but it's tedious at the moment, for finding the right command).
Having so many prefixes /twirssi_*
... /twitter_*
.../tweet
, /dm
, etc... may not help.
Playing Devil's Advocate, I could argue that it's inefficient to put more code in twirssi.pl
when there's a perfectly good using.html
so RTFM'ing / searching in your browser is already available. Let's not duplicate effort.
However, perhaps we could (in this thread) develop the idea of having a /twirrsi <all_cmds_in_short_form>
way of using twirssi, which does what you say (or allows tab-completion to use substring - not just the default prefix - searches).
Another thought, we could have a /twirssi_help
search through using.html
and present that text/help?
Thoughts?
Searching in browser is not really ideal at all when trying to remember a command to type on a smartphone.
It'd be nice if
/twirssi
would output a list of available commands (and even better if,/twirssi <foo>
would output all commands containing the substring<foo>
).